Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.

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 checked 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. You can also follow my personal adventures on Bluesky.
See more from me
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
22 comments
Page: 1/2»
  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
Ok 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
Ok 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
Ok 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?
michaldybczak Jul 19, 2021
I don't understand. Are those 470.42 features in 470.57 or not? If not, when will they be added?
Ehvis Jul 19, 2021
View PC info
  • Supporter Plus
I don't understand. Are those 470.42 features in 470.57 or not? If not, when will they be added?

They are. The release notes duplicate the entire 470.42 release notes as well.
Bogomips Jul 20, 2021
Ok 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?

No, I mean the result was, with dependency errors and I didn't want to investigate further because the standalone install works fine for me.
Eike Jul 20, 2021
View PC info
  • Supporter Plus
No, I mean the result was, with dependency errors and I didn't want to investigate further because the standalone install works fine for me.

Nvidia driver from backports (and even experimental) works great for me for years now. It seems the driver is so independent of the rest that "it just works".


Last edited by Eike on 20 July 2021 at 8:56 am UTC
ziggurat Jul 20, 2021
Next up... Nvidia's take on the Steam Deck!

I know this is a joke and or wishful thinking. But the thing people may not realize is that the Nintendo Switch is Nvidia's "answer" or equivalent of the SteamDeck. The Nvidia Nintendo Switch is the Nvidia handheld that can do a few hours of AAA gaming on the go.

Nvidia I am sure has agreed to a non compete agreement with Nintendo, if not, any competition with the N Switch is eating away at Nvidias potential earnings for an Nvidia branded handheld
Liam Dawe Jul 20, 2021
Update: fresh legacy driver out.
Comandante Ñoñardo Jul 20, 2021
Weird...
I'm on Ubuntu 20.04 LTS and I just got an Nvidia driver update, but it is not the 470.54.02 version, it is the 460.91.03 version...

What is going on with Ubuntu and Nvidia?
CatKiller Jul 21, 2021
View PC info
  • Supporter Plus
Weird...
I'm on Ubuntu 20.04 LTS and I just got an Nvidia driver update, but it is not the 470.54.02 version, it is the 460.91.03 version...

What is going on with Ubuntu and Nvidia?
The PPA got 470 today, so I got automatically updated from the 470 beta. I don't think that Ubuntu habitually moves you from one branch to another unless a branch loses support and they put in a transitional package. The 460 branch did get an update yesterday.

Edit: oh, it was actually the main Ubuntu repo that pulled in the new 470 rather than the PPA.


Last edited by CatKiller on 21 July 2021 at 12:00 pm UTC
Redface Jul 21, 2021
Weird...
I'm on Ubuntu 20.04 LTS and I just got an Nvidia driver update, but it is not the 470.54.02 version, it is the 460.91.03 version...

What is going on with Ubuntu and Nvidia?

There are several Nvidia drivers in the Ubuntu repositories.

Use

 
ubuntu-drivers list

to see which proprietary drivers are available for you hardware.
Or go to Additional drivers in Updates & Software.

Just switch to 470 if you want it, and if you have problems you easily can go back to 460

465 was transitioned to 470, so if you had 465 installed then you would have got 470 now, but since you where on 460 which is still supported you got the latest 460 version.


Last edited by Redface on 21 July 2021 at 1:25 pm UTC
slaapliedje Jul 21, 2021
Ok 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?

No, I mean the result was, with dependency errors and I didn't want to investigate further because the standalone install works fine for me.

Generally dependency errors only occur when you attempt to use stuff outside of the main, contrib, non-free debian repositories, including enabling backports. Sounds like you possibly used some other repository that caused dependency issues. It's why I always shudder when people just suggest 'enable X ppa'. Most of them are not of the quality of what Debian tries to insist their packages are.
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.