Black screen at desktop/kwin AFTER graphical login with KDE after upgrading to Fedora 43

Hello - I am trying to troubleshoot getting a black screen after logging into the desktop after upgrading from Fedora 42, to Fedora 43. I updated my system with dnf first to ensure it was up to date, and then followed the steps here: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/ in the section under ‘Upgrading to the next Fedora KDE Plasma Desktop release.’ Upon rebooting, I logged in and was met with a black screen only the mouse cursor, but am able to move the mouse to the top left and see the virtual desktop icons and Overview which is just a black desktop screen (Settings, Screen Edges, top left is set to ‘Overview’) .

I have confirmed it is not this issue: Fedora 43 KDE sometimes boots to a black screen - as I do indeed get a login screen normally, and am able to log in, so I do not believe it is the plymouth handoff to ssdm. I have also looked at Black Screen after Login Screen - Fedora 41 KDE and [Wayland] After installing Nvidia drivers, screen immediately turns black after logging in with white cursor visible - #12 by badmagician which sounds/looks similar, but are about previous versions anyway

I have additionally disabled the rhgb section in grub, in order to both confirm it is not that, and also facilitate getting back into the previous still-functional kernel ( Linux 6.19.14-108.fc42.x86_64 ). Inspecting journalctl, it seems like there are some dbus issues, as well as one with kwin_wayland ?

Jun 14 17:45:43 skywalker irqbalance[1078]: IRQ 101 affinity is now unmanaged
Jun 14 17:46:05 skywalker cupsd[1354]: Unable to finalize "/etc/cups/subscriptions.conf": Permission denied
Jun 14 17:46:08 skywalker setroubleshoot[2099]: failed to retrieve rpm info for path '/etc/cups/subscriptions.conf.O':
Jun 14 17:46:08 skywalker setroubleshoot[2099]: SELinux is preventing cupsd from unlink access on the file /etc/cups/subscriptions.conf.O. For complete SELinux messages run: sealert -l 7c04f850-3e49-4099-8b49
-5cd8d8c35b76
Jun 14 17:49:08 skywalker sddm-greeter-qt6[1694]: file:///usr/share/sddm/themes/breeze/Main.qml:241:17 Parameter "username" is not declared. Injection of parameters into signal handlers is deprecated. Use Jav
aScript functions with formal parameters instead.
Jun 14 17:49:08 skywalker sddm-helper[2231]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                             Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
                                             If this causes problems, reconfigure your locale. See the locale(1) manual
                                             for more information.
Jun 14 17:49:08 skywalker sddm-helper[2231]: pam_limits(sddm:session): invalid line 3 in '/etc/security/limits.d/95-pipewire.conf' - skipped
Jun 14 17:49:08 skywalker (systemd)[2237]: pam_limits(systemd-user:session): invalid line 3 in '/etc/security/limits.d/95-pipewire.conf' - skipped
Jun 14 17:49:08 skywalker sddm-helper-start-wayland[1677]: "kwin_scene_opengl: Could not delete render time query because no context is current\n"
Jun 14 17:49:08 skywalker dbus-broker-launch[2270]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jun 14 17:49:08 skywalker dbus-broker-launch[2270]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Jun 14 17:49:08 skywalker dbus-broker-launch[2270]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Jun 14 17:49:09 skywalker kwin_wayland[2826]: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0"
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: [XKB-489] us:842:72: numeric keysym "0x1002039" (16785465)
Jun 14 17:49:09 skywalker kwin_wayland[2826]: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0"
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: [XKB-489] us:842:72: numeric keysym "0x1002039" (16785465)
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: [XKB-489] us:843:72: numeric keysym "0x100203a" (16785466)
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: [XKB-489] us:848:72: numeric keysym "0x1001e9e" (16785054)
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: [XKB-489] us:922:81: numeric keysym "0x1002039" (16785465)
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: [XKB-489] us:930:81: numeric keysym "0x100203a" (16785466)
Jun 14 17:49:09 skywalker kwin_wayland[2826]: XKB: Multiple definitions of group 0 name in map 'altgr-intl'; Using 'English (intl., with AltGr dead keys)', ignoring 'English (US, intl., with dead keys)'
Jun 14 17:49:10 skywalker plasma-keyboard[2904]: qtvirtualkeyboard currently is not supported at client-side, use QT_IM_MODULES=qtvirtualkeyboard at compositor-side.
Jun 14 17:49:17 skywalker kwin_wayland[2826]: No QSGTexture provided from updateSampledImage(). This is wrong.
(truncated 68 lines repeating the same message)

