our yearly "your nvidia gpu will finally work on wayland now!"
this post was submitted on 09 Apr 2024
120 points (96.2% liked)
Linux Gaming
15849 readers
23 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 4 years ago
MODERATORS
You can’t deny their support for Wayland has been steadily improving with the latest driver releases. In fact it’s already in a good state if it weren’t for the flickering in certain applications caused by these issues with explicit sync which are currently being addressed.
i tried it recently and it was still pretty buggy for me, too late now though since i had the opportunity to move to amd
am I correct to assume this is the thing that'll fix eg. Steam going full seizure mode under wayland + nvidia?
If by that you mean the flickering crap, then yes.
Exactly that. Awesome and thanks.
Now, aggressive waiting for the updates begins
Nvidia users will also need a DE update, but yeah, we're finally almost there.
Who thought individual compositors having to re-implement base features individually and over and over again would be a good idea?
Same with the dozens of different protocols and portals and all the other magic bullshit. Once feature-complete with X11,Wayland will be of same complexity.
Once feature-complete with X11,Wayland will be of same complexity.
I'm gonna go out on a limb and say the Wayland/X11 devs (same people) know more about the way the X11/Wayland projects are structured than you do.
They absolutely do. And I hope they prove me wrong.
They already have?
It's definitely a large leep, but it's not going to solve everything. I'd say it brings us to ~85% completion. There's still a lot of smaller issues in need of fixing, and some issues unique to specific problem cards. Nvidia needs to put in that last 10% and the community needs to put in that last 4%. The 1% are the tiny bugs spread across the ecosystem that'll get fixed overtime.
Nvidia shouldn't need to put anything in. It's entirely Waylands fault that it does not work well with the already existing hardware and drivers environment.
Nvidia is shit for so many reasons but not because Wayland doesn't work well with it.
If Nvidia had worked together with Wayland devs from the beginning this wouldn't be an issue
Did they worked together with X11 to the same extend they need to work together with Wayland?
If Nvidia had worked together on Xorg, we wouldn't have had all of those shitty Nvidia unique x11 bugs with Nvidia's crappy proprietary drivers in the past.
Cannot confirm any Nvidia unique X11 bugs since everything works perfectly fine since a decade or so for me – but tons of Nvidia unique Wayland bugs (same driver version and same card). I am not quite sure if Nvidia are really the bad one in this specific case.
My whole invironment is full of stuff to make Wayland actually work with Nvidia.
$ cat .config/labwc/environment
GBM_BACKEND=nvidia-drm
__GLX_VENDOR_LIBRARY_NAME=nvidia
LIBVA_DRIVER_NAME=nvidia
QT_QPA_PLATFORM=wayland
WLR_NO_HARDWARE_CURSORS=1
XDG_CURRENT_DESKTOP=wlr
XDG_SESSION_TYPE=wayland
Not one single line of configuration is used for X11.
Here's just a tiny fraction of the Nvidia specific bugs on X11 :
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/380
https://bbs.archlinux.org/viewtopic.php?id=283461
https://forums.developer.nvidia.com/t/16-bit-overlays-broken-with-x11-and-4xx-series-driver/128067
https://bugs.kde.org/show_bug.cgi?id=460341
labwc
You're using a WM bud, wtf do you expect?
You’re using a WM bud, wtf do you expect?
I expect it to work, like Openbox works on X11.
You miss the entire point of WMs then.
You're complaining about 7 lines of configs when the entire point of WMs is for you to literally customize everything through configs.
Shit, you probably don't even need half of that crap. QT_QPA_PLATFORM=wayland is already handled by qt, you only need that when running apps across Waypipe from a headless server environment. By default QT infers your environment from $DISPLY which is always :0 in Wayland.
Thank you for educating me on basic knowledge about WMs, which I use since ove a decade.
I just expect applications behave the same. I have literally not one single line of configuration for X11 in any of my configuration files.
I need this QT variable, otherwise Cura does not work properly.
Cura as in this one? :
Exactly. When the variable is unset the UI shows massive artifacts and weird rendering glitches.
I don't see any graphical glitches on my hardware.
Perhaps you're still on the qt5 version?
Maybe a bug with your Nvidia driver?
Perhaps your WM doesn't have explicit sync yet and your card & driver needs it in this particular case? Perhaps it's running under XWayland?
Wayland#Qt :
While it shouldn't be necessary, to explicitly run a Qt application with the Wayland plugin, use-platform waylandorQT_QPA_PLATFORM=waylandenvironment variable.
As it says above, it should really be inferred by default. Something weird is going on here.
Nvidia's failure to implement the spec correctly is solely their own.
Its not the car manufacturers failure when the road is broken.
It's the car manufacturers failure when they can't properly put their tires on to safely drive on the road or put on tires that weren't up to code to begin with.
Dose this mean using the desktop at all will not take half my GPU?
Are you sure that's not because it's running at a very low frequency?
Not sure how to check, still fairly new.
I did notice the temperatures though. The card normally idles at 30-40c having anything open after a while will have it cooking at 75ish. I would expect it to be in the 50s after a few hours of youtube, or pushing 90-100 gaming. No issues on the Windows half of the install. From what I could piece together it dose seem to be related to Wayland and the drivers. I was thinking of waiting till Nobara updates and hope it goes away.
Seems if I have anything opened and on screen like firefox or the file browser, it gets toasty.
If it's reaching those temps then the answer is probably no. Hope you find a solution
That's wast I was thinking. Hopefully, if I ignore it long enough it will go away with an update.