How is Wayland with NVIDIA now?

[-]

CallMeNepNep@reddit

I have a 3080 and the proprietary drivers and it works perfectly in most cases, the only things I doesn't are when screen sharing in discord and using my drawing tablet, other than that it just works.

[-]

SiliwolfTheCoder@reddit (OP)

Neat. I found screen sharing with Discord did not work anyway with X11, though I found a client called Equibop that allows it

[-]

WojakWhoAreYou@reddit

there's also vesktop that allows screen sharing on wayland

[-]

seventhbrokage@reddit

This is what I came here to say. I was having the worst time trying to get it to work, then someone here recommended vesktop and it magically solved all my issues. It even has a plugin that you can enable right in the settings to get audio control over 100% like in regular desktop discord.

[-]

BidEnvironmental4301@reddit

What it's called?

[-]

seventhbrokage@reddit

Sorry to leave you hanging like that. If you go into the settings and scroll down to the plugins section, it's all the way at the bottom. Called VolumeBooster

[-]

PacketAuditor@reddit

Vesktop

[-]

spupy@reddit

Have you tried Vesktop? Sharing on Wayland works well, including sound.

[-]

CallMeNepNep@reddit

just tried vencord and the only thing I get is three dots with a black background. So you ah same as normal discord

[-]

gmes78@reddit

Those two things are likely unrelated to the Nvidia drivers.

[-]

CallMeNepNep@reddit

yes the tablet is a known Wayland bug in the xppen drivers, and given that that discord works just fin eon x11 it seems, like that one is too

[-]

Dramatic-Swimming463@reddit

I use hyperland on arch in combination with an rtx 4070 for quite some time now it's going very well. I had some issues but these got them self sorted out quickly...

[-]

Ok-386@reddit

Generally ok but X session still feels more polished, smoother and snapper and the system can actually wake up from sleeping. Unless you have a pragmatic reason to use Wayland, I would stick with X for now.

[-]

C0rn3j@reddit

smoother and the system can actually wake up from sleep

It's definitely not smoother, you can objectively test that by seeing how glaringly bad the latency is on high refresh rate screens.

I also don't understand what you mean by waking up from sleep, suspend works fine?

[-]

BulletDust@reddit

X11 is smooth as room temp butter here, while running NVIDIA under Wayland with GSP disabled still results in a max of 80% GPU utilisation in games. Running X11, my RTX 2070S hits 100% utilisation in games no problem.

Furthermore, fractional scaling is still implemented better under X11.

[-]

C0rn3j@reddit

At what framerate?

Try comparing X with Windows if it's actually anything decently over 60Hz, last time I checked it was a night and day difference, and Wayland runs as expected.

while running NVIDIA under Wayland with GSP disabled still results in a max of 80% GPU utilisation in games

You might be able to enable GSP again on latest driver, and if you still run into issues there there are patches you can try - https://github.com/NVIDIA/open-gpu-kernel-modules/pull/658

[-]

BulletDust@reddit

You might be able to enable GSP again on latest driver, and if you still run into issues there there are patches you can try - https://github.com/NVIDIA/open-gpu-kernel-modules/pull/658

Tried that, under KDE it doesn't make a difference. GPU utilization in games maxes out at 80%, something that isn't a problem under X11.

I'm not adding patches, I'll wait until Wayland reaches feature parity with X11. Right now, considering my use case.

[-]

BidEnvironmental4301@reddit

Plasma is f*cked on Wayland, they have a lot of issues on Wayland

[-]

Enough-Meringue4745@reddit

Wayland is choppy as fuck for me. I even have a triple 4090 setup 😂

[-]

MeanEYE@reddit

I even have a triple 4090 setup

Therein lies your problem. It's not a Wayland issue, it's an nVidia issue. Wayland just uses kernel drivers. So if drivers are iffy or lack support, Wayland suffers as result and all the applications relying on it.

[-]

Enough-Meringue4745@reddit

