NVIDIA released its first Linux R620 production-driver build, 620.70.06, and it's mostly here to tidy up messes rather than add features. The headline fix resolves the Assassin's Creed Shadows hang that had plagued Linux gamers for about three months. It also patches Final Fantasy VII Rebirth crashes, improves Wayland performance, and fixes a kernel crash on servers. NVIDIA says it's a sensible upgrade from the 595 series, though users should confirm GPU and distro compatibility first.

NVIDIA ships first Linux R620 driver, ending months-long Assassin's Creed Shadows hang

The 620.70.06 build opens a fresh production branch, but the real win is a fix for a game hang that plagued Linux gamers for months.

NVIDIA has quietly launched the 620.70.06 Linux x64 display driver, the first build in a brand-new production branch called R620. It's out as of today, November 4, and the 549.76-megabyte installer isn't trying to sell you on shiny new features. NVIDIA is using it to clean up the kind of mess that leaks into early branch builds: Wayland correctness, game crashes, and a regression that had been biting Linux gamers for roughly three months.

The headline fix is for Assassin's Creed Shadows. That hang had festered since the 595 series and now gets a proper driver-side resolution.

Why R620 is a big-ish deal

NVIDIA doesn't version its drivers linearly, so this can read like a puzzle. The leading number in a driver version marks the branch. As of this release, the forums list the long-running production track at 595.x and the new-feature branch around 615.x, meaning R620 is a fresh next-generation production line stepping in behind the aging 595 series.

A first build in any production branch tends to be conservative on new features and heavy on stabilization. That describes this release exactly. Worth remembering that the 595 track is also the one whose regressions, the Assassin's Creed hang, plus earlier multi-GPU and VT-switching quirks, NVIDIA is now cleaning up as R620 takes over.

Why Linux gaming makes this worth telling

Linux's share of Steam hardware keeps climbing, largely on the back of Valve's Proton layer and the Steam Deck. Two pieces of the modern graphics stack now dominate the story. Wayland has replaced X.org as the default display server on most new desktops, and Vulkan paired with Proton is how Windows DirectX games actually run on Linux.

Bugs in NVIDIA's Vulkan driver don't show up as generic failures. They show up as one specific game hanging at a specific moment. That's why a single driver update can be the difference between a working afternoon and a broken install.

The full change set

NVIDIA lists eight changes, and they split cleanly into three buckets.

First, Wayland work. NVIDIA says it improved explicit synchronization performance in high-framerate benchmarks on Wayland, a technical way of saying deterministic frame presentation matters most for synthetic benchmarking tools and apps that want precise timing. It also expanded the OpenGL visual indicator, the __GL_SHOW_GRAPHICS_OSD overlay that shows frame times, to all Vulkan backends, and fixed the corruption and flickering that Vulkan apps hit under Wayland when running across multiple GPUs.

The fixes that will actually show up in gaming sessions come next. The Assassin's Creed Shadows regression that caused VK_ERROR_DEVICE_LOST hangs at certain scenes is gone. Final Fantasy VII Rebirth crashes tied to the descriptor_heap config option are fixed as well. A bug that mucked up the minimumIntervalUs frame-rate limit when frame generation is enabled has been corrected, which matters if you play with low-latency and DLSS-style frame generation switched on.

Finally, two system-level hardening items, both described in the notes. Item seven addresses a kernel crash on NUMA systems that have a node with no memory. Item eight fixes a bug that could let the installer place libraries outside the dynamic loader search path, which means fewer of those annoying "shared object not found" errors after a fresh install.

The Assassin's Creed hang, and how it actually got fixed

Here's the part that makes this story interesting. The Assassin's Creed hang didn't just quietly get resolved. It dragged on for about three months across the 595 and early 610 builds, and it needed real community debugging to even figure out what was happening.

The symptom was genuinely annoying: the game would freeze at spots like Amagasaki Castle with no Xid error messages in the kernel log. NVIDIA's usual tell for a GPU problem is an Xid message, and here there was nothing. Reporters said it reproduced across RTX 20, 30, and 40-series cards, with a separate Blackwell bug on 50-series cards muddying the waters.

It got untangled on the vkd3d-proton project's GitHub tracker. Contributor Saancreed tried shotgun debugging, while another user, Boogadaba, narrowed it to a single shader workaround that held up across 20-plus hours of play. That pointed at compute-barrier synchronization between the driver and the hardware. NVIDIA's fix lives on the driver side, so most people won't need to rebuild Proton with any manual patches.

On release day Saancreed wrote, in his words: "there's a good chance this issue has been fixed in latest driver release," pending his own verification.

One fix aimed at servers, not gamers

Item seven, the open GPU kernel modules crash, touches the part of NVIDIA's Linux strategy that most readers won't care about but that quietly signals where the company wants to go.

If you've never dealt with NUMA, it's the architecture where memory access latency depends on which CPU node a memory bank sits in. Servers and high-end workstations run it. Without this fix, such systems kernel-panic under GPU load. That's not a problem for your typical single-CPU gaming rig, and it's worth saying so plainly. But it's exactly the kind of thing NVIDIA needs to nail for its workstation and datacenter ambitions. The R620 branch is validated against the RTX Pro 6000 Blackwell Server Edition and RTX 6000D cards, and ships with CUDA Toolkit 13 bundled.

The open modules are a source-heavy stack you compile against your running kernel, and their transparency has real upside. Independent researchers at Quarkslab have published analyses of exploit paths in the modules' ioctls, which is a good reason to prefer open code over a black box when you can get it.

Where to get it

NVIDIA ships a standalone .run installer for both x86_64 and AArch64. The installer bug mentioned above is fixed in this build, so the install path is a little smoother than before. Head here for the driver details page. 

It's reasonable to be a little skeptical of a first build in a new branch. But this one does the homework you'd want: it fixes real regressions instead of shipping untested features. If you're on the 595 series or an early 610/615 build and you've hit the Assassin's Creed hang, this is the upgrade to grab. Keep in mind that R620 is new, so more fixes are coming.