Nvidia's driver 560 is bricking distros

Ask Fedora
,
1

Hello, I am having a serious problem. I had to quit Pop_OS! because it updated to Nvidia’s driver 560 and it ruined my entire laptop, the entire experience: Games crash, applications take x3 times to open (Firefox takes about 85 seconds to open instead of the usual 10s as in 555), the keyboard and right-click begin to malfunction (keys like ‘n’, ‘b’, Caps Lock, ‘F1’ either get written twice or ignored very constantly, none of this happened before or in my dual boot windows, it’s not dust or a hardware problem) when there is a heavy app loaded, like Boxes, VS Code, World of Warcraft… Sometimes the notepad itself aswell, my Caps Lock behavior will switch (light on = lowercase), but I think I fixed that one. It is incredibly unbearable and annoying.

The worst part of all is that there is no way to downgrade anymore, both in Pop_OS! and Fedora now. I don’t know why they do this, but I tried a lot of things: runfile method (using CLI mode after a reboot), akm, and everything said in this post: Rolling back rpmfusion Nvidia drivers from 560 to 555 - #11 by caferino

Is this it? Is there no way out?

Specs:
OS: Fedora Linux 40 (Workstation Edition)
Host: HP ENVY m7 Notebook
Kernel: 6.11.4-201.fc40.x86_64
Packages: 2727 (rpm), 56 (flatpak)
Shell: bash 5.2.26
Resolution: 1920x1080
DE: GNOME 46.6
WM: Mutter
WM Theme: Adwaita
Theme: Nordic-darker-v40 [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i7-7500U (4) @ 3.500GHz
GPU: Intel HD Graphics 620, NVIDIA GeForce 940MX
Memory: 2032MiB / 15869MiB

AKMODS doesn’t work either, I get these:

caferino@192:~$ sudo /usr/sbin/akmods --force
Checking kmods exist for 6.10.12-200.fc40.x86_64 [ OK ]
Building and installing nvidia-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/nvidia/550.67-1-for-6.10.12-200.fc40.x86_64.failed.log for details

Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
‘/usr/sbin/akmods --force’ as root.

Checking kmods exist for 6.11.4-201.fc40.x86_64 [ OK ]
Building and installing nvidia-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/nvidia/550.67-1-for-6.11.4-201.fc40.x86_64.failed.log for details

Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
‘/usr/sbin/akmods --force’ as root.

caferino@192:~modinfo -F version nvidia
modinfo: ERROR: Module nvidia not found.
caferino@192:~$ dnf list installed nvidia
Installed Packages
akmod-nvidia.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
nvidia-modprobe.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
nvidia-settings.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
xorg-x11-drv-nvidia.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
xorg-x11-drv-nvidia-cuda-libs.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
xorg-x11-drv-nvidia-kmodsrc.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
xorg-x11-drv-nvidia-libs.i686 3:550.67-1.fc40 @rpmfusion-nonfree
xorg-x11-drv-nvidia-libs.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
xorg-x11-drv-nvidia-power.x86_64 3:550.67-1.fc40 @rpmfusion-nonfree
caferino@192:~$

2

Do you have logs that show a problem?
Look in the system journal for kernel panics etc
Look in the user journal for gnome reporting errors.

3

If your hardware has no other issues, check the logs, then the problem is with your note book, not disros being bricked.
Fixing that may well need nvidia to make a fix to the drivers.

4

I am not tech-savy enough to understand the logs. The ones given by akmods talk a lot about missing stuff like this one:

/tmp/akmodsbuild.kGIrftDI/BUILD/nvidia-kmod-550.67/_kmod_build_6.10.12-200.fc40.x86_64/common/inc/nv-linux.h: In function ‘nv_vmap’:
/tmp/akmodsbuild.kGIrftDI/BUILD/nvidia-kmod-550.67/_kmod_build_6.10.12-200.fc40.x86_64/common/inc/nv-linux.h:674:51: warning: suggest braces around empty body in an ‘if’ statement [-Wempty-body]
674 | NV_MEMDBG_ADD(ptr, page_count * PAGE_SIZE);

there are hundreds of those. I feel so lost

5

You may get help with the old drivers.

But its likely that it is easier to fix forward. e.g. fix 560.

If you run with 560 and check the logs maybe there is something that can be done help.

6

I gave the logs a shot, but they are incredibly massive, specially Gnome’s (started from Sep 28, and it had like 1000 core dump lines, about 5,000 lines per day, all red, couldn’t stand holding Enter for so long, it’d take easily hours). It’s hard for me to write this post, my caps lock got inverted, letters ‘n’ ‘b’ are requiring me to press them like 5 times until they get written, and more. Tried to run WoW with this kernel 6.11 and 560 again, but it’s just impossible, right-click just doesn’t work at all. I first tried with 6.10 and 560 out of curiosity, and it was stable the first 5 minutes, but then it went all down very quickly and behaved just the same

I posted the logs from “journalctl -b” here:

7

Usually there are many blocks repeating similar messages. A big part of the success of linux is due to the “given enough eyeballs, all problems are shallow”. Many Nvidia problems are Nvidia firmware that conflicts with recent kernels, so will be present across multiple linux distros. journalctl collects massive amounts of data, and has many “filter” options to help select the relevant records. This is a lot of work. You can check to see if users on both Fedora and other distros have reported similar problems with journalctl records and the see if they match what your system produces.

Using pastebin does not allow others to find your journalctl records with web searches, so you are relying on others to post excerpts as searchable text.

8

It is relatively simple to limit the logs to only one boot period and to trim even that down to relevant portions.
journalctl -b 0 gives only the logs since the last boot
adding additional filters such as with -g (grep) or -p (priority) or --since (time such as since -5 min ) can trim the output significantly and remove a lot of unnecessary verbage in the logs. Once the data shown on screen is reasonably small then it can more easily be read to identify relevant parts.

9

The journalctl log might redundantly spew the same line over and over but unfortunately the timestamp makes a lot of the similar lines look different. So you could try stripping off the timestamp and pipe the result into “uniq”

journalctl -b 0 --no-pager --no-hostname | awk '{ for (i = 4; i <= NF; i++) printf "%s ",$i;print "" }' | uniq > mylog.log

uniq makes sure that consecutive duplicate lines only show one time.

Then you can try filtering that even more with ‘-g nvidia’

journalctl -b 0 --no-pager --no-hostname -g "nvidia"| awk '{ for (i = 4; i <= NF; i++) printf "%s ",$i;print "" }' | uniq > mylog.log

this might help make a much smaller dump log due to

  1. limiting it to one boot with “-b 0”
  2. limiting lines to those containing ‘nvidia’ via the -g option
  3. squashing repeats

If someone knows a slick built-in way to tell journalctl to dump the time stamp, please reply it because I hate resorting to that awk hack

1 Like
10

Sorry for the late reply, I got distracted. Today I tried to run World of Warcraft with nvidia-470 but it’d say the 3D accelerator card is not supported, so I installed 560 back and decided to play the game until it crashed (it has become completely unplayable, it will crash at ~10 minutes of gameplay ― happens more likely after that time and then starting combat with anything, or simply being idle after doing stuff like gathering or fighting early on) and see what could the logs say. I ran the command you suggested and I got this:

audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=nvidia-powerd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
systemd[1]: Started nvidia-powerd.service - nvidia-powerd service.
/usr/bin/nvidia-powerd[934]: nvidia-powerd version:1.0(build 1)
systemd[1]: nvidia-powerd.service: Deactivated successfully.
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=nvidia-powerd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
audit[14314]: SOFTWARE_UPDATE pid=14314 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 msg=‘op=install sw=“kmod-nvidia-6.11.5-300.fc41.x86_64-3:560.35.03-1.fc41.x86_64” sw_type=rpm key_enforce=0 gpg_res=0 root_dir=“/” comm=“dnf” exe=“/usr/bin/dnf5” hostname=? addr=? terminal=? res=success’
akmods[910]: Building and installing nvidia-kmod[ OK ]
kernel: nvidia: loading out-of-tree module taints kernel.
kernel: nvidia: module license ‘NVIDIA’ taints kernel.
kernel: nvidia: module license taints kernel.
kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 560.35.03 Fri Aug 16 21:39:15 UTC 2024
kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
kernel: nvidia-uvm: Loaded the UVM driver, major device number 509.
kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 560.35.03 Fri Aug 16 21:21:48 UTC 2024
kernel: [drm] [nvidia-drm] [GPU ID 0x00000400] Loading driver
kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:04:00.0 on minor 0
kernel: nvidia 0000:04:00.0: [drm] No compatible format found
kernel: nvidia 0000:04:00.0: [drm] Cannot find any crtc or sizes
systemd[1]: nvidia-fallback.service - Fallback to nouveau as nvidia did not load was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/nvidia).
gnome-shell[14417]: Added device ‘/dev/dri/card0’ (nvidia-drm) using atomic mode setting.
/usr/libexec/gdm-x-session[15115]: (II) Applying OutputClass “nvidia” to /dev/dri/card0
/usr/libexec/gdm-x-session[15115]: loading driver: nvidia
/usr/libexec/gdm-x-session[15115]: (==) Matched nvidia as autoconfigured driver 0
/usr/libexec/gdm-x-session[15115]: (II) LoadModule: “nvidia”
/usr/libexec/gdm-x-session[15115]: (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
/usr/libexec/gdm-x-session[15115]: (II) Module nvidia: vendor=“NVIDIA Corporation”
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA dlloader X Driver 560.35.03 Fri Aug 16 21:25:43 UTC 2024
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): Depth 24, (==) framebuffer bpp 32
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): RGB weight 888
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): Default visual is TrueColor
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): Using gamma correction (1.0, 1.0, 1.0)
/usr/libexec/gdm-x-session[15115]: () Option “AllowNVIDIAGpuScreens”
/usr/libexec/gdm-x-session[15115]: (II) Applying OutputClass “nvidia” options to /dev/dri/card0
/usr/libexec/gdm-x-session[15115]: () NVIDIA(G0): Option “SLI” “Auto”
/usr/libexec/gdm-x-session[15115]: () NVIDIA(G0): Option “BaseMosaic” “on”
/usr/libexec/gdm-x-session[15115]: () NVIDIA(G0): Option “AllowEmptyInitialConfiguration”
/usr/libexec/gdm-x-session[15115]: (WW) NVIDIA(G0): Invalid SLI option: ‘Auto’; using single GPU rendering.
/usr/libexec/gdm-x-session[15115]: (WW) NVIDIA(G0): Base Mosaic is available only on screen 0. Disabling Base
/usr/libexec/gdm-x-session[15115]: (WW) NVIDIA(G0): Mosaic.
/usr/libexec/gdm-x-session[15115]: (**) NVIDIA(G0): Enabling 2D acceleration
/usr/libexec/gdm-x-session[15115]: (II) Loading sub module “glxserver_nvidia”
/usr/libexec/gdm-x-session[15115]: (II) LoadModule: “glxserver_nvidia”
/usr/libexec/gdm-x-session[15115]: (II) Loading /usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so
/usr/libexec/gdm-x-session[15115]: (II) Module glxserver_nvidia: vendor=“NVIDIA Corporation”
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA GLX Module 560.35.03 Fri Aug 16 21:27:48 UTC 2024
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA: The X server supports PRIME Render Offload.
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): NVIDIA GPU NVIDIA GeForce 940MX (GM108-A) at PCI:4:0:0
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): (GPU-0)
/usr/libexec/gdm-x-session[15115]: (–) NVIDIA(G0): Memory: 2097152 kBytes
/usr/libexec/gdm-x-session[15115]: (–) NVIDIA(G0): VideoBIOS: 82.08.59.00.7d
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): Detected PCI Express Link width: 4X
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): Validated MetaModes:
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): “NULL”
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): Virtual screen size determined to be 640 x 480
/usr/libexec/gdm-x-session[15115]: (WW) NVIDIA(G0): Unable to get display device for DPI computation.
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): DPI set to (75, 75); computed from built-in default
/usr/libexec/gdm-x-session[15115]: (WW) NVIDIA: Failed to bind sideband socket to
/usr/libexec/gdm-x-session[15115]: (WW) NVIDIA: ‘/var/run/nvidia-xdriver-4eeec4f3’ Permission denied
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA: Reserving 6144.00 MB of virtual memory for indirect memory
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA: access.
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): ACPI: failed to connect to the ACPI event daemon; the daemon
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): may not be running or the “AcpidSocketPath” X
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): configuration option may not be set correctly. When the
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): ACPI event daemon is available, the NVIDIA X driver will
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): try to use it to receive ACPI event notifications. For
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): details, please see the “ConnectToAcpid” and
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): “AcpidSocketPath” X configuration options in Appendix B: X
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): Config Options in the README.
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): Setting mode “NULL”
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): Disabling shared memory pixmaps
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): Backing store enabled
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): Silken mouse enabled
/usr/libexec/gdm-x-session[15115]: (==) NVIDIA(G0): DPMS enabled
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): [DRI2] Setup complete
/usr/libexec/gdm-x-session[15115]: (II) NVIDIA(G0): [DRI2] VDPAU driver: nvidia
systemd[15071]: Started app-gnome-nvidia\x2dsettings\x2duser-15484.scope - Application launched by gnome-session-binary.
systemd[15071]: app-gnome-nvidia\x2dsettings\x2duser-15484.scope: Consumed 374ms CPU time, 136M memory peak.
net.lutris.Lutris.desktop[17205]: 2024-11-01 21:53:28,346: NVIDIA Corporation GM108M [GeForce 940MX] (10de:134d 103c:81d4 nvidia) Driver 560.35.03