X works perfectly

[-]

MeanEYE@reddit

With drivers made for X, tested and debugged over past decades. This is something not many people know, but display drivers use to sit in user space, as opposed to everything else. That's why getting root-less X server was a big achievement back in the day. And warnings about security in X are not without merit.

nVidia just recently started supporting Wayland properly. Which is why I said it's nVidia driver issue, not a protocol issue.

Intel did things right from the beginning, so their support for new display server was there from the beginning. AMD saw the opportunity and seized it. nVidia thought they could strong-arm developers once again, like they have a habit of doing. Luckily it backfired for them. With enough push from AMD, Valve going AMD route for their portable gaming system and enough pressure from elsewhere, they were forced to play game and all of us benefit from that.

[-]

Ok-386@reddit

This actually has some educational value, however it's still missing the point, unless you think this is like an argument for convincing people they should use Wayland instead of X? I get the PoV 'use Wayland to force/encourage Nvidia etc.' however at this point this isn't necessary any more (IMO). We are getting there, it will just take time. Further, we can't even know if it's going to be 'Wayland'. Wayland is probably going to be heavily patched, will change with time and it has its own issues. Neither the protocol perfect, nor the implementation are perfect, and these are two different things. One could theoretically have a perfect protocol (not sure but let's assume), but all implementation could suck.

No one here argues X is 'better', unless better meant better user exerience for most NVidia users. Engineering PoV is something else, but this isn't what this question is about.

[-]

MeanEYE@reddit

Am merely pointing out that hating on X or Wayland is misdirected. Hating on nVidia is the correct choice. Popular open source projects such as these two patch things rather fast. Issue has been with nVidia.

Just measuring end user experience for this reason is not a good metric since many of the big software/hardware manfuacturers have been caught rigging the scales.

Intel was caught purposely crippling performance on competitor CPUs.

nVidia with their GameWorks program helps developer optimize their games for free in which process they keep leaning heavily on tesselation, which is known to work worse on AMD devices. It's anti-competitive and ends up being worse for the end user.

[-]

Synthetic451@reddit

You may need to disable GSP firmware to get rid of the chop. There's a bug with it that decreases performance. See https://github.com/NVIDIA/open-gpu-kernel-modules/issues/538

[-]

is_this_temporary@reddit

You can't make categorical statements like that about someone else's system.

Wayland has all of the infrastructure and design decisions to be smoother and tear free, but hardware and hardware drivers have a lot of unpredictable quirks.

I believe the commenter about their own experience.

[-]

C0rn3j@reddit

You can't make categorical statements like that about someone else's system.

I absolutely can when X is by-design shit, and Wayland should run well by design.

If Wayland runs poorly, it's a bug and needs to be debugged and reported if it isn't already.

X will run poorly in any case.

[-]

Ok-386@reddit

That's not sound reasoning and you seem to lack the nuanse required... For quite a few things.

[-]

Flarebear_@reddit

Design does not matter in the real world. If your program doesn't deal well with failures that that's your programs fault

[-]

Synthetic451@reddit

Have you enabled NVreg_PreserveVideoMemoryAllocations and the associated systemd services? Not enabling those is the number 1 cause of issues with resume from sleep on Nvidia. https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend

[-]

Derpygoras@reddit

This is the type of stuff that gives Wayland the "not ready yet" label.

If a default Windows installation was b0rking unless you do Registry hacks and use beta drivers and whatever, how would you rate it?

[-]

nightblackdragon@reddit

This is not Wayland issue, you won't need to do these things on Intel or AMD hardware.

If a default Windows installation was b0rking unless you do Registry hacks and use beta drivers and whatever, how would you rate it?

Windows users don't blame Windows when some driver breaks something.

[-]

Synthetic451@reddit

To be fair this is more of an Nvidia issue than a Wayland issue. You don't need to do this with Intel and AMD. The sleep issue is just poor out of the box defaults on the part of the Nvidia driver, the GSP issue is just a bug that Nvidia needs to fix.

[-]

BidEnvironmental4301@reddit

OpenTabletDriver works flawlessly on wayland

[-]

PacketAuditor@reddit

good

[-]

Floturcocantsee@reddit

560 with Hyprland has been flawless for me, the only issues I had were when I had two NVIDIA gpus in my system and that was most likely a configuration error on my part (I just took the second GPU out).

[-]

79215185-1feb-44c6@reddit

Wayland on Nvidia with 555 or 560 is great but there are still Wayland issues that I found so frustrating that it was not worth using for me (XWayland Clipboard issues, xdg-desktop-portal issues).

[-]

C0rn3j@reddit

XWayland Clipboard issues

Out of curiosity, which apps do you use that still run on XWayland?

[-]

79215185-1feb-44c6@reddit

Games

[-]

C0rn3j@reddit

How often do you copypaste from games to other windows though?

[-]

79215185-1feb-44c6@reddit

I develop a tool for Star Trek Online where this is one of the main features (shares DPS run results in game) so daily.

[-]

C0rn3j@reddit

I see why that'd be a bit unbearable.

Have you reported a bug for it if there weren't one already?

I have the same issue on kwin with Android Studio, I'll see if I can do the same there, been ignoring it til now, though to be honest at this point I might just wait it out as AS is getting Wayland support soon™ and games don't bother me that much.

[-]

79215185-1feb-44c6@reddit

It's already been reported. I'm surprised more people don't talk about it.

[-]

C0rn3j@reddit

Could you link it?

[-]

79215185-1feb-44c6@reddit

Here's a recent one for Hyprland: https://github.com/hyprwm/Hyprland/issues/7684

Vaxry doesn't give a fuck if it doesn't move his product forward but he'll be the first to shit on other competing projects.

[-]

C0rn3j@reddit

Hmm, that's all Hyprland specific, was hoping it'd link to some generic problem that everyone suffers from.

Suppose I will have to open one for kwin since I can't sem to find one.

[-]

79215185-1feb-44c6@reddit

It is not hyprland specific. It affects everything EXCEPT for KDE.

I fucking hate KDE fanboys. Every single fucking time with their trash bloated DE.

[-]

C0rn3j@reddit

I literally said I have the same issue on Plasma, did you forget already?

The DE is Plasma by the way, KDE is the group.

[-]

susiussjs@reddit

For me I know vscode and almost all my games use xorg, im not sure about discord, telegram, spotify, or steam, google earth, drawio, or libreoffice.

Is there a way to check or find out?

[-]

C0rn3j@reddit

VSC runs on Wayland just fine.

How often do you copy paste in your games between windows?

Is there a way to check or find out?

depends on the compositor, on Plasma you can just open kwin debug and see what runs on X.

Other than Steam+Games, I doubt you'll find much. Hopefully that one will be ironed out in a year or so.

[-]

susiussjs@reddit

vscode has to be made to run on wayland, and that breaks it on gnome. But using kwin I found that basically everything proprietary use x11. google earth, spotify, everything jetbrains, signal, postman, etc.

[-]

C0rn3j@reddit

vscode has to be made to run on wayland, and that breaks it on gnome

Hmm, actually no it doesn't, file a bug report if you're on an up to date version, but you're likely just using outdated software.

[-]

susiussjs@reddit

Gnome doesn't have server side decorations, and there's a lot of other software with no wayland anyway.

[-]

nightblackdragon@reddit

Electron don't need server side decorations as Chromium supports client side decorations.

[-]

susiussjs@reddit

vscode didn't for me. ig there's another flag for that too, but I didn't know back then and don't feel like changing flags and figuring out how electron flags work anymore.

[-]

thomas_m_k@reddit

VS Code runs fine for me under GNOME Wayland with

code --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations &

and

{
    "keyboard.dispatch": "keyCode"
}

in the settings.json.

[-]

susiussjs@reddit

Doesn't it need server side decorations that gnome doesn't have?

[-]

thomas_m_k@reddit

The second flag tells VS Code to have client-side decorations, which is what gnome expects.

[-]

6e1a08c8047143c6869@reddit

vscode has to be made to run on wayland, and that breaks it on gnome. But using kwin I found that basically everything proprietary like google earth, spotify, everything jetbrains, postman, etc use x11.

Electron applications like vscode and spotify just work if you start them with --ozone-platform-hint=wayland and --enable-features=WaylandWindowDecorations. They only use X by default because some people still have issues with wayland.

[-]

C0rn3j@reddit

I don't think the latter parameter is needed anymore?

[-]

6e1a08c8047143c6869@reddit

That's possible. I just read that it was needed on GNOME (which I don't use myself) to fix missing top bars and included it so people don't have any issue.

