Nvidia's Linux driver fixes a Last of Us Part II bug reported on its forum four months ago

Nvidia's Linux driver fixes a Last of Us Part II bug reported on its forum four months ago

Nvidia published Linux display driver 615.78.08 on October 7, and the first thing in its release highlights is a fix for a game bug a player described on Nvidia's own developer forum on May 26. Nvidia's wording is "Fixed blocky corruption observed during gameplay in The Last of Us Part II:", followed by a link straight to the post that raised it.

Nvidia's green eye logo rendered in three dimensions above a white faceted surface

Nvidia's Linux release highlights carry six fixes; the same week's Windows driver lists one. Image: Nvidia

That post sits in Nvidia's "610 release feedback & discussion" topic, opened by an Nvidia moderator account on May 26 and timestamped 18:47 UTC the same evening. A reader trying the 610 drivers on Arch wrote that "the weird blocky volumetric issue in The Last of Us 2 is still there as well", and attached a bug report. Four months and 11 days later Nvidia lists it as fixed.

Nvidia's Unix driver archive, read at 22:09 UTC on October 7, lists three newer packages on that line in between: 610.43 again on July 7, then 610.57 on August 3 and 615.71 on September 9. None of their release notes mentions the game. Nvidia does not say the forum report caused the fix, and nothing in the release establishes that: it links the post as the reference and leaves it there.

The entry is for the Linux x64 display driver, a 529.83 MB download in Nvidia's listing, and it describes the symptom only as blocky corruption during gameplay. What the original report describes is a volumetric effect breaking up into blocks, which is a reader's account of what appeared on screen rather than a diagnosis, and Nvidia has published no detail of the cause.

Six fixes on Linux against one on Windows

Counting the entries in the release highlights for 615.78.08 gives six. Besides The Last of Us Part II, Nvidia changed nvidia.ko "to avoid an interaction problem with certain SELinux configurations when the system is suspended via systemd and NVreg_UseKernelSuspendNotifiers is enabled", linking a Fedora bug filed against selinux-policy on August 6; it added "support for VK_NV_low_latency2 revision 3, to enable improving latency and stutter with vkd3d-proton, particularly when Frame Generation is enabled"; it switched NVreg_UseKernelSuspendNotifiers=1 on by default; it fixed a failure when allocating GPU page tables larger than 2 GiB; and it fixed unvalidated VkHdrMetadataEXT values reaching the Wayland colour-management protocol, which it says could cause a crash.

For comparison, Nvidia's Windows branch shipped 617.42 as a Game Ready driver for Modern Warfare 4 on October 6. Its release notes, read at 22:10 UTC on October 7, record one fixed gaming bug, the Assassin's Creed Shadows crash to desktop numbered 6685219, and "N/A" under fixed general bugs. Both counts here come from each document's own fixed-issues list, and Nvidia's caveat that the list "is only a subset of the total number of changes" applies to the Windows one.

Four weeks between releases on the 615 branch

615.78.08 is the first Linux driver on Nvidia's 615 production branch in 28 days. The previous one, 615.71.09, is dated September 9 in the same listing. The installer on Nvidia's download server weighs 529,834,675 bytes and carries a last-modified date of October 6 at 06:20 UTC, checked at 22:10 UTC on October 7, so the binary was staged a day before the matching source drop on GitHub at 16:30 UTC on October 7.

Linux owners have had a difficult run with Nvidia's recent branches, and Valve's own account of what the 580 driver did to Steam Link VR is the nearest reference point. Nvidia's notes for 615.78.08 say nothing about SteamVR or Steam Link, and the only claim in them about The Last of Us Part II is the one word fixed.

Leave a Comment

Your email address will not be published. Required fields are marked *