Also, in Lutris itself, I’d get dozens of these logs while playing. I asked in Lutris’ Discord to see if they might know what’s up, but from what I read in it it feels related to the cause; I’ve been assuming this whole problem has something to do with loading shaders/graphics from cache, because while playing it feels like something is happening there, but I am not tech savy enough to confirm this. I will keep digging, learning and see if something more useful comes up:

1593.504:07e8:08f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Pipeline cache marked dirty. Flush is scheduled.
1594.505:07e8:08f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Flushing disk cache (wakeup counter since last flush = 71). It seems like application has stopped creating new PSOs for the time being.
1608.880:07e8:08f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Pipeline cache marked dirty. Flush is scheduled.
1609.892:07e8:08f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Flushing disk cache (wakeup counter since last flush = 18). It seems like application has stopped creating new PSOs for the time being.

The error of my right-click not sticking to drag the camera around is still there and has gotten worse. It felt fixed with Fedora 41’s install, but it returned back to normal. It feels like it happens a lot less when the driver is freshly installed, I noticed that while troubleshooting, but it slowly builds up until it becomes very constant, in like 30mins, hence why I assume it has something to do with the cache or its size, but I am not sure yet.

While reading the journal’s logs, I find some errors weird, like the virtual screen size being 480p while my screen is actually running everything at 720p, some permission denied problems I might need to do chown somewhere on, not sure; the random NULL modes and values… I don’t know how to dissect this, feels like I need to know a lot of lore about how these things work, it’s intimidating, but I will try, I been dealing with these issues for the past 2 years, I want to help fix it however I can.

