Need help. Don’t know where to start. A recent update killed KDE Plasma and it only shows a black screen. After several minutes, the login console re-appears. Fortunately Gnome Classic is working. I have read and tried all the other solutions on how to revert using dnf but, the problem persists.
Can someone advise on how to proceed with debugging? What log files are needed? Do I need to create a bug report? etc…
Much thanks
Ray
Firstly thing - post the output from inxi -Fzxx so we can see what kit you have.
Secondly, can you switch to a TTY using Ctrl-Alt-F3 and log in to it?
Hi Steve… Thanks for responding. I can use Gnome Classic but, my preferred KDE Plasma is not working. Also, since this upgraded issue occurred, some of the windows in Gnome have strange artifacts and flickering. Anyhow, here’s the output from inxi…
$ inxi -Fzxx
System:
Kernel: 7.0.12-201.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: GNOME v: 50.2 tk: GTK v: 3.24.52 wm: gnome-shell dm: 1: GDM
2: SDDM note: stopped Distro: Fedora Linux 44 (Workstation Edition)
Machine:
Type: Desktop Mobo: ASRock model: X570 Phantom Gaming X
serial: Firmware: UEFI vendor: American Megatrends
v: P3.20 date: 06/15/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech ERGO M575 Trackball
serial: charge: 95% status: discharging
CPU:
Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 2200 min/max: 2200/4672 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 13: 2200 14: 2200 15: 2200 16: 2200 17: 2200 18: 2200
19: 2200 20: 2200 21: 2200 22: 2200 23: 2200 24: 2200 bogomips: 182399
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: NVIDIA GP102 \[GeForce GTX 1080 Ti\] driver: nouveau v: kernel
arch: Pascal pcie: speed: 2.5 GT/s lanes: 16 ports: active: HDMI-A-1
empty: DP-1,DP-2,DP-3 bus-ID: 10:00.0 chip-ID: 10de:1b06 temp: 45.0 C
Device-2: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-4.2:3 chip-ID: 046d:0843
Display: wayland server: Xwayland v: 24.1.12 compositor: gnome-shell
driver: gpu: nouveau display-ID: 0
Monitor-1: HDMI-1 model: ACR KA272 A res: 1920x1080 hz: 75 dpi: 81
diag: 685mm (26.96")
Monitor-2: HDMI-A-1 model: Acer KA272 A res: 1920x1080 dpi: 81
diag: 685mm (27")
API: EGL v: 1.5 platforms: device: 0 drv: nouveau device: 1 drv: swrast
gbm: drv: nouveau surfaceless: drv: nouveau wayland: drv: nouveau x11:
drv: nouveau
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 26.0.8 glx-v: 1.4
direct-render: yes renderer: NV132 device-ID: 10de:1b06 display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
driver: mesa nvk device-ID: 10de:1b06 device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GP102 HDMI Audio driver: snd_hda_intel v: kernel pcie:
speed: 2.5 GT/s lanes: 16 bus-ID: 10:00.1 chip-ID: 10de:10ef
Device-2: Advanced Micro Devices \[AMD\] Starship/Matisse HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 12:00.4 chip-ID: 1022:1487
Device-3: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-4.2:3 chip-ID: 046d:0843
Device-4: Logitech Headset H390 driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 5-4.3:4
chip-ID: 046d:0a44
Device-5: Schiit Audio Unison Modius E driver: snd-usb-audio type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-4.4:5 chip-ID: 30be:101a
API: ALSA v: k7.0.12-201.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel 82571EB/82571GB Gigabit Ethernet D0/D1
vendor: Hewlett-Packard NC360T Dual Port Server driver: e1000e v: kernel
pcie: speed: 2.5 GT/s lanes: 4 port: e020 bus-ID: 04:00.0
chip-ID: 8086:105e
IF: enp4s0f0 state: down mac:
Device-2: Intel 82571EB/82571GB Gigabit Ethernet D0/D1
vendor: Hewlett-Packard NC360T Dual Port Server driver: e1000e v: kernel
pcie: speed: 2.5 GT/s lanes: 4 port: e000 bus-ID: 04:00.1
chip-ID: 8086:105e
IF: enp4s0f1 state: down mac:
Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
speed: 2.5 GT/s lanes: 1 bus-ID: 08:00.0 chip-ID: 8086:2723
IF: wlp8s0 state: up mac:
Device-4: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 0a:00.0 chip-ID: 8086:1539
IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac:
Device-5: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: speed: 5 GT/s lanes: 1 port: c000 bus-ID: 0c:00.0 chip-ID: 10ec:8125
IF: enp12s0 state: down mac:
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-2:2 chip-ID: 8087:0029
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: bt-v: 5.2 lmp-v: 11
Drives:
Local Storage: total: 3.18 TiB used: 378.21 GiB (11.6%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 46.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 51.9 C
ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
speed: 6.0 Gb/s serial:
ID-4: /dev/sdb vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
speed: 6.0 Gb/s serial:
Partition:
ID-1: / size: 929.91 GiB used: 377.48 GiB (40.6%) fs: btrfs dev: /dev/dm-0
mapped: luks-8c89e769-dd11-47bf-a6cc-a6b385fa1fbf
ID-2: /boot size: 973.4 MiB used: 718.5 MiB (73.8%) fs: ext4
dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 929.91 GiB used: 377.48 GiB (40.6%) fs: btrfs
dev: /dev/dm-0 mapped: luks-8c89e769-dd11-47bf-a6cc-a6b385fa1fbf
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 61.1 C mobo: N/A gpu: nouveau temp: 45.0 C
Fan Speeds (rpm): N/A gpu: nouveau fan: 1206
Info:
Memory: total: 128 GiB note: est. available: 125.71 GiB
used: 6.08 GiB (4.8%)
Processes: 579 Power: uptime: 45m wakeups: 1 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 26
Compilers: clang: 22.1.7 gcc: 16.1.1 Shell: Bash v: 5.3.9
running-in: ptyxis-agent inxi: 3.3.40
Your system is running the nouveau driver, which is, to put it politely, sub-optimal.
Can we assume you were running the rpmfusion drivers? If so your card is no longer supported by the latest nvidia drivers - Nv dropped support for pascal architecture recently, so you need to be using the 580xx drivers (that is the name of the packages you want - the “xx” is indeed part of the package name
Because of this failure, your system is dropping back to nouveau and I suspect you’re seeing the results of it with the latest version of KDE.
Install the 580xx package from the rpmfusion repo, let it build for your kernel. Check the output in /var/cache/akmods/nvidia/.last.log to make sure it’s all successful and returns a 0.
Reboot and I suspect you’ll be golden.
Some users have reported problems with one of the latest versions of plasma after an update.
This topic appears to have found a workaround for recovery that may work for you as well, and waiting for another plasma update with the fix might be best.
I also note that you are using nouveau as the driver for the nvidia card (GTX 1050), and with f44 that card works best with the 580xx nvidia driver.
The exact name is “akmod-nvidia-580xx” and probably make sure to get “nvidia-settings-580xx” too. If the OP wants X11 too, throw in also:
plasma-workspace-x11 and xorg-x11-drv-nvidia-580xx.x86_64
Installing akmod-nvidia-580xx will automatically pull in the matching nvidia-settings package. The only additional package that would need to be explicitly named is the xorg-x11-drv-nvidia-580xx-cuda package.
well, yeah, I didn’t go look at all the dep chains, I’m just saying if a dependency doesn’t pull it in, then get it. That’s what I mean by “make sure to get”
All,
With genuine thanks for the suggestions above, I have made some progress. It seems odd that support for this graphics card would be suspended. They still sell these cards like hotcakes. Anyhow…
I followed the advice to install the “CUDA” package and now, KDE Plasma is working again. Upon restarting the system and checking for updates, “Discover” is saying many updates are available including a bunch of things related to plasma 6.7. I’m a little worried about doing that upgrade. Can anyone offer some advice on how to handle that?
Anyhow, for the sake of others, here are the web-based instructions I followed to install the CUDA 580xx drivers. See below…
Thanks to all.
Ray
Ensure your system is updated.
Enable the RPM Fusion repository.
Enable RPM Fusion Repository
Run the following commands to enable both the free and non-free repositories:
bash
sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf install https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
Install the NVIDIA Driver
Execute the command below to install the akmod-nvidia-580xx driver along with the necessary CUDA package:
bash
sudo dnf install akmod-nvidia-580xx xorg-x11-drv-nvidia-580xx-cuda
Edited by @computersavvy .
I took the liberty of removing your step 4 since the content was already given in steps 1 & 2, plus it contained typos. Repeating the commands given in steps 1 & 2 was unnecessary and would have achieved nothing.
Those cards were first released in 2016 so nvidia provided direct support for almost 10 years. They are getting a bit long in the tooth even though they still function well.
Support is still available with the 580 driver even though nvidia officially ended support in Oct 2025.
The newer 595 driver for linux does not support it, but with fedora, and linux in general, the older driver will still be around for a long time. The card should still be usable and fully functional – probably for another 5 or more years.
I’m running a 1080Ti and it runs just fine. It would be ideal to get another few years out of it. Fingers crossed!
BTW: I let “Discover” do all it’s recommended upgrades and the system still works. I was a bit concerned it would regress to a broken state.
Once again… thanks to all for the assistance on this.
Ray