[-]

nightblackdragon@reddit

If you use KDE then I believe they did some fixes related to Xwayland clipboard recently.

[-]

Branan@reddit

Which DE were you using?

[-]

79215185-1feb-44c6@reddit

I tried both Hyprland and COSMIC. Hyprland had xdg-desktop-portal issues, COSMIC didn't (one of the positive things abouit wlroots. Both have issues with the clipboard on Xwayland (I'm pretty sure all of them have issues with the clipboard on Xwayland it's a Wayland security issue).

[-]

No-Bison-5397@reddit

With all due respect COSMIC is in alpha.

Give GNOME or KDE a spin.

[-]

79215185-1feb-44c6@reddit

I despise both KDE and GNOME. I do use KDE as my default on my server however.

[-]

6e1a08c8047143c6869@reddit

...why do you use a desktop environment on a server?

[-]

79215185-1feb-44c6@reddit

VNC

[-]

ProfessorFakas@reddit

You may already know this, but most OpenSSH builds ship with a built-in SOCKS proxy, just needs setting in your ssh_config or by passing -D.

I like to pair it with the Container Proxy add-on for Firefox. I just configure a specific container to use the proxy and then use it to access anything that needs to go via that route. You can set certain sites to open automatically in a given container, too.

[-]

79215185-1feb-44c6@reddit

