NVIDIA has today released driver version 520.56.06, adding support for NVIDIA RTX 40 series and adding a bunch of new features and fixes for Linux gamers.
New features:
- Implemented support for over-the-air updates in the Proton and Wine NVIDIA NGX build. This feature is disabled by default and can be enabled by setting the "PROTON_ENABLE_NGX_UPDATER" environment variable to a value of "1".
- Updated the Vulkan driver so that the following extensions no longer depend on nvidia-uvm.ko being loaded at runtime:
- VK_KHR_acceleration_structure
- VK_KHR_deferred_host_operations
- VK_KHR_ray_query
- VK_KHR_ray_tracing_pipeline
- VK_NV_cuda_kernel_launch
- VK_NV_ray_tracing
- VK_NV_ray_tracing_motion_blur
- VK_NVX_binary_import
- VK_NVX_image_view_handle
Updates:
- Updated nvidia-installer to allow use of the "--add-this-kernel" feature by non-root users.
- Updated nvidia-installer to display a more accurate progress bar when building the kernel modules.
- Updated nvidia-installer to display a warning message if a Vulkan ICD loader is not detected.
- Reworked nvidia-installer's support for DKMS: the kernel modules will now be optionally registered with DKMS after the installer has already built and installed them on its own. nvidia-installer will now register the kernel modules with DKMS by default when the dkms(8) utility is detected on the system.
- Added a new CUDA Debugger implementation for Pascal and newer architectures as a part of the driver package: libcudadebugger.so (previously released separately as "CUDA GDB Developer Preview").
Fixes:
- Fixed a bug in the Vulkan driver which could lead to corruption in geometry and tessellation control shaders.
- 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.
- Fixed a bug where Marvel's Spider-Man Remastered would sometimes crash with Xid 13 errors on Turing and later.
What are your thoughts on this update? Let us know in the comments.
In related news, in case you missed it, there's a new Mesa NVIDIA Vulkan driver in development.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Finally i can ditch the vulkan dev drivers. Seems graphics pipeline library made into it:
Smooth™ stutterfree gaming ftw!
xpander@archlinux ~ $ vulkaninfo | grep VK_EXT_graphics_pipeline
VK_EXT_graphics_pipeline_library : extension revision 1
xpander@archlinux ~ $ nvidia-smi | grep Version
| NVIDIA-SMI 520.56.06 Driver Version: 520.56.06 CUDA Version: 11.8 |Smooth™ stutterfree gaming ftw!
5 Likes, Who?
Mohandevir Oct 12, 2022
Seriously, I come to the saddening realization that I have no hype left for whatever Nvidia does, anymore. Lately, it all feels like a Porsche publicity when I come by Nvidia announcments; something I'll never pay for. Even the "low end" RTX 3050 is too expensive. I feel less and less concerned by Nvidia. Going AMD asap. I already did with my Steam Deck and I will ditch my GTX 1660 Super (my son's Christmas gift). The replacement GPU for my desktop is already ordered (RX 6500 XT).
Sorry, these are my "toughts on this update". This said, I'm happy for those that are still in the Nvidia camp and to those it will benefit.
Last edited by Mohandevir on 12 October 2022 at 3:48 pm UTC
Sorry, these are my "toughts on this update". This said, I'm happy for those that are still in the Nvidia camp and to those it will benefit.
Last edited by Mohandevir on 12 October 2022 at 3:48 pm UTC
2 Likes, Who?
slaapliedje Oct 12, 2022
Quoting: MohandevirSeriously, I come to the saddening realization that I have no hype left for whatever Nvidia does, anymore. Lately, it all feels like a Porsche publicity when I come by Nvidia announcments; something I'll never pay for. Even the "low end" RTX 3050 is too expensive. I feel less and less concerned by Nvidia. Going AMD asap. I already did with my Steam Deck and I will ditch my GTX 1660 Super (my son's Christmas gift). The replacement GPU for my desktop is already ordered (RX 6500 XT).I have a mix of nVidia and AMD systems. Neither are really the golden child on how to update their drivers. AMD requires kernel updates and using out of band (meaning not the standard repository) mesa libraries (unless you're running a rolling release, neither of these are easy). nVidia usually requires the distribution to keep their packages up to date so that they're easy to install for their users, but the distributions have been generally pretty poor at this.
Sorry, these are my "toughts on this update". This said, I'm happy for those that are still in the Nvidia camp and to those it will benefit.
1 Likes, Who?
Where are the Wayland improvements? I've been waiting for them to support Night Light feature for Wayland for a long time. They also don't support NvFBC and VDPAU in Wayland. This is really frustrating. My pain will not end until I switch to AMD or Intel.
1 Likes, Who?
Quoting: slaapliedjeAMD requires kernel updates and using out of band (meaning not the standard repository) mesa libraries (unless you're running a rolling release, neither of these are easy)This is a widespread notion but I honestly don't get it...
If we were talking about some cryptic app that only exists in AUR I would be agreeing, but we're talking about Mesa here.
How's adding Kisak's (Stable) Mesa PPA in any way difficult on Ubuntu and derivates?
On Linux Mint (even though it's the anthitesys of rolling release, because it's always based on Ubuntu LTS with a bonus ~6 month delay) we have a GUI for adding PPAs (and even 3rd-party Debian repos) called "Software Sources". It's not out-of-the-box, but it's at least a go-here-paste-this-click-ok do-once-and-forget procedure, so not that hard at all, right?
As for kernels, Linux Mint has a GUI for kernel version management offering whatever is available on kernel.ubuntu.org HWE stack for the Ubuntu LTS version it's based on, and kernel updates also follow through the Update Manager. 3 clicks will move you over the newest branch available then normal updates will keep it at the last revision.
On Ubuntu itself this is AFAIK a bit less friendly, but there is UKUU (3rd-party app) to cover the GUI-based kernel management gap and this even supports vanilla kernel.org releases, branch auto-upgrades, etc. There are other similar-purpose apps too, and they work across Ubuntu derivates as well.
0 Likes
More on the post topic, I'm really glad Nvidia caved for opensourcing parts of their driver (however long it it might take to happen) and started paying its technical debt of linux features that should work but don't because of their proprietary spaghetti-code driver
AMD and Intel obviously helped this happen because of their choice to support opensource driver stacks, but in a way I feel Valve also needs to be deeply thanked for this, as AMD alone hasn't picked up the pace (and probably wouldn't) until our linux gaming development patron came around and comissioned everyone to work on everything:
The Linux Kernel and Mesa themselves
RADV
ACO
DXVK
VKD3D
Zync
GameScope
Steam Deck using an AMD APU
...
I'll be waiting with past and current AMD (and maybe soon Intel) GPUs and APUs while they get up-to-speed
Last edited by Marlock on 12 October 2022 at 5:19 pm UTC
AMD and Intel obviously helped this happen because of their choice to support opensource driver stacks, but in a way I feel Valve also needs to be deeply thanked for this, as AMD alone hasn't picked up the pace (and probably wouldn't) until our linux gaming development patron came around and comissioned everyone to work on everything:
The Linux Kernel and Mesa themselves
RADV
ACO
DXVK
VKD3D
Zync
GameScope
Steam Deck using an AMD APU
...
I'll be waiting with past and current AMD (and maybe soon Intel) GPUs and APUs while they get up-to-speed
Last edited by Marlock on 12 October 2022 at 5:19 pm UTC
3 Likes, Who?
Quoting: MarlockThis is a widespread notion but I honestly don't get it...
If we were talking about some cryptic app that only exists in AUR I would be agreeing, but we're talking about Mesa here.
How's adding Kisak's (Stable) Mesa PPA in any way difficult on Ubuntu and derivates?
What about for non-Ubuntu and derivatives?
Consider that it may be a widespread notion because it is true (I don't know). Average users may find it difficult either way, either because they don't know how or they don't know what they don't know.
1 Likes, Who?
mr-victory Oct 12, 2022
"missing endbr" (the issue which needs ibt=off kernel parameter to fix) still not fixed.
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/256
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/256
0 Likes
Quoting: rcritSo, you're saying it might be true of distros that are neither rolling release and/or Arch derivatives, nor Ubuntu and derivatives?Quoting: MarlockThis is a widespread notion but I honestly don't get it...
If we were talking about some cryptic app that only exists in AUR I would be agreeing, but we're talking about Mesa here.
How's adding Kisak's (Stable) Mesa PPA in any way difficult on Ubuntu and derivates?
What about for non-Ubuntu and derivatives?
Are there distros that are intended for ease of use that also don't fit either of those baskets?
0 Likes
Fedora has COPR (same idea as a PPA) but also doesn't even need it most of the time because it has more up-to-date packages than Ubuntu.
It even has special channels for the user to choose to be more up-to-date than the base setup, called updates-testing and rawhide.
Most non-rolling distros have something of the sort, I just picked Ubuntu as an example exactly because it's a particularly big AND particularly slow-to-update distro.
If you're on a distro that's so small that it doesn't have any packaging options like this, it would be comparable to rolling-release distros that don't have the man-power to keep packages updated in a timely manner. The issue then is distro dev team size / distro popularity, not being rolling or not.
Not to mention there are some rolling-release distros that are more conservative like non-rolling ones on purpose like Slackware.
Agreed that most rolling distros tend to elect keeping core packages closer to upstream than Ubuntu, but popular/big non-rolling end up solving that issue too and only tiny ones are left behind in the end... and then only tiny ones that don't piggy-back directly on bigger distro repos, because Mint does have a tiny dev team yet its usage of Ubuntu-related stuff solves this issue for them.
Last edited by Marlock on 12 October 2022 at 8:36 pm UTC
It even has special channels for the user to choose to be more up-to-date than the base setup, called updates-testing and rawhide.
Most non-rolling distros have something of the sort, I just picked Ubuntu as an example exactly because it's a particularly big AND particularly slow-to-update distro.
If you're on a distro that's so small that it doesn't have any packaging options like this, it would be comparable to rolling-release distros that don't have the man-power to keep packages updated in a timely manner. The issue then is distro dev team size / distro popularity, not being rolling or not.
Not to mention there are some rolling-release distros that are more conservative like non-rolling ones on purpose like Slackware.
Agreed that most rolling distros tend to elect keeping core packages closer to upstream than Ubuntu, but popular/big non-rolling end up solving that issue too and only tiny ones are left behind in the end... and then only tiny ones that don't piggy-back directly on bigger distro repos, because Mint does have a tiny dev team yet its usage of Ubuntu-related stuff solves this issue for them.
Last edited by Marlock on 12 October 2022 at 8:36 pm UTC
0 Likes
Patreon
PayPal
See more from me