Arch Linux Pulls the Plug on Pascal: GTX 10 Cards Are Dropped From the Default Path with NVIDIA 590

Key Takeaways

• Arch Linux drops Pascal support in default NVIDIA 590 driver path
• Users must install legacy nvidia‑580xx‑dkms for GTX 10 series GPUs
• Only quarterly security patches for Pascal GPUs until Oct 2028
• Open kernel modules become default for Turing and newer cards
• Lack of open-source driver parity reduces long‑term value of NVIDIA hardware

Pulse Analysis

The shift in Arch Linux’s driver strategy reflects NVIDIA’s broader lifecycle policy, which earmarks the 580 Legacy branch as the final Linux line for Pascal, Maxwell and Volta GPUs. By moving the default path to the 590 series, Arch aligns with NVIDIA’s roadmap but leaves older hardware on a maintenance‑only track. This decision is significant for rolling‑release distributions, where package updates are frequent and users expect seamless transitions. The need to manually install the nvidia‑580xx‑dkms package introduces friction, especially for users who value the convenience of out‑of‑the‑box support.

For end‑users, the practical impact is twofold. First, systems built around GTX 1060‑1080 cards will require extra steps during upgrades, risking driver mismatches or reduced performance if the legacy package is omitted. Second, the open‑source Nouveau driver remains constrained by firmware limits, offering only modest performance on Pascal silicon. In contrast, AMD’s older GPUs benefit from a thriving open‑source ecosystem that continuously improves kernel drivers and Mesa support, extending their usable lifespan on Linux. This disparity underscores the strategic advantage of open driver models for long‑term hardware viability.

From a business perspective, the de‑prioritization of Pascal GPUs accelerates depreciation cycles for organizations that have standardized on NVIDIA’s mid‑range cards. Companies must now budget for driver maintenance or plan hardware refreshes ahead of the October 2028 security cutoff. The move also signals a broader industry trend: proprietary driver vendors are increasingly shifting support burdens onto users, while open‑source communities push for more transparent, sustainable GPU support. Enterprises evaluating future Linux deployments should weigh the total cost of ownership, including potential driver‑related downtime, against the benefits of newer architectures that already enjoy open‑kernel module integration.