Kubuntu fails to boot after updates
Hey there, I could use a little help.
I'm running Kubuntu 24.10 (the non-LTS variant) and after some system updates through KDE's Discovery, I'm unable to boot.
First off, some specs:
Kernel: 6.11.0-14-generic
GPU: GTX 1080 w/ proprietary drivers, version 560 550 stable
I was first greeted with these lines:
[ TIME ] Timed out waiting for device dev-disk-by/x2duuid-[...].device
[DEPEND] Dependency failed for mnt-games.mount
This is not the first time this happened, so I went into recovery mode, opened /etc/fstab to comment out the device-specific line, saved, and rebooted.
The error disappeared, however the system still won't boot and I'm left with these entries visible on screen (abbreviated for clarity):
[ OK ] Started cups.service
[ OK ] Reached target printer.target
[ OK ] Started ipp-usb.service
[ OK ] Finished NetworkManager-wait-online.service
[ OK ] Reached target network-online.target
[ OK ] Started update-notifier-download.timer
[ OK ] Started update-notifier.motd.timer
[ OK ] Reached target timers.target
[ OK ] Started cups-browsed.service
Starting kerneloops.service
[ OK ] Started kerneloops.service
[ OK ] Reached target multi-user.target\
Starting power-profiles-daemon.service
[ OK ] Started power-profiles-daemon.service
[ OK ] Reached target graphical.target
Starting systemd-update-utmp-runlevel.service
[ OK ] Finished Starting systemd-update-utmp-runlevel.service
...and then nothing.
I need to leave, I'll fix the formatting and provide further information as soon as I'm back at my desk.
10 replies
Are you able to plug in a USB with a live iso and troubleshoot from there?
Yes, I am able to boot Kubuntu 24.04.1 from a USB drive.
try choot into the system from a USB drive and check journalctl -e
Okay, first time I do this. I followed this article, made sure the paths are right, but
journalctl -eshows-- No entries --. Any idea where I went wrong?ls -l /andls -l /hometell me I chrooted into the right directory.Edit: I ran these commands
kubuntu@kubuntu:~$ sudo mount -t proc proc /mnt/rescue/prockubuntu@kubuntu:~$ sudo mount -t sysfs sys /mnt/rescue/syskubuntu@kubuntu:~$ sudo mount -o bind /dev /mnt/rescue/devkubuntu@kubuntu:~$ sudo mount -t devpts pts /mnt/rescue/dev/ptskubuntu@kubuntu:~$ sudo chroot /mnt/rescueroot@kubuntu:/# journalctl -eI dug a little deeper and using
journalctl --since yesterdayI could retrieve a proper log. There are a couple of red and yellow entries, some of the latest ones being:Feb 16 12:31:28 radium (udev-worker)[471]: event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument[...]
Feb 16 12:31:28 radium kernel: nvidia: loading out-of-tree module taints kernel.Feb 16 12:31:28 radium kernel: nvidia: module license 'NVIDIA' taints kernel.Feb 16 12:31:28 radium kernel: Disabling lock debugging due to kernel taintFeb 16 12:31:28 radium kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernelFeb 16 12:31:28 radium kernel: nvidia: module license taints kernel.[...]
Feb 16 12:31:37 radium kernel: NVRM: API mismatch: the client has the version 550.144.03, butNVRM: this kernel module has the version 565.77. PleaseNVRM: make sure that this kernel module and all NVIDIA driverNVRM: components have the same version.Feb 16 12:31:38 radium sddm[1280]: Failed to read display number from pipeFeb 16 12:31:38 radium sddm[1280]: Display server stopping...Feb 16 12:31:38 radium sddm[1280]: Attempt 3 starting the Display server on vt 2 failedFeb 16 12:31:38 radium sddm[1280]: Could not start Display server on vt 2The NVIDIA API warning appears several times throughout the log actually, which also implies I was wrong about driver version 560 being installed.
UPDATE:
I was able to recover my system by re-installing the NVIDIA drivers through, in my case,
sudo apt install nvidia-driver-550since the kernel log indicated a version mismatch, presumably due to the Discover updates. Something's still janky with the drivers as I experience massive lag and a ghosting cursor, but I'll figure that out.I'd really appreciate tips on how to prevent this in the future.
Do you have time shift setup? If this happens again you can put the USB in and chroot into the system the run time shift to take you back to a version of your system that worked.
It's on my to-do list, but I haven't gotten around to it yet.
Its a very quick setup. Probably takes ~1min
I'll give it a shot!