Valve drops the Vulkan requirement that broke Steam Link VR, and no beta has it
Valve has removed the Vulkan extension requirement that has been stopping Steam Link VR from starting on Nvidia's 580 driver branch, a failure first filed on September 7. "We have removed the requirement for VK_KHR_maintenance9 and this will be available in the next SteamVR beta update," reads the reply that closed the report on Valve's SteamVR for Linux tracker, posted at 14:38 UTC on October 3.

SteamVR, the app the change lands in. Valve has promised it for the next beta and has not released one. Image: Valve
Nothing has shipped. The newest SteamVR beta is still 2.18.2, which Valve posted on October 1, and the reply names neither a version nor a date for the build that will carry the change.
Pascal owners had no reliable way out
The one fix the report agrees on is a newer Nvidia driver. The owner who diagnosed the fault lists VK_KHR_maintenance9 as absent from 580.159.03 and present from 595.91.07 onwards, and another says VR streaming worked again after a rebase moved him to a 615 build.
Rolling SteamVR back is not a dependable second option. One owner lists the previous branch, 2.16.7, among the versions that return the same error on a 580 driver, alongside the 2.17.9 release and its beta. Another, who had been on the 595 driver before trying it, says 2.16.7 is what finally fixed his 5090.
Nvidia's open kernel modules do not cover Pascal, owners in the report point out, so anyone still on a GTX 10-series card could not take the driver route at all. "Any chance nvidia 580 could be supported? I can't upgrade because I'm still on pascal," one of them wrote on September 28. Later the same day, having established that only the one extension was missing, he added that "there might be a way for SteamVR to work arround the missing support". Five days later that is what Valve did.
The failure reads the same in every report. Steam Link's Vulkan device creation returns VK_ERROR_EXTENSION_NOT_PRESENT, the compositor never initialises, and the host throws "SteamVR Graphics Error You may need to update your computer's graphics driver. (405)". The cards named run from a GTX 1660 Super and an RTX 2060 up to an RTX 5090, on driver builds 580.159.03 through 580.178.04, streaming to a Quest 3S, a Quest 2 and a Steam Frame over the wireless adapter. We covered Valve acknowledging the breakage on September 30.
The diagnosis came from outside Valve
An owner, not Valve, found the missing piece. "The missing extension is VK_KHR_maintenance9. The Vulkan loader names it outright once VK_LOADER_DEBUG is enabled," he wrote on September 19, noting that 580.159.03 "exposes VK_KHR_maintenance1 through maintenance8, but not maintenance9" and that "It is not about AV1, and not about video encode at all."
Valve's own framing stayed broader throughout. "The NVIDIA 580 series driver incompatibility is already fairly well described here," a Valve account wrote on September 28, declining to split the discussion by GPU because "that's not the main factor involved in this issue report". The reply announcing the removal comes from the GitHub account that closed the report, whose profile describes its work as developing Steam Link and SteamVR.
What the change does not promise is a working Pascal setup. Dropping one extension requirement clears one specific startup failure, and nothing in the reply says a 10-series card will then stream VR well, or at all. It leaves untouched the other Linux faults owners have been filing against the same tracker, among them the green and black picture that SteamVR 2.18.2 introduced and then fixed under the same version number.
For anyone on a 580 driver, the practical position on October 3 is unchanged: move to a driver that carries the extension, if the card allows it, or wait for a beta that does not exist yet.