Support us on Patreon
PayPalThe driver release many NVIDIA fans have been waiting on is here today. NVIDIA released the NVIDIA 555.42.02 Beta driver with some necessary upgrades for Wayland support.
Since it's a Beta driver, it should go without saying that there may still be some lingering issues and bugs. This is for testing, but it shouldn't be too long before NVIDIA push out a stable driver with a small version number bump for when it's ready for everyone. Not that this will stop you right? You all want to try it.
The main changes are:
- The GSP firmware is now used by default on all GPUs which support it. It can be disabled by setting the kernel module parameter `NVreg_EnableGpuFirmware=0`.
- Added support for the linux-drm-syncobj-v1 protocol for Wayland explicit sync in EGL.
- Added immediate presentation mode support to Vulkan Wayland WSI. This presentation mode instructs the compositors not to wait for a vertical blanking period to update the application's surface content, which may result in tearing.
- Removed support for Base Mosaic on GeForce, which was previously available only on select GPU boards with some motherboards, and limited to five display devices.
- Enabled HDMI 10 bits per component support by default; disable by loading nvidia-modeset with `hdmi_deepcolor=0`.
- Added an interactive prompt to nvidia-installer to allow selecting between the proprietary and open kernel modules, on systems where both kernel module types are supported.
- Added support for using EGL instead of GLX as the OpenGL ICD for NvFBC.
- Changed the minimum required Linux kernel version from 3.10 to 4.15.
The bug fixes:
- Fixed a bug that caused "Failed to apply atomic modeset" and "Flip event timeout" messages to be printed to the system log when a DRM client such as ddcutil drops "master" permissions while a framebuffer console is being initialized.
- Fixed a bug, when nvidia-drm is loaded with the fbdev=1 module parameter on some kernels, that caused incorrect colors to be displayed.
- Fixed a regression that led to Xid errors when loading the NVIDIA driver on some notebook systems with RTX 4xxx series GPUs.
- Fixed a bug that caused driver build failure when using separate kernel source and output directories on Linux v6.6 and later.
- Fixed a bug that incorrectly allowed `nvidia-smi -r` to reset the primary GPU when using the open kernel modules.
- Fixed a bug that caused vkGetPhysicalDeviceSurfaceSupportKHR to incorrectly report support for Wayland surfaces when nvidia-drm is not loaded with modeset=1.
- Fixed a bug that could cause the display to lock up when suspending on a kernel with CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER enabled with nvidia-drm loaded with modeset=1 and fbdev=1.
- Fixed a bug that could lead to a system hang and "Idling display engine timed out" messages when VT switching on an HDMI Fixed Rate Link (FRL) display.
See it on the NVIDIA website.
Let me know how you get on with it in the comments.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
pleasereadthemanual May 22
This is probably not going to mean much for most Plasma users until October. As far as I know, explicit sync was implemented in Plasma 6.1 and not backported to 6.0 (?). 6.1 will be out in 2 months, but won't be in most distributions until October. It's in GNOME 46, though, from what I recall.
But, awesome, it's only a week later than anticipated. I don't have time or the bravery to test the 555 Beta, though, so I'll just wait until the stable driver is out.
I'm glad NVIDIA pushed the entire Linux Graphics Stack to implement explicit sync too. It makes all of our desktops better.
But, awesome, it's only a week later than anticipated. I don't have time or the bravery to test the 555 Beta, though, so I'll just wait until the stable driver is out.
I'm glad NVIDIA pushed the entire Linux Graphics Stack to implement explicit sync too. It makes all of our desktops better.
2 Likes, Who?
QuoteWill this enable the NvFBC feature for EGL, so obs-nvfbc might work again in OBS?
- Added support for using EGL instead of GLX as the OpenGL ICD for NvFBC.
edit: maybe
https://gitlab.com/fzwoch/obs-nvfbc/-/issues/14
Last edited by Corben on 22 May 2024 at 2:46 am UTC
0 Likes
Ok strange issue with that 555 driver on X11 at least. Huge amounts of frameskips (dualmonitor with different refresh rates)
But disabling the firmware fixes it (like it was with previous drivers):
im not using open kernel drivers.
reported here also: https://forums.developer.nvidia.com/t/555-release-feedback-discussion/293652
Its a beta driver afterall
Last edited by Xpander on 22 May 2024 at 4:28 am UTC
But disabling the firmware fixes it (like it was with previous drivers):
nvidia.NVreg_EnableGpuFirmware=0 im not using open kernel drivers.
reported here also: https://forums.developer.nvidia.com/t/555-release-feedback-discussion/293652
Its a beta driver afterall
Last edited by Xpander on 22 May 2024 at 4:28 am UTC
0 Likes
hardpenguin May 22
Quoting: XpanderI'm on X11, so i don't really have any benefit from that hyped up explicit sync supportMy thoughts as well... Wayland improvements are nice and all but most games and game-adjacent software still default to X11 anyway
0 Likes
pleasereadthemanual May 22
Quoting: hardpenguinXWayland has explicit sync support, which means improvement when you're running your desktop on Wayland and your games through XWayland, but Xorg doesn't have explicit sync support.Quoting: XpanderI'm on X11, so i don't really have any benefit from that hyped up explicit sync supportMy thoughts as well... Wayland improvements are nice and all but most games and game-adjacent software still default to X11 anyway
1 Likes, Who?
Quoting: Xpander> X11found the issue
>dualmonitor with different refresh rates
0 Likes
Quoting: pleasereadthemanualI'm glad NVIDIA pushed the entire Linux Graphics Stack to implement explicit sync too. It makes all of our desktops better.
They dragged us down by 10 years, without supporting GDB, wayland, etc, amd intel always had that figured out, except nvidia, this is a good solution yes, but because of their lazyness we aren't using wayland from default since years
0 Likes
Quoting: VillianQuoting: Xpander> X11found the issue
>dualmonitor with different refresh rates
never been an issue if you sync to highest refresh rate monitor.
0 Likes
Quoting: VillianQuoting: pleasereadthemanualI'm glad NVIDIA pushed the entire Linux Graphics Stack to implement explicit sync too. It makes all of our desktops better.
They dragged us down by 10 years, without supporting GDB, wayland, etc, amd intel always had that figured out, except nvidia, this is a good solution yes, but because of their lazyness we aren't using wayland from default since years
Why are you saying its because of their lazyness and not amd, intels and wayland lazyness? why should nvidia implement something that is legacy everywhere else and amd/intel not implement something that has been the standard for over 10 years and that they have already implemented on windows?
Last edited by nnohonsjnhtsylay on 22 May 2024 at 11:21 pm UTC
1 Likes, Who?
pleasereadthemanual May 22
Quoting: VillianTheir decision not to support GBM for many years held us all back, yes, but their decision not to implement implicit sync was a good decision in my opinion. They used the same tactic as Fedora KDE SIG to push others to support explicit sync, which is good for all GPUs. It means better performance and less buggy drivers.Quoting: pleasereadthemanualI'm glad NVIDIA pushed the entire Linux Graphics Stack to implement explicit sync too. It makes all of our desktops better.
They dragged us down by 10 years, without supporting GDB, wayland, etc, amd intel always had that figured out, except nvidia, this is a good solution yes, but because of their lazyness we aren't using wayland from default since years
2 Likes, Who?
See more from me