Fedora 41 Login Screen Delay with Wayland, KDE Plasma

Hi,

I’m using Fedora 41 with Wayland and KDE Plasma on an HP Victus notebook. My system has both an AMD integrated GPU and an NVIDIA discrete GPU. I installed the NVIDIA drivers from RPM Fusion and have applied all updates.

When I enter my password on the login screen and press Enter, the system freezes for about 1 minute. During this time, I only see the splash screen. If I disable the splash screen, I get a black screen instead, and the system remains unresponsive for the same amount of time. Once the system finally logs in, everything appears to work fine.

To debug, I tested the same installation USB on my desktop PC, which only has an NVIDIA GPU (no integrated GPU). On the desktop, after entering the password, the splash screen briefly appears and the system logs in instantly without any delays.

For reference, here’s a small issue I encountered on the desktop (unrelated to the primary problem): when the monitor goes to sleep, it doesn’t wake up with mouse or keyboard input. I have to turn the monitor off and on to fix it. The monitor is connected via DisplayPort, so this may be the cause.

I’m attaching the outputs of journalctl, systemd-analyze, and inxi for further context.

Could anyone help me troubleshoot this login delay issue on my HP Victus notebook?

Thanks in advance!
journalctl-lastboot-btwifienabled
inxi-SFmxxz
systemd-analyze-user-blame-btwifienabled

Those google drive documents are useless to me. Review them yourself and try to identify each single line. It cannot reasonably be done on my system.

Instead please post the content here by copy and paste using the preformatted text tags so the display is formatted exactly as seen on-screen.

