Gave it another try with 550.40.07-2 (from aur)
Kernel command in full: GRUB_CMDLINE_LINUX="rootfstype=xfs nvidia_drm.fbdev=0 nvidia-modeset.disable_vrr_mclk_switch=0 nvidia_drm.modeset=1"
Also tried it with: GRUB_CMDLINE_LINUX="rootfstype=xfs nvidia_drm.fbdev=0 nvidia-modeset.disable_vrr_mclk_switch=1 nvidia_drm.modeset=1" and with modeset before everything else (if it makes any difference).
My test is factorio steam, as it is native title and presents the issue immediately.
With all of the above the behavior is the same. Screen flickering black. Most noticeably when biters enter the scene. Tried turning off vsync in game and freesync in monitor settings. Nothing changed.
Turning on fbdev breaks my display manager (greetd) and it stops being displayed.
I’ve even tried flatpak and native steam. No changes.
Also tried purging my steam install completely (not really intended to) by deleting .var/app/com.valvesoftware.steam folder. Didn’t change anything.
tldr: No matter what I change, behavior still persists.
My setup info just in case:
Main display: 2560x1080@75hz connected with DP 1.2
Secondary: 1600x900@60hz connected with hdmi to dvi adapter (recognized as hdmi)
GPU: 1080
Wayland
Kernel: linux-zen 6.7.4 (regular kernel shows the same behavior)
If I can provide any more info, please let me know and I will gladly help. At the moment this issue is something I cannot deal with or live with, so I’m gonna have to rollback to 535 again.
On 535 everything is good.
Hi @amrits, thank you so much for your reply and acknowledgement of the issue. I would just like to ask, why did this issue never present itself for most people before 545 and 550? From what I am reading, it seems this has always been an issue, but, me and many others never experienced it until these latest driver releases.
Another thing - whatever made it like this should NEVER have been pushed to release drivers. Whatever you changed to cause this issue should not have stuck between multiple driver revisions, and should’ve been left until these pull requests were merged. I understand you said that the fixes will be approved relatively soon, but we have no idea when that is. People have waited months at this point for a working driver.
I will be sticking to version 535 drivers until this is all sorted out. Hopefully everything is resolved quickly now.
Bug with glamor on XWayland also affect driver 535, and it resolved with NVIDIA explicit-sync patches.
Bug from this topic not reproduced with driver 535, but reproduced with 545 and 550. This bug also affects on native Wayland windows too (e.g. any electron 28 window).
The 545 driver release included some performance optimizations to the presentation pipeline with Xwayland. Unfortunately these may cause some systems or applications to start exhibiting corruption due to a lack of implicit synchronization even if they didn’t with earlier drivers. The underlying issue has always been present, though. There’s just some degree of randomness in whether it actually causes visible symptoms. Eventually a future driver release, combined with this patch set, will solve the problem.
So I guess for now, stick with 535 until explicit sync comes out…
Just adding my 2 cents: Anything above 535 gives me bad flickering/glitching similar to FrostyCoolSlug’s video. This also happens on VLC with hardware decoding and electron apps like Ferdium. I tried the explicit sync patch but had noticeably increased input latency when gaming which I couldn’t stand.
Today though as a workaround to make it bearable I started forcing as much as possible to use Wayland. For CS2 I changed SDL_VIDEO_DRIVER in cs2.sh to wayland, added ELECTRON_OZONE_PLATFORM_HINT=wayland to electron apps, and installed VLC 4.0.0. All these now work glitch free on 550.54.14. Can’t wait for an actual fix.
I’ve personally tested running some games using a build of wine that includes wayland support and it avoided any issue with flickering and seemed to have smooth performance.
There may be two solutions to the flickering issue in the future:
Explicit sync being included in XWayland for which we’re still waiting on this PR.
Running games using the wayland wine driver which doesn’t use XWayland at all
As of today’s date neither solution is ready yet so I suppose it’s a matter of waiting until one of the two solutions is implemented
I have NVIDIA RTX 2070 Super. I see a lot of graphical glitches in Linux Wayland. I don’t see them when I use AMD Graphics or Intel Graphics. Nvidia, will you fix critical Wayland bugs or I should use AMD instead?
Make sure that you have the latest xorgproto/wayland-protocols/xwayland as only they have the explicit sync merged in as well as nvidia driver 555 beta, otherwise the issues will still be present.
Thank you for your reply. I will wait for the official release of 555. I hope Electron apps won’t have black context menu under Wayland using 555 driver.
VS Code, Postman and maybe Slack. Several days ago, I tested Nvidia driver 545 on Fedora. The issue was present there. I see black context menu only when I use Wayland session.
