In KDE mouse moves slower after 2-months update including Nvidia drivers. Like it has input lag.
In systemsettings should be a setting for coursor acceleration.
Are you sure that the Nvidia drivers are operational? There have been issues with recent updates, kernel 6.18 etc.
Sure. I also switched from 6.18 vanilla kernel to default.
Are you using the closed or open NVIDIA driver? Does it occur with Wayland and X11 sessions?
Show the results from
inxi -GSaz
Don’t blame the NVidia drivers for your mouse, especially after applying 2 months worth of Tumbleweed updates. How many packages did you get updated? About 2000?
It doesn’t happen very often, but sometimes defaults change. Also, check if your mouse has a tiny button where you can switch between fast and rough vs. slow and precise movement; my Logitech mouse has one. Check if the status simply toggled.
The mouse settings applet might have more settings now, like a different default speed and different acceleration values. You might want to check there.
Also, check if it’s the mouse in general or just the mouse in your browser. I used Opera a lot over the years, and the mouse speed (or lack of it) was a constant annoyance; I needed a browser extension to get it up to speed (literally).
Whatever it is, I am pretty sure it’s not the graphics drivers.
Sorry but mouse speed is not the same as lag. The mouse events are processed immediately, but the frame showing the new cursor position arrives late, and that lives in the compositor/GPU path. That’s exactly where NVIDIA regressions tend to show up.
Yes, Tumbleweed updates a lot of packages, but it is unlikely that unrelated updates would affect cursor responsiveness without many similar reports. Issues like this usually trace back to compositor timing, vsync, or GPU driver changes rather than input settings.
Closed, I have problems with installing open-nvidia in other topic. Both Xorg and Wayland show cursor slowdown.
Thanks for the update. I’m not surprised to read of the nvidia issues impacting here.
Do you know something related?
Just in case the following is helpful:
It is only likely to help if the lag is coming from the GPU firmware / driver path. I don’t own NVIDIA hardware, but others who do may be able to chime in here. From what I’ve read, the GSP firmware can introduce small delays in frame presentation, which can make the mouse feel laggy even if input events are fast. Disabling it forces the driver to do everything on the main GPU path, reducing these timing issues. It might also impact on power management (higher idle power).
Again, you should disclose your graphics hardware and environment details…
inxi -GSaz
1 Like
Graphics:
Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: ASUSTeK driver: nvidia
v: 580.119.02 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1
empty: DVI-D-1,HDMI-A-1 bus-ID: 07:00.0 chip-ID: 10de:1f82 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,nouveau,vesa alternate: fbdev,nv
gpu: nvidia,nvidia-nvswitch display-ID: 0
Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
Tumbleweed 20251211
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
memory: 3.91 GiB display-ID: :1.0
API: Vulkan v: 1.4.335 layers: 7 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 1650 driver: nvidia v: 580.119.02
device-ID: 10de:1f82 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 21.1.6 256 bits) driver: mesa llvmpipe v: 25.3.1 (LLVM 21.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Not sure why ASUSTeK if GPU is from Gigabyte.
So, you’re using a GTX 1650 (Turing) card with the 580 driver on Plasma Wayland. Try testing with GSP disabled, and see if the observed mouse lag improves.
Create/edit /etc/modprobe.d/nvidia.conf, adding the entry options nvidia NVreg_EnableGpuFirmware=0. Save when done, then rebuild initrd (mkinitrd) and reboot. See if that helps.
If you prefer you can add it as a boot parameter instead: nvidia.NVreg_EnableGpuFirmware=0
1 Like
After this setting I started to get black screen for 3+ seconds after entering KDE main menu.
After this setting I started to get black screen for 3+ seconds after entering KDE main menu. Possible because of transparent background, but it works fine whith other non fullscreen apps.
Got this just watching a video.
AI said need to fix memory behavior
options nvidia NVreg_EnableGpuFirmware=0 NVreg_PreserveVideoMemoryAllocations=1 NVreg_DynamicPowerManagement=0x02
They are respectively for disabling GSP firmware (as already mentioned), avoiding suspend/resume or VRAM corruption issues, and stabilising power management on Turing/Ampere cards.
Did you try applying these driver options yet?
More info:
https://download.nvidia.com/XFree86/Linux-x86_64/435.17/README/dynamicpowermanagement.html
@deano_ferrari PreserveVideoMemoryAllocations is already set;
https://build.opensuse.org/projects/X11:Drivers:Video/packages/nvidia-gfxG06/files/modprobe.nvidia?expand=1
On my run file install I use;
cat /etc/modprobe.d/50-nvidia-tweaks.conf
blacklist nouveau
softdep nvidia post: nvidia-drm nvidia-uvm
options nvidia-drm modeset=1
##Power Management
## Disable runtime D3 power management features
##options nvidia NVreg_DynamicPowerManagement=0x00
## Allow the GPU to go into its lowest power state when no applications are running
options nvidia NVreg_DynamicPowerManagement=0x02
## For suspending, make sure not using tmpfs!
options nvidia NVreg_PreserveVideoMemoryAllocations=1
options nvidia NVreg_TemporaryFilePath=/var/tmp
## Enable the PAT feature
options nvidia NVreg_UsePageAttributeTable=1
## Support for CUDA Stream Memory Operations in user-mode applications
options nvidia NVreg_EnableStreamMemOPs=1
Good to know - not my suggestion though. 
Anyway, good to see an NVIDIA user chime in here.