this post was submitted on 26 Dec 2025
287 points (99.3% liked)

Linux

10798 readers
702 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] kopasz7@sh.itjust.works 2 points 9 hours ago (1 children)

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.

[–] victorz@lemmy.world 2 points 8 hours ago (2 children)

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 2 points 7 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 1 points 6 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.