Jun 14 17:49:29 skywalker kwin_wayland[2826]: Failed to open drm node: "/dev/dri/card1"
Jun 14 17:49:34 skywalker /usr/libexec/xdg-desktop-portal[2836]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached
Jun 14 17:49:34 skywalker kwin_wayland[2826]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did
 not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Jun 14 17:49:42 skywalker login[2984]: pam_limits(login:session): invalid line 3 in '/etc/security/limits.d/95-pipewire.conf' - skipped
Jun 14 17:49:42 skywalker wireplumber[2825]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Jun 14 17:49:42 skywalker kwin_wayland[2826]: Failed to authenticate the drm magic token. path: "/dev/dri/card1" error: Permission denied
Jun 14 17:49:42 skywalker kwin_wayland[2826]: drmModeListLessees() failed: Permission denied
Jun 14 17:49:51 skywalker systemd[2237]: plasma-ksplash.service: start operation timed out. Terminating.
Jun 14 17:49:51 skywalker systemd[2237]: plasma-ksplash.service: Main process exited, code=killed, status=15/TERM
Jun 14 17:49:51 skywalker systemd[2237]: plasma-ksplash.service: Failed with result 'timeout'.
Jun 14 17:49:51 skywalker systemd[2237]: Failed to start plasma-ksplash.service - Splash screen shown during boot.
Jun 14 17:49:54 skywalker systemd[2237]: plasma-kcminit.service: start operation timed out. Terminating.
Jun 14 17:49:54 skywalker systemd[2237]: xdg-desktop-portal.service: start operation timed out. Terminating.
Jun 14 17:49:54 skywalker systemd[2237]: plasma-kcminit.service: Failed with result 'timeout'.
Jun 14 17:49:54 skywalker systemd[2237]: Failed to start plasma-kcminit.service - KDE Config Module Initialization.
Jun 14 17:49:54 skywalker systemd[2237]: Dependency failed for plasma-kcminit-phase1.service - KDE Configuration Module Initialization (Phase 1).
Jun 14 17:49:54 skywalker systemd[2237]: xdg-desktop-portal.service: Failed with result 'timeout'.
Jun 14 17:49:54 skywalker systemd[2237]: Failed to start xdg-desktop-portal.service - Portal service.
Jun 14 17:50:01 skywalker sudo[3467]: pam_limits(sudo:session): invalid line 3 in '/etc/security/limits.d/95-pipewire.conf' - skipped
Jun 14 17:50:01 skywalker sudo[3467]: pam_limits(sudo:session): invalid line 3 in '/etc/security/limits.d/95-pipewire.conf' - skipped
Jun 14 17:50:01 skywalker kernel: exFAT-fs (sdf1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jun 14 17:50:09 skywalker systemd[2237]: dbus-:1.2-org.kde.KSplash@0.service: Failed with result 'exit-code'.
Jun 14 17:50:19 skywalker /usr/libexec/xdg-desktop-portal[3442]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached
Jun 14 17:50:39 skywalker systemd[2237]: plasma-ksmserver.service: start operation timed out. Terminating.
Jun 14 17:50:39 skywalker systemd[2237]: xdg-desktop-portal.service: start operation timed out. Terminating.
Jun 14 17:50:39 skywalker systemd[2237]: plasma-kded6.service: start operation timed out. Terminating.
Jun 14 17:50:39 skywalker systemd[2237]: xdg-desktop-portal.service: Failed with result 'timeout'.
Jun 14 17:50:39 skywalker systemd[2237]: Failed to start xdg-desktop-portal.service - Portal service.
Jun 14 17:50:39 skywalker systemd[2237]: plasma-ksmserver.service: Failed with result 'timeout'.
Jun 14 17:50:39 skywalker systemd[2237]: Failed to start plasma-ksmserver.service - KDE Session Management Server.
Jun 14 17:50:39 skywalker systemd[2237]: plasma-kded6.service: Failed with result 'timeout'.
Jun 14 17:50:39 skywalker systemd[2237]: Failed to start plasma-kded6.service - KDE Daemon 6.
Jun 14 17:51:04 skywalker /usr/libexec/xdg-desktop-portal[3550]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached
Jun 14 17:51:20 skywalker systemd[2237]: plasma-plasmashell.service: start operation timed out. Terminating.
Jun 14 17:51:20 skywalker systemd[2237]: plasma-plasmashell.service: Failed with result 'timeout'.
Jun 14 17:51:20 skywalker systemd[2237]: Failed to start plasma-plasmashell.service - KDE Plasma Workspace.
Jun 14 17:51:25 skywalker systemd[2237]: xdg-desktop-portal.service: start operation timed out. Terminating.
Jun 14 17:51:25 skywalker systemd[2237]: xdg-desktop-portal.service: Failed with result 'timeout'.
Jun 14 17:51:25 skywalker systemd[2237]: Failed to start xdg-desktop-portal.service - Portal service.
Jun 14 17:51:25 skywalker systemd[2237]: plasma-kded6.service: start operation timed out. Terminating.
Jun 14 17:51:25 skywalker systemd[2237]: plasma-kded6.service: Failed with result 'timeout'.
Jun 14 17:51:25 skywalker systemd[2237]: Failed to start plasma-kded6.service - KDE Daemon 6.



I believe it may have to do with the graphics drivers? I have:

  • Created a new user from a vtty, shut down, and relogged in as the new user. Same issue, which I believe confirms nothing in user-space is the issue.
  • Booted from a live usb, which would confirm not a software-parsing-my-hardware issue, like issues I’ve seen with various monitor configs?
  • Additionally, using the previous kernel still works, although curiously, running inxi or fastfetch lists the “current distro” as (Fedora 43), just… using the fc42 kernel? I admittedly assumed that kernels and distros were backward incompatible, i.e., couldn’t load one labeled fc42 while being on the Fedora 43 distro.

inxi of working system:

indoorjetpacks@skywalker:.../usbdrive$ cat known-good_inxi-Fzxx_output.txt 
System:
  Kernel: 6.19.14-108.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 15.2.1
  Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Machine:
  Type: Desktop Mobo: Micro-Star model: PRO X670-P WIFI (MS-7D67) v: 1.0
    serial: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: 1.A0 date: 08/10/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 7700X bits: 64 type: MT MCP arch: Zen 4
    rev: 2 cache: L1: 512 KiB L2: 8 MiB L3: 32 MiB
  Speed (MHz): avg: 5175 min/max: 403/5576 boost: enabled cores: 1: 5175
    2: 5175 3: 5175 4: 5175 5: 5175 6: 5175 7: 5175 8: 5175 9: 5175 10: 5175
    11: 5175 12: 5175 13: 5175 14: 5175 15: 5175 16: 5175 bogomips: 144005
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: Micro-Star MSI
    driver: nvidia v: 580.159.04 arch: Ampere pcie: speed: 16 GT/s lanes: 16
    ports: active: DP-4,HDMI-A-2 empty: DP-5,DP-6 bus-ID: 01:00.0
    chip-ID: 10de:2487
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: Micro-Star MSI
    driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports:
    active: none empty: DP-1, DP-2, DP-3, HDMI-A-1, Writeback-1
    bus-ID: 18:00.0 chip-ID: 1002:164e temp: 56.0 C
  Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-5:5 chip-ID: 046d:085c
  Display: wayland server: Xwayland v: 24.1.12 compositor: kwin_wayland
    driver: gpu: nv_platform,nvidia,nvidia-nvswitch d-rect: 4480x1440
    display-ID: 0
  Monitor-1: DP-4 pos: primary,left model: Asus PB278 res: 2560x1440 hz: 60
    dpi: 109 diag: 685mm (27")
  Monitor-2: HDMI-A-2 pos: right model: Dell S2415H res: 1920x1080 hz: 60
    dpi: 93 diag: 604mm (23.8")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: radeonsi
    device: 3 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.159.04
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:2487 device: 1 type: integrated-gpu
    driver: mesa radv device-ID: 1002:164e device: 2 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:228b
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 18:00.1 chip-ID: 1002:1640
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 18:00.6 chip-ID: 1022:15e3
  Device-4: SteelSeries ApS Arctis Pro Wireless
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 3-3.3:13 chip-ID: 1038:1294
  Device-5: AKAI Professional M.I. APC MINI driver: snd-usb-audio type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-4.1:6 chip-ID: 09e8:0028
  Device-6: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-5:5 chip-ID: 046d:085c
  Device-7: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6:11
    chip-ID: 0db0:3130
  API: ALSA v: k6.19.14-108.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.11 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: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0
    chip-ID: 10ec:8125
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 0d:00.0
    chip-ID: 14c3:0616
  IF: wlp13s0 state: down mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 bus-ID: 3-7:12 chip-ID: 0e8d:0616
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 5.3 lmp-v: 12
Drives:
  Local Storage: total: 11.85 TiB used: 7.6 TiB (64.1%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD Blue SN570 500GB
    size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 46.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 840 Series size: 232.89 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 30 C
  ID-3: /dev/sdb vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 34 C
  ID-4: /dev/sdc vendor: Western Digital model: WD6003FZBX-00K5WB0
    size: 5.46 TiB speed: 6.0 Gb/s serial: <filter> temp: 46 C
  ID-5: /dev/sdd vendor: Toshiba model: HDWD120 size: 1.82 TiB
    speed: 6.0 Gb/s serial: <filter> temp: 41 C
  ID-6: /dev/sde vendor: Samsung model: SSD 870 EVO 4TB size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter> temp: 40 C
  ID-7: /dev/sdf vendor: PNY model: USB 2.0 FD size: 28.91 GiB type: USB
    rev: 2.0 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 93.24 GiB used: 46.6 GiB (50.0%) fs: ext4 dev: /dev/sdb2
  ID-2: /boot/efi size: 511 MiB used: 19.3 MiB (3.8%) fs: vfat
    dev: /dev/sdb1
  ID-3: /home size: 457.38 GiB used: 314.84 GiB (68.8%) fs: ext4
    dev: /dev/nvme0n1p1
  ID-4: /opt size: 294.23 GiB used: 93.37 GiB (31.7%) fs: ext4
    dev: /dev/sde1
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 4.22 GiB (52.7%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 15.62 GiB used: 1.45 GiB (9.3%)
    priority: -1 dev: /dev/sdb4
Sensors:
  System Temperatures: cpu: 68.8 C mobo: 46.2 C gpu: amdgpu temp: 57.0 C
  Fan Speeds (rpm): fan-1: 420 fan-2: 0 fan-3: 0 fan-4: 436 fan-5: 501
    fan-6: 525 fan-7: 0 fan-8: 389 fan-9: 0 fan-10: 0
Info:
  Memory: total: 64 GiB note: est. available: 61.94 GiB used: 14.7 GiB (23.7%)
  Processes: 624 Power: uptime: 17h 57m wakeups: 1 Init: systemd v: 258
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 28
    Compilers: gcc: 15.2.1 Shell: Bash v: 5.3.0 running-in: konsole inxi: 3.3.40

and the borked one, run from the vtty:

indoorjetpacks@skywalker:.../usbdrive$ cat brokenupdate_inxi-Fzxx_output2.txt
System:
  Kernel: 7.0.12-101.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Console: pty pts/0 DM: SDDM Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Machine:
  Type: Desktop Mobo: Micro-Star model: PRO X670-P WIFI (MS-7D67) v: 1.0 serial: <filter>
    Firmware: UEFI vendor: American Megatrends LLC. v: 1.A0 date: 08/10/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 7700X bits: 64 type: MT MCP arch: Zen 4 rev: 2 cache:
    L1: 512 KiB L2: 8 MiB L3: 32 MiB
  Speed (MHz): avg: 5229 min/max: 403/5576 boost: enabled cores: 1: 5229 2: 5229 3: 5229 4: 5229
    5: 5229 6: 5229 7: 5229 8: 5229 9: 5229 10: 5229 11: 5229 12: 5229 13: 5229 14: 5229 15: 5229
    16: 5229 bogomips: 144002
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: Micro-Star MSI driver: nouveau v: kernel
    arch: Ampere pcie: speed: 5 GT/s lanes: 16 ports: active: DP-4,HDMI-A-2 empty: DP-5,DP-6
    bus-ID: 01:00.0 chip-ID: 10de:2487
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: Micro-Star MSI driver: amdgpu
    v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1, DP-2,
    DP-3, HDMI-A-1, Writeback-1 bus-ID: 18:00.0 chip-ID: 1002:164e temp: 50.0 C
  Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-5:5 chip-ID: 046d:085c
  Display: unspecified server: Xwayland v: 24.1.12 compositor: kwin_wayland driver: gpu: nouveau
    tty: 240x67
  Monitor-1: DP-4 model: Asus PB278 res: 2560x1440 dpi: 109 diag: 685mm (27")
  Monitor-2: HDMI-A-2 model: Dell S2415H res: 1920x1080 dpi: 93 diag: 604mm (23.8")
  API: EGL v: 1.5 platforms: device: 0 drv: zink device: 1 drv: radeonsi device: 2 drv: swrast
    gbm: drv: zink surfaceless: drv: zink inactive: wayland,x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.6 note: console (EGL sourced)
    renderer: zink Vulkan 1.4(NVIDIA GeForce RTX 3060 (NVK GA104) (MESA_NVK)), AMD Ryzen 7 7700X
    8-Core Processor (radeonsi raphael_mendocino LLVM 21.1.8 DRM 3.64 7.0.12-101.fc43.x86_64),
    llvmpipe (LLVM 21.1.8 256 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 18:00.1
    chip-ID: 1002:1640
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 18:00.6
    chip-ID: 1022:15e3
  Device-4: SteelSeries ApS Arctis Pro Wireless driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 3-3.3:7 chip-ID: 1038:1294
  Device-5: AKAI Professional M.I. APC MINI driver: snd-usb-audio type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-4.1:6 chip-ID: 09e8:0028
  Device-6: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-5:5 chip-ID: 046d:085c
  Device-7: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-6:11 chip-ID: 0db0:3130
  API: ALSA v: k7.0.12-101.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.11 status: n/a (root, process) with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack
    type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0 chip-ID: 10ec:8125
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 14c3:0616
  IF: wlp13s0 state: down mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s
    lanes: 1 bus-ID: 3-7:12 chip-ID: 0e8d:0616
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter> bt-v: 5.3 lmp-v: 12
Drives:
  Local Storage: total: 11.85 TiB used: 7.59 TiB (64.0%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD Blue SN570 500GB size: 465.76 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 41.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 840 Series size: 232.89 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 33 C
  ID-3: /dev/sdb vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
    serial: <filter> temp: 35 C
  ID-4: /dev/sdc vendor: Western Digital model: WD6003FZBX-00K5WB0 size: 5.46 TiB
    speed: 6.0 Gb/s serial: <filter> temp: 46 C
  ID-5: /dev/sdd vendor: Toshiba model: HDWD120 size: 1.82 TiB speed: 6.0 Gb/s serial: <filter>
    temp: 41 C
  ID-6: /dev/sde vendor: Samsung model: SSD 870 EVO 4TB size: 3.64 TiB speed: 6.0 Gb/s
    serial: <filter> temp: 47 C
  ID-7: /dev/sdf vendor: PNY model: USB 2.0 FD size: 28.91 GiB type: USB rev: 2.0 spd: 480 Mb/s
    lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 93.24 GiB used: 46.61 GiB (50.0%) fs: ext4 dev: /dev/sdb2
  ID-2: /boot/efi size: 511 MiB used: 19.3 MiB (3.8%) fs: vfat dev: /dev/sdb1
  ID-3: /home size: 457.38 GiB used: 314.75 GiB (68.8%) fs: ext4 dev: /dev/nvme0n1p1
  ID-4: /opt size: 294.23 GiB used: 93.37 GiB (31.7%) fs: ext4 dev: /dev/sde1
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 15.62 GiB used: 0 KiB (0.0%) priority: -1 dev: /dev/sdb4

I can see that the drivers are different:

Functional:

Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: Micro-Star MSI
    driver: nvidia v: 580.159.04

Broken:

Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: Micro-Star MSI driver: nouveau v: kernel

But I am unsure why it would work on a live system, but not with the update? Also, would installing the nvidia driver for fc43/kernel 7.0..fc43.x86_64 break my currently-functioning fc43/kernel6.x…fc42.x86_64? I would think that drivers and kernels things are connected to the distro, but the.. fc43 running on fc42 kernel makes me think I am incorrect in my understanding, and don’t really want to break the 6.x kernel install by installing something on the 7.x kernel install.

Any help would be greatly appreciated, and any corrections with any of the things I’ve said (especially the…kernel/distro/drivers relationship) would be appreciated. I am still trying to “learn to fish” in terms of troubleshooting for linux as it were.

Hi. First off, thanks for your thorough description of your problem.

No, they may usually be compatible. For example, we saw recently a case of a F42
distro running with a fc38 kernel.

However, there is a notable potential incompatibility: the version of the nvidia
kernel module should exactly match the one of the userland related software.

In your case, it seems that the nvidia kernel module did not load in the
7.0.12-101.fc43.x86_64 kernel.

Are you using the rpmfusion repositories for the nvidia drivers ?

They are providing the exact same version as you currently have (with the fc42 kernel):

dnf -q list --releasever=43 list akmod-nvidia
Available packages
akmod-nvidia.x86_64 3:580.159.04-1.fc43 rpmfusion-nonfree-updates

Also, can you boot with the working kernel (6.19.14-108.fc42.x86_64), start a root shell
with sudo bash -l and post here what gives:

(
  set -x
  modinfo -k 7.0.12-101.fc43.x86_64 -F version nvidia
  dnf -q list --installed kernel \*nvidia\*
  dnf -q repolist
)

If modinfo gives no output or fails, and assuming you are using rpmfusion, try to rebuild the kmod with:

  • akmods --rebuild --kernels 7.0.12-101.fc43.x86_64 --akmod nvidia

Hello! Thanks, I tried to do enough research/collect enough info that I would ask someone if they told me the issue :laughing:

Thank you! That is interesting and now I will do more research about…how distro releases and the kernel are connected. As I understood it a distro was whatever various decisions about what to include from the upstream of the kernel, so I thought that newer distro versions would not be able to load on older kernels. Although I suppose if nothing-enough-changed with a newer distro release that makes sense?

In any case, yes, as far as I know, I am using the rpmfusion repositories.

It looks like modinfo does fail:

+ modinfo -k 7.0.12-101.fc43.x86_64 -F version nvidia
modinfo: ERROR: Module nvidia not found.

Should the rebuild also be run in the same root login shell?

I believe I understand what that does (rebuilds the module for the nvidia drivers, for that kernel) which…does not get loaded unless that kernel is started? Through whatever that process is that is definitely out of scope for this question haha.

Here is the additional output:

+ dnf -q list --installed kernel '*nvidia*'
Installed packages
akmod-nvidia.x86_64                        3:580.159.04-1.fc43 <unknown>
kernel.x86_64                              6.19.14-100.fc42    updates
kernel.x86_64                              6.19.14-108.fc42    <unknown>
kernel.x86_64                              7.0.12-101.fc43     <unknown>
kmod-nvidia-6.19.14-100.fc42.x86_64.x86_64 3:580.159.04-1.fc43 @commandline
kmod-nvidia-6.19.14-108.fc42.x86_64.x86_64 3:580.159.04-1.fc43 @commandline
kmod-nvidia-7.0.12-101.fc43.x86_64.x86_64  3:580.159.04-1.fc43 <unknown>
libnvidia-container-tools.x86_64           1.19.1-1            <unknown>
libnvidia-container1.x86_64                1.19.1-1            <unknown>
nvidia-container-toolkit.x86_64            1.19.1-1            <unknown>
nvidia-container-toolkit-base.x86_64       1.19.1-1            <unknown>
nvidia-gpu-firmware.noarch                 20260519-1.fc43     <unknown>
nvidia-modprobe.x86_64                     3:580.159.04-1.fc43 <unknown>
nvidia-persistenced.x86_64                 3:580.159.04-1.fc43 <unknown>
nvidia-settings.x86_64                     3:580.159.04-1.fc43 <unknown>
nvidia-texture-tools.x86_64                2.1.2-15.fc43       <unknown>
xorg-x11-drv-nvidia.x86_64                 3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-cuda.x86_64            3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-cuda-libs.i686         3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-cuda-libs.x86_64       3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-kmodsrc.x86_64         3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-libs.i686              3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-libs.x86_64            3:580.159.04-1.fc43 <unknown>
xorg-x11-drv-nvidia-power.x86_64           3:580.159.04-1.fc43 <unknown>
+ dnf -q repolist
repo id                                                              repo name                                                                
Adoptium                                                             Adoptium                                                                 
copr:copr.fedorainfracloud.org:g3tchoo:prismlauncher                 Copr repo for prismlauncher owned by g3tchoo                             
copr:copr.fedorainfracloud.org:teervo:helm-synth                     Copr repo for helm-synth owned by teervo                                 
fedora                                                               Fedora 43 - x86_64                                                       
fedora-cisco-openh264                                                Fedora 43 openh264 (From Cisco) - x86_64                                 
gitlab.com_paulcarroty_vscodium_repo                                 download.vscodium.com                                                    
nvidia-container-toolkit                                             nvidia-container-toolkit                                                 
protonvpn-fedora-stable                                              ProtonVPN Fedora Stable repository                                       
rpmfusion-free                                                       RPM Fusion for Fedora 43 - Free                                          
rpmfusion-free-updates                                               RPM Fusion for Fedora 43 - Free - Updates                                
rpmfusion-nonfree                                                    RPM Fusion for Fedora 43 - Nonfree                                       
rpmfusion-nonfree-updates                                            RPM Fusion for Fedora 43 - Nonfree - Updates                             
slack                                                                slack                                                                    
updates                                                              Fedora 43 - x86_64 - Updates                                             
virtio-win-stable                                                    virtio-win builds roughly matching what was shipped in latest RHEL       
WineHQ 

Curiously, the repos list as <unknown>. More forum searching points me here: After F41 upgrade, dnf list shows repository as "unknown" , as well as the wiki here: Changes/SwitchToDnf5 - Fedora Project Wiki

which I believe would make sense as this was originally setup as fedora 40 if i remember correctly. Running the list query with dnf4 shows the repo source correctly:

+ dnf4 -q list --installed kernel '*nvidia*'
Installed Packages
akmod-nvidia.x86_64                                                  3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
kernel.x86_64                                                        6.19.14-100.fc42                               @System                   
kernel.x86_64                                                        6.19.14-108.fc42                               @updates                  
kernel.x86_64                                                        7.0.12-101.fc43                                @updates                  
kmod-nvidia-6.19.14-100.fc42.x86_64.x86_64                           3:580.159.04-1.fc43                            @System                   
kmod-nvidia-6.19.14-108.fc42.x86_64.x86_64                           3:580.159.04-1.fc43                            @System                   
kmod-nvidia-7.0.12-101.fc43.x86_64.x86_64                            3:580.159.04-1.fc43                            @System                   
libnvidia-container-tools.x86_64                                     1.19.1-1                                       @nvidia-container-toolkit 
libnvidia-container1.x86_64                                          1.19.1-1                                       @nvidia-container-toolkit 
nvidia-container-toolkit.x86_64                                      1.19.1-1                                       @nvidia-container-toolkit 
nvidia-container-toolkit-base.x86_64                                 1.19.1-1                                       @nvidia-container-toolkit 
nvidia-gpu-firmware.noarch                                           20260519-1.fc43                                @updates                  
nvidia-modprobe.x86_64                                               3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
nvidia-persistenced.x86_64                                           3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
nvidia-settings.x86_64                                               3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
nvidia-texture-tools.x86_64                                          2.1.2-15.fc43                                  @updates                  
xorg-x11-drv-nvidia.x86_64                                           3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda.x86_64                                      3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda-libs.i686                                   3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda-libs.x86_64                                 3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-kmodsrc.x86_64                                   3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-libs.i686                                        3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-libs.x86_64                                      3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-power.x86_64                                     3:580.159.04-1.fc43                            @rpmfusion-nonfree-updates

To make sure nothing else was odd, I did some searching to confirm what dnf version i’m using and that seems to be correct, so I am not sure why dnf5 would:

ndoorjetpacks@skywalker:/$ readlink -f /usr/bin/dnf
/usr/bin/dnf5
indoorjetpacks@skywalker:/$ dnf5 --version
dnf5 version 5.2.18.0
dnf5 plugin API version 2.0
libdnf5 version 5.2.18.0
libdnf5 plugin API version 2.2

Loaded dnf5 plugins:
  name: builddep
  version: 1.0.0
  API version: 2.0

  name: changelog
  version: 1.0.0
  API version: 2.0

  name: config-manager
  version: 0.1.0
  API version: 2.0

  name: copr
  version: 0.1.0
  API version: 2.0

  name: needs_restarting
  version: 1.0.0
  API version: 2.0

  name: repoclosure
  version: 1.0.0
  API version: 2.0

  name: repomanage
  version: 1.0.0
  API version: 2.0

  name: reposync
  version: 1.0.0
  API version: 2.0

Loaded libdnf5 plugins:
  name: expired-pgp-keys
  version: 1.0.0
  API version: 2.1

  name: notify_packagekit
  version: 1.3.4
  API version: 2.2

Also, can you boot with the working kernel (6.19.14-108.fc42.x86_64), start a root shell
with sudo bash -l

Out of curiosity, is there any specific reason to do a new bash login as root shell (instead of running it in the current shell and prefixed with root? Or is it more.. to avoid any strangeness with user-space…anything? :sweat_smile:

This shows that akmods has properly build and installed the kmod RPM, but the nvidia module is still unknown to modinfo.

This could happen if a reboot took place during the postinstall of this RPM. this
postinstall does a depmod, mandatory for the just installed kernel module to be used
(by modprobe modinfo …).

One may, but not 100% sure, have a log of that in /var/cache/akmods/nvidia/*failed.log

Simpler: rebuild as I said. See below.

Not mandatory, but correct: akmods needs to be run as root.

You may prefer to run from your user shell:

  • sudo akmods --rebuild --kernels 7.0.12-101.fc43.x86_64 --akmod nvidia

The later, to prevent the case where the root shell has been changed to a different shell
than bash. I use set -x that is bash (sh) specific.

You may try from a root bash shell:

(
  set -x
  depmod 7.0.12-101.fc43.x86_64
  modinfo -k 7.0.12-101.fc43.x86_64 -F version nvidia
)

and if the modinfo is successful, no need to rebuild.

After either that or a rebuild, reboot to the 7.0.12 kernel.

Fantastic :smiley: The rebuild seems to have worked after a reboot!

+ modinfo -k 7.0.12-101.fc43.x86_64 -F version nvidia
580.159.04

Thanks for your help and for the excellent explanations :slight_smile:

Thanks.

This is a well known problem.
I fixed it in some pull-request … that was rejected :frowning: