Linux Gaming

15892 readers

65 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

poVoq@slrpnk.net

Quintus@lemmy.ml

mudle@lemmy.ml

121

NVIDIA driver 555.58 released as stable bringing Wayland Explicit Sync (www.gamingonlinux.com)

submitted 4 months ago by mudle@lemmy.ml to c/linux_gaming@lemmy.ml

6 comments fedilink hide all child comments

The time is finally here. The next big stable update to the NVIDIA proprietary driver for Linux with version 555.58 bringing Wayland Explicit Sync.

Following on from the initial NVIDIA 555.42.02 Beta and the 555.52.04 Beta, NVIDIA noted some rather vague "Minor bug fixes and improvements" since the last Beta. With this release, you should be truly good to go with Wayland on NVIDIA GPUs now.

you are viewing a single comment's thread
view the rest of the comments

[–] independantiste@sh.itjust.works 4 points 4 months ago (1 children)

Oh, I hear there are some pretty major issues with Firefox and explicit sync on Wayland. Does anyone know if fedora will have patches to make sure everything works fine when it releases to rpmfusion? If not then I might wait a bit...

[–] tarsisurdi 1 points 4 months ago* (last edited 4 months ago) (1 children)

What issues are you aware people have been experiencing?

I’m currently running 555.52.04 (this driver’s beta release) on F40 + GNOME Wayland and Firefox has been working flawlessly. Video playback using PiP has also improved a lot for me although IDK if it’s related to explicit sync or Wayland itself. Before installing these drivers I was using X and that feature would annihilate my desktop’s performance.

[–] independantiste@sh.itjust.works 1 points 4 months ago

I have seen reports of Firefox crashing under Wayland and that the way to make it work was to disable Wayland in Firefox or iirc to add a kernel parameter. Maybe it was fixed in Firefox too, but I saw some people saying the flatpak was somehow now affected (?)