No boot with kernel 6.2

[hui]

https://bugzilla.opensuse.org/show_bug.cgi?id=1208938

Maybe related…

[suse_rasputin]

…bug is with AMD GPU, but maybe related? Have no “netconsole” here…

[suse_rasputin]

btw: what was the procedure to lock the old 6.1.12 kernel from being purged with next zypper dup with new 6.2.x kernel?

[hui]

zypper al PACKAGE_NAME

https://en.opensuse.org/SDB:Zypper_manual_(plain)
Search for “Package Locks Management”

[malcolmlewis]

@suse_rasputin add the version to the multiversion.kernels section in /etc/zypp/zypp.conf.

[hui]

Malcoms tip can also be found by typing “how to lock the kernel” into the forum search:

How to lock the kernel?

I’ve not been able to update (dup) for awhile due to bad timing I guess on my part as every time I run a dup my nvidia drivers don’t work due to a new kernel being installed. Generally I just wait a few weeks and try again when the issues has been addressed for the new kernel. Anyways I’m months behind due to this and was wanting to try and just pin (lock) the kernel thinking this might work. I’m using yast and have selected “kernel-default , kernel-default-devel and kernel-devel” and choose to…

[arvidjaar]

@suse_rasputin

Any ideas?

As usual - boot without “quiet” and with “plymouth.enable=0” on kernel command line. It may provide some information what happens.

[suse_rasputin]

Here we go:

https://paste.opensuse.org/pastes/d907959dc4f6

[suse_rasputin]

…while dmesg of successfull boot with kernel 6.1.12 looks like this

https://paste.opensuse.org/pastes/42eb9a461c0c

[suse_rasputin]

uname -a
Linux dell2TW062021 6.1.12-1-default #1 SMP PREEMPT_DYNAMIC Wed Feb 15 05:31:41 UTC 2023 (373f017) x86_64 x86_64 x86_64 GNU/Linux

so the line in zypp.conf looks now like

multiversion.kernels = latest,latest-1,running,6.1.12-1-default

will that keep kernel 6.1.12 for future zypper dups with new 6.2 kernels?

[malcolmlewis]

@suse_rasputin You need to use the full version number from zypper se -si kernel-default

[suse_rasputin]

zypper se -si kernel-default
Loading repository data...
Reading installed packages...

S  | Name           | Type    | Version    | Arch   | Repository
---+----------------+---------+------------+--------+------------------------
i+ | kernel-default | package | 6.1.12-1.1 | x86_64 | (System Packages)
i+ | kernel-default | package | 6.2.1-1.1  | x86_64 | openSUSE-Tumbleweed-Oss

so now it reads

multiversion.kernels = latest,latest-1,running,6.1.12-1.1

Correct now?

[malcolmlewis]

@suse_rasputin yes, that looks better.

[suse_rasputin]

…I found that MESA-dri-nouveau was still installed (but not xf86-nouveau), removed the MESA thing and rebooted, didn’t change much

https://paste.opensuse.org/pastes/9d02f4cbd0fc

btw. the system is really, really hung up at this point, power button not working, only way to interact is REISUB…

Other point: Is it possible to make the working 6.1.12 kernel the default for booting?

[malcolmlewis]

@suse_rasputin sure, via YaST Bootloader, last tab on right, change in the drop down.

[Speciolution]

Not sure if this helps anything but Arch has the same Problem with 6.2
Only when dualbooting and only if the Bootloader is not from Arch. I can’t explain more as I am not a tech person. Just search for “Arch 6.2 boot problem”. Also Brodie Robertson on Youtube has a short video about it (latest Video as of March 8)

I don’t know if openSUSE did the same with Kernel 6.2

[suse_rasputin]

Still no new 6.2 kernel in TW here. Am I the only one with related problems (with NVIDIA graphics and no UEFI/secure boot)?

[arvidjaar]

@suse_rasputin

Am I the only one with related problems?

May be (at least only one having this particular combination that triggers thus problem). Have you opened bug report?

[malcolmlewis]

@suse_rasputin as a Tumbleweed user you should be following the Factory Mailing list, new details there today…

[suse_rasputin]

Nope, just a dumb user here…