Driving an AE86 apparently feels just like using wayland with NVIDIA
Driving an AE86 apparently feels just like using wayland with NVIDIA
You're viewing a single thread.
-
Can anybody who has actually used Nvidia with wayland in the last 6 months tell me what problems you have? As a recreational PC user I have noticed 0 issues with my setup:
- Ryzen 3600
- Nvidia GTX 1660
- Arch
- Nvidia-open driver
- Gnome / KDE / Hyprland (currently Gnome) running on wayland
I came from Windows 2-3 months ago, my daily usage has been more or less unaffected, especially when it comes to something I could pin to specifically nvidia + wayland.
All the above just makes it seem like nvidia + wayland bad is just a circlejerk.
-
RTX 2080 here, and this is the major blocker for me with Nvidia + Wayland: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317
This issue causes XWayland apps to effectively render previous frames very sporadically, and it's especially very noticeable in Electron apps. Discord for example, sometimes someone will send a message and the message will appear, then disappear, then reappear, then disappear over and over again until it finally syncs back up. The user isn't actually deleting and resending their message of course, but the render state of the app is basically "jumping backwards through time".
Tried out the 544 beta driver, and while we did get Night Light/Color support (and that incessant top-screen flicker bug was fixed, occurred in both Wayland and X11), I started to notice the aforementioned issue heavily occurring in IntelliJ which is a Java based development tool which unfortunately is the final deal breaker for me since I can't really work when I write a line of code, and it disappears, reappears, disappears, then reappears again.
This only occurs via XWayland, and surprisingly games don't seem to get hit with it (in my case) so I suppose if you only use Wayland native apps like a web browser then it's fine - otherwise, it makes things very difficult. It also occurs on both Mutter (GNOME) and KWin (KDE) but I imagine there isn't a compositor where this doesn't happen due to what causes the actual problem in the first place.
After trying the 545 beta and the problem getting worse, it's put the nail in the coffin for me on Nvidia and I'll be picking up a 6700XT after my next paycheck comes in. It is a beta driver yes, but the root of the issue is due to the architecture of their driver which isn't going to be magically redone in between the beta and "stable" release.
So, no - I wish it was just a circlejerk, and realistically I can't see how it'd end up being this popular if it was just user error.
-
Fair point, I have probably experienced this as I had weird input issues on native linux discord, I switched to WebCord, which solved the issue. before I pinpointed the issue, so I had no clue it is specific to nvidia + wayland.
And yes, I specifically mentioned I use my PC recreationally to point out that my usecases are not too specific, so maybe I do not see the issues because of that.
-
-
In my case, windows start to flickr intensively after a while. I tried a bunch of flags and workarounds but nothing worked for me.
I use the proprietary driver, though.
-
Well of course you haven't had any issues you could pin specifically to NVIDIA + Wayland. Because according to your post you're specifically using Nouveau + Wayland. Be kind of strange for a driver you don't have installed to be causing you issues.
And you didn't need to point out you're an Arch user, we could tell just from the sense of superiority dripping off your comment.
-
I mean, i used nvidia with KDE and nvidia-dkms with hyprland, no difference.
E: The question is about nvidia cards playing with wayland anyway. Also afaik nvidia-open is not the same driver as noveau.
I mentioned the distro to point out I am not using a driver package that is 6 months old.
we could tell just from the sense…
Calm down buddy, no need to project your insecurities all over the place, everyone can tell you are a raging dick anyway.
E2: Brb, gonna check comments…
A device that allows me to kill any billionaire, world leader, or politician remotely, anywhere in the world, without them being able to stop me.
Oh, I see, you are just unhinged.
E3: I though about it a second more and I blocked you. Partly because I did not want to engage with your dumb ass, but mostly since I figured it would piss you off.
-
Three edits on one comment, I feel pretty special. Must really have bothered him if he had to come back twice. 😂
-
-
I didn't know Nouveau is entirely different GPU vendor! /s
-
It's fine, everyone was a newbie at one time.
-
-
-
I'm using it presently, and aside from a few quirks in electron app rendering (slack input box flickers sometimes; things like that), it's been solid:
- Ryzen 9 3900X (24)
- GeForce RTX 4070 Ti
- Fedora 38
- Nvidia proprietary driver
- Hyprland (used Gnome before and it was fine)
I use it daily for work and some gaming (CP2077, BG3 of late) and it works well.
Before I'd updated the video card, I had a AMD 5700 xt and it mostly worked, but I was getting sporadic driver crashes (card would reset), which was annoying.
-
Yea, I had no clue that it is an Nvidia + Wayland issue, I had something similar in discord, i switched to webcord before pinpointing the issue and it solved it. More of a nuisance than a real problem in my case though.
-
I found proton to be unreliable. Never got hat in time to play correctly.
-
Sure, it is not a 100% everything runs solution, but it is probably 85%+, maybe even 90%+ works solution. To call it unreliable knowing the history of gaming on Linux is a little odd, maybe we just have different expectetions.
The level of certainty I can now have that a game will run on linux is so high that I am happy not wasting my time and money with games that wont.
I have tried switching to linux off and on since about original TBC or WotLK days, I always ended up switching back because things were too finicky, or I couldnt get most games to work. Now it just works for so many things that I am happy ditching things that don't.
-
Oh sure, it's just I found switching off of Wayland resolved most of my issues with proton.
-
Oh I see, I missed that fact, I thought you were talking about proton in general.
The only time I had problems with wayland - proton (I think) was with stanley parable, which I outlined somewhere in this thread (I am a little lost honestly, have gotten a ton of replies).
But in either of our cases I doubt the problem was nvidia - wayland, rather just wayland.
-
Yeah I should have added more details.
Yeah that's a high probability. I don't have any amd GPUs to test with, newest one I have is a Radeon x1900 haha
-
-
-
-
-
Yes, 3060 and Wayland/gnome act funny after resuming the machine from sleep while connected to a second display.
-
Some applications, e.g. Firefox will not update properly after a resume when screen config has been changed while asleep. That is, if I undock my laptop and then resume, Firefox won't visibly scroll or change, but buttons invisibly move which I know because where the mouse cursor changes when hovering changes after playing with the scroll wheel. Only fix is killing Firefox and restarting. Maybe it's a snap thing.
-
On resume, wallpaper for gdm is painted on secondary monitor while laptop display stays dark, even though that's where the login prompt etc is. A quick close/open of the laptop lid forces the main display to come back online.
-
Suspend works fine for me on Wayland/Gnome, firefox only gets closed when I reboot. I use nvidia-open though, i remember before I had to take extra steps to enable proper nvidia suspend behaviour, or I had similarproblems(there was a specific package and some configs to change).
Now mind you this is an nvidia not nvidia - wayland issue afaik.
-
-
Laptop support is not where it needs to be especially when it comes to dual GPU.
-
I used KDE with Wayland briefly a few months ago. The right-click menu would look very glitchy. Items disappeared until hovered over, and then disappeared again when moving the mouse. Firefox also had some issue where it would only take half the screen.
-
Interesting, but I doubt this was an nvidia + wayland problem, or if it was, it had been since fixed. My first DE was KDE and I used the regular nvidia driver with it, for sure did not notice anything wrong with right click menus.
-
I've used multiple different distros before and after, all Xorg, and never encountered similar problems. There were bugzilla reports for the Firefox issue I had, all of them attributing it to Wayland.
-
I mean, it might be a wayland issue, sure. And I am not saying wayland as a whole is perfect, I am just saying I don’t feel I generally have experienced nvidia + wayland problems as opposed to just wayland problems.
Although I did concede that I did have an electron issue which turns out was an NV + W issue and I just didn’t know.
I use FF and had no issues on either KDE, Hypr or GNOME, as well as used KDE around 2 months ago and didn’t notice any right click problems, so I imagine whatever it was got fixed since you tried it.
-
-
-
-
I've noticed some sleep issues. my solution was telling my computer to just turn off my monitors instead
-
Just replied to another comment about suspend issues with nvidia.
Have you tried doing something like this arch wiki entry
-
nah my workaround is fine and I went with that as soon as I noticed the problem. I can eat the extra 20w worth on my power bill
you know how it is, no such thing as a temporary solution
-
-
-
For me it was buggy but usable on arch running the LTS kernel on my rtx 3060 on KDE and gnome.
RN I'm running debian 12 which still defaults to X11 and even that is still a bit buggy on gnome.
Just don't use the bleeding edge and you'll be ok