I run proprietary Nvidia drivers as well and Wayland runs so much better than Xorg now that I’m permanently coming over to Wayland. I’m extremely happy rn with Wayland

  • bulwark@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    6 months ago

    Not gonna lie, I specifically bought an AMD GPU laptop so I could run a Wayland WM. After trying and failing with my old nvidia optane razor laptop I gave up on Nvidia. I still use it on my desktop tho. It’s so much smoother than X-11.

    • Pasta Dental@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      6 months ago

      It should be noted that for some reason, people in Linux communities seem to never watch hardware accelerated video content, because AMD 6000 and 7000 have HUGE issues regarding video decoding on Linux, Im talking full system crash or full system freezes after 30 minutes of watching videos on youtube (and thats without mentionning the video freezing for a few seconds with the audio still going, and then catching up, and refreezing a few seconds later). It caused me to install Chrome which does not have hardware acceleration yet to watch youtube if I wanted to have an uptime of more than 1.5 days.

      These issues have only been reported on AMD’s iGPUs though, so I think dedicated graphics cards should be fine. But anyways, for this reason alone, I would just recommend Intel chips for most users, especially now with the new Intel Gen 1 Ultra or whatever its called, the GPU is basically on-par with AMD and the CPU is very close as well.

      • ruabmbua@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        Hm weird. Running 6000 series igpu with hw decoding on, no issues.

        On desktop 7000 series dGpu, also no issues.

        There were some Frame drops in the past, but current kernel + Mesa has no issues for me.

        • Pasta Dental@sh.itjust.works
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          I am monitoring this issue mainly, and I saw recently they seemed to have a fix, but I am not really interested in patching my drivers because its my daily driver computer

          • Kevin@lemmy.ca
            link
            fedilink
            arrow-up
            0
            ·
            6 months ago

            From what I understand, the updated firmware image has passed all the tests and will be included in an upcoming release. My system has been rock solid for a few weeks now with it running, but if you aren’t up to dropping the blob in yourself it sounds like you’ll have it officially soon (assuming you run a distro that keeps those up to date).

  • jj4211@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    I keep trying Wayland and an in the middle of an attempt. I use fedora maniacally updated, Nvidia, and plasma shell. I’m about to abort again:

    -even configured to directly use Wayland, I see chrome based browsers glitch out on occasion, and when it starts glitching it just keeps on glitching

    -plasma panel stops updating multiple times a day, staying frozen including the clock

    -sometimes kwin starts, but plasmashell has to run manually, and per above has to be restarted on occasion

    -occasionally it just forgets what the monitor resolution is supposed to be and reverts to 1024x768

    -the blur translucency effect glitches around mouse cursor

    -immersedvr doesn’t support Wayland

    On the flip side, xorg problems are: -occasionally kwin can’t grab keyboard for some effects until restarted. This is a well documented bug butt other than it being xorg specific, doesn’t seem to be figured out.

    -some things tear in ugly ways, but not nearly as bad as the chrome glitch under Wayland.

    Maybe kwin isn’t a great Wayland compositor, maybe Nvidia drivers are still not up to snuff. Ultimately, it’s not viable for me. Further kwin is a huge factor for “why Linux desktop” for me, gnome shell is more limited even than Windows for my workflows.

    • merthyr1831@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Definitely think NVidia has got some ways to go on improving Wayland drivers. AMD has its share of issues but they’re a lot less obtrusive than what you’re describing

  • Holzkohlen@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    I can recommend a hybrid setup. That works well with Wayland as long as you set that one kernel parameter. Otherwise the two GPUs won’t be in sync and you get glitches when using the dedicated one.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    6 months ago

    Have fun with your 10% FPS drop, undocumented glitches, and zero support for 45 degree tilted monitors lol

    • Crashumbc@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      45 degree tilted monitors lol

      WTH? That’s a “thing” who or why would you even do that?

        • drathvedro@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          6 months ago

          Somewhere in Xorg, there exists a patch that fixes vertical sync so that glxgears could be displayed by printing out every individual frame. And honestly, that’s one of the main reasons to love linux ecosystem - because things are not done out of necessity, it facilitates the development of most flexible software with least assumptions and most freedom in how you can use it.

          • Shareni@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            6 months ago

            So this here I think is the best monitor orientation for software development. It provides the longest line lengths and no longer need to worry about that pesky 80 column limit.

            ultra wide monitor

            I’m scared

    • Ooops@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      That’s because the drivers are bullshit but not the problem in general. They work well for some very specific cards, not at all for other and in general it’s just random hit or miss.

      And then, to make it more fun, not all wayland compositors are born equal either.

      • FierroGamer@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        Any recommendations? Or knowledge of which cards work best with it? I’m thinking on trying it out again, never tried it on my 3070

        • Nyanix@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          Not to be flippant about it, but I just recommend trying it and seeing how it works for you. You can have both Xorg and Wayland installed, you just change out which one you’re using at the login window

  • Slyme@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    I’ve been using NVIDIA under Wayland for a few months now and it’s been… alright? No major issues on v535 (however v545 is buggy as hell for me, Minecraft would show a black screen whenever too many pixels were updated – needless to say, I downgraded).

    However, I’d still love to swap to an AMD GPU because of better Linux support, maybe keep my current GPU for passthrough.

      • Slyme@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        Tried 550, didn’t fix anything. The game window still blinks black.

  • merthyr1831@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    my ONLY gripe with wayland rn is the lack of global hotkey support, which currently breaks Discord/other’s “push to talk” feature unless you install a webserver to control your mic via your compositor’s hotkey system and HTML requests 😭

    I suppose push to talk can and should be owned by the desktop and not any particular app, but Id like an interim protocol until then

      • merthyr1831@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        They must implement their own workaround/protocol for this. On KDE 5 it’s still missing. Hopefully they have something cookin for KDE 6 but since it wouldnt be standards-compliant there’s no guarantee

  • haui@lemmy.giftedmc.com
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    I‘m running kde on debian stable. I‘ll let you know when my branch is ready. Until then its X11 all the way. Wayland wont even let me log in.

        • Pantherina@feddit.de
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          Ok thats not that new, I think Fedora is on 5.27.10 and its pretty perfect. I know many bugs that will only be fixed in Plasma 6 5 though (which is probably more stable than 5.27 as its to much tested).

          Excited for Fedora 40!

                • Pantherina@feddit.de
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  6 months ago

                  It lacks fractional scaling which is totally ironic because their gestures mainly make sense on modern touchpads, which are only on laptops. These laptops mostly have 14in HiDPI displays and you need 125% scaling for them, but in GNOME this doesnt exist at all and if you force enable it its blurry.

                  And something else like dynamic refresh rates, tearing or something that I never noticed.

  • SorryQuick@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    Are you using the new 550 drivers? They are supposed to include lots of wayland related fixes. I might try it myself once they update it on the arch repo. Last time I tried, my 2060 and 525 drivers just did not go with wayland, at all.

    • nexussapphire@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      545 right now and the only issues I have is kde panels crashing and horrible screen tearing in games because of my gsync only monitor. I xorg has a toggle for gsync but can’t work around that damn monitor on Wayland for some reason.

  • SquishyPandaDev@yiffit.net
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    Bought a new AMD GPU to run Wayland. Here’s to NVIDIA getting their shit together or, more likely, going bankrupt.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 months ago

      That’s hilarious. 😄 Linux users dropping Nvidia en-masse would be like a half a percent blip on their desktop market share. Probably couldn’t even tell if it’s a rounding error.

      This is a company that’s speculated to drop the desktop consumer market altogether at some point. They make so much money from other industries it’s obscene. I suspect they only keep the gaming and desktop crowd around for the drama and the publicity. They don’t really give a shit anymore.

      Which would be sad in a way because Linux gaming was built on Nvidia. For the longest time it was the one manufacturer you could count on to be there and deliver decent, accelerated Linux drivers consistently.

      • andrew@lemmy.stuart.fun
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        Well to be fair, most AI workloads are on Linux and that’s a huge fraction of their sales. But desktop Linux, yeah, not going to notice at all.

    • Pyro@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      Consider all the gamers with more money than sense buying 4090s for the price of cars and, more importantly, many companies buying datacenter cards for their next generative AI project (not that I think many of them will last).

      I don’t see Nvidia running out of money any time soon.

  • Reygle@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    Yeah Wayland rules- problem for me is I’m hopelessly addicted to Synergy for mouse and keyboard sharing, and it doesn’t work on Wayland yet>< I’m 100% team red and my fancy new display won’t do 4k@144hz on X11 so that’s frustrating. 144 and no Synergy or 1440p 144hz and Synergy

    • Kevin@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Input Leap is a Synergy fork with mostly working compatibility for Gnome Wayland, and Waynergy works well as a client on sway (and possibly kde?)

    • bnason@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      Try rkvm. It even works outside of X/Wayland. The only downside is the lack of copy/paste which I’m still trying to find a solution to.

      • Reygle@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        Quite interesting- found it on github, so switching appears to be keybound with rkvm, huh?

        • bnason@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          Yep, I use the key bind, Ctrl+Alt+s, to switch and I can use my mouse and keyboard on the other computer.

          • Reygle@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            6 months ago

            Alot less convenient than synergy but do-able. I may take the time to try to understand it in the future, appreciente the info.
            I tweeted @synergy and they say a wayland-compatible version is due later this year, so there’s a good chance I’ll just wait and be lazy.