News report

Valve Flags NVIDIA 580 Driver Incompatibility With Steam Link VR on Linux

Valve has identified NVIDIA's 580-series Linux driver as incompatible with Steam Link VR in an open SteamVR tracker issue, with Vulkan device creation failing.

On this page
  1. Valve points to the NVIDIA 580 driver branch
  2. The missing-extension diagnosis is narrower than Valve's confirmation
  3. Pascal users have the least obvious escape route

Valve points to the NVIDIA 580 driver branch

Valve has identified NVIDIA's 580-series Linux graphics driver as the common incompatibility behind Steam Link VR failures tracked in an open SteamVR-for-Linux issue. The report was opened September 7 after Steam Link successfully connected to a headset but SteamVR failed while creating its Vulkan device.

The visible failure is SteamVR graphics error 405. Logs attached to the report show vkCreateDevice returning VK_ERROR_EXTENSION_NOT_PRESENT (-7), which prevents the compositor from initializing even though the network session and headset detection have already succeeded.

What the current SteamVR-for-Linux evidence establishes
LayerObserved statusWhat it means
Steam Link connectionConnects and identifies the headsetThe failure occurs after basic pairing/network setup
Vulkan device creationFails with VK_ERROR_EXTENSION_NOT_PRESENTSteamVR cannot initialize the required Vulkan device
NVIDIA branchValve identifies the 580 series as incompatibleThe issue is not being treated as one specific GPU model
VK_KHR_maintenance9Reporter diagnostics identify it as missing on tested 580 driversThis is strong tracker evidence, but the extension diagnosis comes from users rather than a formal NVIDIA release note
Fix timelineNo public fix date in the trackerUsers should not assume a SteamVR or NVIDIA fix has already shipped

The missing-extension diagnosis is narrower than Valve's confirmation

Community diagnostics in Valve's tracker identify VK_KHR_maintenance9 as the extension Steam Link VR requests but NVIDIA 580-series systems in the thread do not expose. That fits the VK_ERROR_EXTENSION_NOT_PRESENT failure, but Core Tech Tips is keeping the attribution precise: Valve has confirmed the 580-series incompatibility, while the maintenance9 identification comes from reporter debugging in the public issue.

The original report initially considered missing AV1 video encode support because the first affected system used a Turing GPU. Reports from newer NVIDIA hardware helped rule out that simple explanation and shifted the investigation toward the driver branch and Vulkan extension set.

Pascal users have the least obvious escape route

The tracker includes reports spanning multiple NVIDIA generations, reinforcing Valve's point that fragmenting the issue by GPU model is not useful when the shared factor is the 580 driver series. Some users report success after moving to newer driver branches, but those are individual reports rather than a universal workaround validated by Valve.

That distinction matters particularly for older Pascal hardware, where users in the thread say moving to newer open-module driver branches is not an available path. Valve has not published a fix timeline or a supported 580-series workaround in the issue, so the safest status is unresolved incompatibility rather than a promised fix.

Sources

Primary and technical sources

These sources support the reporting and analysis above. Current stories are updated when later evidence materially changes the facts.

  1. 01 ValveSoftware / GitHub

    [BUG] Steam Link VR: vkCreateDevice fails with VK_ERROR_EXTENSION_NOT_PRESENT on NVIDIA 580
  2. 02 Valve / Steam Support

    SteamVR for Linux Support
  3. 03 MIXED

    Valve confirms Nvidia's 580 driver branch breaks Steam Link VR on Linux

Related

Technical guide

How to Back Up Installed Drivers in Windows 11

Export third-party driver packages from the Windows 11 driver store with PnPUtil, preserve them before a reinstall, and understand what the backup does and does not contain.