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.

  • Val@anarchist.nexusEnglish
    0·
    11 days ago

    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.

  • Jack@slrpnk.net
    0·
    11 days ago

    What is the difference between arch drivers and say pop_os (my current daily)?

    • KuzhinierSileon@lemmy.worldOP
      0·
      11 days ago

      I was working on a little Intel NUC on the side that had memory issues. And during that I just sudo pacman -Syu on my main machine without thinking.

      I did also read the announcement before upgrading which makes it even better IMO.

        • KuzhinierSileon@lemmy.worldOP
          0·
          10 days ago

          I use ext4, but the fix was just installing linux-headers. I simply was of the impression that I had already installed those. Most likely I had installed them on one of my laptops and simply just had that vivid memory still in my head. Once I installed them the problem solved itself after a reboot.

  • chocrates@piefed.worldEnglish
    0·
    11 days ago

    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

  • deadcade@lemmy.deadca.de
    0·
    11 days ago

    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 the linux kernel, get linux-headers. If you have linux-lts, get linux-lts-headers. If you’re not sure on this, the command pacman -Q | grep linux searches for installed packages containing linux in 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) and nvidia-580xx-utils (Acceleration, like 3D and video decoding). If you have Steam or play Windows games under Wine, be sure to get lib32-nvidia-580xx-utils too.

    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-dkms but were missing your kernel headers, you should reinstall it after installing your kernel headers.

    • skarn@discuss.tchncs.de
      0·
      11 days ago

      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?

    • KuzhinierSileon@lemmy.worldOP
      0·
      11 days ago

      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.

  • Ooops@feddit.org
    0·
    11 days ago

    “Doesn’t help” is a bit unspecific for an actual answer.

    I simply installed nvidia-580xx-dkms and nvidia-580xx-utils and that was all. If you did not already use the dkms-driver package before you of course also need <your kernel>-headers and dkms (but the latter should be pulled as a dependency for nvidia-580xx-dkms anyway)…

    Which automatically asks for the removal of nvidia-open (the standard package for the base linux kernel) or nvidia-open-dkms and nvidia-open-utils that replaced the earlier nvidia, nvidia-dkms, nvidia-utils packages when 590 hit.

    PS: If you still have stuff using 32bit add (you might have guessed the scheme by now…) lib32-nvidia-580xx-utils to replace lib32-nvidia-open-utils

    • KuzhinierSileon@lemmy.worldOP
      0·
      11 days ago

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

  • Ada@piefed.blahaj.zoneEnglish
    0·
    11 days ago

    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

    • Lojcs@piefed.socialEnglish
      0·
      11 days ago

      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

        • Lojcs@piefed.socialEnglish
          0·
          11 days ago

          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