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.

  • Jumuta
    2·
    7 days ago

    try choot into the system from a USB drive and check journalctl -e

    • joulethief@discuss.tchncs.deOP
      2·
      6 days ago

      Okay, first time I do this. I followed this article, made sure the paths are right, but journalctl -e shows -- No entries --. Any idea where I went wrong? ls -l / and ls -l /home tell me I chrooted into the right directory.

      Edit: I ran these commands
      kubuntu@kubuntu:~$ sudo mount -t proc proc /mnt/rescue/proc
      kubuntu@kubuntu:~$ sudo mount -t sysfs sys /mnt/rescue/sys
      kubuntu@kubuntu:~$ sudo mount -o bind /dev /mnt/rescue/dev
      kubuntu@kubuntu:~$ sudo mount -t devpts pts /mnt/rescue/dev/pts
      kubuntu@kubuntu:~$ sudo chroot /mnt/rescue
      root@kubuntu:/# journalctl -e

      • joulethief@discuss.tchncs.deOP
        2·
        6 days ago

        I dug a little deeper and using journalctl --since yesterday I 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 taint
        Feb 16 12:31:28 radium kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
        Feb 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, but
        NVRM: this kernel module has the version 565.77. Please
        NVRM: make sure that this kernel module and all NVIDIA driver
        NVRM: components have the same version.
        Feb 16 12:31:38 radium sddm[1280]: Failed to read display number from pipe
        Feb 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 failed
        Feb 16 12:31:38 radium sddm[1280]: Could not start Display server on vt 2

        The NVIDIA API warning appears several times throughout the log actually, which also implies I was wrong about driver version 560 being installed.