• Korhaka@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 hours ago

      You don’t have to updare your drivers though, isn’t this normal with older hardware?

      • Victor@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        4 hours ago

        You don’t have to updare your drivers though.

        Not sure if you’re on Windows or Linux but, on Linux, we have to actively take explicit actions not to upgrade something when we are upgrading the rest of our system. It takes more or less significant effort to prevent upgrading a specific package, especially when it comes in a sneaky way like this that is hard to judge by the version number alone.

        On Windows you’d be in a situation like “oh, I forgot to update the drivers for three years, well that was lucky.”

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

          It makes me wonder why the package still auto updates if it detects you’re using the driver that would be removed, surely it could do some checks first?

          Would be vastly preferable to it just breaking the system.

    • kopasz7@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 hours 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
        1
        ·
        4 hours 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.

        • MangoPenguin@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 hours 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.

        • kopasz7@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 hours 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.