I did not know this. I will have to read up. I only use ssh as a generic reverse proxy or for ssh/scp/sshfs.

[-]

ProfessorFakas@reddit

In that case, I'm happy to have shared a useful trick!

[-]

ultrasquid9@reddit

Cosmic isn't built with wlroots, but rather uses smithay, which is a rust-based compositor library.

[-]

79215185-1feb-44c6@reddit

Thanks for correcting the mistake.

[-]

Branan@reddit

Yeah, any apps trying to do anything "interesting" with the clipboard won't work, and that is by design in Wayland.

I was surprised you said you had issues, since I've had no problems using KDE Connect and Plasma's clipboard manager to send clipboard data back and forth from my phone to both native and XWayland apps. But in my case the apps that need special permissions are tightly coupled to the compositor as part of the Plasma DE.

But if your workflow relies on apps that do fancy clipboard things without that coupling, you'll definitely have a bad time.

[-]

ItsLiyua@reddit

If you're talking about the clipboard being wiped after closing the app you copied from that's an intended feature. If you want a regular clipboard you need a clipboard manager like https://github.com/sentriz/cliphist

[-]

1smoothcriminal@reddit

Last few updates changed everything! high recommend

[-]

Iwisp360@reddit

Well I don't need Xorg anymore

[-]

nightblackdragon@reddit

On current NVIDIA driver it's pretty good actually, no issues for me on KDE.

[-]

Meqdadfn@reddit

Not ready yet. Still freezes and lags and artifacts here and there.

[-]

C0rn3j@reddit

freezes and lags and artifacts here and there

That's definitely not the current experience past 555, either you had out of date driver or the rest of the OS components.

[-]

Meqdadfn@reddit

560 still have issues

[-]

pago6x@reddit

