• Victor@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    10 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
      ·
      10 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.

      • Victor@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        23 minutes 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.

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

      • Victor@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        35 minutes 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.