For a Linux-first gaming PC, AMD is the lower-friction choice: its graphics driver is part of the kernel and Mesa, so it works at install and updates with the system. NVIDIA GeForce cards still run Linux games well, especially with DLSS and ray tracing, but they depend on a separately packaged driver, and DirectX 12 games under Proton are the area where users report the biggest gap. If you already own an RTX card, keep it; if you are buying for Linux, lean toward AMD.
The structural difference that explains everything
AMD’s kernel driver, amdgpu, is open source and ships inside the Linux kernel. The Vulkan driver most games use through Proton, RADV, ships inside Mesa, the open-source graphics stack that distributions update alongside the rest of the system. When you update your distro, your GPU driver updates with it, tested against the same kernel.
NVIDIA’s stack is split. The userspace driver that runs your games, with the Vulkan and OpenGL implementations, is proprietary and distributed by NVIDIA. The kernel side is now open-source for modern cards, but it still has to be built or packaged for each kernel version. Distributions handle this differently: some pre-build the modules, some compile them on your machine through DKMS, and immutable distributions like Bazzite ship them in the image. When the packaging layer breaks, your display breaks with it, which is why NVIDIA problems tend to appear right after a kernel or driver update.
Driver branches: what your NVIDIA card can still use
The most useful fact when evaluating an NVIDIA card for Linux is its generation, because NVIDIA has been retiring older ones from current drivers.
| GPU generation | Series examples | Driver situation |
|---|---|---|
| Turing, Ampere, Ada, Blackwell | GTX 16 series, RTX 20, 30, 40, 50 | Current drivers with the open kernel modules, which depend on the GPU’s onboard GSP processor |
| Pascal and Volta | GTX 10 series, Titan V | No longer supported by the 590 series; stay on the 580 legacy branch |
| Maxwell | GTX 900 series, GTX 750 Ti | Same: the 580 legacy branch is the last supported release |
| Older (Kepler and earlier) | GTX 600 and 700 series | Far older legacy branches; unsuitable for modern gaming |
The practical consequence: a Pascal or Maxwell card will keep working, but only on a frozen driver that gets occasional compatibility fixes and no new features. Some distributions now install the open kernel modules by default, so owners of older cards must choose the legacy package deliberately. On Arch-based systems, for example, that means installing the 580xx packages from the user repository instead of the main driver.
AMD has no equivalent cliff. Older Radeon cards stay on the same kernel driver for years, although the oldest generations use a previous kernel driver that gets fewer improvements.
What actually differs while gaming
- DirectX 12 through Proton. Most modern Windows games use DirectX 12, which Proton translates to Vulkan through VKD3D-Proton. On NVIDIA hardware users report lower performance in some of these games than on Windows or on comparable AMD cards. Published community measurements span a wide range, from a modest loss to roughly a third, and vary with the game, so any single number deserves suspicion. DirectX 11 titles, which go through DXVK, are generally reported to be much less affected.
- Upscaling and frame generation. DLSS works under Proton on GeForce cards, which is a real advantage for RTX owners. AMD users get FSR, and support for the newest FSR generation depends on the specific Radeon generation plus current Proton and Mesa versions.
- Ray tracing. NVIDIA’s hardware and driver are stronger here on Windows and on Linux, so ray tracing heavy games are a point in favor of GeForce.
- Wayland. Modern desktops use Wayland, and NVIDIA’s support improved considerably with explicit sync in the 555 series and later, provided your compositor also supports it. Older driver and compositor combinations show flicker or out-of-order frames.
- Handhelds and small PCs. Handheld gaming PCs that run Linux are overwhelmingly AMD based, and the software around them is built for that hardware.
- Productivity. NVIDIA’s CUDA and hardware video encoder are strong for creative and AI work. AMD relies on ROCm and VAAPI, which have narrower software support.
The open-source NVIDIA path
NVK is an open-source Vulkan driver for NVIDIA GPUs inside Mesa. It is improving quickly, and recent Mesa releases added features such as mesh shaders and experimental DLSS support. For most newer games, though, it still trails the proprietary driver in performance, so it suits people who value an all-open stack more than raw frame rate. Treat it as a project to watch rather than a replacement for the official driver today.
Setting up an NVIDIA card correctly
- Identify your GPU generation first. It decides whether you need the current branch or the 580 legacy branch, and installing the wrong one is the top cause of a missing driver after an update.
- Prefer your distribution’s packaged driver over NVIDIA’s installer script. Packaged drivers are rebuilt with each kernel update and removed cleanly; manually installed ones are not, and a kernel update can leave you at a text console.
- Handle Secure Boot before installing. Third-party kernel modules must be signed, so either enroll a signing key when prompted or choose a distribution that ships signed modules. Without that, the driver silently fails to load.
- Confirm modesetting is on. Check that the file /sys/module/nvidia_drm/parameters/modeset contains Y. Wayland sessions and smooth frame pacing depend on it, and most current packages enable it automatically.
- Verify the driver is the one rendering your games. Run nvidia-smi to confirm the driver and a Vulkan info tool to confirm the GPU is detected. On hybrid laptops, games run on the integrated GPU unless you request offload to the discrete one.
- Keep the previous kernel installed. If a kernel update outpaces the driver, you can boot the older kernel and fix things from a working desktop.
Typical failure modes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| Boots to a text console after an update | Kernel module not rebuilt for the new kernel | Boot the older kernel, reinstall the driver package, rebuild modules |
| Driver will not load, nothing in logs | Secure Boot rejects unsigned modules | Enroll a signing key or disable Secure Boot |
| Old card has no driver after a system upgrade | Current branch no longer supports the card | Install the 580 legacy branch with proprietary modules |
| Flicker or tearing on Wayland | Old driver or compositor lacking explicit sync | Update both, or use an X11 session as a stopgap |
| Game uses the integrated GPU on a laptop | Offload not requested | Set the game to use the discrete GPU through the distro’s offload option |
| Low frame rate in a DirectX 12 game | Proton translation overhead specific to this title | Try a different Proton build, or the DirectX 11 mode if the game offers one |
Which GPU should you buy or keep?
| Your situation | Recommendation |
|---|---|
| Building a new PC mainly for Linux | AMD Radeon: driver included, rolling updates, fewer packaging surprises |
| Already own an RTX card | Keep it, use the open kernel modules, and run a distribution that handles the driver for you |
| Want DLSS or heavy ray tracing | GeForce RTX, accepting the extra driver maintenance |
| Own a Pascal or Maxwell card | Stay on the 580 legacy branch and plan an upgrade, preferably to a card with current driver support |
| Use CUDA for work as well as games | NVIDIA, with a distribution that packages the driver cleanly |
| Buying a gaming handheld | AMD-based device; there is no meaningful NVIDIA option |
Whichever vendor you choose, aim for enough video memory for your target resolution. Treat 8 GB as the floor for a new 1440p build, since running out forces textures into system memory and causes stutter regardless of driver quality.
Frequently Asked Questions
Is AMD or NVIDIA better for Linux gaming?
AMD is easier because its driver ships with the kernel and Mesa, and DirectX 12 games under Proton tend to behave closer to Windows. NVIDIA is still a strong option for DLSS and ray tracing, as long as you keep its driver packaging in good order.
Do NVIDIA GTX 10 series cards still work on Linux?
Yes, but only on the 580 legacy driver branch. Newer driver releases have dropped Pascal, so you will not receive new features, and you must pick the legacy package manually on distributions that default to the open modules.
Does DLSS work on Linux?
DLSS works under Proton on supported GeForce cards in games that offer it. It requires the proprietary NVIDIA driver, so it is not available through the open-source NVK driver by default.
Which Linux distribution is best for NVIDIA?
Choose one that packages the driver for you: an image-based distribution with an NVIDIA image, or a mainstream distribution with a signed driver option. These avoid the manual module building that causes most boot problems after updates.
Does Wayland work with NVIDIA now?
Yes, on recent drivers and compositors with explicit sync, which arrived in the 555 series. Older combinations can flicker, so update the driver and desktop together.
