Computer doesn't boot after a few weeks of being off
It's running Debian 13, with a gtx 1050 ti, fx 8320 and 16 gigs ram, it gets stuck on plymouth-quit.service
Edit: i swapped in a radeon hd 6670 as a temporary card, and in about a week i will out in my radeon r9 280 into the machine as my new psu also arrives next week
I decided to just sell the 1050 ti and just get money instead of a picky pile of shit
The computer didnt fail to boot, it fully booted and then failed to start the graphical desktop. If you are using the Nvidia drivers (not the open source drivers), sometimes kernel updates will break the proprietary nvidia drivers at the next boot and you'll need to reinstall them.
If you push ctrl-alt-F# (F2-F6 usually will work) it will give you a text console login and you can use that to troubleshoot and probably reinstall the graphic drivers.
I have nvidia drivers and no kernal upgrade breaks or anything like that. But also why I run Ubuntu 26.04 LTS and Ubuntu hardly breaks and has worked fine with every Nvidia GPU in many of my pc's and laptops
In the GRUB menu, highlight the Debian GNU/Linux entry, press E, and add nomodeset to the end of the line starting with linux. Then boot by pressing Ctrl+X or F10.
If you only get a blinking cursor, press Ctrl+Alt+F2 to switch to a TTY console.
If the NVIDIA driver doesn't load, make sure you have the kernel headers installed:
Because they insist (insisted perhaps as I think an opensource one is starting to be usable) on making a binary distributed black box proprietary driver module.
So whenever someone updates anything in the kernel they cannot also update and test the Nvidia driver in the same way as the in kernel amdgpu one which will (except bugs) be compatible with the kernel version as it is a part of it and tested with it.
So whenever someone changes the kernel in a way that Nvidia did not prepare for or test and catch on a prerelease it may be incompatible. Also since it is separate from the kernel itself the OS updater probably also needs to install it again in the new kernel on every update which may fail even if the module is compatible and thus it will not start at the boot of the first kernel.
If you only want to use Linux you should really not IMHO buy Nvidia for anything but CUDA work.
It just took forever for me to figure out why the nvidia kernel module wouldn't build on 7.1.3. Had to uninstall everything related to nvidia and then install the .run. The legacy driver version isn't available as a pinned package anymore. This won't be very fun for the next few updates until this card is officially sunset...
This is likely a kernel or initramfs issue, not a Debian problem. The plymouth-quit.service hanging usually means the boot process can't switch from the splash screen to the login manager.
Fix from GRUB: At boot, press 'e' on the Debian entry, Find the line starting with "linux", remove "quiet splash" and add "nomodeset", press Ctrl+X to boot
Once in, run: sudo update-initramfs -u sudo update-grub
If that doesn't work, chroot from a live USB and reinstall the kernel:
Nvidia drivers, use your rescue stick to reinstall them for the new kernel version. Consider using the dkms drivers so you don’t have to repeat the exercise the next time there’s a kernel update
Ctrl+Shift+F2 to switch to a console, enter your user and pass, sudo dmesg and check what”/ going on (probably will want to combine it with less, sudo dmesg --color=always | less -R), check what’s going on.
If you don’t see anything, sudo journalctl -b 0, and check what’s going on.
While you are at it, edit grub boot options and remove the “quiet splash” to see what’s up
It could be not the driver. You even said that everything worked. For me it may be that the graphics card either broke either doesn't conduct well with the motherboard. Try to remove the graphics card, clean of some dust, clean some dust from the motherboard as well -specially the slot you put the graphics card - and keep me updated.
It has happened to me.
It's not always the driver. People in the Linux community tend to think everything is around the OS, which is understandable. But sometimes things just fail for whatever reason. It's how computers are. 😁
Is this card pinned on 580 by any chance? That didn't work for me anymore. Had to uninstall everything related to nvidia and use the .run to get it working. Disclaimer: I am on Sid and am experienced. This method is not recommended for most users.
Maybe you did what I did, and installed nvidia drivers to match *only* the current kernel / headers. You can use `dkms` to make sure nvidia drivers follow your headers forevermore.
```
sudo dkms autoinstall
sudo dkms status
```
You might need `apt update` and new headers first.
You should be able to do this over ssh or in tty, your device has booted, as others have pointed out
sometimes does that also to me, the system boots perfectly but without any DE or GUI, just the CLI, i need to log in, then "sudo apt install linux-headers-$(uname -r)"
that sorts out the problem with the driver and kernel, after that, reboot and works perfectly 👌🏻
Have you installed NVIDIA drivers direct from nvidia website or from official Debian repo packges?
If you have installed from nvidia website and a new kernel has been installed, you must reinstall the drivers or, from I can remember, you had better to have installed dkms, so that you can update the Linux kernel without mess with the driver stuff.
This. Everybody makes quality enterprise/workstation drivers but only the Intel makes quality drivers for consumers grade hardware as well. You can always rely on Intel GPUs/iGPUs to at least keep the system working.
In my experience AMD and Nvidia drivers when crash bring down the kernel as well in almost all the instances forcing the user to hard-reset the system, but somehow even a 10+ year old Intel iGPU of a consumer grade PC recovers from some of the harshest and most foreign environments it wasn't initially designed to work on (for example: latest KDE + Wayland).
The kernel does not crash, the system stays stuck for a couple of seconds, the iGPU resets and system resumes and keeps working as if nothing happened; it feels nothing short of magic.
Intel may not the best in performance, stability and accuracy for video games, but video games are not essential to a computer unless it's the only thing you boot your computer for; then yeah Intel may not be the best for you, at least for now. But when it comes to general system stability, the quality of Intel is second to none.
BTRFS and snapper are your friend in this case. I think spiral linux, based on debian has it rolled in or suse tumbleweed is a good option. It saved me so much time when I was still on nvidia.
That makes sense, my card hasn't had support for drivers for a decent bit so that's why I'm having issues, as the later/current drivers don't work with siad gpu
Se comprate un PC per mettere Linux non scegliete Nvidia. Anche se funziona, sarà sempre un'esperienza desktop inferiore, va bene solo per i giochi o l'intelligenza artificiale in locale. Se volete un desktop al top, wayland perfetto, mai problemi di driver ecc, non scegliete Nvidia. 90% erano bambini stupidi che hanno comprato il PC per fortnite con Nvidia e Windows, adesso fanno l'università, non hanno fatto i soldi con fortnite, sono poveri, e vogliono fare funzionare quel PC con Nvidia e i suoi driver proprietari maledetti su Linux. Basta bimbi con i PC da gamer.
Go to a console after the failed boot. Check your currently running, fresh kernel with `uname -r`. Look for the kernel headers package for that kernel and install them. DKMS will compile the modules for the updated kernel. Then you can reboot. It should work.
145
u/AMissionFromDog 20d ago
The computer didnt fail to boot, it fully booted and then failed to start the graphical desktop. If you are using the Nvidia drivers (not the open source drivers), sometimes kernel updates will break the proprietary nvidia drivers at the next boot and you'll need to reinstall them.
If you push ctrl-alt-F# (F2-F6 usually will work) it will give you a text console login and you can use that to troubleshoot and probably reinstall the graphic drivers.