# Mesa 26.2: DLSS Hits Linux via Open-Source NVK Driver > Source: > Published: 2026-08-19 05:07:33+00:00 Mesa 26.2 shipped August 5, and it brought something that felt unlikely two years ago: DLSS now runs on Linux through NVIDIA’s open-source [NVK Vulkan driver](https://www.phoronix.com/news/Mesa-26.2-Released). Not through a proprietary blob, not through a hack — through Mesa itself, the graphics stack that ships by default in your distro. The release also adds mesh shader support to NVK and brings OpenCL 3.1 to five backends, but the DLSS story is the one that tells you where this project is headed. ## How DLSS Works on NVK The mechanism is less mystical than it sounds. NVK now implements `VK_NVX_binary_import` , a Vulkan extension that lets a driver load and execute prebuilt NVIDIA CuBIN binaries — ELF-like containers of CUDA code compiled for NVIDIA hardware. DLSS binaries already ship with games or the DLSS SDK. NVK loads them directly. No reimplementation required. To enable it, set an environment variable before launching a game through Steam: ``` NVK_EXPERIMENTAL=dlss %command% ``` The feature is marked experimental because bugs remain and it requires the GPU to have compatible CuBIN bytecode available for its architecture. The proprietary NVIDIA driver supports a PTX-to-bytecode translation path that NVK does not yet have, so older GPUs or edge-case architectures may not work. For most users on modern NVIDIA hardware running Proton, this is worth testing now. What makes this notable beyond the technical implementation: NVIDIA chose to support `VK_NVX_binary_import` in the Vulkan spec. That was a quiet policy decision that made NVK’s DLSS path possible. The open-source driver didn’t have to break anything to get here — it just needed the extension to exist, and NVIDIA provided it. That matters for the long-term trajectory of open-source graphics on Linux. ## NVK Gets Mesh Shaders Mesa 26.2 adds `VK_EXT_mesh_shader` to NVK, the last major Vulkan driver in the Mesa family without it. AMD’s RADV and Intel’s ANV both had mesh shaders already. Mesh shaders replace the fixed vertex/geometry pipeline with programmable GPU-side geometry generation. Unreal Engine 5’s Nanite virtual geometry system requires them, as does a growing number of DX12 and native Vulkan titles. NVK users running games through Proton that require this extension no longer need to fall back to the proprietary blob driver. ## OpenCL 3.1 on Five Backends Rusticl, Mesa’s OpenCL implementation, now supports OpenCL 3.1 across five backends: Asahi (Apple AGX), Iris (Intel), Radeonsi (AMD), llvmpipe (CPU software), and Zink (Vulkan-based). New subgroup extensions — `cl_khr_subgroup_rotate` and `cl_khr_subgroup_ballot` — land alongside 32-bit target support for ARM SoCs and embedded hardware. The Mesa project also maintains a community libclc fork that passes the [OpenCL CTS with Mesa/Rusticl](https://docs.mesa3d.org/relnotes/26.2.0.html), providing a stable support path after upstream libclc branches go EoL. If you write GPU compute workloads for Linux and have been waiting for a complete open-source OpenCL 3.1 story, this is the release where it becomes real. ## Intel’s Jay Compiler: Experimental, But Watch This Intel is quietly rebuilding its shader compiler. Jay is a new SSA-based compiler for Intel Xe architectures, introduced experimentally in Mesa 26.2 alongside a complete rewrite of the `intel/gen` instruction encoding module (115 commits from Caio Oliveira). Jay [now passes Vulkan CTS on Xe2 and Xe3 hardware](https://hwbusters.com/news/intels-jay-shader-compiler-now-passes-vulkan-conformance-on-xe2-and-xe3/). It is not production-ready, but Intel’s ANV driver also enables `VK_EXT_descriptor_heap` by default in this release — a Vulkan extension that improves descriptor management for DXVK and VKD3D-Proton, the translation layers that handle Steam Play gaming. Intel is making a long-term bet that a clean-slate compiler beats incremental work on the old encoder. Based on the CTS results, that bet is on track. ## How to Get Mesa 26.2 **Arch Linux**: Already available — rolling release ships within 48 hours of Mesa releases.** Ubuntu**: Use the kisak-mesa PPA:`sudo add-apt-repository ppa:kisak/kisak-mesa && sudo apt update && sudo apt upgrade` **Fedora**: Rawhide has it; stable releases follow within a week via system updates or COPR.** SteamOS**: Valve handles Mesa updates — 26.2 will arrive in a future SteamOS release automatically. Check your current version with `glxinfo | grep "Mesa"` . One practical note: wait for Mesa 26.2.1 before deploying in production environments, as the first point release typically catches regressions from the feature release. For gaming and experimentation, 26.2.0 is ready now. ## The Gap Is Closing A quarterly Mesa release adding DLSS support, mesh shaders, and a five-backend OpenCL 3.1 story would have looked like an ambitious wishlist two years ago. Mesa 26.2 ships all of it. The [open-source GPU driver ecosystem](https://www.gamingonlinux.com/2026/08/mesa-26-2-0-released-with-lots-of-improvements-for-linux-steamos-graphics-drivers/) is not slowly catching up to proprietary drivers — it is closing that gap in large, observable chunks, release by release. Proprietary drivers still lead on ray tracing, CUDA compute, and some performance edge cases. But for Linux gaming and Vulkan workloads, the distance is shrinking to the point where “use the blob” is increasingly a preference rather than a requirement. Mesa 26.2 is another data point in that direction, and the trend is accelerating.