11

Do you know which nvidia driver is installed. There seem cases where the newer nvidia open driver has exhibited memory leaks and over time causes problems. The proprietary drivers have not exhibited this behavior.

dnf list installed '*nvidia*' should tell us the answer.

12

Ran both inxi -SMGxx and dnf list instaled ‘nvidia’ to see what’s up, got this:

caferino@192:~$ inxi -SMGxx
System:
…
Graphics:
Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
v: kernel arch: Gen-9.5 ports: active: HDMI-A-1,eDP-1 empty: none
bus-ID: 00:02.0 chip-ID: 8086:5916
Device-2: NVIDIA GM108M [GeForce 940MX] vendor: Hewlett-Packard
driver: nvidia v: 560.35.03 arch: Maxwell pcie: speed: 2.5 GT/s lanes: 4
bus-ID: 04:00.0 chip-ID: 10de:134d
…

caferino@192:~$ dnf list installed ‘nvidia’
Updating and loading repositories:
Fedora 41 - x86_64 - Updates 100% | 21.0 KiB/s | 9.1 KiB | 00m00s
github_git-lfs-source 100% | 1.8 KiB/s | 2.7 KiB | 00m01s
github_git-lfs 100% | 2.5 KiB/s | 2.7 KiB | 00m01s
Fedora 41 - x86_64 - Updates 100% | 645.0 KiB/s | 1.1 MiB | 00m02s
Repositories loaded.
Installed packages
akmod-nvidia.x86_64 3:560.35.03-1.fc41 rpmfusio
kmod-nvidia-6.11.5-300.fc41.x86_64.x86_64 3:560.35.03-1.fc41 @command
nvidia-modprobe.x86_64 3:560.35.03-1.fc41 rpmfusio
nvidia-settings.x86_64 3:560.35.03-1.fc41 rpmfusio
xorg-x11-drv-nvidia.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-cuda-libs.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-kmodsrc.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-libs.i686 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-libs.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-power.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-xorg-libs.x86_64 3:560.35.03-5.fc41 rpmfusio

