Valve enables NVIDIA drivers in the main SteamOS tree

Valve has enabled the NVIDIA driver inside the main tree of SteamOS, according to its software developer Pierre-Loup Griffais, in the clearest sign yet that the company intends its console-style operating system to run on hardware it did not build.

What Valve actually said

Asked by IGN about progress on NVIDIA support, Griffais said the work is ongoing and the path is open but not finished: “Yeah, we're working on it hard... We've done a few things like we've enabled the driver now in the main tree of SteamOS, so you can get things to light up on certain generations, but in terms of the performance difference between that driver and where the state of the art is, there's definitely still a little bit of a rift that we're trying to work on, but it's getting better day-to-day.” The report carrying his answer was published on 16 September.

Why a SteamOS machine has always meant AMD

Every device Valve has shipped with SteamOS inside it, from the Steam Deck to the Steam Machine and the Steam Frame, runs on AMD silicon, so AMD has been the only sensible target for the operating system's graphics stack. Support for NVIDIA means SteamOS can be offered on hardware Valve does not control, which is the entire argument for the Steam Machine idea: a console-like experience on a PC someone already owns. There is a knock-on effect beyond Valve's own devices. SteamOS is built on Arch Linux, and work that lands upstream benefits anyone running an NVIDIA card on Linux, where drivers are often a release or two behind what Windows gets.

What is still missing

There is no list of supported generations, no performance figures and no release date. Griffais describes cards lighting up on certain generations, which is a weaker commitment than a support matrix, and he is explicit that a gap against the state of the art remains. Nothing here changes what anyone should buy this month; it changes what Valve expects its software to run on in a year or two.

Our opinion

NVIDIA's Linux driver has been the awkward third option for a decade: it works, it is rarely the version everyone else ships, and it has historically been the last thing fixed when a new game arrives. Valve putting it in the main tree matters far more than a changelog line suggests, because that phrase is a plumbing statement rather than a feature announcement, and it means the driver is now part of what SteamOS builds against instead of something a user bolts on afterwards. The careful reading of Griffais's answer is that Valve is being honest about the gap, which is the right instinct: the Steam Machine promise only holds together if a card someone already owns performs like a card someone already owns. Until there is a generation list and a number attached to that rift, treat this as a commitment to a direction rather than a release to plan around.