Arch Wayland Gpu?

What's the current state of GPUs for Wayland? Last time I was running a Arch as a daily driver the general consensus was to get an AMD GPU, since nouveau wasn't quite up to snuff, and Nvidia's proprietary drivers didn't play nice. When I tried an AMD GPU though it was kind of ass, even on Windows.

Has anything changed with the state of GPU/driver recommendations? I want to get back into using linux for my desktop, but when my day to day is riddled with small graphical glitches and tearing, it's just not worth it.

Workload is just normal desktop crap, videos, browsing, gaming. 4k 144hz primary monitor, 1080p 144hz secondary for reference.

A Conspiracy Theorist Is Talking Shirt $21.68

POSIWID: The Purpose Of A System Is What It Does Shirt $21.68

A Conspiracy Theorist Is Talking Shirt $21.68

  1. 4 weeks ago
    Anonymous

    >Nvidia
    Doesn't work
    >AMD/Intel
    "Works" if you think random flickering, apps only being displayed as a black screen and your system crashing if you move the mouse when the system is under heavy load as working. Even shit like VScode is nearly unusable under Wayland (2s delay on keyboard typing to appearing on a screen). Just look at the KDE 6 rollout to see the utter state of wayland.
    >inb4 muh krashde
    Kde has the best wayland compositor so it's only worse elsewhere.

    • 4 weeks ago
      Anonymous

      >it's only worse elsewhere.
      no complaints here
      >t. wlroots user

      • 4 weeks ago
        Anonymous

        >Proposal: Don't send events to blocked clients
        >Sorry, but no, we don't workaround bugs in wlroots.
        >closed wontfix
        Literally worse than the wayland devs, at least they acknowledged that there's a problem that needs to be fixed, even if they perpetually drag their heels on it.

    • 4 weeks ago
      Anonymous

      Nvidia works with Wayland if you stick to corporate stable distributions like Ubuntu LTS and RHEL.
      AMD works, for a very loose definition of works, if you don't buy a 7000 series card.

      So what's the goto for the arch or fedoras of the world? Proprietary drivers and no wayland? I'm not a VScode user, but if something as heavily used by devs as that can't even hold its weight, then what's the point.

      I've got no problem getting into the weeds with configs and building different things from source to try out open source projects, different DEs, whatever, but there's got to be some whitelist of hardware/drivers by now, surely?

      • 4 weeks ago
        Anonymous

        >I've got no problem getting into the weeds with configs
        Arch, artix (arch without systemd) or nix. If you use X I recommend awesomewm, it's a framework to build your own environment with a nice lua API. Use the git master though (awesome-git or w/e on Nix), the stable release is very old and there are a lot of changes in upstream coming, your config will break on the next stable release if you use current stable.

        I have an RX 7600, I tried Hyprland for a while and it just didn't cut it, the animations are fancy but any time an application lags for even a second and you move your mouse it's a crash. There aren't any practical benefits to Wayland.

    • 4 weeks ago
      Anonymous

      Nvidia works with Wayland if you stick to corporate stable distributions like Ubuntu LTS and RHEL.
      AMD works, for a very loose definition of works, if you don't buy a 7000 series card.

      >nvidiots seething
      sent from my sapphire pulse 7800xt powered desktop running hyprland

    • 4 weeks ago
      Anonymous

      Wayland theoretically supports explicit sync now. You're going to need to wait a few months for support through the stack.
      >GPU/driver recommendations
      Nvidia proprietary on Xorg for now. The open sores userland driver maintainer trooned out and red hat is currently NIHing nouveau with a new rust driver called nova, where code quality is obviously going to be secondary to ensuring linus can't chuck rust out of the kernel like he did c++.

      kwin is literally the worst part of KDE and always has been. With regards to wayland they just lift other people's protocols and call it their own, like how the "KDE" hdr/color protocol was written by josh ashton. Really it's kind of amazing how much of the plasma 6 hype is based on lies.

      Nvidia works with Wayland if you stick to corporate stable distributions like Ubuntu LTS and RHEL.
      AMD works, for a very loose definition of works, if you don't buy a 7000 series card.

      AMD works if you don't mind half broken VRR and reclocking.

      • 4 weeks ago
        Anonymous

        >last year
        Danzer is a big time RH gatekeeper for mesa, xorg and wayland. Something tells me Nvidia paid a bribe to get explicit sync merged like valve did for tearing.

        • 4 weeks ago
          Anonymous

          >like valve did for tearing

          qrd?

      • 4 weeks ago
        Anonymous

        >Nvidia proprietary on Xorg for now.
        More like the next 5 years. Wayland still has major problems and Plasma defaulting to it really showed just how bad the situation is. You have horrible compatibility issues through xwayland still (sure did love spending 40 minutes figuring out why drag and drop in Ardour was completely fricked), performance in some games is unacceptably bad and a large number of applications just fricking tank. It's very literally only usable if you're in the terminal 24/7

        • 4 weeks ago
          Anonymous

          >Wayland still has major problems and Plasma defaulting to it really showed just how bad the situation is.
          I wasn't surprised in the least. I run even GNOME on X too because, despite Wayland having been the default on it for even longer, it STILL has bullshit issues like mouse cursor stuttering on high load. It's mind boggling that GNOME on X is a better experience than GNOME on Wayland despite having received far less development during the past ~8 years.

          If anyting, another major DE defaulting on Wayland despite still being worse than X will only increase complaints and give more visibility to this situation.

          No, I'm not on Nvidia.

      • 4 weeks ago
        Anonymous

        >AMD works if you don't mind half broken VRR and reclocking.
        idk what you mean, fedora 40 with 6900xt here, vrr works and both gpu and memory clocks work fine as well

        • 4 weeks ago
          Anonymous

          >vrr works and both gpu and memory clocks work fine as well
          That's literally not true. The GPU reclocks into the lowest state constantly unless you use the 3D_FULL_SCREEN power profile. Memory clocks get set to max on essentially every EDID that specifies more 1080/60hz. Monitors return to their base refresh rate for a couple of miliseconds during every VRRed frame. All of those issues date back to RDNA1 and are seen in RDNA2 and RDNA3.
          t. actual 6900xt owner that lurked the DRM tracker religiously
          https://gitlab.freedesktop.org/drm/amd/-/issues

          >like valve did for tearing

          qrd?

          it's widely believed that the tearing protocol getting merged involved a "donation" to collabora since wayland upstream was absolutely, fanatically against allowing screen tearing/disabling the mandatory vsync because
          >every frame is perfect

          • 4 weeks ago
            Anonymous

            Valve told them to stop being shitheads

          • 4 weeks ago
            Anonymous

            >The GPU reclocks into the lowest state constantly unless you use the 3D_FULL_SCREEN power profile.
            i haven't encountered any issues with that
            >Memory clocks get set to max on essentially every EDID that specifies more 1080/60hz.
            see pic rel, fedora 40, i know it used to be an issue, but some recent kernel fixed it
            >Monitors return to their base refresh rate for a couple of miliseconds during every VRRed frame.
            i've encountered that with hdr, it's some issue with compositing taking too long, maybe try a newer kernel or de?
            it's still the way my a770 behaves with vrr, but it works fine on rdna 2, there's even a fix for hdr

        • 4 weeks ago
          Anonymous

          >vrr works and both gpu and memory clocks work fine as well
          That's literally not true. The GPU reclocks into the lowest state constantly unless you use the 3D_FULL_SCREEN power profile. Memory clocks get set to max on essentially every EDID that specifies more 1080/60hz. Monitors return to their base refresh rate for a couple of miliseconds during every VRRed frame. All of those issues date back to RDNA1 and are seen in RDNA2 and RDNA3.
          t. actual 6900xt owner that lurked the DRM tracker religiously
          https://gitlab.freedesktop.org/drm/amd/-/issues
          [...]
          it's widely believed that the tearing protocol getting merged involved a "donation" to collabora since wayland upstream was absolutely, fanatically against allowing screen tearing/disabling the mandatory vsync because
          >every frame is perfect

          >VRR is broken
          https://gitlab.freedesktop.org/drm/amd/-/issues/2066
          >MEMCLK stuck at max
          https://gitlab.freedesktop.org/drm/amd/-/issues/1403
          >reclocking is too aggressive
          https://gitlab.freedesktop.org/drm/amd/-/issues/1500
          Seriously saying a 6900xt works fine is moronic when the 6000 series has the most bugs. Even though mine works pretty well I'm not buying AMD again after seeing how well they've "supported" RDNA cards.

          Valve told them to stop being shitheads

          So did hundreds of people. I seriously doubt getting bullied on the gitlab made the difference. The wayland people went out of their way to design the protocol around mandatory vsync+implicit sync when they were obsolete by the time of the first stable wayland release in 2013. Stable is being really generous since you couldn't do much more than run a terminal in weston back then.

      • 4 weeks ago
        Anonymous

        >Wayland theoretically
        Yes.
        >Wayland practically
        No.

    • 4 weeks ago
      Anonymous

      >KDE 6
      Jesus, KDE 6 has to be the worst KDE release ever and a true testament to how shit Wayland really is. Even many die hard KDE fans judged it quite harshly.

  2. 4 weeks ago
    Anonymous

    Nvidia works with Wayland if you stick to corporate stable distributions like Ubuntu LTS and RHEL.
    AMD works, for a very loose definition of works, if you don't buy a 7000 series card.

  3. 4 weeks ago
    Anonymous

    I use built-in intel graphics with arch and it just works

  4. 4 weeks ago
    Anonymous

    Using gayland on KDE 5 with RX 580 since specific software I need performs better on it, works fine just like x11
    Never used Nvidia so I have no idea

    • 4 weeks ago
      Anonymous

      >since specific software I need performs better on it
      Like what?

      • 4 weeks ago
        Anonymous

        Development builds of Inkscape, better performance but they hit some GTK 3 bugs causing it to freak out on X11 with GUI frequently not re-rendering last time I've checked

  5. 4 weeks ago
    Anonymous

    Nvidia rtx 3060 works fine for me in wayland

  6. 4 weeks ago
    Anonymous

    >Amd
    Almost
    >Nvidia
    Extra steps and still some issues
    >Intel
    Perfect

  7. 4 weeks ago
    Anonymous

    >What's the current state of GPUs for Wayland?
    None of them work as well as it does with X11.

  8. 4 weeks ago
    Anonymous

    On CachyOS /w Hyprland on Nvidia - no issues at all and runs like a dream.

    Skill issue in responses.

  9. 4 weeks ago
    Anonymous

    I switched to gayland because plasma6 glitched my panel in X11

  10. 4 weeks ago
    Anonymous

    [...]

    https://i.imgur.com/iWn69An.png

    What's the current state of GPUs for Wayland? Last time I was running a Arch as a daily driver the general consensus was to get an AMD GPU, since nouveau wasn't quite up to snuff, and Nvidia's proprietary drivers didn't play nice. When I tried an AMD GPU though it was kind of ass, even on Windows.

    Has anything changed with the state of GPU/driver recommendations? I want to get back into using linux for my desktop, but when my day to day is riddled with small graphical glitches and tearing, it's just not worth it.

    Workload is just normal desktop crap, videos, browsing, gaming. 4k 144hz primary monitor, 1080p 144hz secondary for reference.

    [...]

    [...]

    .

  11. 4 weeks ago
    Anonymous

    Nvidia + Wayland work fine, but I think it depends on your card. My main workstation is rock solid with a 4090, but I also have an older machine with a 980 and it works too.

    However, I'm not on a shit distro like Arch. I use Fedora Kinoite, so stability is kind of a given. YMMV

  12. 4 weeks ago
    Anonymous

    Been running Arch with KDE Wayland on my 6700XT for about 2.5 years now and haven't had many issues to begin with. From what I've seen KDE's compositor is more feature complete than GNOME's at the moment.

  13. 4 weeks ago
    Anonymous

    >wayland shill pulling double duty for AMD
    Not getting a (you). Anons can look at the issue tracker for themselves.

Your email address will not be published. Required fields are marked *