F41 crashing on connecting External Monitor in KDE Plasma. Working fine in Xfce

Ask Fedora
, , , ,
1

When I’m connecting External Monitor to my F41 laptop, both the screens (laptop & external monitor) are turning black & after sometime, I’m back in SDDM login screen.

If I try to login again, I’m again getting the black screen & back to SDDM login screen. Login loop basically.

If I remove the HDMI & login, then it is working.

If I remove the following boot parameters, I’m able to login with the External Monitor connected:

rd.driver.blacklist=nouveau modprobe.blacklist=nouveau

Only facing this issue in KDE Plasma. Xfce is working fine.

journalctl logs:

Jan 14 10:45:53 fedora systemd[1887]: Started drkonqi-coredump-launcher@754-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:53 fedora drkonqi-coredump-launcher[13272]: Unable to find file for pid 16498 expected at "kcrash-metadata/gmenudbusmenuproxy.31b045bf5dd8404c9330523d61f7684f.16498.ini"
Jan 14 10:45:53 fedora systemd[1887]: Started drkonqi-coredump-launcher@755-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:53 fedora drkonqi-coredump-launcher[13275]: Unable to find file for pid 16534 expected at "kcrash-metadata/org_kde_powerdevil.31b045bf5dd8404c9330523d61f7684f.16534.ini"
Jan 14 10:45:53 fedora systemd[1887]: Started drkonqi-coredump-launcher@756-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:53 fedora drkonqi-coredump-launcher[13278]: Unable to find file for pid 16550 expected at "kcrash-metadata/xembedsniproxy.31b045bf5dd8404c9330523d61f7684f.16550.ini"
Jan 14 10:45:53 fedora systemd[1887]: Started drkonqi-coredump-launcher@757-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13281]: Unable to find file for pid 16548 expected at "kcrash-metadata/kaccess.31b045bf5dd8404c9330523d61f7684f.16548.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@758-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13284]: Unable to find file for pid 16576 expected at "kcrash-metadata/xdg-desktop-portal-kde.31b045bf5dd8404c9330523d61f7684f.16576.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@759-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13286]: Unable to find file for pid 16672 expected at "kcrash-metadata/org_kde_powerdevil.31b045bf5dd8404c9330523d61f7684f.16672.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@760-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13288]: Unable to find file for pid 20422 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.20422.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@761-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13292]: Unable to find file for pid 20527 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.20527.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@762-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13294]: Unable to find file for pid 20647 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.20647.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@763-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13298]: Unable to find file for pid 20759 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.20759.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@764-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13300]: Unable to find file for pid 20882 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.20882.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@765-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13303]: Unable to find file for pid 21000 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.21000.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@766-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13306]: Unable to find file for pid 21122 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.21122.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@767-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13310]: Unable to find file for pid 21243 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.21243.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@768-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13312]: Unable to find file for pid 21352 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.21352.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@769-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13315]: Unable to find file for pid 21474 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.21474.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@770-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13318]: Unable to find file for pid 21581 expected at "kcrash-metadata/kwin_wayland.31b045bf5dd8404c9330523d61f7684f.21581.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@771-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13322]: Unable to find file for pid 20432 expected at "kcrash-metadata/kcminit.31b045bf5dd8404c9330523d61f7684f.20432.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@772-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13326]: Unable to find file for pid 21596 expected at "kcrash-metadata/drkonqi.31b045bf5dd8404c9330523d61f7684f.21596.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@773-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13329]: Unable to find file for pid 20654 expected at "kcrash-metadata/drkonqi.31b045bf5dd8404c9330523d61f7684f.20654.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@774-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13332]: Unable to find file for pid 20428 expected at "kcrash-metadata/ksplashqml.31b045bf5dd8404c9330523d61f7684f.20428.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@775-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13334]: Unable to find file for pid 21020 expected at "kcrash-metadata/drkonqi.31b045bf5dd8404c9330523d61f7684f.21020.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@776-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13337]: Unable to find file for pid 21119 expected at "kcrash-metadata/drkonqi.31b045bf5dd8404c9330523d61f7684f.21119.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@777-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13341]: Unable to find file for pid 20879 expected at "kcrash-metadata/drkonqi.31b045bf5dd8404c9330523d61f7684f.20879.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@778-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:54 fedora drkonqi-coredump-launcher[13344]: Unable to find file for pid 20538 expected at "kcrash-metadata/drkonqi.31b045bf5dd8404c9330523d61f7684f.20538.ini"
Jan 14 10:45:54 fedora systemd[1887]: Started drkonqi-coredump-launcher@779-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13347]: Unable to find file for pid 21818 expected at "kcrash-metadata/kded6.31b045bf5dd8404c9330523d61f7684f.21818.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@780-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13350]: Unable to find file for pid 21813 expected at "kcrash-metadata/ksmserver.31b045bf5dd8404c9330523d61f7684f.21813.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@781-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13353]: Unable to find file for pid 22062 expected at "kcrash-metadata/gmenudbusmenuproxy.31b045bf5dd8404c9330523d61f7684f.22062.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@782-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13356]: Unable to find file for pid 22038 expected at "kcrash-metadata/kdeconnectd.31b045bf5dd8404c9330523d61f7684f.22038.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@783-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13357]: Unable to find file for pid 22074 expected at "kcrash-metadata/xembedsniproxy.31b045bf5dd8404c9330523d61f7684f.22074.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@784-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13362]: Unable to find file for pid 22043 expected at "kcrash-metadata/xwaylandvideobridge.31b045bf5dd8404c9330523d61f7684f.22043.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@785-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13365]: Unable to find file for pid 22064 expected at "kcrash-metadata/kaccess.31b045bf5dd8404c9330523d61f7684f.22064.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@786-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13368]: Unable to find file for pid 22066 expected at "kcrash-metadata/plasmashell.31b045bf5dd8404c9330523d61f7684f.22066.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@787-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13370]: Unable to find file for pid 22072 expected at "kcrash-metadata/xdg-desktop-portal-kde.31b045bf5dd8404c9330523d61f7684f.22072.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@788-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13373]: Unable to find file for pid 22070 expected at "kcrash-metadata/org_kde_powerdevil.31b045bf5dd8404c9330523d61f7684f.22070.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@789-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13377]: Unable to find file for pid 22262 expected at "kcrash-metadata/gmenudbusmenuproxy.31b045bf5dd8404c9330523d61f7684f.22262.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@790-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13380]: Unable to find file for pid 22352 expected at "kcrash-metadata/xembedsniproxy.31b045bf5dd8404c9330523d61f7684f.22352.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@791-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13382]: Unable to find file for pid 22348 expected at "kcrash-metadata/kaccess.31b045bf5dd8404c9330523d61f7684f.22348.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@792-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13386]: Unable to find file for pid 22455 expected at "kcrash-metadata/gmenudbusmenuproxy.31b045bf5dd8404c9330523d61f7684f.22455.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@793-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13389]: Unable to find file for pid 22390 expected at "kcrash-metadata/plasmashell.31b045bf5dd8404c9330523d61f7684f.22390.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@794-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13391]: Unable to find file for pid 22415 expected at "kcrash-metadata/xdg-desktop-portal-kde.31b045bf5dd8404c9330523d61f7684f.22415.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@795-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13395]: Unable to find file for pid 22444 expected at "kcrash-metadata/org_kde_powerdevil.31b045bf5dd8404c9330523d61f7684f.22444.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@796-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13398]: Unable to find file for pid 22522 expected at "kcrash-metadata/xembedsniproxy.31b045bf5dd8404c9330523d61f7684f.22522.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@797-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13402]: Unable to find file for pid 22526 expected at "kcrash-metadata/kaccess.31b045bf5dd8404c9330523d61f7684f.22526.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@798-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13405]: Unable to find file for pid 22591 expected at "kcrash-metadata/gmenudbusmenuproxy.31b045bf5dd8404c9330523d61f7684f.22591.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@799-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:55 fedora drkonqi-coredump-launcher[13407]: Unable to find file for pid 22597 expected at "kcrash-metadata/xdg-desktop-portal-kde.31b045bf5dd8404c9330523d61f7684f.22597.ini"
Jan 14 10:45:55 fedora systemd[1887]: Started drkonqi-coredump-launcher@800-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:56 fedora drkonqi-coredump-launcher[13411]: Unable to find file for pid 22649 expected at "kcrash-metadata/xembedsniproxy.31b045bf5dd8404c9330523d61f7684f.22649.ini"
Jan 14 10:45:56 fedora systemd[1887]: Started drkonqi-coredump-launcher@801-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:56 fedora drkonqi-coredump-launcher[13413]: Unable to find file for pid 22648 expected at "kcrash-metadata/kaccess.31b045bf5dd8404c9330523d61f7684f.22648.ini"
Jan 14 10:45:56 fedora systemd[1887]: Started drkonqi-coredump-launcher@802-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:56 fedora drkonqi-coredump-launcher[13417]: Unable to find file for pid 22619 expected at "kcrash-metadata/plasmashell.31b045bf5dd8404c9330523d61f7684f.22619.ini"
Jan 14 10:45:56 fedora systemd[1887]: Started drkonqi-coredump-launcher@803-9555-1000.service - Launch DrKonqi for a systemd-coredump crash (PID 9555/UID 1000).
Jan 14 10:45:56 fedora drkonqi-coredump-launcher[13419]: Unable to find file for pid 22641 expected at "kcrash-metadata/org_kde_powerdevil.31b045bf5dd8404c9330523d61f7684f.22641.ini"
2

