There used to be many threads and “tech expert sites” cautioning again using wayland with the nvidia proprietary drivers. I am wondering if that is lore or history now or whether this is still to be avoided.
If it is history, I am assuming that it would be true also for leap 16…
Is use of wayland with nvidia proprietary drivers to be used with caution or avoided anymore?
Experiences! good or bad?
Running a test and potentially losing my graphics puts me in a position where I can’t get in contact with the forum to get help. So I am asking others.
@tckosvic Don’t know about Leap 15.6, but all fine on Leap 16.0 with a Quadro T400 and closed driver via the rpms running GNOME/Wayland (the iGPU is Intel 630 as a Display Controller).
Likewise Nvidia Containers on Leap 16.0 with a Quadro P400 and a Tesla P4 and closed rpms.
The reason I use the closed driver is it rebuilds on a kernel update.
On Tumbleweed I use the run (no secure boot) file and open driver with a just Quadro RTX4000 with GNOME/Wayland powering three screens.
I used to have these problem issues with a Nvidia Graphics card (rtx 4060) and Wayland. These days Wayland seems to work fine with a nvidia card (although I still use x11).
Yes, i used to have problems with nvidia on wayland but now there are no problems, I am using the proprietary drivers with the open kernel modules on Hyprland (wayland)
If you’re using a standard desktop install, and don’t use auto-login, you have the option of choosing what kind of session you would like. I have multiple users setup. Rather than playing with Wayland on my main account, which has always used X11, I have a separate account where I test Wayland.
Wayland appears to work just fine with OpenSUSE’s provided new open drivers from-Nvidia (GeForce RTX 3060 on a Plasma6 desktop). For the most part Wayland seems snappier.
The only issues I have with Wayland are:
Positions of windows are not saved and restored between logins.
Plasma6 on Wayland forces desktop scaling for monitors where the DPI is too small. For example a 27" 4K monitor would be scaled so that it is no longer 4K - 1cm/1inch on screen is no longer 1cm/1inch on paper, and images viewed 100% may not actually be at 100% (depends on viewer DPI awareness). There are unsupported ways of disabling scaling - but being unsupported they may one day break.
For the moment I’m sticking with X11 to avoid the above issues.
I have been using Tumbleweed for quite some time; issues appear here and there all the time, but in the last update I experienced a catastrophic failure of Wayland.
Namely, I have two monitors, and now when I move the cursor of the mouse to the different monitor, the system simply freezes and I cannot even switch to tty.
Switching to X11 helped resolve this issue.
(though might be wrong about it) Using Rust, vibe coding -
There you have it.
was using Tumbleweed with nvidia gtx1050ti with the graphics drivers provided by opensuse nvidia repositories without problems, except that firefox was running without GPU acceleration in which case i used to compile the va-api driver and did some configs here and there to make it accelerate. On the side note - I am glad that i have switched to AMD gpu since half an year already, everything is so smooth on this side.