I suspect that my nvidia graphics card has been damaged and it is causing many problems in my fedora setup, like the system lags a lot when playing videos in vlc or any media player and the system blacks out from time to time.
So I uninstalled the graphics driver (I am on laptop so I can’t remove the graphics card) using sudo dnf remove xorg-x11-drv-nvidia\* I found at reddit.
But after restarting I notice that in About section:
llvmpipe shows up in place of nvidia and intel integrated graphics is also missing.
And with those the sound and network (wifi) drivers are now gone too! And now the whole system is lagging, and weird flickers and colors are showing up on the screen.
NOTE: After waiting for a while, I did not find a fix here, so I am posting this on reddit as well.
System abouts:
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.11-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8300H CPU @ 2.30GHz
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: TUF GAMING FX504GD_FX80GD
System Version: 1.0
Nvidia doesn’t want you to use that card. Get a cheap Intel ARC B570/580 instead and reward their competitor
Be aware that ur videocard is old and nvidia stoped supporting this video card in modern version of drivers
My graphics card is GTX 1050.
I know and nvidia already said bye to this generation
I have a GTX 1060 and I’m stuck on kernel 6.16.5, maybe OP should downgrading the kernel
llvmpipe means you only have software graphics rendering. You got rid of the graphics driver, so that’s not in usage. As for intel graphics, perhaps you need to ensure that you have mesa-dri-drivers installed? Or maybe somehow the intel kernel module has been blacklisted?
“mesa-dri-drivers-25.2.7-3.fc43.x86_64” is already installed.
I don’t remember doing anything involving intel kernel module. But since there are no sound and network drivers too, I think something did affect it.
Anything in dmesg? Run
$ inxi -Farzyto see what shows up in hardware.nvidia-smi -ais their info. Stuff should show up in dmesg through.deleted by creator
inxi -Farzy
Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: ASUSTeK driver: N/A arch: Gen-9.5 process: Intel 14nm built: 2016-20 bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300 Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: ASUSTeK driver: N/A non-free: 550-580.xx+ status: current (as of 2025-08; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1c8d class-ID: 0302 Device-3: IMC Networks USB2.0 HD UVC WebCam driver: N/A type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:3 chip-ID: 13d3:5666 class-ID: 0e02 serial: <filter> Display: wayland server: Xwayland v: 24.1.9 compositor: kwin_wayland driver: N/A display-ID: 0 Monitor-1: Unknown-1 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 96 size: 508x285mm (20x11.22") diag: 582mm (22.93") modes: 1920x1080 API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast wayland: drv: swrast x11: drv: swrast inactive: gbm API: OpenGL v: 4.5 vendor: mesa v: 25.2.7 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 21.1.5 256 bits) device-ID: ffffffff:ffffffff memory: 7.42 GiB unified: yes display-ID: :0.0 API: Vulkan v: 1.4.321 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM 21.1.5 256 bits) driver: mesa llvmpipe v: 25.2.7 (LLVM 21.1.5) device-ID: 10005:0000 surfaces: N/A Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandrsudo dmesg | grep -i nvidia
[ 8.560355] nvidia: loading out-of-tree module taints kernel. [ 8.560387] nvidia: module license 'NVIDIA' taints kernel. [ 8.560407] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 8.560411] nvidia: module license taints kernel. [ 10.162158] nvidia-nvlink: Nvlink Core is being initialized, major device number 234 [ 10.181614] nvidia 0000:01:00.0: enabling device (0006 -> 0007) [ 10.404048] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 580.105.08 Wed Oct 29 23:15:11 UTC 2025 [ 10.491564] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. [ 10.727186] nvidia_modeset: Unknown symbol acpi_video_register_backlight (err -2) [ 10.727220] nvidia_modeset: Unknown symbol __acpi_video_get_backlight_type (err -2) [ 16.643779] nvidia_modeset: Unknown symbol acpi_video_register_backlight (err -2) [ 16.643828] nvidia_modeset: Unknown symbol __acpi_video_get_backlight_type (err -2) [ 23.093267] nvidia_modeset: Unknown symbol acpi_video_register_backlight (err -2) [ 23.093310] nvidia_modeset: Unknown symbol __acpi_video_get_backlight_type (err -2) [ 23.317882] nvidia_modeset: Unknown symbol acpi_video_register_backlight (err -2) [ 23.317935] nvidia_modeset: Unknown symbol __acpi_video_get_backlight_type (err -2) [ 23.822227] nvidia_modeset: Unknown symbol acpi_video_register_backlight (err -2) [ 23.822297] nvidia_modeset: Unknown symbol __acpi_video_get_backlight_type (err -2)Sorry, for the delay, - sleep. These are the places I check, but I am no expert kernel dev or anything.
I had a similar-ish issue in an embedded Arch yesterday. Apparently there was an upstream change in the organization of Linux firmware. It was in the pacman manual intervention news feed from a few months ago, like October I think. Anyways, I just had to update that Arch build by removing the Nvidia firmware. The arch instructions were to delete all entries in Linux-firmware and rebuild them with pacman after a -Syu update. I am on obscure hardware on that device, and the error I was getting was specifically related to the older Nvidia firmware modules. So I only removed them and it resolved my issue. IIRC, the Arch news mentioned something about how these firmware files got relocated upstream. Maybe this was not resolved correctly for your firmware by the Fedora packagers.
