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

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

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