This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Boot-up issue after last system update

Tags: None
(comma "," separated)
User avatar
peerwal
Registered Member
Posts
27
Karma
0
OS
Hi everybody,

wondering if anybody else experienced this behavior: The most recent system update obviously installed kernel 5.11. 0.250. Since then my desktop stops booting right during the initial boot sequence (first boot-splash appears) and I can only get it up and running if I step back to kernel 5.8. My configuration is as follows:

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-64-generic (64-bit)
Graphics Platform: X11
Processors: 6 × Intel® Xeon® CPU X5650 @ 2.67GHz
Memory: 11.7 GiB of RAM
Graphics Processor: Quadro FX 580/PCIe/SSE2

I couldn't find any bug report or other comment on this issue. So, I am wondering if this failure may be due to my hardware being not really up-to-date? Would be great, if anybody had some hint about how to solve the problem.
vwgtiturbo
Registered Member
Posts
1
Karma
0
I also have the issues you describe (however I am on older hardware, Intel NUC from 2016 or so). If I press ESC during boot to see the messages, it hangs at random spots in the process. However, if I press CTRL+ALT+F2, I can 'sudo startx' and the GUI will load (although I can only do it with sudo, which means I can only run the GUI as root). I'm too inexperienced on the desktop distros to figure out how to choose the older kernel/remove the newer kernel...
User avatar
peerwal
Registered Member
Posts
27
Karma
0
OS
'sudo startx' doesn't work for me although I don't see any errors in the xorg log file. Seems our problems may have different reasons. However, the easiest way to change kernel is to use the GRUB menu. Just keep the <SHIFT> key pressed during the BIOS boot procedure until the GRUB menu shows up. Using the 'Extended options...' item lets you select the kernel you want the system to use.

Edit: According to information given at other forums the issue seems to be caused by an incompatibility of (some?) NVidia drivers (mine is nvidia 340.108). So, the solution seems to be: revert to a previous driver and wait for a fix of the actual drivers.


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft