SUMMARY Today I updated Neon 5.22.4, using Discover, and after the installation(s) and reboot(s), laptop froze on Neon startup splash. I was able to Alt-F2 to log in via CLI. I found a [thread on the Neon forums](https://forum.kde.org/viewtopic.php?f=309&t=172175&sid=683dca1e932bc55ef0216b2f1b9c2539) that suggested there is a problem with the Nvidia 340.108 driver under Kernel 5.11.0-25, and to use the Grub menu to boot to Kernal 5.8.0-63 instead. This workaround has allowed me to log into Plasma. STEPS TO REPRODUCE 1. Apply current updates in Discover 2. Allow machine to install and reboot OBSERVED RESULT Neon Boot Splash freezes, but I can Alt-F2 to the CLI. EXPECTED RESULT Expected to be able to log in via GUI/Plymouth login screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.13.3 ADDITIONAL INFORMATION sudo inxi -Fxxx: https://bin.privacytools.io/?66a914c115f9d56f#2J19XX2qKhZmjtwFA1zHMyeS4LyeAcM5E51MdeHMNJhk Please let me know if I can provide more info. Thanks!
Hi. I found [this thread on the Nvidia Linux Dev Forums] (https://forums.developer.nvidia.com/t/nvidia-340-108-driver-kernel-5-11-support/182663) ...that points out incompatibility between nvidia-340.108 and the 5.11.x kernel. I will report my bug there. It looks like Nvidia has been notified, but they don't seem to be doing anything about it at the moment. I have uninstalled `nvidia-340` and gone back to the nouveau driver, and all seems well in Neon 5.22.4 with the 5.11.0-27 kernel (updated since I reported this). I don't know if any further action is required here, other than watching for an update to nvidia-340.
We can probably close this. I worked around it by removing the Nvidia drivers and using Nouveau.
Thank you for your bug report! However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since before 01/01/2025. Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's. Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report. Thanks for understanding!