It's ok most of the time, but there are still some annoying issues that probably won't get fixed anytime soon. I think that everyone has to try it out himself, because it highly depends on what you do. A lot of people are very happy on wayland+nvidia.

To me the biggest issue is google meet. The browser is stuttering like I have no resources left on my PC. When I screenshare, I my voice cuts. However, this might be a general issue on wayland, because I have similar experience on my intel laptop where I don't have dedicated GPU.

[-]

commodore512@reddit

Depends how new the GPU. If you watch Action Retro, old Nvidia doesn't work as well as old AMD. He tried installing Linux with 3D acceleration on a 12-year-old mac and Nvidia's drivers gave him hell on modern kernels. An AMD GPU that old, no problem, from what I heard Vulkan works just fine on a 7970.

I think the RTX GPUs would be fine though though I never used it I'm just judging based on the comments I read.

[-]

Derpygoras@reddit

"I have used it with no problems" is a worthless testimony, yall. It's about as useful as "I flew over Afghanistan without dying". Your lack of experience bears no weight unless you add some problem you have actually observed to be resolved, or tell us what you use the PC for. Like, can you Alt-TAB from a fullscreen game yet without being met with a black screen? Have you even ever tried?

I find it wild that Ubuntu is about to force Wayland upon us very soon, when you still have to patch things up manually to make it work almost as good as X. With the most ubiquitous cadre of GPUs in history, no less.

[-]

Current-Tea-8800@reddit

https://wearewaylandnow.com/

[-]

zuegg@reddit

After the recent driver updates bringing explicit sync, I was finally able to get external monitor working without artifacts/tearing on my optimus laptop.

I'm using sway and only had problems with xdg-desktop-portal/screen sharing, until I figured out it wasn't working because of a env var for prime offload I had set and forgotten.

I'm not gaming, but I'd say things are shaping up nicely to the point I'm not using x11 since a few weeks now.

[-]

redpandapro@reddit

I’m on the latest version of sway but still tearing :( are you on master branch by any chance? As I understood it there are still some patches not in release right now

[-]

zuegg@reddit

Yes forgot to mention I'm on master for both wlroots and sway, explicit sync patches for both projects are yet to be released. There's also a "nvidia-wlroots" patch I applied to wlroots, but I honestly don't know if that's still required, might try to compile without it and see how it goes

[-]

redpandapro@reddit

Thanks! Im going to try that too :)

[-]

rocketstopya@reddit

I have rtx 3060 and I cant find issues now on Arch KDE.

[-]

apollo-ftw1@reddit

555 it works

Cosmic + pop! Os seems to work the best for me out of box

[-]

DocalLOL@reddit

Still can’t edit any GPU settings on Wayland. It sure is more optimized and smooth, but not being able to edit performance settings is a huge deal breaker for me. GreenWithEnvy saves my life everyday and having a little bit smoother experience with Wayland isn’t enough for me to leave X11 yet.

[-]

dgm9704@reddit

you can do it from command line though

[-]

Linneris@reddit

Runs great for me with KDE Plasma 6.1. The only issue I have is that Flatpak Firefox for some reason crashes under native Wayland, so I have to run it under XWayland.

[-]

AsexualSuccubus@reddit

My understanding is all the major compositors support latest NVIDIA drivers well.

Programming with libdrm and gbm API I've had a couple issues with a 1050ti that are just fucking stupid. I think the one that got the biggest eye roll from me was asking if buffer format with flags was supported returning true but then using those flags failing. You just have to have workarounds for NVIDIA.

[-]

eriomys@reddit

when I installed 555 and 560, laptop would freeze after standby so I reverted back to 550 that is in the official repository

[-]

fireclaw722@reddit

I will be using graphically intensive apps including games

Use X11. Performance on anything that actually uses the GPU will suffer under Wayland, because the driver is only recently built for it.

There's still a ton of issues and it isn't quite ready yet. Maybe in a couple of years, but we've been saying that since 2015, so maybe sometime in the distant future NVIDIA will actually be usable on Linux...

