NVIDIA today released two new Linux drivers. The big one is the NVIDIA 565.57.01 Beta, along with a one-liner update in the stable 550.127.05 release.
The stable release driver 550.127.05 mentions "Fixed a bug which could cause applications using GBM to crash when running with nvidia-drm.modeset=0".
While the bigger NVIDIA 565.57.01 Beta includes various new features and fixes I've split below for easy reading.
New Features & Improvements
- Re-enabled GLX_EXT_buffer_age on Xwayland. This extension had been previously disabled on Xwayland due to a bug which is now fixed.
- Added support for mmap of exported DMA-BUF objects.
- Added several new per-plane and per-CRTC vendor-specific properties to nvidia-drm. These properties may be used by Wayland compositors to program the GPU's color pipeline for HDR hardware acceleration.
- Introduced a driver optimization to mitigate the performance loss from the 'd3d9.floatEmulation' option in DXVK.
- Updated the framelock settings page of the nvidia-settings control panel to use the GTK3 theme text color rather than defaulting to white for the text color, improving legibility with some themes.
- Implemented support for VK_EXT_depth_clamp_control.
- Reduced some cases of stutter with OpenGL syncing to vblank while using GSP firmware.
Bug Fixes:
- Fixed a bug that could cause suspend/resume to fail when using the NVreg_PreserveVideoMemoryAllocations option: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/472
- Fixed a bug that caused the cursor image to be truncated on Gamescope: https://github.com/ValveSoftware/gamescope/issues/1099
- Fixed a bug that caused FarCry 5 running through DXVK to display a black screen.
- Fixed some performance regressions that were observed with Vkd3d 2.9.
- Fixed a bug that could cause flickering in some applications when using Unified Back Buffer (UBB).
- Fixed a bug which could cause incorrect and/or washed out colors to be displayed with HDR scanout: https://bugs.kde.org/show_bug.cgi?id=482780
- Implemented support for VK_EXT_depth_clamp_control.
- Fixed a bug which could cause applications using GBM to crash when running with nvidia-drm.modeset=0.
- Fixed a bug that could cause kernel crashes upon attempting KMS operations through DRM when nvidia_drm was loaded with modeset=0.
Let me know your thoughts in the comments!
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
Quoting: Vortex_AcheronticI am really starving for explicit sync but 560 is still NFB or Beta. Neither or which are packaged by openSUSE
(Checks repo) You're not wrong! For my Tumbleweed system I've created a small script to update my drivers 'the hard way' as I like to have the latest release installed.
1 Likes, Who?
Vortex_Acherontic about 4 hours ago
Quoting: robvvQuoting: Vortex_AcheronticI am really starving for explicit sync but 560 is still NFB or Beta. Neither or which are packaged by openSUSE
(Checks repo) You're not wrong! For my Tumbleweed system I've created a small script to update my drivers 'the hard way' as I like to have the latest release installed.
Yeah thought of it too. But then remembered I use systemd-boot, TPM 2.0 FDE and secure boot on Aeon. Even the official driver package was a bit flunky at first during install and updating. So I decided to not break my system and wait patiently :D
Which reminds me ... I believe there was a question lately on the bug tracker. *moves out*
0 Likes
Quoting: ShabbyXAnyone knows how to have a convenient get-the-latest-nvidia-driver setup on Debian? On Ubuntu, they had something in the settings to choose the latest driver. In Debian, the nvidia driver is always waaay behind.AFAIK there was some command line option you can run official Nvidia driver .run file with to generate .deb files you can then install with dpkg.
0 Likes
Patreon
PayPal
See more from me