linux-drm-syncobj-v1: new protocol (!90) · Merge requests · wayland / wayland-protocols · GitLab
gitlab.freedesktop.org
This is a new Linux explicit synchronization protocol based on DRM synchronization objects 1.

Since nvidia drivers do not properly implement implicit sync, this protocol not existing is the root cause of flickering with nvidia graphics on Wayland. This MR being merged means that Wayland might finally be usable with nvidia graphics with the next driver release.

EDIT: Nvidia dev posted that support is planned in the 555 driver, with beta release planned for May 15: https://github.com/NVIDIA/egl-wayland/pull/104#issuecomment-2010292221

  • pr06lefs@lemmy.ml
    211·
    8 months ago

    Questions from someone still on xmonad/x11, with 3 computers that have nvidia cards:

    Do all nvidia cards have trouble in wayland currently, or is it just some subset?

    Is it really unususable, or just really annoyingly flickery?

    Would my card be usable now (without this merge) if I was using the nouveau driver?

    Once this is merged, will all nvidia cards work in wayland? Or do we not really know yet.

    • SuperIce@lemmy.worldEnglish
      37·
      8 months ago

      The Nvidia driver on Wayland has been decent for a couple of years and stabilized a lot over the past ~6 months. The flickering issue was specific to XWayland. Normal Wayland apps don’t have flickering problems (not quite sure why tbh), but XWayland apps would often rapidly flicker between 2 frames since it only supported implicit sync, which confused the Nvidia driver, which only supports explicit sync. Now with a Wayland protocol for explicit sync, XWayland can be updated to support it and resolve the flickering there.

    • unique_hempOP
      21·
      8 months ago

      Nouveau should have already been fine, this should fix the proprietary driver’s issues. AFAIK this is a core issue of the proprietary driver, so should affect all cards.

      I tried Wayland on my 16xx series GPU, Electron apps were only annoying, but games were unplayable. The desktop itself and Wayland native apps worked fine, though.

    • Lojcs@lemm.ee
      5·
      8 months ago

      In addition to what others said a recent Nvidia driver update also added a workaround to reduce out of order frames without explicit sync. Ime it just made it so that resizing a flickering window makes it stop.

    • Sina@beehaw.org
      4·
      8 months ago

      It’s not really card related, but rather it just comes up sometimes in niche circumstances. I only had this on my second monitor and then it went away with an nvidia driver update. (since then i moved to amd)

    • blipblip [he/him, they/them]@hexbear.netEnglish
      3·
      8 months ago

      I only have experience with my current GPU (3070 ti) and only in Hyprland, but the only flickering I have is in steam windows, everything else works flawlessly on 535 driver. Still excited that it may be fixed soon!

      • dimath@ttrpg.network
        1·
        8 months ago

        On 3060 mobile, there is flickering in steam and chrome, but it’s usable. In chrome I believe it can be fixed by disabling hardware acceleration.

    • matcha_addict@lemy.lol
      2·
      8 months ago

      For what it’s worth, I have only minor issues on wayland with nvidia, and all were fixable by changing some configuration option or something.

      Maybe my demands aren’t too heavy, but I do play games. I also use gentoo which makes fixing things easier.

      • unique_hempOP
        2·
        8 months ago

        Maybe if your games are Wayland native or you’re still running the 535 driver? I saw fbdev=1 as a workaround, but that made things very jello-y.

        • NoisyFlake@lemm.ee
          2·
          8 months ago

          I think 535 is the only option for Wayland gaming right now, everything else is a flickery mess.