Confused on Steam Play and Proton? Be sure to check out our guide.
We do often include affiliate links to earn us some pennies. See more here.

NVIDIA 470.57.02 released as the next stable Linux driver (updated)

By - | Views: 23,502

On top of today NVIDIA revealing RTX and DLSS from Arm, plus the DLSS SDK updated for native Linux games they've now released the first stable driver of the 470 series with 470.57.02.

Compared with the monster that was the Beta release of NVIDIA 470.42.01 that gave us the likes of DLSS for Proton, hardware accelerated OpenGL and Vulkan rendering on Xwayland, and asynchronous reprojection this is a much smaller focused release to fix up some issues. However, it does also promote all the huge features from the previous Beta release to a stable driver for everyone to use!

Here's what's new and specific to just this release:

  • Updated the nvidia-settings command line interface to confirm successful assignment of string attributes. This makes the behavior more consistent with other types of attribute assignments.
  • Fixed a bug that could cause flickering in Blender and Steam when running on Xwayland.
  • Fixed a bug that caused GTK+3 applications using the GtkGLArea class to crash when running on Xwayland.
  • Added a workaround for DOOM Eternal, which avoids an application bug where Vulkan swapchain recreation events are not properly handled. On desktops like GNOME where the window is initially redirected to the compositor, this may prevent the game from flipping (and thus enabling G-SYNC).
  • Added a workaround for Far Cry 5 when run through DXVK, which avoids a shader race condition bug that was previously exposed by new compiler optimizations.

See the release notes for everything.

Update July 20, 2021: NVIDIA also released the 390.144 legacy driver update with these fixes:

  • Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided.
  • Fixed a driver installation failure on Linux kernel 5.11 release candidates, where the NVIDIA kernel module failed to build with error "fatal error: asm/kmap_types.h: No such file or directory".
Article taken from GamingOnLinux.com.
26 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
22 comments
Page: 1/3»
  Go to:

Mohandevir Jul 19, 2021
Next up... Nvidia's take on the Steam Deck!
Corben Jul 19, 2021
Waiting for the driver to arrive in the PPA again :D
Also hoping for less jitter with async reprojection in VR... I mean it should be "stable" now, right? ^^
Bogomips Jul 19, 2021
Ok new big stable NVIDIA driver is here. Now waiting for the release of Bullseye after the full freeze…
fearnflavio Jul 19, 2021
View PC info
  • Supporter Plus
That's great!
I just expect this also fixes the overclock feature. Even using coolbits=12 on my settings, on the Beta driver, I wasn't being able to overclock my card.
vipor29 Jul 19, 2021
should fix doom eternal launching as well seeing the game requires the 470 drivers to run.probably has no issues with amd cards.
Bumadar Jul 19, 2021
Although I fully agree nvidia has the better/faster/feature driver I moved to amd about 2-3 years ago. Tbh it was not out of some open source vs closed source purity reason I have to admit. Simple reason was I love my tumbleweed and although there is a repo or you can do it the hardware (kernel sources, build etc) new kernels where always a gamble, checking forums when a new version came out,locking kernel till was sure it would work.... In that respect I am glad I changed over, much more relaxing :)
slaapliedje Jul 19, 2021
Quoting: BogomipsOk new big stable NVIDIA driver is here. Now waiting for the release of Bullseye after the full freeze…
Worse situation is it'll be in backports. But I'm betting it can hit the exception for making it into Bullseye. Maybe?
tfa Jul 19, 2021
Did someone test the driver by chance on an optimus laptop? Since 470 the laptop fails to initialize my 1650 max-q. Had to roll back to 465 so it worked again.


Last edited by tfa on 19 July 2021 at 8:56 pm UTC
Bogomips Jul 19, 2021
Quoting: slaapliedje
Quoting: BogomipsOk new big stable NVIDIA driver is here. Now waiting for the release of Bullseye after the full freeze…
Worse situation is it'll be in backports. But I'm betting it can hit the exception for making it into Bullseye. Maybe?

For the NVIDIA drivers I'm outside the repos, every time I tried it was clunky at best.
slaapliedje Jul 19, 2021
Quoting: Bogomips
Quoting: slaapliedje
Quoting: BogomipsOk new big stable NVIDIA driver is here. Now waiting for the release of Bullseye after the full freeze…
Worse situation is it'll be in backports. But I'm betting it can hit the exception for making it into Bullseye. Maybe?

For the NVIDIA drivers I'm outside the repos, every time I tried it was clunky at best.
sudo apt install -t buster-backports nvidia-driver

That's too clunky?
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.