Valve confirms Nvidia's 580 driver branch breaks Steam Link VR on Linux
Valve has confirmed that Nvidia's 580 driver branch cannot run Steam Link VR on Linux, calling it "the NVIDIA 580 series driver incompatibility" in a reply on its own SteamVR-for-Linux tracker on September 28. Seven owners have posted in the thread since it opened on September 7, on cards ranging from a GTX 1080 Ti to an RTX 5090, and the four failing machines whose driver version is given were all on 580 releases: 580.159.03, 580.173.02 and 580.178.04.
The Steam Frame at an angle with its head strap and both controllers on a beige surface. One owner hit the same failure streaming to a Frame over its wireless adapter. Image: Valve
The failure is abrupt. Steam Link connects, the headset is identified, and then vkCreateDevice returns -7, VK_ERROR_EXTENSION_NOT_PRESENT, the compositor never starts and SteamVR puts up error 405 with the text "You may need to update your computer's graphics driver."
It bites across headsets as well as cards: the reports cover a Quest 2, a Quest 3, a Quest 3S and a Steam Frame running its wireless adapter on Fedora 43. The first theory was wrong, too. The owner who opened the report suspected AV1 video encode, since every other Vulkan video encode extension was present on the Turing card, until an owner on an RTX 4060 posted the identical -7 failure, which undercut the idea.
One missing Vulkan extension stops the device
The extension is VK_KHR_maintenance9, which an owner on an RTX 2060 pinned down on September 19 by turning on Vulkan loader debugging and catching the loader saying it outright: "Device extension VK_KHR_maintenance9 not supported by selected physical device or enabled layers." The owner wrote that "NVIDIA 580.159.03 exposes VK_KHR_maintenance1 through maintenance8, but not maintenance9", one version short of what SteamVR asks for.
That diagnosis is an owner's rather than Valve's, but it fits what the thread shows. The driver branch is what the failing machines hold in common, which is the point Valve made when it told the thread it was "pointless to fragment the discussion based on the specific GPU using the driver".
Newer drivers work, and Pascal owners say they are stuck
Two owners have reported their own ways out, each on one machine. One on an RTX 5090 moved to Nvidia 595.91.07 and then dropped SteamVR to the previous 2.16.7 branch; another moved to 615.71.09 by rebasing a Bazzite install onto Nvidia's open kernel modules, and says VR streaming then worked.
Two owners say neither route is open to a GTX 10-series card. "Any chance nvidia 580 could be supported? I can't upgrade because I'm still on pascal", one asked on September 28. The other checked Nvidia's open kernel modules and agreed that they do not cover Pascal cards.
Valve has confirmed a cause, not a fix
What Valve has said is that the 580 branch is the incompatibility and that the GPU model is not the main factor. It has not said whether SteamVR will work around the missing extension, has published no support article or known-issues note, and has given no timeline; the report is open, unassigned and carries no fix.
Owners on a working driver have their own Steam Link complaints, including the way it grabs an Nvidia card for VR streaming with no way to override it. For anyone on 580, the shorter version is that the Vulkan device is never created at all.
