NVIDIA today released the NVIDIA 470.74 driver for Linux from their "Production Branch" which includes some important bug fixes so you might want to upgrade now if you've been holding off.
One issue that has been coming up for users of Steam Play Proton is that Direct3D 12 games have been seeing high system memory usage, which has caused many Windows games to become unplayable. Thankfully this driver fixes that! Thanks to that fix most people should be able to upgrade to 470.74. Other fixes include:
- Fixed a bug that could cause GPU applications to exit when resuming from suspend.
- Added an application profile to disable FXAA for Firefox to prevent visual corruption.
- Fixed a Vulkan performance regression that affected rFactor2.
- Fixed a bug that could cause the /proc/driver/nvidia/suspend power management interface to fail to preserve and restore video memory allocations when the NVreg_TemporaryFilePath module parameter for nvidia.ko specified an invalid path.
- Fixed a bug that caused nvidia-drm.ko to crash when loading with DRM-KMS enabled (modeset=1) on Linux v5.14.
When will you get the updated driver? Well that all depends on your distribution.
So what's next for NVIDIA and Linux? Currently we're waiting on the update they announced to bring DLSS to Proton for Direct3D titles. NVIDIA said this would arrive during September but it looks like currently some of the work has yet to be merged into the various places needed. More on that when we have it.
Fixed a bug that could cause GPU applications to exit when resuming from suspendChrome and Steam?
Added an application profile to disable FXAA for Firefox to prevent visual corruption.
This was corrected on the previous version... ????
Hope the fix will make it to the PPA soon.
I could copy and paste my usual NV driver situation rant from another site here, but to keep it short: Way too sucky, hello Windows...
Boo
This driver seems to break Gsync.
https://forums.developer.nvidia.com/t/nvidia-470-74-breaks-gsync-support-monitor-modulates-between-0-or-144hz-and-flickers-black/189716
This driver seems to break Gsync.
The monitors mentioned in that thread aren't gsync monitors though. So I'm hoping that they only broke gsync for freesync compatible monitors. In either case, thanks for the heads up. Now I can keep an eye on it before I upgrade.
See more from me