NVIDIA 4060 + Wayland performance being very laggy

[YamiYukiSenpai]

Hello,

• OpenMandriva Lx version: 25.02

• Desktop environment (KDE, LXQT…): Plasma

• Description of the issue (screenshots if relevant):
  NVIDIA performance in Plasma Wayland is very hitchy, even in Plasma 6.3.2
  Areas where blur is expected is just transparent (usually a sign that graphics isn’t running properly)

Can’t replicate the problem in KDE Neon or Kubuntu (both Wayland) & with the same GPU. KDE Neon setup has been the same setup since Plasma 5, and switched to Wayland during alpha/beta of Plasma 6 on Neon experimental.

• Relevant informations (hardware involved, software version, logs or output…):

$ nvidia-smi 
Sun Mar  2 00:41:19 2025       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.124.04             Driver Version: 570.124.04     CUDA Version: 12.8     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4060        Off |   00000000:07:00.0  On |                  N/A |
| 30%   38C    P8            N/A  /  115W |     395MiB /   8188MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A            1118      G   /usr/bin/kwalletd6                        2MiB |
|    0   N/A  N/A            1297      G   /usr/bin/kded6                            2MiB |
|    0   N/A  N/A            1318      G   /usr/bin/plasmashell                    112MiB |
|    0   N/A  N/A            1345      G   ...it-kde-authentication-agent-1          2MiB |
|    0   N/A  N/A            1492      G   htmlscript                               66MiB |
|    0   N/A  N/A            1497      G   /usr/bin/kdeconnectd                      2MiB |
|    0   N/A  N/A            1514      G   /usr/bin/kalendarac                       2MiB |
|    0   N/A  N/A            1563      G   ...ibexec/xdg-desktop-portal-kde          2MiB |
|    0   N/A  N/A            1718      G   /usr/lib64/libexec/baloorunner            2MiB |
|    0   N/A  N/A            1725      G   /usr/bin/kinfocenter                     51MiB |
|    0   N/A  N/A            1768      G   /usr/bin/konsole                          2MiB |

Operating System: OpenMandriva ROME 25.02
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-desktop-0.rc4.2omv2590 (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4060/PCIe/SSE2
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-8.2

log.txt (75.6 KB)

$ sudo dmesg | grep -E "nvidia|drm|fb"
[    0.000000] Command line: BOOT_IMAGE=/@boot/vmlinuz-6.14.0-desktop-0.rc4.2omv2590 root=UUID=05e5305b-99e0-46cc-a1f8-6b49c85565ae ro rootflags=subvol=@ nouveau.modeset=0 nvidia-drm.modeset=1 nvidia-drm.fbdev=1 quiet splash logo.nologo audit=0 rd.timeout=120 dm_mod.use_blk_mq=1 rd.systemd.show_status=0 systemd.show_status=0
[    0.000001] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[    0.018842] PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfeffbfff]
[    0.021670] Kernel command line: BOOT_IMAGE=/@boot/vmlinuz-6.14.0-desktop-0.rc4.2omv2590 root=UUID=05e5305b-99e0-46cc-a1f8-6b49c85565ae ro rootflags=subvol=@ nouveau.modeset=0 nvidia-drm.modeset=1 nvidia-drm.fbdev=1 quiet splash logo.nologo audit=0 rd.timeout=120 dm_mod.use_blk_mq=1 rd.systemd.show_status=0 systemd.show_status=0
[    0.874248] fbcon: Taking over console
[    1.831268] ACPI: bus type drm_connector registered
[    3.521370] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[    3.532890] systemd[1]: modprobe@drm.service: Deactivated successfully.
[    3.533013] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[    4.092149] nvidia: loading out-of-tree module taints kernel.
[    4.092158] nvidia: module license 'NVIDIA' taints kernel.
[    4.092162] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    4.092163] nvidia: module license taints kernel.
[    4.524183] nvidia-nvlink: Nvlink Core is being initialized, major device number 236
[    4.529216] nvidia 0000:07:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[    4.580883] nvidia_modeset: no symbol version for nvidia_get_rm_ops
[    4.594955] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  570.124.04  Tue Feb 25 03:39:21 UTC 2025
[    4.598553] [drm] [nvidia-drm] [GPU ID 0x00000700] Loading driver
[    5.994173] [drm] Initialized nvidia-drm 0.0.0 for 0000:07:00.0 on minor 0
[    5.994227] nvidia 0000:07:00.0: vgaarb: deactivate vga console
[  567.838060] nvidia_uvm: module uses symbols nvUvmInterfaceDupAddressSpace from proprietary module nvidia, inheriting taint.
[  567.864923] nvidia-uvm: Loaded the UVM driver, major device number 234.

Continuation of this post:

Plasma 6 Wayland felt hitchy/stuttery on NVIDIA RTX 4060

