linux4noobs

1633 readers

8 users here now

linux4noobs

Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.

Seeking Support?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 2 years ago

MODERATORS

PlutoParty@programming.dev

Kubuntu fails to boot after updates (discuss.tchncs.de)

submitted 1 week ago* (last edited 5 days ago) by joulethief@discuss.tchncs.de to c/linux4noobs@programming.dev

10 comments fedilink hide all child comments

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.~~

you are viewing a single comment's thread
view the rest of the comments

[–] joulethief@discuss.tchncs.de 2 points 5 days ago* (last edited 5 days ago) (1 children)

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.de 2 points 5 days ago* (last edited 5 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.