Never trust AI results without verification.I payed my dues and learnd if I don’t understand precisly what the KI reports and if it cannot explain it to me, so that it is really clear to me I don’t use its suggestions.
1 Like
No, don’t reboot, that’s potentially not booting up again. I don’t use dracut, wait for someone with dracut-knowledge.
1 Like
sudo reinstall-kernels should do the trick.
3 Likes
Please check following thread.
Maybe there is some helpful information for you.
1 Like
You have been faster than me … 
1 Like
is there any statement/article to read with regards to split linux packages and why they do that?
Would be curious to read why they split the firmware into different packages as well.
Maybe this old Arch news explains it in parts:
https://archlinux.org/news/linux-firmware-202201190c6a7b3-2-requires-kernel-53-and-package-splitting/
1 Like
I just landed on that page as well, if they did it in the past it would have been useful and informative that they had added it to yesterday’s new update as well.
they says in that article to reduce disk space but they still shipped it in bundles of multiple packages.. so what is the logic on that?
Thanks @TheRaOct & @marteng69! Seems the other thread was never really resolved…
Looks like the generated files in /efi/66… are the same after doing a sudo reinstall-kernels, and that gave no errors. So I guess the broken pipe must be from something else in the script that calls it.
Anyway, reboot worked fine, and all seems okay.
2 Likes
In some thread @dalto had mentioned that it was due to dracut and that it was no problem to restart. By the way, I do this every time I get this message. Never had a problem.
sudo reinstall-kernels is an option either 
1 Like
@Moonbase59 found it here.
1 Like
No TPM would be true here. Still a little disturbing, seeing an error message on kernel updates.
1 Like
I don’t know that. I’m technically out of my depth
That’s why you have the forum to ask about it 
No, seriously. This is of course somewhat confusing for some users. Of course, I don’t know how to handle this technically. Maybe you have to intervene directly in dracut, which would be beyond our capabilities
2 Likes
If I remember the news at the time they split linux-firmware into linux-firmware and linux-firmware-whence it was said that they will not install all firmware data with it. If you check pacman -Ss linux-firmware- you may see that there are more packages that are not installed.
1 Like
I’m new to EndeavourOS, just been running it for some weeks now, but this broke my system and I’m not sure why yet.
First I followed above instructions, no errors, but a black screen and complete crash on reboot.
In an attempt to mitigate the issue I chrooted back in and manually installed linux-firmware-amdgpu and reran reinstall-kernels, both with no errors; the issue persisted.
At this point I was unsure if there was something with the kernel or the linux-firmware, since both had been updated and hadn’t worked yet; so I rolled back linux-firmware to 20250508.788aadc8-2 via USB chroot and all is well again, the system is completely up-to-date save for the linux-firmware packages at the time of writing.
My boot log is showing me this, seems to be something with the amdgpu driver anyway, I’m running a 9070 XT, is this a known issue, or? 
Any help appreciated! 
jun 22 14:03:11 Pacifist kernel: [drm] amdgpu kernel modesetting enabled.
jun 22 14:03:11 Pacifist kernel: amdgpu: Virtual CRAT table created for CPU
jun 22 14:03:11 Pacifist kernel: amdgpu: Topology: Add CPU node
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
jun 22 14:03:11 Pacifist kernel: [drm] initializing kernel modesetting (IP DISCOVERY 0x1002:0x7550 0x148C:0x2435 0xC0).
jun 22 14:03:11 Pacifist kernel: [drm] register mmio base: 0xF6C00000
jun 22 14:03:11 Pacifist kernel: [drm] register mmio size: 524288
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 0 <soc24_common>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 1 <gmc_v12_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 2 <ih_v7_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 3 <psp>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 4 <smu>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 5 <dm>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 6 <gfx_v12_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 7 <sdma_v7_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 8 <vcn_v5_0_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 9 <jpeg_v5_0_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 10 <mes_v12_0>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
jun 22 14:03:11 Pacifist kernel: amdgpu: ATOM BIOS: 113-EXT108779-100
jun 22 14:03:11 Pacifist kernel: Console: switching to colour dummy device 80x25
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
jun 22 14:03:11 Pacifist kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 16304M 0x0000008000000000 - 0x00000083FAFFFFFF (16304M used)
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
jun 22 14:03:11 Pacifist kernel: [drm] Detected VRAM RAM=16304M, BAR=16384M
jun 22 14:03:11 Pacifist kernel: [drm] RAM width 256bits GDDR6
jun 22 14:03:11 Pacifist kernel: [drm] amdgpu: 16304M of VRAM memory ready
jun 22 14:03:11 Pacifist kernel: [drm] amdgpu: 31938M of GTT memory ready.
jun 22 14:03:11 Pacifist kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: PCIE GART of 512M enabled (table at 0x00000083DAB00000).
jun 22 14:03:11 Pacifist kernel: [drm] Loading DMUB firmware via PSP: version=0x07002F00
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: Found VCN firmware Version ENC: 1.7 DEC: 9 VEP: 0 Revision: 49
jun 22 14:03:11 Pacifist kernel: usb 1-7: new high-speed USB device number 3 using xhci_hcd
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: failed to load ucode DMCUB(0x3D)
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x11)
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000002e, smu fw if version = 0x00000032, smu fw program = 0, smu f>
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
jun 22 14:03:11 Pacifist kernel: [drm] Display Core v3.2.325 initialized on DCN 4.0.1
jun 22 14:03:11 Pacifist kernel: [drm] DP-HDMI FRL PCON supported
jun 22 14:03:11 Pacifist kernel: usb 1-7: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=61.60
jun 22 14:03:11 Pacifist kernel: usb 1-7: New USB device strings: Mfr=0, Product=1, SerialNumber=0
jun 22 14:03:11 Pacifist kernel: usb 1-7: Product: USB2.0 Hub
jun 22 14:03:11 Pacifist kernel: hub 1-7:1.0: USB hub found
jun 22 14:03:11 Pacifist kernel: hub 1-7:1.0: 4 ports detected
jun 22 14:03:11 Pacifist kernel: [drm] Wait for DMUB auto-load failed: 3
jun 22 14:03:11 Pacifist kernel: [drm] DMUB hardware initialized: version=0x07002F00
jun 22 14:03:11 Pacifist kernel: usb 1-8: new high-speed USB device number 4 using xhci_hcd
jun 22 14:03:11 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:12 Pacifist kernel: usb 1-8: New USB device found, idVendor=0e8d, idProduct=0616, bcdDevice= 1.00
jun 22 14:03:12 Pacifist kernel: usb 1-8: New USB device strings: Mfr=5, Product=6, SerialNumber=7
jun 22 14:03:12 Pacifist kernel: usb 1-8: Product: Wireless_Device
jun 22 14:03:12 Pacifist kernel: usb 1-8: Manufacturer: MediaTek Inc.
jun 22 14:03:12 Pacifist kernel: usb 1-8: SerialNumber: 000000000
jun 22 14:03:12 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:12 Pacifist kernel: usb 1-10: new full-speed USB device number 5 using xhci_hcd
jun 22 14:03:12 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:12 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:12 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:12 Pacifist kernel: usb 1-10: New USB device found, idVendor=b58e, idProduct=9e84, bcdDevice= 1.00
jun 22 14:03:12 Pacifist kernel: usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
jun 22 14:03:12 Pacifist kernel: usb 1-10: Product: Yeti Stereo Microphone
jun 22 14:03:12 Pacifist kernel: usb 1-10: Manufacturer: Blue Microphones
jun 22 14:03:12 Pacifist kernel: usb-storage 1-4:1.0: USB Mass Storage device detected
jun 22 14:03:12 Pacifist kernel: scsi host6: usb-storage 1-4:1.0
jun 22 14:03:12 Pacifist kernel: usbcore: registered new interface driver usb-storage
jun 22 14:03:12 Pacifist kernel: usbcore: registered new interface driver uas
jun 22 14:03:12 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:12 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:13 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:13 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:13 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:13 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:13 Pacifist kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
jun 22 14:03:13 Pacifist kernel: scsi 6:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 4
jun 22 14:03:13 Pacifist kernel: sd 6:0:0:0: Attached scsi generic sg0 type 0
jun 22 14:03:13 Pacifist kernel: sd 6:0:0:0: [sda] 15554304 512-byte logical blocks: (7.96 GB/7.42 GiB)
jun 22 14:03:13 Pacifist kernel: sd 6:0:0:0: [sda] Write Protect is off
jun 22 14:03:13 Pacifist kernel: sd 6:0:0:0: [sda] Mode Sense: 43 00 00 00
jun 22 14:03:13 Pacifist kernel: sd 6:0:0:0: [sda] No Caching mode page found
jun 22 14:03:13 Pacifist kernel: sd 6:0:0:0: [sda] Assuming drive cache: write through
1 Like
Same problem for me with my 9700 xt 
1 Like
Thank you! Did my nightly update and ran into this problem. Rebooted and tried again, but problem recurred. Then I saw this and directions worked a treat.
Also on 9070 XT and ran into the same problem and fixed by rolling back linux-firmware.
2 Likes