Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.

NVIDIA 555.42.02 Beta driver out bringing Wayland explicit sync

By - | Views: 40,423

The 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.
14 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 came back to check 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.
See more from me
24 comments
Page: 1/3»
  Go to:

Minux May 21
Hell... It's about time!

https://youtu.be/_J6-3l3hCm0?feature=shared


Last edited by Minux on 21 May 2024 at 2:07 pm UTC
Lintux May 21
Now its Time to implement it in Plasma 6.
And we need it in the Arch Repos.
furzegulo May 21
Quoting: LintuxNow its Time to implement it in Plasma 6.
And we need it in the Arch Repos.

i believe cachyos has plasma6-git version in their repos, which already has explicit sync enabled.
Xpander May 21
seems to work without issues so far:
xpander@archlinux ~ $ nvidia-smi | grep Version
| NVIDIA-SMI 555.42.02              Driver Version: 555.42.02      CUDA Version: 12.5     |


I'm on X11, so i don't really have any benefit from that hyped up explicit sync support
Quoting: Xpanderseems to work without issues so far:
xpander@archlinux ~ $ nvidia-smi | grep Version
| NVIDIA-SMI 555.42.02              Driver Version: 555.42.02      CUDA Version: 12.5     |


I'm on X11, so i don't really have any benefit from that hyped up explicit sync support
Well, me too, but it's obvious that in time I won't be; even Mint (which I use) is starting to get with the program. So I'm happy to see all the pieces get into place.
I also don't even use NVIDIA. But even so, good news about Linux working better is good news.
pilk May 21
Really excited for this to come to my distro. I've just been kinda living with the flickering, but I'm hype that, pretty soon, I won't have to.
nebadon2025 May 21
I just installed 555 Beta driver on Kubuntu 24.04 and nothing is changed for me, everything still flickers like crazy in wayland, in my first 20 minutes or so of using it, it feels worse than 550 and 545 drivers did, steam is flickering like crazy now.
pilk May 21
Quoting: nebadon2025I just installed 555 Beta driver on Kubuntu 24.04 and nothing is changed for me, everything still flickers like crazy in wayland, in my first 20 minutes or so of using it, it feels worse than 550 and 545 drivers did, steam is flickering like crazy now.

Kubuntu 24.04 chose to stay on Plasma 5, I'm unsure whether explicit sync is gonna apply there, or what version of XWayland it's on. It'll get Plasma 6 in 24.10.
KDE Neon's got the same Ubuntu LTS base, but it's on the latest Plasma 6. Maybe that's worth a shot.


Last edited by pilk on 21 May 2024 at 5:48 pm UTC
TopHat May 21
Seems to work fine with Discord (no longer Explicit Sync issues), but whew, Steam still is a mess under my Arch/EndeavourOS set up. Glitchy mess on Wayland when opening up (resizing the window fixes it), and no GPU acceleration seems like for Big Picture mode, with that causing it to be a tad glitchy.

(For the record: using KWin 6 fork with the Explicit Sync things added in)


Last edited by TopHat on 21 May 2024 at 6:19 pm UTC
I wonder if nvidia is ever going to fix the issue with cuda power usage when nvenc is used.
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


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.