[-]

tinix0@reddit

I have 4080 and its fine since 555 with KDE 6 as everyone says. Havent had opportunity to test 560 since nvidia only packages the lts drivers for opensuse.

[-]

CthulhusSon@reddit

RTX 3060ti with the 560 drivers & I'm spending more time using Wayland than X11 these days, I'm even thinking of removing XFCE as I haven't fired it up in weeks.

[-]

Obnomus@reddit

Nice perfect for my use case

[-]

UDxyu@reddit

Haven't used x11 since nearly the start of this year had some minor issues but it is flawless recently

[-]

Celibistrial@reddit

On a 1050ti its still bad

[-]

oneiros5321@reddit

Been fully Wayland with Nvidia for 2 months. I haven't experienced any issues so far.

[-]

VisceralMonkey@reddit

My understanding is that HDR with NVIDIA and Wayland is still not working correctly, is that not everyone elses experience? At least with KDE?

[-]

Byakkott@reddit

I'm having no problems with the 560 version. AMD CPU, and NVIDIA GPU in Arch, using KDE. Just follow the step-by-step guide on Archwiki and GG. I'm playing BDG3, Spider-Man Remastered, No Man's Sky, Black Myth Wukong, etc. I'm also developing in Python and Go without problems and doing livestreams on Twitch

[-]

EternalFlame117343@reddit

The games run all well but steam glitches on 550 driver :( I had to get rid of the hardware acceleration

[-]

C0rn3j@reddit

550 is not supported, you need 555 minimum and a Wayland compositor up to date enough to support explicit sync.

[-]

EternalFlame117343@reddit

:') it hasn't come to Ubuntu 24.04 yet :')

[-]

Groovy_bugs@reddit

The 555 was good on X11, but the 560 works like a charm. I am using KDE. I will try it with Wayland and give you an update.

[-]

demize95@reddit

I was running Wayland with the proprietary drivers before 555 (3080, gentoo, plasma 5), and it was mostly fine, with some minor issues.

After upgrading to plasma 6 and the 555 driver, pretty much all my issues went away. Really good experience now.

[-]

BrokenG502@reddit

I haven't seen a single issue since 555. I would argue that it was usable/ok before 555, but some apps did have very annoying flickering. The worst culprit for me at the time was RDR2, where the pause menu would flicker badly making it difficult to distinguish which option was where and what I had selected. I also had a few flickering issues when clicking on images in discord, but everything else worked well enough.

Since 555 I haven't seen any of that. I recently switched to river and it seems to work fine with proprietary drivers despite them being officially unsupported. Sway also appears to work fine, but I didn't get around to properly testing it, so it could be riddled with issues for all I know.

[-]

Mundane_Bus9491@reddit

Driver 555 was a God-sent. Before it didn't work at all. Now you can't tell the difference.

[-]

art-solopov@reddit

I've tried it with Nouveau. Regarding NVidia (as in, not counting DE/app weirdness and errors), it mostly works. The only problem I saw is Dwarf Fortress suddenly not running for some reason.

[-]

Frossstbiite@reddit

I switched to x11

[-]

Ok_Leave_2149@reddit

With 555 I haven't had any issues.

[-]

WojakWhoAreYou@reddit

I'm using 560 drivers on gnome wayland and it works almost perfectly, it's ready for daily drive, and I haven't touched x11 in three months now, and I've switched to wayland with driver 550

[-]

Fofeu@reddit

I have a GTX 2070 Super and am daily driving sway for \~3 months now.

I'm switching between nouveau and nvidia-open drivers. Using nouveau, I have 0 issues and everything works great, but performance isn't the best. Largely enough for emacs, firefox and co, but gaming isn't great (Factorio works !). Using nvidia-open, "normal" apps have graphical artifacts (squares that don't update with the rest of the frame), but anything that runs fullscreen (i.e. games) works great.

[-]