Running legacy graphics hardware—such as NVIDIA Kepler-based GPUs (GT 710, GT 720, GT 730)—on modern Linux distributions often presents a challenge. NVIDIA officially dropped support for the 470.xx driver series, meaning stock drivers frequently fail to build against newer Linux kernels.
This step-by-step tutorial covers how I successfully installed and patched the NVIDIA 470 driver on modern Linux distributions.
Important Setup Notes:
- Target Hardware: Legacy systems running in Legacy BIOS / GPT partitioned drive.
- Display Server: These legacy drivers require an X11 / X.org session (e.g., XFCE, LXQt, or MATE desktop environments).
- Multi-Boot Notice: My machines uses a primary GRUB bootloader on a different partition (master GRUB), system configuration is best handled locally within each distribution rather than overriding master GRUB configs.
Installing NVIDIA 470 on Debian / Ubuntu (Mainline Patch Method)
Because official Debian and Ubuntu repositories no longer maintain out-of-the-box patches for the 470 driver on high-numbered modern kernels, we utilize the community-maintained translation toolkit joanbm/nvidia-470xx-linux-mainline.
Step 1: Drop to a Headless TTY
“CTRL + ALT + F1” to go out of desktop | GUI and bring up terminal. Login is required (existing user and pwd).
To start GUI I type:
starxNext is required to prevent my desktop environment or display manager (LightDM, GDM, SDDM) from holding file locks on graphics libraries
sudo systemctl isolate multi-user.target Thoroughly Purge Previous Failed Builds
Wipe out any corrupted compilation residues or broken module hooks:
sudo apt purge nvidia*
sudo apt autoremoveStep 2:Install Build Dependencies & Clone Patch Repository
Install the necessary compiler toolchain, DKMS, and GL libraries, then fetch the translation patches:
sudo apt update
sudo apt install git build-essential dkms linux-headers-$(uname -r) libglvnd-devClone the community patch repository designed specifically to bridge 470 to modern kernels (6.12, 6.13, etc.):
git clone https://github.com/joanbm/nvidia-470xx-linux-mainline
cd nvidia-470xx-linux-mainlineIf git not installed:
sudo apt install gitStep 3: Execute Automated Patching & DKMS Setup
Run the installer with the --dkms flag to automatically apply the compatibility bridge and register the driver with DKMS:
sudo ./install --dkmsNow I see the text based interface that guides me, asking to confirm setup and configuration options.
On first run it failed. But there is a catch.
If it exits without installing for reason of “Nouveaou” being used. That is good and not too critical sign.
Scrip will try and detect “other method” of “Blacklisting Nouveaou”, and also ask if I want to apply a method provided by install script. I want that.
If it says that it fails to install driver. I reboot and run the script again.
Since I followed a guide provided by AI on first try I also typed in terminal:
sudo echo "options nvidia-drm modeset=1" | sudo tee /etc/modprobe.d/nvidia-drm.confThis might help install script on next run after reboot.
What this script does behind the scenes: It downloads the official NVIDIA 470.256.02 .run file, extracts it, injects the necessary conditional C-macros (like fixing the 6.12+ DRM client hotplug changes), and then registers the successfully patched source tree into DKMS.
Step 6:
Return to Graphical Mode and Reboot. Switch my default target back to graphical and reboot your machine:
sudo systemctl set-default graphical.target
sudo rebootVerifying Success After Reboot
Once the system boots back up into your desktop, immediately open a terminal and run your two diagnostic checks:
- Check if the kernel driver is active:Bash
nvidia-smi(If this outputs your GT 710/720/730 specs and VRAM usage, the bridge is working!) - Check hardware acceleration:Bash
glxinfo | grep "OpenGL renderer"(It must list your NVIDIA GPU model instead ofllvmpipe).
Installing NVIDIA 470 on EndeavourOS / Arch Linux (Recommended AUR Route)
Great experience and the result right out of the box.
Now, even that the install-patch-compile process takes longer than on Debian/Ubuntu, it was flawless.
For Arch-based distributions like EndeavourOS, the community maintains patched driver sources directly inside the Arch User Repository (AUR). This approach is the cleanest and most resilient against rolling kernel upgrades.
Step 1: Install Kernel Headers & Base Tools
I open a terminal with “CTRL + ALT+ F4” – go in TTY; “CTRL + ALT+ F7” back to GUI.
To ensure your system build packages and kernel headers are up to date I type and run (press “Enter”):
sudo pacman -Syu --needed base-devel linux-headers linux-lts-headers dkms(Note: If you run linux-lts, install linux-lts-headers as well).
Remove conflicting graphics drivers and purge any conflicting open-source drivers or newer NVIDIA modules with:
sudo pacman -Rdd nvidia nvidia-utils nvidia-dkms nouveau 2>/dev/nullStep 2: Build the Patched 470 Driver via AUR
Run yay without root privileges to compile and register the 470 branch:
yay -S nvidia-470xx-dkms nvidia-470xx-utils nvidia-470xx-settingsDKMS will compile the module against your running kernel automatically. (Watching the build output. This can take long depending on PC)
When DKMS completed compiling I proceed to reboot.
My PC is multi OS boot and I selected the default EndeavourOS GRUB menu entry.
nvidia-smi confirmed ALL OK! And I run Unigine Valley benchmark without problems.
That is a huge victory! The fact that nvidia-smi works right out of the box shows the AUR package (nvidia-470xx-dkms) is successfully building the compatibility layer for your setup.
More tips and considerations
To keep this studio workstation completely stable and prevent future updates from breaking my graphics setup, here is my straightforward, long-term maintenance strategy:
1. How Updates Work with nvidia-470xx-dkms
Because I installed the DKMS variant, I do not need to reinstall the driver manually every time EndeavourOS updates its kernel.
- Normal Kernel Updates: Whenever
pacmanoryayupdates mylinuxkernel, a post-install hook automatically runsdkmsin the background to recompile the 470 module against the new kernel headers automatically. - AUR Updates: When the Arch community pushes new patches for major kernel releases (e.g., Linux kernel standard updates), running
yay -Syuwill update both my system packages and thenvidia-470xx-dkmssource patches at the same time.
2. Lock In Low-Maintenance Rules (Recommended)
To keep this a true “set-and-forget” studio rig without surprises during system updates, I can follow these three simple rules:
Rule A: I keep the linux-lts Kernel Installed as a Safety Net
Having the Long Term Support (LTS) kernel installed on EndeavourOS ensures that even if a bleeding-edge main kernel update breaks the patch temporarily, I can immediately select the LTS entry from my GRUB menu and keep working.
In EndeavourOS terminal, running:
sudo pacman -S linux-lts linux-lts-headers(DKMS will automatically build a copy of the 470 driver for the LTS kernel as well).
Rule B: I Don’t Blindly Update Right Before a Session
I treat my studio machine like a production console:
- Avoiding running
yay -Syuright before a recording or mix session. - When I do update, run:
Bashyay -SyuAnd take a quick glance at the terminal output to ensure DKMS finishes without red errors before restarting.
3. Cleaning Up the “Master GRUB” Menu Entries
In my Ubuntu Master GRUB menu, seeing multiple entries for EndeavourOS (such as EndeavourOS, EndeavourOS (fallback-initramfs), or EndeavourOS (linux-lts)) is completely normal:
- Standard EndeavourOS Entry: Boots the active kernel.
- Fallback Entry: Boots with extra diagnostic tools loaded in memory in case a driver or system file gets corrupted.
- LTS Entry: Boots my rock-solid Long Term Support kernel.
To refresh and clean up Ubuntu’s Master GRUB list at any time:
Boot into Ubuntu and run:
sudo update-grubUbuntu’s os-prober will scan all drive partitions, remove stale boot entries, and organize the current operating systems neatly.
Summary Checklist
Your system is now fully configured:
- Hardware acceleration is running via the NVIDIA 470 driver.
- DKMS manages driver updates automatically during
pacman/yaysystem upgrades. - Ubuntu handles multi-boot routing across your partitions cleanly.
System-Level Configuration & Blacklisting
To prevent the open-source nouveau driver from conflicting with NVIDIA’s proprietary module, blacklisting rules must be enforced.
EndeavourOS Configuration (Dracut Setup)
If my EndeavourOS installation utilizes dracut to build its initial RAM disk (initramfs), I create a local module configuration:
- Create a dracut rule to force-load the NVIDIA modules:
Bashsudo nano /etc/dracut.conf.d/nvidia.confAdd the following line (include the inner spaces):
Plaintextforce_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm " - Force kernel DRM modesetting locally:
Bash:sudo nano /etc/modprobe.d/nvidia.conf
Add the following line:
Plaintextoptions nvidia_drm modeset=1 - Rebuild your initramfs:
Bash:sudo dracut-rebuild
A Note on Debian / Ubuntu Blacklisting:
While manual modprobe configs and GRUB modifications (
nvidia-drm.modeset=1) are common recommendations, they are not always required on standard Debian/Ubuntu installs if the installation script or package manager configures blacklisting successfully during the DKMS setup. If my Debian/Ubuntu installation boots fine and detects hardware rendering, manual file overrides can safely be omitted.
Verification & Maintenance
Once installation completes, return to the graphical target or reboot your machine:
sudo systemctl set-default graphical.target
sudo rebootHow to Verify the Driver is Active
After logging back into my desktop, I open a terminal and run the following checks:
- Verify GPU Hardware Communication:
Bashnvidia-smiIf active, this command outputs my graphics card model (e.g., GeForce GT 710/730) and driver version470.xx. - Verify Hardware-Accelerated Rendering:
Bashglxinfo | grep "OpenGL renderer"The output should display my NVIDIA graphics card name. If it outputsllvmpipe, software rasterization is still active.
Long-Term Maintenance Tip
Because both setups utilize DKMS (Dynamic Kernel Module Support), my system will automatically attempt to recompile the 470 driver whenever a kernel package update runs in the background.

Leave a Reply