This is a landmark achievement for the open-source graphics community, but it comes with important caveats. Here's everything you need to know.
The journey to DLSS on NVK began in late 2025 with Autumn Ashton, a Valve developer working on Linux graphics drivers. In a breakthrough announcement, Ashton shared that after just three days of work, they had gotten DLSS running on NVK . The key was implementing the VK_NVX_binary_import Vulkan extension, which allows an application to import and execute NVIDIA's precompiled CUDA binaries .
DLSS is essentially a collection of CUDA kernels, so enabling the driver to load and run those precompiled binaries was the critical enabler . Ashton also implemented the VK_NVX_image_view_handle extension, which DLSS uses to pass image view descriptors for its kernel launches .
However, the patches sat for some time as Ashton's activity in Mesa development decreased. Developer Thomas Andersen picked up the work about two months before the merge, fixing merge conflicts and other issues before the code was finally integrated into the Mesa 26.2 development branch, moving DLSS support from a proof-of-concept to an experimental feature .
DLSS on NVK is not enabled by default. Users must explicitly opt in using environment variables, a common approach for experimental driver features .
NVK_EXPERIMENTAL=dlss: Enables DLSS if precompiled support for the GPU is found in the DLSS library .NVK_EXPERIMENTAL=dlss_backwards_compat: Allows using DLSS bytecode intended for earlier GPU architectures, if compatible .The driver relies on precompiled CUDA binaries (CuBIN files) that contain the DLSS kernels. The VK_NVX_binary_import extension loads these ELF files and executes them directly on the GPU hardware .
According to Phoronix, the feature works with recent games launched through Steam Play, Valve's compatibility layer that runs Windows games on Linux .
The experimental nature of this implementation means several important limitations remain:
NVK can only run DLSS on GPUs for which precompiled bytecode exists in the DLSS library. If your GPU doesn't have a matching binary, DLSS simply won't enable . This is a key difference from NVIDIA's proprietary driver, which can compile PTX (parallel thread execution) intermediate code into GPU-specific bytecode on the fly — a capability NVK currently lacks .
Because NVK cannot handle PTX (the intermediate CUDA representation), older games or titles that lack precompiled binaries for modern GPU architectures will not work with DLSS on NVK . This is a significant limitation for backwards compatibility.
The feature is behind the NVK_EXPERIMENTAL flag precisely because it is not yet ready for broad use . As one developer noted in the #nouveau IRC channel, it is meant to be easier to test without breaking existing functionality . Broad benchmark data comparing NVK DLSS performance with the proprietary driver is not yet available .
This change is specific to Mesa's NVK driver on Linux. It does not affect Windows gaming or the proprietary NVIDIA driver on Windows .
Despite its experimental status, this merge is a significant milestone for several reasons:
Closing the feature gap: NVK is an open-source, community-developed driver (primarily by Collabora, Red Hat, and Valve) that has steadily matured since its Vulkan 1.3 conformance in Mesa 24.1 . Adding DLSS support closes a major feature gap versus NVIDIA's proprietary Linux driver .
A foundation for the future: The experimental flags and GPU architecture limitations mean this initial implementation is a foundation. As the DLSS library grows to include more GPU targets and the driver matures, broader support is expected.
Timeline: Mesa 26.2 stable release is expected around August 2026, at which point Linux gamers will have a more accessible path to DLSS on the open-source driver .
This is a landmark achievement for the open-source graphics community, but it comes with important caveats. Here's everything you need to know.
The journey to DLSS on NVK began in late 2025 with Autumn Ashton, a Valve developer working on Linux graphics drivers. In a breakthrough announcement, Ashton shared that after just three days of work, they had gotten DLSS running on NVK . The key was implementing the VK_NVX_binary_import Vulkan extension, which allows an application to import and execute NVIDIA's precompiled CUDA binaries .
DLSS is essentially a collection of CUDA kernels, so enabling the driver to load and run those precompiled binaries was the critical enabler . Ashton also implemented the VK_NVX_image_view_handle extension, which DLSS uses to pass image view descriptors for its kernel launches .
However, the patches sat for some time as Ashton's activity in Mesa development decreased. Developer Thomas Andersen picked up the work about two months before the merge, fixing merge conflicts and other issues before the code was finally integrated into the Mesa 26.2 development branch, moving DLSS support from a proof-of-concept to an experimental feature .
DLSS on NVK is not enabled by default. Users must explicitly opt in using environment variables, a common approach for experimental driver features .
NVK_EXPERIMENTAL=dlss: Enables DLSS if precompiled support for the GPU is found in the DLSS library .NVK_EXPERIMENTAL=dlss_backwards_compat: Allows using DLSS bytecode intended for earlier GPU architectures, if compatible .The driver relies on precompiled CUDA binaries (CuBIN files) that contain the DLSS kernels. The VK_NVX_binary_import extension loads these ELF files and executes them directly on the GPU hardware .
According to Phoronix, the feature works with recent games launched through Steam Play, Valve's compatibility layer that runs Windows games on Linux .
The experimental nature of this implementation means several important limitations remain:
NVK can only run DLSS on GPUs for which precompiled bytecode exists in the DLSS library. If your GPU doesn't have a matching binary, DLSS simply won't enable . This is a key difference from NVIDIA's proprietary driver, which can compile PTX (parallel thread execution) intermediate code into GPU-specific bytecode on the fly — a capability NVK currently lacks .
Because NVK cannot handle PTX (the intermediate CUDA representation), older games or titles that lack precompiled binaries for modern GPU architectures will not work with DLSS on NVK . This is a significant limitation for backwards compatibility.
The feature is behind the NVK_EXPERIMENTAL flag precisely because it is not yet ready for broad use . As one developer noted in the #nouveau IRC channel, it is meant to be easier to test without breaking existing functionality . Broad benchmark data comparing NVK DLSS performance with the proprietary driver is not yet available .
This change is specific to Mesa's NVK driver on Linux. It does not affect Windows gaming or the proprietary NVIDIA driver on Windows .
Despite its experimental status, this merge is a significant milestone for several reasons:
Closing the feature gap: NVK is an open-source, community-developed driver (primarily by Collabora, Red Hat, and Valve) that has steadily matured since its Vulkan 1.3 conformance in Mesa 24.1 . Adding DLSS support closes a major feature gap versus NVIDIA's proprietary Linux driver .
A foundation for the future: The experimental flags and GPU architecture limitations mean this initial implementation is a foundation. As the DLSS library grows to include more GPU targets and the driver matures, broader support is expected.
Timeline: Mesa 26.2 stable release is expected around August 2026, at which point Linux gamers will have a more accessible path to DLSS on the open-source driver .