Hello, OpenMandriva Lx version: 24.12 Desktop environment (KDE, LXQT…): Plasma 6 Description of the issue (screenshots if relevant): I just started using OpenMandriva today, and currently playing it on my VM with GPU passthrough (RTX 4060) on my gaming PC. I’m testing this on Plasma 6 Wayland, and the cursor movement and reaction felt hitchy. After a while One thing to note was that when I installed NVIDIA driver using the Welcome app, it suddenly brought me back to the login scre…

Hope this log helps. I haven’t had the time to play around with this VM, so the original post closed.

I tried the fallback X session, but it just loads a terminal window of sorts with white background.

I’ll try to generate the part where desktop crashes to SDDM, but I haven’t had luck. Whenever it crashes, I forget to generate it.

Bug report in KDE’s bug tracker:
https://bugs.kde.org/show_bug.cgi?id=500936

[daemonx]

Hello,
ok wayland is very tricky, yes I get it others have invested more into wayland more, still is not there yet(my opinion), I love nvidia, but sucks for linux, any way there are ways we find the problem, now you commented that even in X11 you are having this issue, that seems to be a bigger configuration problem then, my first questions will be how did you installed the GPU driver? what process or what source?

[YamiYukiSenpai]

@daemonx

how did you installed the GPU driver? what process or what source?

from the repo

[WilsonPhillips]

I have an Nvidia card and I will say Wayland is a no go. X11 is the only way to go right now.

You installed Wayland and got buyer's remorse

You have installed the Wayland version of Plasma OMLx ROME and you don’t want to re-install to get X11. Or Vice Versa. Here’s how. UPDATED: info from @ben79 Wayland to X11 sudo dnf in task-plasma6-x11 --refresh X11 to Wayland sudo dnf in task-plasma6-wayland --refresh Reboot and select the proper session at the bottom left of login screen.

[pastorczo13]

With my Nvidia card Wayland is a no go, and that goes for me with most distributions. Wayland is honestly not there yet.

[YamiYukiSenpai]

I agree that Wayland on NVIDIA sucks in comparison to AMD or Intel, but for me, I have been using Wayland whenever possible, and have been fine enough that I can actually game on Neon Unstable whenever I test it out. There has to be something that’s broken that causes the performance to be very stuttery on OpenMandriva.

I’ll test on a gaming laptop with AMD+NVIDIA 1650 Ti, just in case something is borked with the VM. For that one, I know Neon & Pop!_OS alpha are working fine on it.
Perks of that laptop is that it has a 2TB NVME as its main (currently on Pop!_OS alpha with Cosmic) + 2TB SATA (where I can play around with other distros).

[zeroability]

@YamiYukiSenpai

Can’t replicate the problem in KDE Neon or Kubuntu (both Wayland) & with the same GPU. KDE Neon setup has been the same setup since Plasma 5, and switched to Wayland during alpha/beta of Plasma 6 on Neon experimental.

I cannot stress this enough. This comparison has no meaning without understanding what versions they are using, what patches they applied during packaging, and several other factors that could be tied to the compiler we use. KDE Neon is Plasma + Ubuntu. Ubuntu holds versions back. Which is good, because their support channels are often silent when you put in a bug request. Basically, they understand that their userbase is just there to consume the product so they tailor their distribution to meet that goal.

I will also echo what others here have already said:

Wayland is a user beware package, and will be for quite some time to come. You are welcome to use it, but you will be testing. We are not on the hook financially to make Wayland work like other distributions are, so we will need your help as you are doing now.

Newer nvidia cards are having problems with nouveau and nvidia v.565. We recently added 570 (though beta) to see if it alleviates some issues. If you have not done so already, use the open kmod since nvidia is now recommending that as the default for newer cards.

[zeroability]

@YamiYukiSenpai

I’ll test on a gaming laptop with AMD+NVIDIA 1650 Ti, just in case something is borked with the VM. For that one, I know Neon & Pop!_OS alpha are working fine on it.
Perks of that laptop is that it has a 2TB NVME as its main (currently on Pop!_OS alpha with Cosmic) + 2TB SATA (where I can play around with other distros).

My GTX 960 doesn’t work with wayland at all. Same situation applies with Pop. They don’t follow the same guidelines that we do and OMLx is not based on Pop, Ubuntu, Debian, Fedora, or anything else other than Mand/rake/riva and a little bit of ROSA.

[YamiYukiSenpai]

@zeroability

Wayland is a user beware package, and will be for quite some time to come. You are welcome to use it, but you will be testing. We are not on the hook financially to make Wayland work like other distributions are, so we will need your help as you are doing now.

That’s what I’d like to do, hence why I’m testing & reporting bugs.
Also, I’m sorta invested in Wayland since it has improved my experience greatly compared to X11.

I setup an Arch VM with same setup as the OpenMandriva VM (and my other VM GPU setups), and I don’t see the same issues (less cores since I cloned from Arch with LXQt)

@zeroability

a little bit of ROSA.

what’s ROSA?

[rugyada]

@YamiYukiSenpai

what’s ROSA?

ROSA Linux is a distro. OpenMandriva developers worked with their developers on the former Mandriva code, at the very beginning of both the inceptions.