Check out our Monthly Survey Page to see what our users are running.
We do often include affiliate links to earn us some pennies. See more here.

In a nice big win for open source, NVIDIA has today officially revealed that they've released open source Linux GPU kernel modules. Additionally, driver version 515.43.04 is out. This is a huge step and hopefully the sign of more to come from NVIDIA.

This release is a significant step toward improving the experience of using NVIDIA GPUs in Linux, for tighter integration with the OS and for developers to debug, integrate, and contribute back. For Linux distribution providers, the open-source modules increase ease of use. They also improve the out-of-the-box user experience to sign and distribute the NVIDIA GPU driver. Canonical and SUSE are able to immediately package the open kernel modules with Ubuntu and SUSE Linux Enterprise Distributions.

NVIDIA

NVIDIA say that with each new driver release, they will be publishing the sources mentioned on GitHub, and they will be accepting contributions from the community and other developers.

For now, data center GPUs are "production ready" but normal GeForce and Workstation GPUs (what we all use) are at an "alpha quality" for Turing and Ampere but NVIDIA plans to continue improving on it and "fully featured GeForce and Workstation support will follow in subsequent releases and the NVIDIA Open Kernel Modules will eventually supplant the closed-source driver". NVIDIA has also been working with the likes of Canonical, Red Hat, and SUSE for better packaging and deployment of it all.

There's still quite a long road ahead, as NVIDIA say it currently doesn't conform to the upstream Linux kernel design and so can't go upstream yet but they have plans to work on "an upstream approach" with help again from Canonical, Red Hat, and SUSE. For now, NVIDIA say it can serve as a way to also "help improve the Nouveau driver" since it will be able to use the same firmware as the main proprietary NVIDIA driver.

As for the driver release version 515.43.04, here's the main changes:

  • Added support for the VK_EXT_external_memory_dma_buf and VK_EXT_image_drm_format_modifier Vulkan extensions. To use this functionality, the nvidia-drm kernel module must be loaded with DRM KMS mode setting enabled. See the DRM KMS section of the README for guidance on enabling mode setting.
  • Changed nvidia-suspend.service, nvidia-resume.service, and nvidia-hibernate.service to use WantedBy= rather than RequiredBy=dependencies for systemd-suspend.service and systemd-hibernate.service.This avoids a problem where suspend or hibernate fails if the NVIDIA driver is uninstalled without disabling these services first.
    See https://github.com/systemd/systemd/issues/21991
    If these services were manually enabled, it may be necessary to update their dependencies by running sudo systemctl reenable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service
  • Interlaced modes are now disabled when active stereo is enabled.
  • NVIDIA X Server Settings will now display the quit confirmation dialog automatically if only there are pending changes that need to be manually saved. The corresponding configuration option to control the appearance of the quit dialog was thus also removed.
  • Removed the warning message about mismatches between the compiler used to build the Linux kernel and the compiler used to build the NVIDIA kernel modules from nvidia-installer. Modern compilers are less likely to cause problems when this type of mismatch occurs, and it has become common in many distributions to build the Linux kernel with a different compiler than the default system compiler.
  • Updated nvidia-installer to skip test-loading the kernel modules on systems where no supported NVIDIA GPUs are detected.
  • Updated nvidia-installer to avoid a race condition which could cause the kernel module test load to fail due to udev automatically loading kernel modules left over from an existing NVIDIA driver installation. This failure resulted in an installation error message "Kernel module load error: File exists".
  • Updated the RTD3 Video Memory Utilization Threshold (NVreg_DynamicPowerManagementVideoMemoryThreshold) maximum value from 200 MB to 1024 MB.

With those changes, it means the start of support for Gamescope on NVIDIA drivers too!

Source code up on GitHub, driver release here.

Also, you can read the take from Red Hat's Christian F.K. Schaller on it here.

Update: oh, and remember how NVIDIA wanted to get NVIDIA Image Scaling into Proton? Well, a Pull Request is now up for Gamescope support, where it might be more likely to be accepted since it makes a bit more sense there perhaps.