That can easily be done by placing ``` on the lines preceding and following the pasted text or by highlighting the pasted text then click the </> button on the toolbar for the text entry screen.

1 Like

Hi Jeff,

First of all, thank you for your help. I’ve already checked the logs and am sharing the filtered parts from journalctl that caught my attention:

Oca 10 14:24:17 fedora systemd[1676]: app-org.kde.plasma\x2dfallback\x2dsession\x2drestore@autostart.service: Control process exited, code=killed, status=15/TERM
Oca 10 14:24:17 fedora systemd[1676]: app-org.kde.plasma\x2dfallback\x2dsession\x2drestore@autostart.service: Failed with result 'timeout'.
Oca 10 14:24:17 fedora systemd[1676]: Failed to start app-org.kde.plasma\x2dfallback\x2dsession\x2drestore@autostart.service - Plasma Session Restore.
Oca 10 14:24:17 fedora systemd[1676]: app-spice\x2dvdagent@autostart.service: Control process exited, code=killed, status=15/TERM
Oca 10 14:24:17 fedora systemd[1676]: app-spice\x2dvdagent@autostart.service: Failed with result 'timeout'.
Oca 10 14:24:17 fedora systemd[1676]: Failed to start app-spice\x2dvdagent@autostart.service - Spice vdagent.
Oca 10 14:24:17 fedora systemd[1676]: plasma-powerdevil.service: start operation timed out. Terminating.
Oca 10 14:24:17 fedora systemd[1676]: plasma-powerdevil.service: Failed with result 'timeout'.
Oca 10 14:24:17 fedora systemd[1676]: Failed to start plasma-powerdevil.service - Powerdevil.
Oca 10 14:24:17 fedora systemd[1676]: xdg-desktop-portal.service: start operation timed out. Terminating.
Oca 10 14:24:17 fedora systemd[1676]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 2.
Oca 10 14:24:17 fedora systemd[1676]: Starting plasma-powerdevil.service - Powerdevil...
Oca 10 14:24:17 fedora systemd[1676]: xdg-desktop-portal.service: Failed with result 'timeout'.
Oca 10 14:24:17 fedora systemd[1676]: Failed to start xdg-desktop-portal.service - Portal service.

The output of systemd-analyze user-blame is as follows:

1min 16.460s app-org.kde.kalendarac@autostart.service
     45.244s app-at\x2dspi\x2ddbus\x2dbus@autostart.service
     45.226s app-imsettings\x2dstart@autostart.service
     45.226s app-geoclue\x2ddemo\x2dagent@autostart.service
     45.223s app-org.freedesktop.problems.applet@autostart.service
     45.220s app-org.kde.kdeconnect.daemon@autostart.service
     45.220s app-liveinst\x2dsetup@autostart.service
     45.218s app-org.kde.plasma\x2dfallback\x2dsession\x2drestore@autostart.service
     45.216s app-nvidia\x2dsettings\x2duser@autostart.service
     45.216s app-spice\x2dvdagent@autostart.service
     45.216s app-org.kde.kunifiedpush\x2ddistributor@autostart.service
     45.214s app-orca\x2dautostart@autostart.service
     45.214s app-org.kde.xwaylandvideobridge@autostart.service
     45.213s app-org.kde.kgpg@autostart.service
     45.213s app-org.kde.discover.notifier@autostart.service
     45.210s app-vmware\x2duser@autostart.service
     45.205s app-xdg\x2duser\x2ddirs@autostart.service
     45.205s app-xdg\x2duser\x2ddirs\x2dkde@autostart.service
     33.154s plasma-powerdevil.service
     32.336s xdg-desktop-portal.service
      7.261s xdg-desktop-portal-gtk.service
      3.772s grub-boot-success.service
       913ms plasma-kcminit.service
       180ms plasma-plasmashell.service
       172ms plasma-ksmserver.service
       145ms plasma-kded6.service
       143ms plasma-baloorunner.service
       142ms plasma-xdg-desktop-portal-kde.service
       132ms plasma-kactivitymanagerd.service
       106ms plasma-polkit-agent.service
        62ms dconf.service
        58ms plasma-kcminit-phase1.service
        42ms app-anydesk@autostart.service
        42ms at-spi-dbus-bus.service
        41ms app-anydesk_global_tray@autostart.service
        37ms gvfs-daemon.service
        37ms xdg-document-portal.service
        28ms plasma-kglobalaccel.service
        27ms kde-baloo.service
        14ms unity-gtk-module.service
        11ms obex.service
        11ms plasma-kwin_wayland.service
         8ms dbus.socket
         7ms uresourced.service
         7ms plasma-restoresession.service
         6ms systemd-tmpfiles-setup.service
         6ms dbus-broker.service
         5ms app-vboxclient@autostart.service
         5ms xdg-permission-store.service
         4ms ssh-agent.service
         3ms plasma-ksplash-ready.service

The inxi report looks like this:

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 (KDE Plasma)
Machine:
  Type: Laptop System: HP product: Victus by HP Gaming Laptop 16-s0xxx
    v: Type1ProductConfigId serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: HP model: 8BD4 v: 79.53 serial: <superuser required>
    part-nu: 7Z4L9EA#AB8 UEFI: Insyde v: F.26 date: 10/16/2024
Battery:
  ID-1: BAT1 charge: 69.5 Wh (100.0%) condition: 69.5/70.1 Wh (99.2%)
    volts: 17.0 min: 15.4 model: Hewlett-Packard PABAS0241231 serial: <filter>
    status: full
Memory:
  System RAM: total: 32 GiB available: 30.62 GiB used: 4.72 GiB (15.4%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Bottom - Slot 1 (top) type: DDR5 size: 16 GiB speed: 5600 MT/s
    volts: 1 note: check manufacturer: Hynix part-no: HMCG78AGBSA095N
  Device-2: Bottom - Slot 2 (under) type: DDR5 size: 16 GiB speed: 5600 MT/s
    volts: 1 note: check manufacturer: Hynix part-no: HMCG78AGBSA095N
CPU:
  Info: 8-core model: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics bits: 64
    type: MT MCP arch: Zen 4 rev: 1 cache: L1: 512 KiB L2: 8 MiB L3: 16 MiB
  Speed (MHz): avg: 400 min/max: 400/5137 boost: enabled cores: 1: 400
    2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400
    12: 400 13: 400 14: 400 15: 400 16: 400 bogomips: 121374
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile]
    vendor: Hewlett-Packard driver: nvidia v: 565.77 arch: Lovelace pcie:
    speed: 16 GT/s lanes: 8 ports: active: none empty: HDMI-A-1
    bus-ID: 01:00.0 chip-ID: 10de:2820
  Device-2: Advanced Micro Devices [AMD/ATI] Phoenix1
    vendor: Hewlett-Packard driver: amdgpu v: kernel arch: RDNA-3 pcie:
    speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3,
    DP-4, DP-5, Writeback-1 bus-ID: 05:00.0 chip-ID: 1002:15bf temp: 44.0 C
  Device-3: Chicony HP True Vision FHD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 04f2:b792
  Display: wayland server: Xwayland v: 24.1.4 compositor: kwin_wayland
    driver: N/A display-ID: 0
  Monitor-1: eDP-1 res: 1707x960 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 780M (radeonsi gfx1103_r1 LLVM
    19.1.5 DRM 3.59 6.12.8-200.fc41.x86_64) device-ID: 1002:15bf
    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:15bf device: 1
    type: discrete-gpu driver: N/A device-ID: 10de:2820 device: 2 type: cpu
    driver: N/A device-ID: 10005:0000
Audio:
  Device-1: NVIDIA AD106M High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:22bd
  Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
    Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1640
  Device-3: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
    vendor: Hewlett-Packard driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
  Device-4: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3
  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: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 14c3:0616
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: eno1 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: 1-5:2 chip-ID: 0e8d:223c
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 1.4 TiB used: 41.41 GiB (2.9%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: PC801 HFS001TEJ9X101N
    size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 42.9 C
  ID-2: /dev/sda vendor: A-Data model: SX 8200PNP size: 476.94 GiB type: USB
    rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 474.94 GiB used: 40.77 GiB (8.6%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 973.4 MiB used: 527.5 MiB (54.2%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 1022 MiB used: 120.2 MiB (11.8%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 474.94 GiB used: 40.77 GiB (8.6%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 58.1 C mobo: 44.2 C gpu: amdgpu temp: 47.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Info:
  Processes: 402 Power: uptime: 30m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 10
    Compilers: gcc: 14.2.1 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.36

I’ve done some research online and tried a few solutions, but none of them worked.
I also have another laptop with an Intel integrated GPU and an NVIDIA GTX 1650 (discrete GPU), powered by an i5 processor. I installed Fedora 41 on that laptop using the same installation media, applied updates, and installed the NVIDIA drivers via RPM Fusion (exactly the same way as I did on the problematic laptop). The result was flawless. That laptop had no issues whatsoever.

Based on this, I reinstalled Fedora 41 on my problematic laptop with the RTX 4070. I applied updates, and up until that point, everything worked perfectly. However, as soon as I installed the NVIDIA drivers from RPM Fusion, the same issues reappeared as before.

A while back, I was using Fedora but switched to Pop!_OS because it worked seamlessly with laptops that have dual GPUs and NVIDIA cards. I used Pop!_OS for a long time, but since it’s no longer receiving updates (their new version with Wayland is still in alpha), I started encountering issues and decided to return to Fedora.

Thank you in advance for your help!

I see several instances of the autostart.service with timeout, as well as a seemingly long time for xdg-desktop-portal.service All those seem to be apps that are auto-starting and it seems something is causing a timeout in startup there.

While I am not an expert with KDE I would suggest 2 addtional commands that may help to narrow down the cause of this delay.
systemd-analyze blame
and
systemd-analyze plot > bootplot.svg

The svg file is a graphical image in text format that can be opened in a browser to see the actual steps involved. Specific apps/services that take a long time will show with an extended red bar following the service name. You then can investigate the cause of the long delay in startup of those specific services. Often some may be waiting for an earlier service to complete startup before they can complete…

Hello, I am attaching the logs.

5.962s NetworkManager-wait-online.service
4.144s sys-module-fuse.device
4.075s dev-ttyS3.device
4.075s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
4.071s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
4.071s dev-ttyS2.device
4.070s dev-ttyS0.device
4.070s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
4.069s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
4.069s dev-ttyS1.device
4.064s dev-tpmrm0.device
4.064s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
4.051s sys-module-configfs.device
3.634s dev-disk-by\x2ddiskseq-1\x2dpart2.device
3.634s sys-devices-pci0000:00-0000:00:08.3-0000:07:00.3-usb6-6\x2d1-6\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
3.634s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart2.device
3.634s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartnum-2.device
3.634s dev-disk-by\x2dpartuuid-c6b3b679\x2dd096\x2d4c03\x2dab33\x2da3c8c71a136d.device
3.634s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusbv3\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart2.device
3.634s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2duuid-d459825f\x2d7cab\x2d47ad\x2dbc7d\x2d5b4f87d61955.device
3.634s dev-disk-by\x2duuid-d459825f\x2d7cab\x2d47ad\x2dbc7d\x2d5b4f87d61955.device
3.634s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartuuid-c6b3b679\x2dd096\x2d4c03\x2dab33\x2da3c8c71a136d.device
3.634s dev-disk-by\x2did-usb\x2dADATA_SX_8200PNP_152D05831A73\x2d0:0\x2dpart2.device
3.634s dev-sda2.device
3.633s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartnum-3.device
3.633s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dlabel-fedora.device
3.633s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartuuid-d5acd3e5\x2dd5b7\x2d467d\x2d8bde\x2d8231602fe149.device
3.633s dev-sda3.device
3.633s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart3.device
3.633s dev-disk-by\x2dlabel-fedora.device
3.633s sys-devices-pci0000:00-0000:00:08.3-0000:07:00.3-usb6-6\x2d1-6\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda3.device
3.633s dev-disk-by\x2did-usb\x2dADATA_SX_8200PNP_152D05831A73\x2d0:0\x2dpart3.device
3.633s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2duuid-1d59b48d\x2d9c7b\x2d4c5c\x2da722\x2d1a1a461699d7.device
3.633s dev-disk-by\x2ddiskseq-1\x2dpart3.device
3.633s dev-disk-by\x2duuid-1d59b48d\x2d9c7b\x2d4c5c\x2da722\x2d1a1a461699d7.device
3.633s dev-disk-by\x2dpartuuid-d5acd3e5\x2dd5b7\x2d467d\x2d8bde\x2d8231602fe149.device
3.633s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusbv3\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart3.device
3.632s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartuuid-da72b63e\x2d5536\x2d4503\x2d8360\x2d06df81399f08.device
3.632s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart1.device
3.632s dev-disk-by\x2ddiskseq-1\x2dpart1.device
3.632s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartnum-1.device
3.632s dev-sda1.device
3.632s dev-disk-by\x2duuid-66DB\x2dC3A9.device
3.632s sys-devices-pci0000:00-0000:00:08.3-0000:07:00.3-usb6-6\x2d1-6\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
3.632s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusbv3\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart1.device
3.632s dev-disk-by\x2dpartuuid-da72b63e\x2d5536\x2d4503\x2d8360\x2d06df81399f08.device
3.632s dev-disk-by\x2did-usb\x2dADATA_SX_8200PNP_152D05831A73\x2d0:0\x2dpart1.device
3.632s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2duuid-66DB\x2dC3A9.device
3.632s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
3.632s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
3.582s dev-disk-by\x2ddiskseq-1.device
3.582s dev-sda.device
3.582s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusbv3\x2d0:1:1.0\x2dscsi\x2d0:0:0:0.device
3.582s dev-disk-by\x2dpath-pci\x2d0000:07:00.3\x2dusb\x2d0:1:1.0\x2dscsi\x2d0:0:0:0.device
3.582s dev-disk-by\x2did-usb\x2dADATA_SX_8200PNP_152D05831A73\x2d0:0.device
3.582s sys-devices-pci0000:00-0000:00:08.3-0000:07:00.3-usb6-6\x2d1-6\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda.device
3.511s dev-nvme0n1p2.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-3c06d57c\x2dfd9a\x2d4c5f\x2dbc16\x2ddc359843a631.device
3.511s dev-disk-by\x2did-nvme\x2deui.ace42e003ad477012ee4ac0000000001\x2dpart2.device
3.511s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S\x2dpart2.device
3.511s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
3.511s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S_1\x2dpart2.device
3.511s dev-disk-by\x2ddiskseq-2\x2dpart2.device
3.511s dev-disk-by\x2dpartuuid-3c06d57c\x2dfd9a\x2d4c5f\x2dbc16\x2ddc359843a631.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
3.511s sys-devices-pci0000:00-0000:00:02.4-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
3.511s dev-disk-by\x2duuid-4AAA\x2dA0CD.device
3.511s dev-disk-by\x2did-nvme\x2deui.ace42e003ad477012ee4ac0000000001\x2dpart1.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
3.511s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S_1\x2dpart1.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-830a2dc2\x2dbb08\x2d45b7\x2dab40\x2d8392fd43d38e.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-4AAA\x2dA0CD.device
3.511s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S\x2dpart1.device
3.511s sys-devices-pci0000:00-0000:00:02.4-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
3.511s dev-disk-by\x2dpartuuid-830a2dc2\x2dbb08\x2d45b7\x2dab40\x2d8392fd43d38e.device
3.511s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
3.511s dev-disk-by\x2ddiskseq-2\x2dpart1.device
3.511s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
3.511s dev-nvme0n1p1.device
3.510s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S_1\x2dpart3.device
3.510s dev-disk-by\x2ddiskseq-2\x2dpart3.device
3.510s dev-disk-by\x2dpartuuid-c5f87577\x2da2c5\x2d4f44\x2d8b68\x2df149c0473f0e.device
3.510s dev-nvme0n1p3.device
3.510s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
3.510s dev-disk-by\x2did-nvme\x2deui.ace42e003ad477012ee4ac0000000001\x2dpart3.device
3.510s dev-disk-by\x2duuid-FADAAB65DAAB1D3F.device
3.510s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
3.510s sys-devices-pci0000:00-0000:00:02.4-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
3.510s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-FADAAB65DAAB1D3F.device
3.510s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-c5f87577\x2da2c5\x2d4f44\x2d8b68\x2df149c0473f0e.device
3.510s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S\x2dpart3.device
3.510s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
3.510s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
3.505s dev-disk-by\x2ddiskseq-2.device
3.505s dev-disk-by\x2did-nvme\x2deui.ace42e003ad477012ee4ac0000000001.device
3.505s dev-nvme0n1.device
3.505s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S.device
3.505s sys-devices-pci0000:00-0000:00:02.4-0000:04:00.0-nvme-nvme0-nvme0n1.device
3.505s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
3.505s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S_1.device
3.503s dev-disk-by\x2duuid-04746E91746E8570.device
3.503s dev-nvme0n1p4.device
3.503s dev-disk-by\x2dpartuuid-67b8ab42\x2d755c\x2d41ee\x2d933e\x2d6b82784521bb.device
3.503s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-04746E91746E8570.device
3.503s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S\x2dpart4.device
3.503s dev-disk-by\x2did-nvme\x2dSK_hynix_PC801_HFS001TEJ9X101N_SYC9N00981270985S_1\x2dpart4.device
3.503s dev-disk-by\x2did-nvme\x2deui.ace42e003ad477012ee4ac0000000001\x2dpart4.device
3.503s dev-disk-by\x2ddiskseq-2\x2dpart4.device
3.503s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-4.device
3.503s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-67b8ab42\x2d755c\x2d41ee\x2d933e\x2d6b82784521bb.device
3.503s sys-devices-pci0000:00-0000:00:02.4-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
3.503s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart4.device
 672ms initrd-switch-root.service
 633ms akmods.service
 565ms plymouth-read-write.service
 307ms NetworkManager.service
 282ms firewalld.service
 276ms upower.service
 201ms udisks2.service
 195ms abrtd.service
 155ms systemd-tmpfiles-setup-dev-early.service
 151ms user@1000.service
 148ms packagekit.service
 146ms rsyslog.service
 142ms systemd-vconsole-setup.service
 140ms systemd-tmpfiles-setup.service
 130ms chronyd.service
 128ms polkit.service
 125ms systemd-fsck@dev-disk-by\x2duuid-d459825f\x2d7cab\x2d47ad\x2dbc7d\x2d5b4f87d61955.service
 125ms systemd-udev-trigger.service
 124ms ModemManager.service
 124ms systemd-fsck@dev-disk-by\x2duuid-66DB\x2dC3A9.service
 123ms smartd.service
 123ms accounts-daemon.service
 120ms tuned.service
 119ms systemd-journal-flush.service
 113ms unbound-anchor.service
 105ms tuned-ppd.service
  89ms lvm2-monitor.service
  87ms systemd-nsresourced.service
  64ms systemd-hostnamed.service
  63ms bluetooth.service
  63ms var-lib-nfs-rpc_pipefs.mount
  61ms systemd-journald.service
  59ms systemd-logind.service
  57ms systemd-udevd.service
  56ms avahi-daemon.service
  49ms dev-zram0.swap
  49ms dbus-broker.service
  46ms systemd-resolved.service
  45ms systemd-homed.service
  45ms systemd-sysctl.service
  44ms systemd-tmpfiles-setup-dev.service
  44ms sssd-kcm.service
  43ms systemd-userdbd.service
  41ms gssproxy.service
  40ms systemd-binfmt.service
  38ms dracut-cmdline.service
  38ms dracut-pre-udev.service
  38ms plymouth-switch-root.service
  37ms cups.service
  35ms dev-hugepages.mount
  34ms dev-mqueue.mount
  34ms systemd-fsck-root.service
  33ms sys-kernel-debug.mount
  33ms systemd-random-seed.service
  33ms systemd-backlight@backlight:amdgpu_bl1.service
  33ms systemd-oomd.service
  33ms sys-kernel-tracing.mount
  32ms rpc-statd-notify.service
  32ms kmod-static-nodes.service
  31ms systemd-user-sessions.service
  30ms uresourced.service
  30ms boot-efi.mount
  30ms wpa_supplicant.service
  29ms modprobe@dm_mod.service
  29ms modprobe@efi_pstore.service
  28ms switcheroo-control.service
  28ms modprobe@loop.service
  28ms audit-rules.service
  28ms plymouth-quit-wait.service
  27ms systemd-update-utmp-runlevel.service
  27ms plymouth-quit.service
  27ms user-runtime-dir@1000.service
  23ms dracut-shutdown.service
  21ms dracut-pre-pivot.service
  21ms initrd-udevadm-cleanup-db.service
  21ms systemd-zram-setup@zram0.service
  20ms rtkit-daemon.service
  20ms systemd-rfkill.service
  17ms modprobe@configfs.service
  16ms plymouth-start.service
  16ms modprobe@fuse.service
  13ms systemd-network-generator.service
  12ms initrd-parse-etc.service
  12ms systemd-udev-load-credentials.service
  11ms boot.mount
  11ms modprobe@drm.service
  10ms home.mount
  10ms initrd-cleanup.service
  10ms systemd-update-utmp.service
   9ms systemd-modules-load.service
   8ms proc-sys-fs-binfmt_misc.mount
   8ms auditd.service
   7ms systemd-remount-fs.service
   6ms systemd-sysusers.service
   4ms sys-fs-fuse-connections.mount
   3ms tmp.mount
 128us systemd-homed-activate.service

This shows ~10 seconds for the firmware, followed by 10+ seconds for the loader (grub), followed by a 13 second boot time with ~4 seconds for configuring devices and ~5 seconds to start the network.

None of that seems unreasonable to me.
33 seconds total from power on to fully booted and 20+ seconds of that is firmware and grub.

I tested the other notebook I mentioned earlier (GTX1650) and observed the same logs. The timeframes are also similar to the ones in these last two logs. However, one difference I noticed in the earlier logs is the line:

xdg-desktop-portal.service: start operation timed out. Terminating.

I’ve also noticed that both on Ubuntu and Arch, others have reported similar issues. In most cases, the system fully boots and logs in, but launching applications takes about 20-25 seconds, causing delays. I don’t have that problem—once the system is up, everything works normally.

The issue seems to occur during the boot and load process. As you mentioned, it’s likely timing out due to something else before fully loading. Interestingly, after the system is completely booted, the xdg-desktop-portal.service runs without any issues.

Unfortunately, I haven’t been able to draw any conclusions from this yet.

In the meantime, I reinstalled Fedora 41 with GNOME just to test things out. While there are errors and warnings on the system, none of them seem to cause any noticeable impact on functionality. My goal is not to continue with GNOME, but I’m sharing this information for reference, in case something stands out.

1.103s org.gnome.SettingsDaemon.PrintNotifications.service
 690ms org.gnome.Shell@wayland.service
 653ms org.gnome.SettingsDaemon.Power.service
 650ms xdg-desktop-portal.service
 621ms org.gnome.SettingsDaemon.Wacom.service
 619ms org.gnome.SettingsDaemon.MediaKeys.service
 610ms org.gnome.SettingsDaemon.Color.service
 608ms org.gnome.SettingsDaemon.Keyboard.service
 446ms evolution-source-registry.service
 135ms org.gnome.SettingsDaemon.XSettings.service
 129ms gvfs-goa-volume-monitor.service
  95ms tracker-miner-fs-3.service
  82ms xdg-desktop-portal-gnome.service
  74ms evolution-calendar-factory.service
  70ms org.gnome.SettingsDaemon.Sound.service
  66ms xdg-desktop-portal-gtk.service
  62ms org.freedesktop.IBus.session.GNOME.service
  59ms gvfs-gphoto2-volume-monitor.service
  54ms uresourced.service
  52ms gnome-session-manager@gnome.service
  50ms grub-boot-success.service
  50ms org.gnome.SettingsDaemon.Sharing.service
  49ms org.gnome.SettingsDaemon.Smartcard.service
  46ms org.gnome.SettingsDaemon.UsbProtection.service
  46ms evolution-addressbook-factory.service
  40ms org.gnome.SettingsDaemon.Rfkill.service
  40ms gvfs-mtp-volume-monitor.service
  37ms gvfs-udisks2-volume-monitor.service
  36ms org.gnome.SettingsDaemon.ScreensaverProxy.service
  34ms at-spi-dbus-bus.service
  31ms gvfs-afc-volume-monitor.service
  27ms systemd-tmpfiles-clean.service
  26ms dbus-broker.service
  26ms org.gnome.SettingsDaemon.Housekeeping.service
  26ms org.gnome.SettingsDaemon.A11ySettings.service
  25ms gnome-session-monitor.service
  24ms dconf.service
  24ms org.gnome.SettingsDaemon.Datetime.service
  21ms gnome-session-signal-init.service
  18ms gvfs-metadata.service
  16ms xdg-document-portal.service
  12ms gvfs-daemon.service
   7ms dbus.socket
   5ms systemd-tmpfiles-setup.service
   4ms xdg-permission-store.service
Jan 16 09:42:25 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PEP.DETY], AE_NOT_FOUND (20240827/psargs-332)
Jan 16 09:42:25 fedora kernel: ACPI Error: Aborting method \_SB.WMID.GTPS due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Jan 16 09:42:25 fedora kernel: ACPI Error: Aborting method \_SB.WMID.RDCF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Jan 16 09:42:25 fedora kernel: ACPI Error: Aborting method \_SB.WMID.WHCM due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Jan 16 09:42:25 fedora kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Jan 16 09:42:25 fedora kernel: Bluetooth: hci0: Failed to claim iso interface
Jan 16 09:42:26 fedora kernel: 
Jan 16 09:42:28 fedora abrt-notification[1412]: System encountered a non-fatal error in find_patch()
░░ Subject: ABRT has detected a non-fatal system error
░░ Defined-By: ABRT
░░ Support: https://bugzilla.redhat.com/
░░ Documentation: man:abrt(1)
░░ 
░░ WARNING: CPU: 2 PID: 0 at arch/x86/kernel/cpu/microcode/amd.c:662 find_patch+0x177/0x180
░░ 
░░ Use the abrt command-line tool for further analysis or to report
░░ the problem to the appropriate support site.
Jan 16 09:42:43 fedora gdm-password][2268]: gkr-pam: unable to locate daemon control file
Jan 16 09:42:43 fedora systemd[2294]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2428.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 166 and the job result is failed.
Jan 16 09:42:43 fedora systemd[2294]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2431.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 170 and the job result is failed.
Jan 16 09:42:43 fedora systemd[2294]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2434.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 174 and the job result is failed.
Jan 16 09:42:45 fedora gnome-shell[1579]: Connection to xwayland lost
Jan 16 09:42:45 fedora gnome-shell[1579]: Xwayland terminated, exiting since it was mandatory
Jan 16 09:42:45 fedora gnome-shell[1579]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly
                                          @resource:///org/gnome/shell/ui/init.js:21:20
Jan 16 09:42:45 fedora /usr/libexec/gdm-wayland-session[1632]: Failed to launch bus: Bus exited with code 0

Hi,
I’ve spent a lot of time investigating this issue. I tried different approaches and tested multiple operating systems:

  • Tuxedo: Wayland + KDE
  • Manjaro: X11 + KDE
  • Fedora: Wayland + Gnome
  • Fedora: Wayland + KDE

I also tested on 3 different computers:

  1. Laptop: AMD integrated GPU + Nvidia discrete GPU
  2. Laptop: Intel integrated GPU + Nvidia discrete GPU
  3. Desktop: Single Nvidia GPU

Here are my findings:

  • X11 + KDE works without any issues.
  • Wayland + Gnome also works without any issues.
  • Wayland + KDE works fine on the following setups:
    • Dual GPU: Intel integrated GPU + Nvidia discrete GPU.
    • Single Nvidia GPU.
  • Wayland + KDE causes issues on the following setup:
    • Dual GPU: AMD integrated GPU + Nvidia discrete GPU.

I really wanted to use KDE, but I don’t want to stick with X11 because it struggles with managing dual monitors with different resolutions. This is why I prefer Wayland. Since Gnome works flawlessly with Wayland, I’ve decided to continue using Fedora 41 with Gnome.

I hope this issue gets resolved in future updates. Thank you for your help!

’ve been using Fedora 41 with Wayland and GNOME for a while now. Initially, there were no issues, but after extended use, I started experiencing some problems. Firefox froze and crashed a few times, and once, it even logged me out and took me back to the login screen. I reviewed the logs, and they clearly indicate an issue with the integrated AMD GPU.

Previously, I used POP_OS! with X11 and GNOME, and I don’t recall experiencing similar problems. Based on the logs, it seems that the issue is related to the AMD integrated graphics under Wayland. I’m unsure whether to switch back to X11, but it seems like it could provide a more stable experience.

Here are the logs for reference:

Oca 20 15:42:32 fedora kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1115366, emitted seq=1115368
Oca 20 15:42:32 fedora kernel: amdgpu 0000:05:00.0: amdgpu: Process information: process firefox pid 230095 thread firefox:cs0 pid 230193
Oca 20 15:42:34 fedora kernel: amdgpu 0000:05:00.0: amdgpu: MES failed to respond to msg=RESET
Oca 20 15:42:34 fedora kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Oca 20 15:42:36 fedora kernel: amdgpu 0000:05:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Oca 20 15:42:36 fedora kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Oca 20 15:42:36 fedora kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Oca 20 15:42:37 fedora kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Oca 20 15:45:53 fedora kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
Oca 20 15:46:03 fedora kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=1220092, emitted seq=1220094
Oca 20 15:46:03 fedora kernel: amdgpu 0000:05:00.0: amdgpu: Process information: process gnome-shell pid 229280 thread gnome-shel:cs0 pid 229300
Oca 20 15:46:05 fedora kernel: amdgpu 0000:05:00.0: amdgpu: MES failed to respond to msg=RESET
Oca 20 15:46:05 fedora kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Oca 20 15:46:07 fedora kernel: amdgpu 0000:05:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Oca 20 15:46:07 fedora kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Oca 20 15:46:07 fedora kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Oca 20 15:46:08 fedora kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Oca 20 15:46:09 fedora systemd-coredump[233493]: [🡕] Process 229280 (gnome-shell) of user 1000 dumped core.
                                                 
                                                 Module libmpg123.so.0 from rpm mpg123-1.32.9-1.fc41.x86_64
                                                 Module libopus.so.0 from rpm opus-1.5.2-1.fc41.x86_64
                                                 Module libvorbisenc.so.2 from rpm libvorbis-1.3.7-11.fc41.x86_64
                                                 Module libFLAC.so.12 from rpm flac-1.4.3-5.fc41.x86_64
                                                 Module libgsm.so.1 from rpm gsm-1.0.22-7.fc41.x86_64
                                                 Module libsndfile.so.1 from rpm libsndfile-1.2.2-5.fc41.x86_64
                                                 Module libpulsecommon-17.0.so from rpm pulseaudio-17.0-2.fc41.x86_64

Every time I tried to post something using Firefox or access OneDrive through Edge, I encountered the same error. The issue persisted until I restarted my computer. After restarting, the problem no longer occurred. From what I’ve observed, these errors seem to start appearing after my computer has been running for 4-5+ hours continuously.

Tomorrow, I will start using my computer again from the morning and check if the issue occurs again.

I installed Astra Monitor, but when it required components like amdgpu_top, I set up AMD repositories and installed the necessary drivers using:

amdgpu-install --no-dkms --usecase=hip,opencl.

Maybe that’s why everything is running smoothly,

I’ve been using Fedora with GNOME and Wayland for the past week, and so far, I haven’t encountered any issues. It’s working smoothly and stable. When I have some free time, I’ll reinstall KDE on a different disk and test it again (I’ll also try the amdgpu-install --no-dkms --usecase=hip,opencl process). I’ll share my updates here once I have the results.
Thank you!