Latest Kernel update to 6.14.0-24-generic does not boot KDE neon

Help
1

Hello everyone.

I received kernel updates this morning right after I logged into my system. Did the update as I have done many times in the past without any error message after sudo pkcon update. I then did a sudo apt autoremove and again no error message but it removed older kernels as it should.

I then rebooted my machine but for some odd reason it did not accept my BIOS password (which I typed in 3 times and I 100% it was the correct PW).

I then turned off my machine in an attempt to clear the ā€˜stuck stateā€™, unplugged the power cord and waited for a few minutes and then rebooted. This time my BIOS password was accepted. I was then greeted by that first KDE neon dark boot screen with that white curser at the top left, and got stuck there.

After 10 minutes I knew KDE neon wasnā€™t going to boot so I turned off my laptop again. Restarted it after a minute and via left ā€˜Shiftā€™ right after my BIOS password entry got accepted again :slight_smile: I got into the GRUB Menu. There I selected ā€˜Advanced options for KDE neonā€™, which showed me a list with the current and a few older kernels. I selected the previous kernel 6.11.0-29-generic and then it booted up again as before. This suggests there is a kernel issue (new kernel not booting properly).

Iā€™m still very new to Linux and I need help now, please:

  1. How do I prevent my machine wanting to boot into the new kernel next time I start it, i.e. can I somehow make the latest kernel inactive while I wait for a kernel fix?
  2. Where do I report this kernel issue properly?

Thank you in advance for your help!

PS: I have provided as much detail as I could on the steps that I took to boot back into my machine, in the hope it might help others who are also new to Linux and who might be experiencing these or similar issues with the new kernel update.

----- Info about my system -----

Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.11.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 Ɨ AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Memory: 8 GiB of RAM (6.7 GiB usable)
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: Acer
Product Name: Aspire A315-41
System Version: V1.18

1 Like
2

Hello,

I too had a problem with update. Rebooted and got a ā€œpress a keyā€ and the a pink kernel panic screen.
I also booted into previous kernel.
After chatting with an A.I. , long story short the solution was to do the following in the terminal:

ls /boot/vmlinuz-* | grep 6.14

and then, run the following with the result return by the previous command (the 6.14.0-24-generic in my case).

sudo update-initramfs -u -k 6.14.0-24-generic

Hope it helps

1 Like
3

I got the pink screen of death too. Sadly your solution did not work for me. Upon booting into 6.11 Plasma greeted me with an ā€œupdate failedā€ message. Clicking on repair did not repair it.

4

Thanks for sharing and Iā€™m glad it worked in your case. I didnā€™t get the pink kernel panic screen but after I managed to boot into 6.11, the AI I talked to suggested to try and reboot into 6.14 again, after checking that the kernel update was properly installed.

The AI suggested that when I booted into 6.11, my system:

  • May have finalized module registration for 6.14
  • Ran initramfs updates or dkms operations behind the scenes
  • Rebuilt driver dependencies that were glitchy on first launch

Not sure how this could happen as one would hope that all this is done when I get my prompt back. Anyway, I followed the AIā€™s suggestion and rebooted into 6.1 and it worked.

5

Typo in the last sentence, should have said 6.14 (not 6.1).

6

I have the same problem, so itā€™s not just you.

7

When you boot the old kernel edit the /etc/default/grub and remove the splash option in the GRUB_CMDLINE_LINUX_DEFAULT=ā€œā€ then you will have a chance of seeing the boot messages and where it is failing. Not some useless fancy graphics that tells you exactly nothing about the startup processes. This is one of the first edits I make as I actually want to see if something fails when booting giving me a chance to correct it. You have to run update-grub after doing the edit to have the new settings used either with sudo in front of the commands or as root for both.

1 Like