We need the info about the nvidia driver and system config.
It seems that something related to using the nvidia driver may be causing this since when nouveau is allowed to load it does not happen.
dnf list --installed \*nvidia\* for the driver info
inxi -Fzxx for the system info

3

dnf list --installed \*nvidia\*

Installed packages
akmod-nvidia.x86_64                       3:565.77-1.fc41                  rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.12.6-200.fc41.x86_64.x86_64 3:565.77-1.fc41                  @commandline
kmod-nvidia-6.12.7-200.fc41.x86_64.x86_64 3:565.77-1.fc41                  @commandline
kmod-nvidia-6.12.8-200.fc41.x86_64.x86_64 3:565.77-1.fc41                  @commandline
libva-nvidia-driver.x86_64                0.0.13^20241108git259b7b7-2.fc41 <unknown>
nvidia-gpu-firmware.noarch                20241210-1.fc41                  updates
nvidia-modprobe.x86_64                    3:565.77-1.fc41                  rpmfusion-nonfree-nvidia-driver
nvidia-persistenced.x86_64                3:565.77-1.fc41                  rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                    3:565.77-1.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64                3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64           3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.i686        3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64      3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64        3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.i686             3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64           3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64          3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-xorg-libs.x86_64      3:565.77-3.fc41                  rpmfusion-nonfree-nvidia-driver

