• kopasz7@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        I believe the same SW version is packaged. Nvidia said they’d drop support in the 580 release, but they shifted it to 590 now.

        The arch issues are another layer of headache by the maintainers changing the package names and people breaking their systems on update when a non-compatible version is pulled replacing the one with still pascal support in it.

        • Victor@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          2 months ago

          Not really a problem of Arch, but of the driver release model, then, IMO. You’d have this issue on Windows too if you just upgraded blindly, right? It’s Nvidia’s fault for not naming their drivers, or versioning/naming them in a way that indicates support for a set of architectures. Not just an incrementing number willy nilly.

          • kopasz7@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            3
            ·
            2 months ago

            It’s 2025, can we not display a warning message in pacman? Or letting it switch from nvidia-590 to nvidia-legacy?

            I’m not an arch user, I admit, I don’t like footguns.

            • Victor@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              2 months ago

              TIL Arch is a footgun. 🤡 cope. 😉

              But yeah, I agree, if package maintainers were astute there, a warning would’ve probably been good somehow. Not sure pacman supports pre-install warnings. Maybe? It does support warning about installing a renamed/moved package. But the naming would’ve had to be really weird for everyone involved if the warning would be clear in that case.

              • kopasz7@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                2 months ago

                I admit, all distros are a different degree of footguns, I’m saying this as a nix user. lol

                • Victor@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  2 months ago

                  Just as with anything you do in life, take action with a healthy side of precaution.

                  This is a life lesson. I’ve learned to be careful around the oven. I’ve also learned to be careful running volatile commands. 😅

          • MangoPenguin@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            Windows doesnt drop to CLI and break if the graphics driver is missing. But also GPU driver updates are not forced on you just by updating the system.

            • Victor@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              2 months ago

              Windows doesnt drop to CLI and break if the graphics driver is missing.

              Okay. Kind of a matter of definition of “breaking” but sure.

              But also GPU driver updates are not forced on you just by updating the system.

              Right. But on Linux they happen automatically when upgrading the rest of your system, is what I was saying.

    • MangoPenguin@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      Windows doesn’t force update your driver and remove support though, and even if it did it won’t drop you to some CLI, it will still work.

      • kopasz7@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        2 months ago

        Rolling distros also only update when you tell them. It is the user who is pulling the trigger on the footgun in both cases.

        I’d say the main difference is that arch users are more trigger-happy about being up to date.

        Also, I think pacman should at least warn you if the problem is enough to warrant a post on the arch website.

        • MangoPenguin@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 months ago

          Sorta, but you run one command to update everything at once, and even though the system knows what GPU you have it still seems to update the driver to one thats not compatible, instead of holding that update back.

          Also if it didn’t warn the user when updating, the user had no idea they were pulling any trigger, especially when Linux falls back to CLI after this instead of just falling back to a basic driver.

          • kopasz7@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            What you described is what happaned with arch. The transitioning shouldn’t have happened this way, IMO.

            Other distros usually don’t send their users to TTY after an update if they can help it.

            On the long term, the situation is the same on linux and windows: you choose the latest driver and live with that given feature set and its bugs.

        • christopher@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          I think pacman should at least warn you if the problem is enough to warrant a post on the arch website.

          It will, if you install the informant package from the aur or the chaotic-aur unofficial repo.

          Otherwise you can follow the advice in the wiki System maintenance page, which says to read the home page, or news RSS feed, or arch-announce mailing list before upgrading.