No boot with kernel 6.2

English Install/Boot/Login
#1

Hi again!

Have here a n older Dell Precision with NVIDIA graphics, no special graphics driver installed:

sudo lspci
[sudo] password for root: 
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 02)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation G92GLM [Quadro FX 3700M] (rev a2)
03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)
09:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5761e Gigabit Ethernet PCIe (rev 10)

System boots fine with kernel 6.1.12 and these boot parameters

splash=silent ipv6.disable=1 quiet net.ifnames=0

but with kernel 6.2.1 (zypper dup this morning) the boot process freezes after loading initial ram disk with black screen with two text lines (also occuring on successfull boot process, so test is of no diagnositc value).

In journalctl there is no info on this boot process.

Booting with old kernel works just fine.

Any ideas?

Older laptop, Tumbleweed, nvidia and nouveau drivers
Black screen after tumbleweed dup
#2

Did you try to disable secure boot as the new kernel recieved lock patches which prevents loading unsigned kernel modules? Informations were provided on the mailing lists…

#3

Can you login remotely after a short wait to be sure boot completed?

#4

No secure boot, simple BIOS.

#5

As nothing in

journalctl

(only shutdown after zypper dup and then the boot with old kernel 6.1.12)

there is no such thing as a “successful boot” (without grphics) in this case, I assume :slight_smile:

#6

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

Maybe related…

#7

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

#8

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? :slight_smile:

#9 
zypper al PACKAGE_NAME

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

#10

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

1 Like
Keeping more than two kernels ready for boot
#11

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

#12

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

1 Like
#13

Here we go:

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

Kernel 6.2 AMD GPU boot stuck because of iommu
#14

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

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

#15 
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? :slight_smile:

Need help with zypper addlock matching
#16

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

1 Like
#17 
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? :slight_smile:

#18

@suse_rasputin yes, that looks better.

1 Like
#19

…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?

#20

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

1 Like