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

  • JoshCodes@programming.dev
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    1 year 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.ca
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

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

    • UkaszGra@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

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

    • Pasta Dental
      link
      fedilink
      arrow-up
      3
      ·
      1 year 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)

    • HouseWolf@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year 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.

      • Lojcs@lemm.ee
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        edit-2
        1 year ago

        Backend hackery? You just install it and it works

        • HouseWolf@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          1 year 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.

      • tostiman
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Kubuntu 23.04 comes with wayland preinstalled and it works with my Nvidia card

        • HouseWolf@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          1 year 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.

      • vd1n@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

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

    • taaz@biglemmowski.winOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year 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

  • Hubi@feddit.de
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    1 year ago

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

  • taaz@biglemmowski.winOP
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year 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
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year 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]@whiskers.bim.boats
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year 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.

  • vd1n@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Are you sure your are running nvidias drivers? Not the generic ones?