inxi -Fzxx

System:
  Kernel: 6.12.8-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-5.fc41
  Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 41 (Forty One)
Machine:
  Type: Laptop System: ASUSTeK product: TUF Gaming FX505DT_FX505DT v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: FX505DT v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: FX505DT.316 date: 01/28/2021
Battery:
  ID-1: BAT0 charge: 24.8 Wh (82.1%) condition: 30.2/48.2 Wh (62.7%)
    volts: 10.7 min: 11.9 model: FX50442 serial: N/A status: discharging
CPU:
  Info: quad core model: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
    bits: 64 type: MT MCP arch: Zen/Zen+ note: check rev: 1 cache: L1: 384 KiB
    L2: 2 MiB L3: 4 MiB
  Speed (MHz): avg: 2393 min/max: 1400/2100 boost: enabled cores: 1: 2393
    2: 2393 3: 2393 4: 2393 5: 2393 6: 2393 7: 2393 8: 2393 bogomips: 33537
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: ASUSTeK
    driver: nvidia v: 565.77 arch: Turing pcie: speed: 2.5 GT/s lanes: 8 ports:
    active: none empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1f91
  Device-2: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
    Series / Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel
    arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: none
    bus-ID: 05:00.0 chip-ID: 1002:15d8 temp: 50.0 C
  Device-3: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 13d3:56a2
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau,radeon alternate: fbdev,nv,vesa
    dri: radeonsi gpu: nvidia,amdgpu display-ID: 0
  Monitor-1: eDP-1 res: 1600x900 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 1 drv: radeonsi
    gbm: drv: kms_swrast surfaceless: drv: nvidia wayland: drv: radeonsi x11:
    drv: radeonsi
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 24.3.2 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Vega 8 Graphics (radeonsi raven
    LLVM 19.1.5 DRM 3.59 6.12.8-200.fc41.x86_64) device-ID: 1002:15d8
    display-ID: :0.0
  API: Vulkan v: 1.3.296 surfaces: xcb,xlib,wayland device: 0
    type: integrated-gpu driver: N/A device-ID: 1002:15d8 device: 1
    type: discrete-gpu driver: N/A device-ID: 10de:1f91 device: 2 type: cpu
    driver: N/A device-ID: 10005:0000
