You are not logged in.
Hello! I recently updated to linux-firmware-amdgpu 20260910-1 on my computer and noticed that on boot, it was giving me a bunch of DMUB errors on start up, about 200ish once investigated. It returned "(date and time) (devicename) kernel: amdgpu 0000:04:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data" over 200 times in quick secession, especially on boot. I myself have a AMD Radeon 680M [Integrated] GPU. The only way I've been able to fix it is by downgrading the package to 20260810-2, which was before my system-wide update. I figured I'd post this in case anyone else with an AMD Radeon 680M is experiencing the same thing...
Last edited by Ulchel (Today 06:13:43)
Offline
yeah downgrade to previous version, my system could not even boot to tty im mad af
Last edited by qwemaze (Today 08:23:18)
Offline
Offline
Even though i can boot now with downgrade there is still that error coming up when i reboot my system.
Offline
Even though i can boot now with downgrade there is still that error coming up when i reboot my system.
Does your system's initrd need to be rebuilt? Was the error present before the upgrade?
Offline
Same here, using AM5 System with Radeon 9070XT.
As this is the Newbie Corner I just want to make sure doing the right steps.
Downgraded package from cache:
pacman -U file:///var/cache/pacman/pkg/linux-firmware-amdgpu-20260810-2-any.pkg.tar.zstExclude fom update in /etc/pacman.conf:
IgnorPkg = linux-firmware-amdgpuRebuild initrd:
mkinitcpio -p linuxreboot
My system still freezes when entering KDE.
Offline
I had to downgrade both linux-firmware-amdgpu (from 20260910-1 to 20260810-2) and ddcutil (from 3.0.0-1 to 2.2.7-1) for everything to work again. But I also got different errors, like this: https://gitlab.freedesktop.org/drm/amd/ … items/5811. Desktop is running on the iGPU (Raphael, Ryzen 9 7900), the RX 9060 XT shouldn't matter.
Edit: Probably this ddcutil issue: https://github.com/rockowitz/ddcutil/issues/629. Gonna update the firmware again and see if it works with only that one held back.
Edit: It's only ddcutil for me (but I guess some unlucky person could be hit by both issues). And the workaround mentioned in the issue linked above does work.
Last edited by goeb (Today 19:23:34)
Offline
Thanks goeb for the tip with ddcutil. Downgrading to 2.2.7-1 worked for me.
I did not revert to the newer gpu firmware so far. I am just glad to be able to use my pc again.
Offline
Thanks goeb for the tip with ddcutil. Downgrading to 2.2.7-1 worked for me.
I did not revert to the newer gpu firmware so far. I am just glad to be able to use my pc again.
I've downgraded ddcutil and then upgraded linux-firmware & friends back to the latest version, and its working fine.
So it does seem to be an issue with ddcutil. It has already been reported upstream to ddcutil, and there is a workaround to get it working on the latest version, but you might as well leave it downgraded for now.
Ryzen 7 9850X3D | AMD 7800XT | KDE Plasma
Offline
same with rembrandt cards, after upgrade to ddcutil-3.0.0-1
512M of VRAM memory ready
15696M of GTT memory ready.
[drm] GART: num cpu pages 262144, num gpu pages 262144
[drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
[drm] Loading DMUB firmware via PSP: version=0x0400004A
[drm] *ERROR* Error getting DMUB FW meta info: 4
[drm] use_doorbell being set to: [true]
[VCN instance 0] Found VCN firmware Version ENC: 1.33 DEC: 4 VEP: 0 Revision: 21
reserve 0xa00000 from 0xf41e000000 for PSP TMR
failed to load ucode DMCUB(0x3F)
psp gfx command LOAD_IP_FW(0x6) failed and response status is (0xFFFF0008)
RAS: optional ras ta ucode is not available
RAP: optional rap ta ucode is not available
SECUREDISPLAY: optional securedisplay ta ucode is not available
smu driver if version = 0x00000004, smu fw if version = 0x00000004, smu fw program = 4, smu fw version = 0x0445443c (69.68.60)
SMU is initialized successfully!
[drm] Display Core v3.2.384 initialized on DCN 3.1.2
[drm] DP-HDMI FRL PCON supported
[drm] Wait for DMUB auto-load failed: 3
[drm] DMUB hardware initialized: version=0x0400004A
[drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataI cannot boot with an external monitor. with the integrated panel, it takes much longer but eventually i do get an image and machine seems to work normally.
Offline
The ddcutil issue probably needs its own thread to avoid confusion assuming there are two distinct issues.
Offline