Article taken from GamingOnLinux.com.
59 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.
See more from me
The comments on this article are closed.
53 comments
Page: «4/6»
  Go to:

dpanter May 12, 2022
Be very careful with your enthusiasm people, remember who you're dealing with here. One step towards a good move does not absolve Nvidia from decades of anti-competitive strategies and shady business dealings.
I do not forget and I do not forgive.

This is positive news, yes... but make sure you read the fine print like has been pointed out a couple of times already in these comments. Not the time to be celebrating just yet. If we're talking about hell freezing over, this is more like the first snowflake appearing in the burning skies with hopefully many more joining soon.

And I'm sure the hack had nothing to do with this at all...
lejimster May 12, 2022
Oh wow, I totally missed this story yesterday. I have been sticking with AMD because of their open source drivers and how well it all just works. With this announcement I'm not totally opposed to getting a Nvidia GPU for my next upgrade.
STiAT May 12, 2022
Quoting: edoThe article should have explained what is open-source and what is not. I assume the driver itself is still not open source

The kernel driver/modeset driver etc. are open source.

The userspace ones (OpenGL, Vulkan etc.) are not.

It's about hardware support. We will have to look to Mesa /nouveau for a userspace driver implementation. Which will be a lot easier with a DRM driver available, but still will take time, and just getting the kernel driver mainlined / compliant will take time. Until that it will live out of tree, but can be provided by distros and used instead of the current nouveau drm kernel driver, to be used by the nouveau implementation in Mesa.

I think :-)


Last edited by STiAT on 12 May 2022 at 1:36 pm UTC
iWeaker4You May 12, 2022
Quoting: edoThe article should have explained what is open-source and what is not. I assume the driver itself is still not open source

NVIDIA releases open source Linux GPU KERNEL MODULES
iWeaker4You May 12, 2022
NVIDIA Kernel modules + Nouveau
could be the future
ssj17vegeta May 12, 2022
Hold on people, if I get it correctly, they didn't open-source their whole drivers, just the DKMS.

Of course, it's still very good news and definitely a step on the right path !
Dribbleondo May 12, 2022
Has...hell frozen over?
STiAT May 12, 2022
Quoting: ssj17vegetaHold on people, if I get it correctly, they didn't open-source their whole drivers, just the DKMS.

Of course, it's still very good news and definitely a step on the right path !
Quoting: ssj17vegetaHold on people, if I get it correctly, they didn't open-source their whole drivers, just the DKMS.

Of course, it's still very good news and definitely a step on the right path !

It still helps a lot. My preferred version would probably be the kernel drivers properly maintained with the kernel, and the userspace actually with support from Nvidia and others becoming Mesa/nouveau.

I don't see the need to make userspace libs open source. AMD does not either, they help (or rather basically develop mostly on their own) the open source Mesa version too.

I could see Nvidia going the same path, keeping their userspace closed source but lending a helping hand to Mesa/nouveau. I'd like that actually, so we in the end have one library for userspace drivers - Mesa.

We'll see what happens, but actually hopefully the kernel upgrade not breaking akms / compiling of the nvidia module would be very welcome indeed. It does not happen often, but happend to me once since the beginning of the year in Fedora. Though, Fedora went on while they knew this would break it for Nvidia users since it's out-of-tree, within this open source change this could become a kernel module in-tree for Fedora too. Which I'd like.
Shmerl May 12, 2022
Quoting: STiATI don't see the need to make userspace libs open source. AMD does not either, they help (or rather basically develop mostly on their own) the open source Mesa version too.

AMD supports both radeonsi (open source OpenGL for AMD in Mesa) and amdvlk (open source Vulkan for AMD, but not part of Mesa). So their full stack is open source. Mesa has radv for it.

So for Nvidia to be on par, someone has to implement open source Vulkan for them. Open source OpenGL in Mesa for it already exists (though not supported by Nvidia).


Last edited by Shmerl on 12 May 2022 at 6:08 pm UTC
TheRiddick May 12, 2022
It's only a driplet of FOSS support. We will have to see where this leads over the next 12 months.
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.
Buy Games
Buy games with our affiliate / partner links: