try choot into the system from a USB drive and check journalctl -e
linux4noobs
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.
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
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.
UPDATE:
I was able to recover my system by re-installing the NVIDIA drivers through, in my case, sudo apt install nvidia-driver-550
since 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!
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.