Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

BlueberryJuice · 2025-10-03 18:43:47

Hello all,

After upgrading my system before shutting down earlier in the day (03/10/2025) and turning my machine back on several hours later, I noticed my display configuration was a mess.

I am using KDE Plasma with an AMD GPU with Mesa 25.2.3 drivers.
My main monitor (180Hz, Display port) is stuck at 60 Hz while my 2nd monitor (75 Hz, HDMI) is completely unresponsive and doesn't display anything.
I have tried restoring all packages to a date prior to this distro upgrade (01/10/2025) to no avail.
KDE Plasma's Display Configuration settings indicate: "60.00 Hz" is the only refresh rate supported by this display.
In Hyprland, I noticed my main monitor's refresh rate reaches 120hz. The 2nd monitor is still completely off and still does not display anything.
I have also noticed my 2nd monitor, which displays the same stuff as my main monitor, is also off and non-functional in the UEFI as well as the Ly display manager.

I tried searching for topics describing the same issue, but couldn't find any with a solution that applied for my machine.
I'd gladly appreciate any ideas you might have !

Thanks in advance !

Last edited by BlueberryJuice (2025-10-03 23:18:35)

seth · 2025-10-03 19:29:43

I have also noticed my 2nd monitor, which displays the same stuff as my main monitor, is also off and non-functional in the UEFI as well as the Ly display manager.

Cable? Second GPU? Does the monitor work when you attach it to a different computer?

What does "stuck" mean? Did you try to change the frequency?

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and the outputs of

kscreen-doctor outputs

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/

BlueberryJuice · 2025-10-03 20:15:55

Thank you for your rapid response !

1: Yes, the monitor works when attached to a different computer. It also works on this machine, as when the main monitor is unplugged, the 2nd monitor works properly.

2: I can't seem to change the frequency in the KDE Plasma Display configurations settings, despite the monitor's setting being at 180 Hz.

3: Here is the complete system journal for the boot: http://0x0.st/KMJh.txt

4: kscreen-doctor outputs gives no output.
The second command outputs the following:

/sys/class/drm/card0
/sys/class/drm/card0/edid: No such file or directory
=================
/sys/class/drm/card0-Unknown-1
EDID of '/sys/class/drm/card0-Unknown-1/edid' was empty.
=================

seth · 2025-10-03 20:20:01

W/o event looking at the journal, you're running on the simpledrm device

There're two AMD GPUs but you're possibly

Oct 03 21:01:36 kglw kernel: amdgpu: ATOM BIOS: 113-EXT78395-001
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/psp_13_0_0_sos.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <psp> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/smu_13_0_0.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <smu> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/dcn_3_2_0_dmcub.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <dm> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/gc_11_0_0_pfp.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <gfx_v11_0> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/sdma_6_0_0.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <sdma_v6_0> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/vcn_4_0_0.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <vcn_v4_0> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/gc_11_0_0_mes_2.bin failed with error -2
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: amdgpu: try to fall back to gc_11_0_0_mes.bin
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: Direct firmware load for amdgpu/gc_11_0_0_mes.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <mes_v11_0> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
Oct 03 21:01:36 kglw kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: enabling device (0006 -> 0007)
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 0 <nv_common>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 1 <gmc_v10_0>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 2 <navi10_ih>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 3 <psp>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 4 <smu>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 5 <dm>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 6 <gfx_v10_0>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 7 <sdma_v5_2>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 8 <vcn_v3_0>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: detected ip block number 9 <jpeg_v3_0>
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: Fetched VBIOS from VFCT
Oct 03 21:01:36 kglw kernel: amdgpu: ATOM BIOS: 102-RAPHAEL-008
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: Direct firmware load for amdgpu/psp_13_0_5_toc.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <psp> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: Direct firmware load for amdgpu/dcn_3_1_5_dmcub.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <dm> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: Direct firmware load for amdgpu/gc_10_3_6_pfp.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <gfx_v10_0> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: Direct firmware load for amdgpu/sdma_5_2_6.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <sdma_v5_2> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: Direct firmware load for amdgpu/vcn_3_1_2.bin failed with error -2
Oct 03 21:01:36 kglw kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* early_init of IP block <vcn_v3_0> failed -19
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: Fatal error during GPU init
Oct 03 21:01:36 kglw kernel: amdgpu 0000:13:00.0: amdgpu: amdgpu: finishing device.

lacking linux-firmware-amdgpu?

BlueberryJuice · 2025-10-03 20:32:22

linux-firmware-amdgpu was indeed missing ! Simply installing it fully resolved the issue.

Thank you very much for your input !

seth · 2025-10-03 20:38:23

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
(you might have to shorten the present subject)

Arch Linux

#1 2025-10-03 18:43:47

Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

#2 2025-10-03 19:29:43

Re: Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

#3 2025-10-03 20:15:55

Re: Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

#4 2025-10-03 20:20:01

Re: Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

#5 2025-10-03 20:32:22

Re: Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

#6 2025-10-03 20:38:23

Re: Monitor stuck at 60hz, 2nd monitor not working after upgrade (SOLVED)

Board footer