NVIDIA 520.56.06 Linux Driver Released With OTA Updates For Proton/Wine NVIDIA NGX Build

[Guest]

• Fixed a regression in 515.76 that caused blank screens and hangs when starting an X server on RTX 30 series GPUs in some configurations where the boot display is connected via HDMI.

That's pleasant to hear. That was the first time a NVIDIA driver update actually broke something for me on Linux. It was fixed a while back on the open driver, but it's nice the standalone driver has it now.

WTF?
A closed source driver downloading stuff from the internet and installing it on the system?
So glad I'm not an Nvidia user!

Yeah, because NVIDIA will allow unsigned code from anyone to download of course, and distro package maintainers will make sure to allow it too. Lmao

Do you really believe NVIDIA implemented this for nefarious purposes and without any security checks?

[Guest]

What the heck are "NGX updates?" Never heard that before, and a search doesn't turn up anything.

https://github.com/jp7677/dxvk-nvapi/wiki/Tips-and-tricks-for-usage-with-DXVK-NVAPI#dlss-2x

I don't know for sure if it's just updating those 2 DLLs. Those DLLs are required to get DLSS working on Linux, so it seems related to RTX features. I vaugely recall hearing NVIDIA ships small updates like that on the Windows driver, but maybe it's only with GeForce Experience.

[ssokolow]

I'm curious how that NGX updating would work. Do they require a specially permissioned spot in the filesystem outside $HOME? Do they throw the files into the default WINEPREFIX and hope for the best (wouldn't get me since I use PlayOnLinux as my prefix manager). Do they download them on-the-fly in the background when the Wine-side driver gets initialized? (Won't get me since I run Wine and PlayOnLinux under Firejail with networking blocked)

I'm reminded of how much hassle it was to get the solvers working a few days ago when I was finishing up helping get PySolFC on Flathub, because their build process assumed you would either install the custom CMakery into /usr (immutable location of the Flatpak runtime) instead of /app or have network access not sandboxed off during the build phase for reproducibility (which flatpak-builder does).

[tuke81]

What the heck are "NGX updates?" Never heard that before, and a search doesn't turn up anything.

It's said on driver's readme as always:

http://us.download.nvidia.com/XFree86/Linux-x86_64/520.56.06/README/ngx.html

[sarmad]

What does over-the-air update mean anyway? It sounds like some flashy term used by sales departments to describe the same update process that we've had for ages.

[gsrcrxsi]

anyone seeing a performance regression on this driver vs 515.76?

I'm on Linux kernel 6, and was using 515.76 fine, but with the headache of the 30-series/HDMI black screen bug. I was working around this by leaving HDMI unplugged until the OS booted

updating to 520.56.06 fixed that bug, but performance seems worse. unfortunately only these two drivers seem to support linux 6.0. so either I have black screen bug with good performance or no black screen bug with bad performance . OpenCL compute workload.

[aufkrawall]

This driver greets me with fugly banding.

[partcyborg]

What does over-the-air update mean anyway? It sounds like some flashy term used by sales departments to describe the same update process that we've had for ages.

The term OTA update is most commonly used these days when describing android os updates delivered over the LTE network.

[sarmad]

The term OTA update is most commonly used these days when describing android os updates delivered over the LTE network.

So it is indeed just a flashy term for describing updates!

[ssokolow]

So it is indeed just a flashy term for describing updates!

In this context, probably a flashy term for "updates that don't have to wait for the usual means", since OTA is contrasted with "update by plugging your phone into your PC".