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 Oct 23
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
Caldathras Oct 23
Quoting: Purple Library GuyI find people who think their narrow knowledge specialty is the only important thing really annoying. And this is just ridiculous--I have lived through the entire trajectory of computing being even slightly accessible to people, starting from the TRS-80 model 1 my dad bought when I was 12, and there was never a time when many people would have understood that kind of note. Which doesn't say they shouldn't have notes like that--there are perfectly good reasons. But you can't have a declinism story when we were never in a place to decline from.Absolutely! I especially agree with the point about narrow knowledge specialty. It is possible to put things in layman's terms and still make an accurate and clear statement. Plain language legal contracts demonstrate this. Some might think that the failure to do this in many professions is because it would remove the exclusivity of their club ... but I think that it is simply that they get so used to thinking in their professional shorthand that they forget that outsiders do not speak it too.
2 Likes, Who?
So far the driver has been as good as the previous one. No issues to report. No regressions noticed yet.
but since i didn't have any issues with 560.xx drivers, i don't really have anything to try to see what got fixed for my usecases or games. will see about vkd3d performance i guess, but i don't play many modern games and the ones with dx12 i played seemed to run with no perf issues on 560 already, but will keep an eye on this.
edit: ok tested gamescope and yeah the cursor rendering seems to be fixed now. That was the final issue with gamescope for me. Though i don't really like gamescope, cause i have to force cursor grab in Warhammer Online, otherwise every mouse move just points me to look at the floor. With forced curosr grab thats fine, but i cant escape to second monitor easily without switching workspace.
Last edited by Xpander on 24 October 2024 at 8:35 am UTC
but since i didn't have any issues with 560.xx drivers, i don't really have anything to try to see what got fixed for my usecases or games. will see about vkd3d performance i guess, but i don't play many modern games and the ones with dx12 i played seemed to run with no perf issues on 560 already, but will keep an eye on this.
edit: ok tested gamescope and yeah the cursor rendering seems to be fixed now. That was the final issue with gamescope for me. Though i don't really like gamescope, cause i have to force cursor grab in Warhammer Online, otherwise every mouse move just points me to look at the floor. With forced curosr grab thats fine, but i cant escape to second monitor easily without switching workspace.
Last edited by Xpander on 24 October 2024 at 8:35 am UTC
1 Likes, Who?
Patreon
PayPal
See more from me