getsolus / getsolus/packages

Proposal for Legacy Nvidia branch to replace 470

Open
#7,978 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Topic: Hardware Support
Dominant language
Python
Stars
141
Forks
146
Avg merge
11h 7m
Merged PRs (30d)
407

Description

Objective:
To streamline NVIDIA driver maintenance in Solus by replacing the EOL 470 branch with the 580 LTS branch, providing a stable path for Maxwell (900-series) and Pascal (10-series) users through 2028. Keeping 10-series cards (like the GTX 1080 Ti) supported is important because those cards are still very capable for 1080p gaming and productivity in 2026, and losing them would alienate a significant portion of the user base.

The Strategy:
As Solus transitions the nvidia-glx-driver (Main) to the 590 series, which defaults to the Open Kernel Modules and drops support for older architectures, we should introduce nvidia-legacy-driver based on the 580 branch.

Proposed Structure:

  • nvidia-glx-driver (Main): Moves to 590+ (Open Kernel Modules for Turing/RTX 20 series and newer).
  • nvidia-legacy-driver (Legacy): Moves to 580 (Proprietary for Maxwell/Pascal/Volta).
  • nvidia-470-glx-driver: Deprecated and removed (Users with Kepler cards encouraged to move to Nouveau/NVK).

Benefits:

  • Maintenance: Consolidates all pre-RTX users into a single, slow-moving LTS branch (580) that NVIDIA will support with security patches until October 2028.
  • Wayland Modernization: The 580 branch uses GBM and supports Explicit Sync, allowing older cards to finally run Wayland sessions (GNOME/Plasma) without the flickering and lag inherent in the 470/EGLStreams branch.
  • Future Proofing: This creates a naming convention (-legacy) that can be reused in the future (e.g., when Turing eventually hits legacy status) without needing to rename packages for every major version drop.
  • Support Gap: Provides a fallback for users whose hardware may technically support the 590 branch but encounters regressions with the new Open Kernel implementation.

In closing, not trying to step on toes and you guys are probably on this already in your strategy talks, but I figured I might as well put this out there. Please don't hesitate to close it if you feel like it as it will not hurt my feelings. I am not AI 😎

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the nvidia-glx-driver, nvidia-legacy-driver, and nvidia-470-glx-driver package definitions first. Check how the proposed 580 and 590 branches, hardware support, and package transitions fit the repository's current structure. Done means the maintainers have an agreed migration plan and the affected packages are updated consistently.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.