Edit: “Updating to the legacy 580xx drivers doesn’t show me a desktop anymore”, just in case someone else can stumble upon this by searching something similar.
Thanks to @deadcade@lemmy.deadca.de and @Ooops@feddit.org I did try fixing it out of curiosity. I had forgotten to install linux-headers. Hopefully someone who actually has the same problem as me, and needs to fix it, can use the tips given in the comments. On my end, I just had to install linux-headers and one reboot later it worked.
Always check if you have all needed packages and don’t just “remember” that you had them installed.
Is nouveau open source driver for nvidia actually good for such old gpus?
Not for quite a few games. Some lighter titles might get away with it, but not a lot.
I just went over to NVK. I shouldn’t really waste my time playing the graphic intensive games anyway. The indies are better.
I tried dkms but it took so long to install I gave up.
OP has a pascal GPU, the Nouveau kernel drivers for pascal (which you need for nvk) aren’t really suitable because they can’t change the clock at runtime, you are stuck at boot clock (which you can configure)
“Doesn’t help” is a bit unspecific for an actual answer.
I simply installed
nvidia-580xx-dkmsandnvidia-580xx-utilsand that was all. If you did not already use the dkms-driver package before you of course also need<your kernel>-headersanddkms(but the latter should be pulled as a dependency fornvidia-580xx-dkmsanyway)…Which automatically asks for the removal of
nvidia-open(the standard package for the baselinuxkernel) ornvidia-open-dkmsandnvidia-open-utilsthat replaced the earliernvidia,nvidia-dkms,nvidia-utilspackages when 590 hit.PS: If you still have stuff using 32bit add (you might have guessed the scheme by now…)
lib32-nvidia-580xx-utilsto replacelib32-nvidia-open-utilsThis is the way. I will edit the text of the meme to show the solution at the top. As I had said to another commenter, I could’ve sworn I had linux-headers installed. This is why you check even if you are sure you have a package. Hopefully someone having this issue will stumble upon it randomly.
linuxmemes
Dropping an extensive explanation and how-to is a meme.
Honestly I would’ve much more appreciated it if they told me to RTFM /j (I already had) (I didn’t pay the slightest attention)
You need a couple things:
- The kernel driver (dkms)
- Userspace component
- Kernel headers (for dkms)
First get your kernel headers, this is easy enough, but varies based on which kernel you have installed. The format of the package name is
{kernel}-headers. If you have thelinuxkernel, getlinux-headers. If you havelinux-lts, getlinux-lts-headers. If you’re not sure on this, the commandpacman -Q | grep linuxsearches for installed packages containinglinuxin the name. If you have multiple kernels installed, get the headers for all of them.Then install (from AUR) at least
nvidia-580xx-dkms(display out) andnvidia-580xx-utils(Acceleration, like 3D and video decoding). If you have Steam or play Windows games under Wine, be sure to getlib32-nvidia-580xx-utilstoo.Also of note is the order in which you install things. Having the kernel headers installed is important for the DKMS modules to install succesfully. If you already have
nvidia-580xx-dkmsbut were missing your kernel headers, you should reinstall it after installing your kernel headers.I keep hitting my face on the fact that DKMS modules somehow don’t depend on the kernel headers and these have to be installed manually. This happened to me both in Arch and in Debian.
Why does everyone seem to think that this makes sense?
Thank you very much. I could’ve sworn I had linux-headers installed. Frankly, I might’ve had them on a different device for some other reason. This is why you check your packages kids.
RIP. Time to pull out the backup, amiright?
right… the backup…