Available packages
akmod-nvidia-390xx.x86_64 3:390.157-12.fc41 rpmfusio
akmod-nvidia-470xx.x86_64 3:470.256.02-3.fc41 rpmfusio
golang-github-nvidia-container-toolkit.x86_64 1.16.1-1.fc41 fedora
golang-github-nvidia-container-toolkit-devel.noarch 1.16.1-1.fc41 fedora
golang-github-nvidia-nvlib-devel.noarch 0.6.1-1.fc41 fedora
golang-github-nvidia-nvml-devel.noarch 0.12.4.0-3.fc41 fedora
kmod-nvidia.x86_64 3:560.35.03-1.fc41 rpmfusio
kmod-nvidia.x86_64 3:560.35.03-1.fc41 rpmfusio
kmod-nvidia-390xx.x86_64 3:390.157-12.fc41 rpmfusio
kmod-nvidia-470xx.x86_64 3:470.256.02-3.fc41 rpmfusio
libva-nvidia-driver.i686 0.0.12-3.fc41 fedora
libva-nvidia-driver.x86_64 0.0.12-3.fc41 fedora
nvidia-gpu-firmware.noarch 20241017-2.fc41 fedora
nvidia-persistenced.x86_64 3:560.35.03-1.fc41 rpmfusio
nvidia-persistenced.x86_64 3:560.35.03-1.fc41 rpmfusio
nvidia-query-resource-opengl.x86_64 1.0.0-18.fc41 fedora
nvidia-query-resource-opengl-lib.i686 1.0.0-18.fc41 fedora
nvidia-query-resource-opengl-lib.x86_64 1.0.0-18.fc41 fedora
nvidia-settings-390xx.x86_64 390.157-4.fc41 rpmfusio
nvidia-settings-470xx.x86_64 3:470.256.02-2.fc41 rpmfusio
nvidia-texture-tools.i686 2.1.2-10.fc41 fedora
nvidia-texture-tools.x86_64 2.1.2-10.fc41 fedora
nvidia-texture-tools-devel.i686 2.1.2-10.fc41 fedora
nvidia-texture-tools-devel.x86_64 2.1.2-10.fc41 fedora
nvidia-xconfig.x86_64 3:560.35.03-1.fc41 rpmfusio
nvidia-xconfig.x86_64 3:560.35.03-1.fc41 rpmfusio
pcp-pmda-nvidia-gpu.x86_64 6.3.1-1.fc41 fedora
xorg-x11-drv-nvidia-390xx.x86_64 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-cuda.x86_64 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-cuda-libs.i686 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-cuda-libs.x86_64 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-devel.i686 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-devel.x86_64 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-kmodsrc.x86_64 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-libs.i686 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-390xx-libs.x86_64 3:390.157-4.fc40 rpmfusio
xorg-x11-drv-nvidia-470xx.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-cuda.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-cuda-libs.i686 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-cuda-libs.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-devel.i686 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-devel.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-kmodsrc.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-libs.i686 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-libs.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-470xx-power.x86_64 3:470.256.02-1.fc41 rpmfusio
xorg-x11-drv-nvidia-cuda.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-cuda.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-cuda-libs.i686 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-cuda-libs.i686 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-devel.i686 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-devel.i686 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-devel.x86_64 3:560.35.03-5.fc41 rpmfusio
xorg-x11-drv-nvidia-devel.x86_64 3:560.35.03-5.fc41 rpmfusio
caferino@192:~$

