Title, I can’t switch to Wayland because of nVidia (and because I love Awesome WM).

  • JoshCodes
    11•2 years ago

    X11 doesn’t limit it, but you will want to enable “Force composition pipeline” to prevent screen tearing. nvidia and Wayland work together btw. It’s not a match made in heaven but they do work.

    • @gianni@lemmy.caEnglish
      5•2 years ago

      It’s simply not worth it. I used Wayland for a couple years but ended up switching back to X11 on nVidia hardware.

    • Pasta Dental
      3•2 years ago

      It does work, but its just really glitchy and unstable. Idk how many times Ive woke my pc from sleep and my cursor was just a giant square of gibberish pixels. Or the fact that night light still does not work on GNOME + Wayland because the proprietary driver does not support GAMMA_LUT (this issue has been open for years btw)

    • @UkaszGra@lemmy.world
      3•2 years ago

      I think forcing pipeline enables vsync or something because there is noticeable input delay when playing on 60hz screen.

    • @taaz@biglemmowski.winOPEnglish
      2•2 years ago

      1. I love my AwesomeWM setup. Unless someone completely rewrites it, it will never work with Wayland (as far as I have read the gh issues).

      2. I need this PC to “just work” and I have seen a lot of problems with Wayland and Nvidia drivers, top-quality gaming is a secondary on this one so X11 has been the choice.
        Though I am aware stuff is getting better, should probably try it anyway

    • @HouseWolf@lemmy.ml
      2•2 years ago

      When I tried Wayland on Gnome using my RTX3080 it either wouldn’t load into desktop or if I did it would lead to a bunch of visual glitches.

      Haven’t tried it through KDE yet tho as it requires some backend hackery to even allow you enable Wayland with an Nvidia card.

      Edit: So some people have been able to get Wayland working on Nvidia fine so it’s worth trying out yourself, Tho I’ve personally not had any luck.

        • @HouseWolf@lemmy.ml
          3•2 years ago

          Alright so after seeing your comment I decided to give it another try.

          I’m running Plasma 5.27.7 which is what came when I installed when I grabbed EndeavourOS. But it doesn’t come with the Wayland session included so I grabbed plasma-wayland-session from the AUR, And same issue as last time I can’t launch it from the login screen.

          I know people have gotten it working fine but on my hardware for whatever reason I’ve had little luck.

      • @vd1n@lemmy.ml
        1•2 years ago

        I mostly use fedora. I never had an issue with my 1080 or laptops 1060… But those are old now…

        • @HouseWolf@lemmy.ml
          2•2 years ago

          Yeah Wayland support apparently doesn’t come shipped with the KDE install on EndeavourOS, Last time to tried to get it running was on an older version of Ubuntu a few months back.

          I’ll install it and try it out now tho thanks.

  • @Hubi@feddit.de
    5•2 years ago

    No. I have a 144Hz monitor and a 60Hz monitor and both work at their maximum frame rate.

  • @taaz@biglemmowski.winOPEnglish
    4•2 years ago

    Thank you everyone, was rather sure that variable refresh rates of different monitors were a hard problem for X11.

    So, in nvidia-settings I made my 120Hz one the primary and set the refresh rate from auto to the highest for both monitors (120, 60)

    The only difference I noticed was that easyeffects window is now completely unreadable, somehow the text and frames bleeds out/blurs and only gets sharp when hovered with mouse but still buggy. Force-compositon-pipeline did not help there.
    Will have to diagnose tomorrow.

  • @priapus@sh.itjust.worksEnglish
    3•2 years ago

    No, you can force it to run both monitors at the highest refresh rate, but this can cause tearing on the lower refresh rate monitors. From what I remember, you can choose the monitor to sync to in the Nvidia X settings.

  • lckdscl [they/them]English
    3•2 years ago

    Edit: here’s the relevant commit that addresses this (I think).

    No. I can’t remember what the default behaviour is now. But that isn’t true anymore. Source: I’m currently on X11 and my 144 Hz works next to my 75 Hz one with nvidia.