NVIDIA's 615.78.08 New Feature Branch build targets Linux gamers head-on: lower Proton latency, a Wayland HDR crash fix, and smarter suspend handling. Here's what actually changes on your machine, and how to upgrade without surprises.

NVIDIA usually treats its Linux driver as a quiet dependency — something that keeps X.Org or Wayland from falling over. The 615.78.08 release, dropped October 7 in the R615 New Feature Branch, is different: nearly every highlighted fix is aimed at people who actually play games on Linux. Six fixes landed on the Linux side. For comparison, NVIDIA's Windows Game Ready driver released the same week listed one.

That's not a typo worth scrolling past. Let's decode what each fix does for your rig.

The headline: Proton gets its latency diet

The biggest technical change is revision 3 of the VK_NV_low_latency2 Vulkan extension. In plain terms, it gives applications timing hints about when to start recording the next frame, shrinking the gap between your mouse input and what hits the screen. NVIDIA says it "improves latency and reduces stuttering with VKD3D-Proton, especially when Frame Generation is enabled."

VKD3D-Proton is the translation layer that turns Direct3D 12 calls into Vulkan so Steam Play titles run on Linux at all. Latency through a translation layer is the kind of thing you feel before you measure — that vague muddiness in mouse response that no amount of settings-tweaking fixes. If you play modern AAA titles with DLSS Frame Generation (NVIDIA's AI frame interpolation), this is the fix you've been waiting for. Reflex now also works correctly on Wayland surfaces through NvLowLatencyVk.dll, so native Vulkan games get the same treatment.

The practical upshot: NVIDIA is visibly investing in closing the Windows–Linux gaming gap at the driver level, not just telling Proton to figure it out.

The bugs that die

  • The Last of Us Part II blocky corruption. Volumetric effects breaking into blocks — reported on NVIDIA's own forums four months ago — is fixed. Small in the changelog, huge if that's your current playthrough.
  • Wayland HDR crash. Unvalidated VkHdrMetadataEXT values were leaking into the Wayland color-management-v1 protocol and could crash the session. If you've been avoiding HDR on Wayland because it felt fragile, this is the patch to watch.
  • Page-table allocation failure above 2 GiB. Large GPU page-table allocations could fail outright. On cards with big VRAM pools, this is the difference between a smooth session and a mysterious allocation error.
  • PRAGMATA Xid 109 on Wayland and display scaling artifacts on Blackwell cards are gone, along with Smooth Motion freezes on cold app starts and Alt-Tab window switches.

Suspend stops being a coin flip

Two suspend changes matter for laptops:

  1. nvidia.ko no longer trips over certain SELinux configurations when systemd suspends the machine with NVreg_UseKernelSuspendNotifiers enabled (this traces back to a Fedora selinux-policy bug report from August).
  2. NVreg_UseKernelSuspendNotifiers=1 is now enabled by default — the kernel handles video memory preservation during sleep and hibernation automatically.

If you've trained yourself to save everything before closing a lid on an NVIDIA laptop, this release is trying to earn that trust back. Test it once deliberately (suspend, resume, check VRAM-heavy apps) before you assume it's fixed on your config.

Should you upgrade? The branch decision

615.78.08 sits on the New Feature Branch: you get fixes the moment they're ready, in exchange for some of the Long-lived Branch's rock-solid stability. This one is explicitly aimed at enthusiasts on recent builds. If your setup is a gaming desktop you patch weekly, upgrade — the Proton latency and Wayland HDR fixes are worth it. If your machine is a work laptop that happens to have an NVIDIA GPU, wait for these fixes to land in the Long-lived Branch.

The safe upgrade drill:

# check what you're running now
nvidia-smi --query-gpu=driver_version --format=csv,noheader
# after upgrading via your distro's package manager, confirm the module rebuilt
dkms status | grep nvidia
sudo reboot
# verify
nvidia-smi

Then sanity-check: launch one Proton game with Frame Generation, test a sleep cycle, and — if you're on Wayland — toggle HDR once to confirm no compositor crash.

Sources