Was told by the Lutris team (shotout to OJ, a real OG), that these logs I have shown are reporting that my driver isn’t working or installed correctly, but they find it weird that inxi -SMGxx shows otherwise.

Doesn’t look like your nvidia driver is installed correctly = try inxi -SMGxx and check what it says
Also, I had issues with Fedora 41 and getting nvidia 560 drivers working during beta - saw the same issues with akmods that you show in your posting

I have a possible cause, I will investigate, but: when I upgraded to Fedora 41, I remember running inxi -SMGxx early on and being told the driver 560 was still installed, however, after some secondary updates and a restart, I got prompted with a notification telling me to do the new Fedora 41 Mokutil’s process to sign the 560’s driver. I noted the given key, restarted and applied it all fine, which allowed my games to work (WoW specifically), and it worked pretty well for that entire day, not sure what happened overtime for it to start breaking again. Anyway, I have been uninstalling and installing the driver back on/off to test things, tried the driver 470 too, but it wouldn’t work at all with WoW (“3D accelerator not compatible”). I am wondering if maybe the Mokutil’s signing process has to be done again? Everytime the driver is reinstalled? I never got the prompt notification to do it again, for either the 470 or the reinstalled 560, and that’s confusing me. Is it a one-time thing? If not, I think I might need to do it again through the terminal, but I’m still not sure this is it, because WoW does detect the GPU and launches, but the logs given by Lutris are saying the driver is not working/installed according to the Lutris team.

