NVIDIA today released the 570.86.16 Beta driver for Linux which includes various new features, and a few good bug fixes too. Quite an exciting one too since it brings support for VRR on systems with multiple displays.
This is a Beta driver available for preview, but it should be good enough for most gamers to use but it may also come with issues as it hasn't yet been through their full testing like their certified drivers.
New Features and Tweaks:
- Added support for VRR on systems with multiple displays.
- 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 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.
- 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.
- 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.
- 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.- 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.
Bug Fixes:
- Fixed a bug that caused the nvidia-settings control panel to crash when querying VRR attributes on some monitors.
- Fixed a bug that could cause some Vulkan applications to crash when responding to window resize events.
- Fixed a bug that could cause some multi-threaded OpenGL applications, for example Civilization 6, to crash when running on Xwayland.
- Fixed a bug that could cause games to crash when the "PROTON_ENABLE_NGX_UPDATER" environment variable was set to a value of "1".
- Fixed a bug, introduced in 555.58, where some DVI outputs would not work with HDMI monitors.
- 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
Some you may have missed, popular articles from the last month:
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.
For all the shit Nvidia gets for their Linux drivers they've been crushing it as of late. Glad they see the writing on the wall with Wayland.
1 Likes, Who?
Installed the 570 driver last week (leaked cuda 570.86.10 and 570.86.15) and it is running great so far. Going to install the 570.86.16 in a hour or 2. Nvidia did a great job with this driver.
Last edited by MichelN86 on 30 Jan 2025 at 4:42 pm UTC
Last edited by MichelN86 on 30 Jan 2025 at 4:42 pm UTC
0 Likes
Does multi-monitor VRR work with Wayland only, or both X11 and Wayland with this driver?
0 Likes
So far been great on MATE, X11 at least
No new issues to report yet, tiny bit of perf improvement (~5%) on dx12 games (cyberpunk2077 and wrc generations) since the 565 drivers.
xpander@archlinux ~ $ nvidia-smi | grep Version
| NVIDIA-SMI 570.86.16 Driver Version: 570.86.16 CUDA Version: 12.8 |
No new issues to report yet, tiny bit of perf improvement (~5%) on dx12 games (cyberpunk2077 and wrc generations) since the 565 drivers.
0 Likes
Pretty sure Multi-VRR can ONLY be done on Wayland. X11 is not capable of it. As I'm told.
A earlier release of this had a HDMI2.1 bug which caused blackouts in Multi VRR mode or disabled VRR or black flickering in games.
A earlier release of this had a HDMI2.1 bug which caused blackouts in Multi VRR mode or disabled VRR or black flickering in games.
0 Likes
NOPE
VRR not fixed. Broke still. Shame
VRR not fixed. Broke still. Shame
0 Likes
See more from me