The backup specifically created for recovery…
The recovery backup…
Designed to backup the recovery…:
That backup?
It turned into a Llama 8 billion parameter didn’t it?
Recovery’s backup
Blessed be CachyOS for setting that shit up for me automatically.
While I agree snapper (what CachyOS uses) I very useful, it is important to draw a distinction between snapshots (snapper) and a proper backup tool (borg or restic). Snapshots are usually stored on the same drive, so in the event of a drive failure/corruption you are still very fucked. Proper backup programs also have other important features, like the ability to select remote locations, setup encryption, etc. DO NOT rely on snapper to (always) save your ass.
That being said, I fucking love snapper and it was the main feature I was missing from openSUSE.
While the distinction can be important, the snapshots from right before the update are exactly what you want in this case over some actual but always somewhat outdated real backup
Snapper can save you from OS destruction, not disk destruction.
Distro hopped recently. Loving it.
Now I get to say “I use Arch, btw” while still having nfi what I’m doing.
I like diving into the deep end and drown a few times too.
Have you heard of .pacnew files yet?
It should be illegal to use pacman without
pacman-contribinstalled forcheckupdates(no risk of partial upgrades) and for comparing and merging.pacnew-files withpacdiff…It was today when I first heard of it!
Using Arch for ~7 years or so! Both servers and desktops. Always just manually
vimdiff’ed things.
AMDs AMDingly
What is the difference between arch drivers and say pop_os (my current daily)?
The difference is how often they’re updated.
You have btrfs and snapper, and just roll back to a working version in the grub menu, and install the legacy drivers before it all goes wrong
I have ext4 and efistub, and the attention span of a squirrel.
I have never before felt so much kinship from a single comment.
I started to read your comment, but there’s a car 100 metres up the road…
How do you roll back in the grub menu? Is that a feature of grub?
When I update the kernel it replaces both options in systemd-boot so rolling back snapper is a scary endeavor due to kernel - system mismatchs
grub-btrfs (But you have to use grub)
It seems it requires you don’t mount the EFI system partition over /boot so it’s included in snapshots, and systemd-boot doesn’t support booting from arbitrary partitions
Sell nvidia and buy amd.
Already bought intel. I am quite fond of the B580.
how is it? I heard it’s a good hardware but terrible drivers, at least on windows. I don’t know the state of intel GPU drivers on Linux.
It’s quite an upgrade from my previous setup so I cannot tell you if it is good since my comparison is a 1050ti… But they’ve also made improvements to the drivers, even on windows as far as I remember.
Good, as long as you checked the driver situation beforehand right… Right?
I did and I am quite happy with the state of them. Also Linus himself is using a B580 so it can’t be that bad (he doesn’t game on it)
Oh man, I remember fondly the days of booting to no gui. Typing out error codes to another computer to Google.
I don’t think I miss it. Linux has been super stable for me for a decade maybe, and I’ve been trying to game on it, so I used to have to fight with “faster” drivers all the time
Modern schoolkids don’t read, so Arch should consider making 20-minute videos for every update. And a song like some of the *BSD.
Did you uninstall the official driver first? That is, the
nvidiapackage?nvidiawas automatically replaced withnvidia-open(alsonvidia-open-lts,nvidia-open-dkmsetc).Simply installing
nvidia-580xx-dkms,nvidia-580xx-utils(andlib32-nvidia-580xx-utilsbecause Steam still needs all that 32bit stuff), which automatically removes the 590-open stuff because of conflicts, should be all you need to do.PS: And of course your kernel’s header package if you did not use dkms before… (
dkmsshould be pulled as a dependency automatically)
Boot into a live boot install of some distro on a USB drive.
I did try that as well. The legacy drivers did install from the tty, still the system doesn’t see them, for lack of a better word. It is not a big issue though. I had already planned on upgrading since my current setup is very old.
Half of the new components have already arrived. The current PC will become a little home server running either Ubuntu or Debian most likely.
I just thought the situation was funny.
Did you also uninstall all of the components of the new driver as per the arch site?
Otherwise it’s investigate from the tty as to what driver, if any is in use for the gpu pci device.
That isn’t neccessary.
nvidia-openautomatically replaced nvidia (same fornvidia-open-dkms,nvidia-open-utilsetc) when 590 hit and installing any of those nvidia-580xx packages will ask to remove them because they conflict.Yessir. I did remove everything that was from the 590 driver before I installed everything from the legacy 580xx. I might have to load a kernel module somewhere, maybe. But the effort is not worth the payout. My data on the machine itself is not unrecoverable thankfully.
I have a 3080, so 590 is fine for me. But, I’m sure the legacy one is a dkms. But the process of installing that should be done as part of the install. E.g. you install, reboot
What does
lspci -kshow for the card in terms of Kernel driver in use, and kernel modules? Also what doesdkms statussay?If the module is installed and showing in dkms status and showing as used in lspci -k, it should be available for desktop environments.
I do agree in terms of effort when things go wrong though. I remember when I was a lot younger and I had no problems just sitting in front of my keyboard finding whatever the latest problem is. Now, I want to be doing things with my PC.
But, a bit of debugging might be worthwhile before doing a new installation.
I have never used Arch. And it may not be worthwhile for OP. But I am pretty confident that I could get that thing working again.
Booting into a rescue live-boot distro on USB, mount the Arch root somewhere, bind-mounting /sys, /proc, and /dev from the host onto the Arch root, and then chrooting to a bash on the Arch root and you’re basically in the child Arch environment and should be able to do package management, have DKMS work, etc.
Just for the record, Arch USB ISO has
arch-chrootcommand that does everything needed. So it’s quite easy to troubleshoot, when needed. Just mount what you need andarch-chrootthere.But, they shouldn’t need rescue. The issue is no nvidia driver, but you can still login from the text terminals. Ctrl + Alt + F3, F4 etc etc. In fact when the window environment fails to load it should drop back to terminal.
Yeah, that’s what I did. But it didn’t drop to terminal because it was stuck on
/dev/sda2: clean. At first I thought it hadn’t booted at all. Frankly I think that was simply the last thing my monitor got from the GPU before it simply gave up. So i had to switch to TTY manually. That is my best guess.
Arch live ISO gives you
arch-chrootwhich does all the binds automatically
deleted by creator
Did you not see the news item you get before it allows you to start the update?
I was working on a little Intel NUC on the side that had memory issues. And during that I just
sudo pacman -Syuon my main machine without thinking.I did also read the announcement before upgrading which makes it even better IMO.
@KuzhinierSileon no video moment




















