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 @[email protected] and @[email protected] 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.

  • Skullgrid@lemmy.world
    4·
    15 hours ago

    Hey Look, it’s me! I am on nobara against my fucking will. I spent all saturday screaming.

    I’m going to refer the shit out of this thread in my news battle to get my goddamn debian OS back. DNF is scary and I can’t use signal.

    Here’s my notes (WARNING: THESE NOTES LEAD TO FAILURE) :

    
- get verson info for KDE and NVIDIA drivers
https://metadata.ftp-master.debian.org/changelogs//non-free-firmware/n/nvidia-graphics-drivers/nvidia-graphics-drivers_550.163.01-2_changelog
https://packages.debian.org/trixie/nvidia-driver
https://packages.debian.org/search?keywords=nvidia&searchon=names&suite=trixie&section=all
https://stackoverflow.com/questions/17999695/debian-package-dependencies-installing-specific-version-not-the-latest


added changes to /etc/apt/sources.list
https://wiki.debian.org/NvidiaGraphicsDrivers?action=show&redirect=NVIDIA#Debian-13_notes

2 - 16
5 - 18
8-17


16 deb http://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware
17 deb http://security.debian.org/debian-security/ trixie-security contrib non-free main non-free-firmware
18 deb http://deb.debian.org/debian/ trixie-updates non-free-firmware non-free contrib main

2 deb http://deb.debian.org/debian trixie main (contrib) non-free-firmware
5 deb http://deb.debian.org/debian trixie-updates main non-free-firmware (non-free contrib)
8 deb http://security.debian.org/debian-security/ trixie-security (contrib) main non-free-firmware


added git to /etc

ran
  git config --global --add safe.directory /etc
because I was geting thsi eror :
  fatal: detected dubious ownership in repository at '/etc'
  To add an exception for this directory, call:

installing drivers
  https://wiki.debian.org/NvidiaGraphicsDrivers?action=show&redirect=NVIDIA#Debian-13_notes
    apt install nvidia-kernel-dkms nvidia-driver


    WARNING: No kernel headers were found, skipping module build.
             To get the headers for the running kernel (6.12.57+deb13-amd64)
             please install the linux-headers-6.12.57+deb13-amd64 package.
   ran
        apt install linux-headers-generic
   to resolve

   I DID ACTUALL RUN THE FOLLOWING
   _____
   Post-installation steps for Trixie

    Optionally verify the result of the DKMS module compilation:

    # dkms status

    If you plan to use wayland (which is a default for both the Gnome and KDE Plasma desktops since Debian 12 "Bookworm") make sure to follow the Wayland Modesetting notes below.

        If gnome starts with X11, you may enable wayland support by enabling NVreg_PreserveVideoMemoryAllocations=1 as mentioned below.

        If you plan to use suspend/hibernate functionality under KDE desktop environment, you may want to add another option to avoid graphics "glitches" after wakeup/restore:
        Warning: skip this step if you have Optimus hybrid graphics

        # echo "options nvidia NVreg_PreserveVideoMemoryAllocations=1" >> /etc/modprobe.d/nvidia-options.conf

    In most cases a restart of the system is recommended to fully load the new driver. For wayland, check again if modeset is properly set, as described above.

    _____https://wiki.debian.org/NvidiaGraphicsDrivers?action=show&redirect=NVIDIA#Wayland_configuration and this wayland shit too
    _____
  • deadcade@lemmy.deadca.de
    91·
    2 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
      24·
      2 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
      8·
      2 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.

  • Val@anarchist.nexusEnglish
    17·
    2 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.

    • edinbruh@feddit.itEnglish
      3·
      2 days ago

      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)

  • ZILtoid1991@lemmy.world
    3·
    2 days ago

    I’m safe, my ThinkPad doesn’t have an iGPU, and there’s no instructions on how to solder one onto an L440 motherboard.

  • Ada@piefed.blahaj.zoneEnglish
    18·
    2 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
      3·
      2 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
          2·
          2 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

  • silasmariner@programming.dev
    2·
    2 days ago

    Omg I remember running into something like this about 12 years ago. TTY did help but did need a reboot. I had to arch-chroot off the live usb so many times that night, my first ever Linux installation and I fucked up the bootloader and initial packages so hard so many times. I felt so cool when I was able to switch to another tty without needing yet another usb boot. Thanks for that memory.

  • chocrates@piefed.worldEnglish
    9·
    2 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

  • Lembot_0006@programming.dev
    92·
    2 days ago

    Modern schoolkids don’t read, so Arch should consider making 20-minute videos for every update. And a song like some of the *BSD.

  • Jack@slrpnk.net
    4·
    2 days ago

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

    • KuzhinierSileon@lemmy.worldOP
      4·
      2 days ago

      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.

        • KuzhinierSileon@lemmy.worldOP
          1·
          2 days ago

          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.

          • r00ty@kbin.life
            2·
            2 days ago

            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 -k show for the card in terms of Kernel driver in use, and kernel modules? Also what does dkms status say?

            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.

            • tal@lemmy.todayEnglish
              1·
              2 days ago

              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.

              • r00ty@kbin.life
                3·
                2 days ago

                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.

                • KuzhinierSileon@lemmy.worldOP
                  1·
                  2 days ago

                  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.

              • wltr@discuss.tchncs.de
                1·
                2 days ago

                Just for the record, Arch USB ISO has arch-chroot command that does everything needed. So it’s quite easy to troubleshoot, when needed. Just mount what you need and arch-chroot there.