Poor performance on KDE after installing NVIDIA proprietary drivers

Ask Fedora
, , , , , , ,
1

I’m having issues with performance after installing the proprietary Nvidia drivers on Fedora 39 KDE Spin - tabbing between programs is slow, laggy animations, navigating lines of code in VSCode feels sluggish. This is my first time on Linux so I’m not sure on how to troubleshoot this.

I am running a dual boot with Windows 11, so I have secure boot enabled. Initially I attempted to install the Nvidia driver through the RPM fusion repository, however I believe the driver wasn’t loading because of secure boot and I was getting the “NVIDIA kernel module missing. Falling back to nouveau” error.

I have followed this guide parts 1 through 3 to install and sign the driver. While executing the .run Nvidia driver I downloaded (ver 535.154.05) in CLI mode, I also was prompted and execute the following line to uninstall other Nvidia drivers:

sudo yum remove xorg-x11-drv-nvidia\* kmod-nvidia\*

I also attempted part 5 of the guide, however some build failed after running:

spack install gcc@12.3.0

Here is my sudo inxi -Fxmz paste:

System:
  Kernel: 6.6.11-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-13.fc39 Console: pty pts/4 Distro: Fedora release 39 (Thirty Nine)
Machine:
  Type: Desktop Mobo: ASRock model: B450M Steel Legend serial: N/A
    UEFI: American Megatrends v: P2.60 date: 07/31/2019
Memory:
  System RAM: total: 16 GiB available: 15.54 GiB used: 5.05 GiB (32.5%)
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM 0 type: no module installed
  Device-2: DIMM 1 type: DDR4 size: 8 GiB speed: 3200 MT/s
  Device-3: DIMM 0 type: no module installed
  Device-4: DIMM 1 type: DDR4 size: 8 GiB speed: 3200 MT/s
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2
    rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2200 min/max: 2200/4208 boost: enabled cores: 1: 2200
    2: 2200 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200
    11: 2200 12: 2200 bogomips: 86236
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: ASUSTeK driver: nvidia
    v: 535.154.05 arch: Turing bus-ID: 07:00.0
  Device-2: Microdia [] driver: snd-usb-audio,uvcvideo type: USB
    bus-ID: 5-4:2
  Display: server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau
    gpu: nvidia,nvidia-nvswitch resolution: 1: 1920x1080~144Hz
    2: 1080x1920~60Hz
  API: EGL v: 1.5 drivers: nvidia platforms: active: gbm inactive: N/A
  API: OpenGL v: 4.6.0 vendor: nvidia v: 535.154.05 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
  API: Vulkan v: 1.3.268 drivers: nvidia,llvmpipe surfaces: xcb,xlib
    devices: 2
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 07:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel bus-ID: 09:00.4
  Device-3: Focusrite-Novation Scarlett Solo (3rd Gen.)
    driver: snd-usb-audio type: USB bus-ID: 1-6:5
  Device-4: Microdia [] driver: snd-usb-audio,uvcvideo type: USB
    bus-ID: 5-4:2
  API: ALSA v: k6.6.11-200.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.1 status: n/a (root, process)
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel port: f000 bus-ID: 05:00.0
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 924.07 GiB used: 30.96 GiB (3.4%)
  ID-1: /dev/nvme0n1 vendor: SanDisk model: ADATA SX6000LNP size: 476.94 GiB
    temp: 43.9 C
  ID-2: /dev/sda vendor: A-Data model: SU630 size: 447.13 GiB temp: 36 C
Partition:
  ID-1: / size: 475.35 GiB used: 30.65 GiB (6.4%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 278.8 MiB (28.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 43.9 MiB (7.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 475.35 GiB used: 30.65 GiB (6.4%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.8 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 378 Uptime: 1h 57m Init: systemd target: graphical (5) Compilers:
  gcc: 13.2.1 Packages: 19 note: see --rpm Shell: Sudo v: 1.9.14p3
  inxi: 3.3.31

Any sort of help will be greatly appreciated!

2

These days it is very dangerous to take advice from random internet sites – some are just misleading, but others seem designed to reduce security (and using the site tells evil-doers where to find your insecure system!).

is outdated, as dnf is the current command-line package manager:

% ls -l /usr/bin/yum
lrwxrwxrwx. 1 root root 5 Dec  7 20:00 /usr/bin/yum -> dnf-3

Currently yum just runs dnf-3, but new versions of dnf may add capabilities not available with yum, so best to stick with dnf. Advice to use yum may not be current.

Searching the Fedora Project site will provide more reliable information than you have found with wider searches (but since Fedora relies on volunteer efforts, some documents are outdated).

The instructions from the RPM Fusion repository do work with secure boot, but secure boot on dual-boot systems is sometimes blamed for issues created by Windows “fastboot” or a “race” issue with dnf building the module from source. The installer doesn’t have a mechanism to check that the module build has finished, so many people end up rebooting too quickly and wind up running nouveau.

Secure boot should not be a problem. Recent threads here describe how to recover from a failed RPM Fusion install.

3

I thought YUM was handled by dnf as an alias, but I could be mistaken.

4

That guide as already noted is extremely dated.

The recommended procedure for installing the nvidia drivers on fedora is to do so using dnf and the rpmfusion repo.

https://rpmfusion.org/Howto/NVIDIA
and

both show the steps to follow.

5

please refer Here