Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
We do often include affiliate links to earn us some pennies. See more here.

Following on from the 570.86.16 Beta that was released on January 30th, NVIDIA have today put up a new stable driver release with 570.124.04. As a reminder following a recent security bulletin, you'll want to ensure you're up to date.

Since the 570.86.16 Beta release these are the new changes for the stable driver:

  • Fixed a bug that could prevent displays from being restored correctly when resuming from suspend on some systems with multiple displays.
  • Fixed a regression which stopped VRR from working on HDMI displays.
  • Fixed an issue which caused stuttering and performance issues when scrolling windows in Wayland with GSP firmware enabled.
  • Fixed a bug that resulted in corruption or application crashes when using PRIME render offloading between two NVIDIA GPUs with modeset=1 enabled in nvidia-drm.
  • Added a new kernel module parameter, 'conceal_vrr_caps', to the nvidia-modeset kernel module. This parameter may be used to enable usage of features on some displays such as ULMB (Ultra Low Motion Blur) which are incompatible with VRR. See the "Direct Rendering Manager Kernel Modesetting" (DRM KMS) chapter of the README for further information.

To save you a click and for those who didn't try the Beta, all these below are also included in 570.124.04 that were first released via the 570.86.16 Beta:

  • Fixed a bug that caused the nvidia-settings control panel to crash when querying VRR attributes on some monitors.
  • Updated the nvidia-settings control panel to use NVML rather than NV-CONTROL to control GPU clocks and fan speed. This allows related functionality to work when using Wayland, where the NV-CONTROL X extension is not available. Note that as a result, some operations which were previously available to unprivileged users, due to the privileges of the X server, may now require elevated privileges.
  • Added support for VRR on systems with multiple displays.
  • Added an application profile to improve performance on Indiana Jones and the Great Circle.
  • Added an application profile to resolve a corruption issue on Assassin's Creed Valhalla and Assassin's Creed Mirage.
  • Implemented support for the VK_KHR_incremental_present extension.
  • Fixed a bug that could cause some Vulkan applications to crash when responding to window resize events.
  • Updated GPU overclocking control to be available by default in nvidia-settings, for GPU boards that support programmable clock control. Previously, this was only available when bit 3 was set in the "Coolbits" X config option.
  • Disabled a power saving feature on Ada and above generation GPUs for surfaces allocated with the DRM Dumb-Buffers API, for example, when using a DRM fbdev. The power saving feature could cause black screens for DRM Dumb-Buffers which use front buffer rendering instead of KMS flips.
  • Fixed a bug that could cause some multi-threaded OpenGL applications, for example Civilization 6, to crash when running on Xwayland.
  • Added support for querying Dynamic Boost status via the 'power' file in /proc/driver/nvidia/gpus/*.
  • Enabled 32 bit compatibility support for the NVIDIA GBM backend.
  • Added a new kernel module parameter, 'conceal_vrr_caps', to the nvidia-modeset kernel module. This parameter may be used to enable usage of features on some displays such as ULMB (Ultra Low Motion Blur) which are incompatible with VRR. See the "Direct Rendering Manager Kernel Modesetting" (DRM KMS) chapter of the README for further information.
  • Fixed a bug that could cause games to crash when the "PROTON_ENABLE_NGX_UPDATER" environment variable was set to a value of "1".
  • Added /usr/share/nvidia/files.d/sandboxutils-filelist.json which lists all the driver files used by container runtime environments such as nvidia-container-toolkit and enroot.
  • Added support for the systemd suspend-then-hibernate method of system sleep. This feature requires systemd version 248 or newer.
  • Enabled the nvidia-drm fbdev=1 option by default. When supported by the kernel and the nvidia-drm modeset=1 option is enabled, nvidia-drm will replace the system's framebuffer console with one driven by DRM.
    This feature can be disabled by setting fbdev=0.
  • Implemented a feature that allows low latency display interrupts to be serviced even when the system is under heavy contention. This is especially useful for reducing stutter when using virtual reality.
    This feature is experimental and disabled by default.
    This feature can be enabled by loading nvidia.ko with the `NVreg_RegistryDwords=RMIntrLockingMode=1` kernel module parameter.
  • Fixed a bug, introduced in 555.58, where some DVI outputs would not work with HDMI monitors.
  • In Linux kernel 6.11, drm_fbdev_generic was renamed to drm_fbdev_ttm. Use drm_fbdev_ttm when present to keep supporting direct framebuffer access needed for Wayland compositors to present content on newer kernels.
  • In linux-next commit 446d0f4849b1, output_poll_changed is removed from struct drm_mode_config_funcs. Do not implement the function pointer member when not present to ensure the driver can compile with newer kernels. The driver now supports enumerating modes on hotplug events through the DRM fbdev API.
  • In linux-next commit 446d0f4849b1, intended to be included in Linux kernel 6.12, output_poll_changed is removed from struct drm_mode_config_funcs. Do not implement the function pointer member when not present to ensure the driver can compile with newer kernels. Populating modes for DRM connectors during hotplug events will not be supported with r535 and kernels containing the relevant commit.
  • Fixed a bug that could cause external displays to become frozen until the next modeset when using PRIME Display Offloading with the NVIDIA dGPU acting as the display offload sink.

Source: NVIDIA

Article taken from GamingOnLinux.com.
5 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
You can also find comments for this article on social media: Mastodon
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.
5 comments Subscribe

MrDerby 4 hours ago
Great progress! Now just rewrite the whole driver stack in RUST
dancoleman 4 hours ago
Fixed an issue which caused stuttering and performance issues when scrolling windows in Wayland with GSP firmware enabled.

Can't wait to upgrade tonight and realize with disappointment that this doesn't fix Steam or flatpaks flickering.
seamoose 3 hours ago
The NVidia installer now asks "Multiple kernel module types are available for this system. Which would you like to use?" with the options being "NVIDIA Proprietary" and "MIT/GPL" - anyone care to summarize what you get with MIT/GPL?
CatKiller 2 hours ago
  • Supporter Plus
The NVidia installer now asks "Multiple kernel module types are available for this system. Which would you like to use?" with the options being "NVIDIA Proprietary" and "MIT/GPL" - anyone care to summarize what you get with MIT/GPL?
https://www.gamingonlinux.com/2024/05/nvidia-switching-to-open-kernel-modules-by-default-in-future-driver-update-for-turing/
linuxjacques 41 minutes ago
I guess I won't update to the 3:570.86.16-3.fc40 version which only became available on rpmfusion today.
I wasn't going to anyway - kernel series update (6.13) and nvidia binary update almost always means trouble.

I'll wait (some more).
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!
Login / Register