I was also told:

I tried Nobara with the new 565 drivers and on KDE Plasma, was not a great experience - lots of weird issues that I remember from 535 on Mint

13

I’m no longer using Nvidia, but in the past, the Nvidia firmware package was required.

14

The 470 driver does not support wayland and can only be used reliably with the X11 DE. It also does not support the newer GPUs (3000 & 4000 series at least and possibly 2000 series).

George has a point. The nvidia-gpu-firmware package is missing from the installed list and can normally be reinstalled with sudo dnf install nvidia-gpu-firmware

15

Got rid of the lutris constant logs, but not the crashes yet. I will try this guide given in a similar post I saw here to see if it’s specifically the driver or my laptop, but I think I cannot disable my Intel GPU through the BIOS, it shows up as the VGA controller, Nvidia for the 3D one (https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/)

16

A guide from 9 years ago may well lead you into deeper trouble.

1 Like
17

Often users who follow guides and/or use software from INTTF encounter major problems that are solved by removing everything from INTTF and installing things from rpmfusion instead.

18

things got worse with today’s update. I DIDN’T Complete the guide i sent in the past reply, it didn’t work. i don’t have any INTTF PACKAGES INSNTALLED, ut right ow my etire laptop is sufferig the error istead of just WoW, my caps lock, ‘b’ annd ‘n’ either get igored or repeated radomly. i WAS FINE usig the laptop this past week y switchig etwee x11 ad waylad ecause I found cons and pros with each one of them: Wayland allows me to play wOw nonstop with these errors with the keys, while x11 crashes after 10mins of gameplay, completely. hOWEVER, in x11 everything loads quicker, some gnome extensions like Hide Top Bar glitch a lot less with Brave. Both of them didn’t suffer these key errors outside woW or very heavy laggy apps. It’s weird, but at least it was working fine, until today, I updated ad rebooted as prompted by Software, but now both my X11 and wAYLANND instances are suffering this wild bug. I’M NOT seeing anything significant in the logs yet, but I will test this on Ubuntu next, dual boot this, although i’M sure uuntu will puch back too because pop_os had the same issues, this is pretty critical, i CANNNOT work like this

I learnt my lesson, I will make backups/timeshift everytime before updatig

TEMPORARY SOLUTION: I think using Gnome Classic fixed this issue for now, I haven’t felt it happen here. I did try disabling all the extensions I had in the normal one, but the problem was still happening. It’d happen a lot in some apps like the terminal, the app search bar, google search, this forum… But it was flawless in apps like VS Code, ChatGPT and Text Editor, it’s so odd. Right now it’s working pretty well; I will keep testing Gnome Classic now, never tried it before, maybe it is also flawless in WoW and more, maybe it was Gnome all along, I will see

19

TEMPORARY SOLUTION: …

Bad news, the problem seeped to the classic gnome versions as well. They happen a lot less, but are still prevalent and constant. I installed Ubuntu on a different partition and gave it a shot, but sadly, it presented the same problem, a lot less, probably because it’s a fresh install, and I’ve noticed it builds up, but it still happens, so maybe it is actually a hardware problem or something worse. Since Day One I had this laptop, sometimes, while gaming or doinng something heavy, keys will stay stuck until I press them again. I tried so many things, but never managed to fix it in either Windows, Pop or Fedora, now Ubuntu too. I will never buy an HP product in my life ever again.