Kernel 6.12.30 upgrade then stuck at `starting openmamba`

[einar.hjortdal]

On saturday I updated openmamba with sudo dnf update and got a kernel upgrade.
After the dnf transaction concluded, I used openmamba for an extensive amount of time and then shut it off.
Today at boot, I am stuck at starting openmamba. It seems to be responsive to keyboard input because ctrl+alt+del triggered a reboot.
I was able to boot into openmamba by using kernel 6.12.20 found in the advanced options for openmamba grub entry.
What do I do to identify the cause of the issue?

[Silvan]

Hi,
does access to any virtual console work by pressing CTRL-ALT-F2..F8? This would allow retrieving log information from the console to identify the cause of the issue.
If not, the only way to get useful information would be to start the kernel with the “debug” menu choice (or removing “quiet splash” from Grub command line).
Did you by any chance install the “nvidia” proprietary driver?

[einar.hjortdal]

Silvan wrote:

Hi, does access to any virtual console work by pressing CTRL-ALT-F2..F8? This would allow retrieving log information from the console to identify the cause of the issue. If not, the only way to get useful information would be to start the kernel with the “debug” menu choice (or removing “quiet splash” from Grub command line). Did you by any chance install the “nvidia” proprietary driver?

CTRL-ALT-F2..F8 do not seem to work. Starting the kernel with debug messages doesn’t show any useful messages, the only line shown is the efi stub loaded initrd.

I do have the nvidia_470 package installed on 6.12.20 and it still seems to work when booted with this kernel. I had my own suspicion that the cause of the issue is that, but I have no proof.

[einar.hjortdal]

It must be the nvidia_470 package. I’ve uninstalled I can successfully start kernel 6.12.30
However, if I install nvidia_470 while running kernel 6.12.30, the problem reappears on the next reboot.

[einar.hjortdal]

I think the recent merges fixed the issue

[Silvan]

Ok. Release 470.256.02-5mamba supposingly fixed it.

[Author]

Posts