Audio:
  Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:10fa
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
    lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3
  Device-3: GN Netcom Jabra EVOLVE 20 MS driver: jabra,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-2:2 chip-ID: 0b0e:0300
  API: ALSA v: k6.12.8-200.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
    vendor: AzureWave driver: rtw_8822be v: N/A pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 04:00.0 chip-ID: 10ec:b822
  IF: wlp4s0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 13d3:3526
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 1.38 TiB used: 120.66 GiB (8.6%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 38.9 C
  ID-2: /dev/sda vendor: Crucial model: CT1000BX500SSD1 size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 28 C
Partition:
  ID-1: / size: 196.3 GiB used: 120.61 GiB (61.4%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 1023 MiB used: 52.7 MiB (5.2%) fs: vfat
    dev: /dev/nvme0n1p1
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: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p4
Sensors:
  System Temperatures: cpu: 52.1 C mobo: N/A gpu: amdgpu temp: 52.0 C
  Fan Speeds (rpm): cpu: 2800
Info:
  Memory: total: 24 GiB available: 23.27 GiB used: 6.01 GiB (25.8%)
  Processes: 318 Power: uptime: 2h 10m wakeups: 1 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: clang: 19.1.5
    gcc: 14.2.1 Shell: Bash v: 5.2.32 running-in: konsole inxi: 3.3.36
4

I see 2 things that I would investigate.

  • The libva-nvidia-driver may not be necessary. You might try removing it first then work on getting the external monitor working before worrying about that package.
    sudo dnf remove libva-nvidia-driver --noautoremove

  • Once that is done then rebuild the nvidia driver.
    sudo akmods --rebuild --force.

After the rebuild completes see if a reboot solves the problem with the external monitor.

You can always reinstall the libva-nvidia-driver package if it is necessary.

I am not sure if I understand the config.
Is this a single machine with both KDE Plasma and Xfce as desktops on the same system?

EDIT
I notice that the firmware has a date of 01/28/2021. Is that the latest available firmware?

Some systems have shown problems with the latest kernels when running older firmware and updating the firmware often fixes them.
sudo fwupdmgr get-updates will show if there is firmware that can be updated from within linux. If there are available updates then sudo fwupdmgr update should perform the updates.

The asus web site shows this for the bios firmware

image
image1310×898 90.8 KB

5

I tried these:
sudo dnf remove libva-nvidia-driver --noautoremove
sudo akmods --rebuild --force
it didn’t resolved the issue.

Is this a single machine with both KDE Plasma and Xfce as desktops on the same system?

Yes, I was using Xfce for the last 6 months & installed KDE Plasma just 3 days ago on the same system with:
dnf group install kde-desktop-environment

Xfce was running on X11 & KDE Plasma is on Wayland (I guess, I’m just using the default).

I notice that the firmware has a date of 01/28/2021. Is that the latest available firmware?

Yeah it seems so, I check in that website too.

sudo fwupdmgr get-updates is telling me “No updates available”.

6

Should I try reinstalling the Nvidia proprietary drivers?

7

Maybe try the plasma x11 session (i guess sudo dnf install plasma-workspace-x11)

1 Like
8

Maybe try the plasma x11 session (i guess sudo dnf install plasma-workspace-x11)

Yes, this is working as expected but every youtuber & redditer is shouting to switch to Wayland. :sweat_smile: