The problem with the new update linux-firmware [SOLVED]

karr · 2025-06-22 11:51:57

The problem with the new update. I have completed -
# pacman -Rdd linux-firmware
# pacman -Syu linux-firmware
after that, my system stopped booting. Installed amd gpu. It's just a black screen, and there's nothing I can do. With the nomodeset parameter, I can log in to the system. How can I fix it?

Last edited by karr (2025-06-22 18:03:45)

karr · 2025-06-22 12:49:19

Here is my conclusion dmesg | grep -i -E "(amdgpu|radeon|drm|error|fail)"
[ 0.430177] ACPI: bus type drm_connector registered
[ 0.464028] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[ 0.464029] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
[ 0.464707] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[ 0.478279] RAS: Correctable Errors collector initialized.
[ 2.288001] [drm] amdgpu kernel modesetting enabled.
[ 2.288102] amdgpu: Virtual CRAT table created for CPU
[ 2.288107] amdgpu: Topology: Add CPU node
[ 2.288143] amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
[ 3.297165] systemd[1]: Starting Load Kernel Module drm...
[ 3.305282] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 3.305334] systemd[1]: Finished Load Kernel Module drm.
[ 3.693831] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 3.693833] cfg80211: failed to load regulatory.db
[ 14.414079] platform INT3515:01: deferred probe pending: Serial bus multi instantiate pseudo device driver: Error creating i2c-client, idx 0

LuxFerre · 2025-06-22 12:52:08

I had the same issue this morning, no time to try to fix yet but I'll probably chroot and revert the update if possible.

Any other ideas?

Also, did you run mkinitcpio -P after pacman? I didn't and I feel like I should have...

Last edited by LuxFerre (2025-06-22 12:55:54)

karr · 2025-06-22 12:55:55

With nomodeset parameters, I can log in, but I probably won't need a chroot. mkinitcpio -P does not help.

Last edited by karr (2025-06-22 12:57:57)

seth · 2025-06-22 13:09:00

Is the dmesg from the boot w/ "nomodeset"?
Fail to boot, do not reboot w/ the power button but frenetically press ctrl+alt+del or use https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
Reboot nomodeset and then please post your complete system journal for the previous (failing) boot:

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

intellq · 2025-06-22 13:39:00

I can confirm the problem with Radeon RX 9070 XT.

After upgrading to linux-firmware-amdgpu version 20250613.12fe085f-6, black screen (instead of SDDM).

Downgrading to 20250613.12fe085f-5 fixed the problem:
sudo pacman -U ./linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst

Last edited by intellq (2025-06-22 13:41:24)

karr · 2025-06-22 13:41:32

here's what happened http://0x0.st/8IIt.txt

seth · 2025-06-22 13:50:57

июн 22 23:25:46 archlinux kernel: Command line: initrd=\initramfs-linux.img root=PARTUUID=97281fb2-c6f8-458f-bf96-b44dc5052d05 zswap.enabled=0 rw rootfstype=ext4 nomodeset

That boot was "nomodeset" - that's pointless.
The relevant boots are those that fail w/ kms enabled.

karr · 2025-06-22 14:14:50

http://0x0.st/8Ils.txt Maybe I did everything right?
I did, it didn't help sudo pacman -U /var/cache/pacman/pkg/linux-firmware-20250613.12fe085f-5-any.pkg.tar.zst

Scimmia · 2025-06-22 14:17:33

Downgrading the metapackage is pointless, there's nothing in it. You have to downgrade the actual firmware package.

karr · 2025-06-22 14:20:25

Scimmia wrote:

Downgrading the metapackage is pointless, there's nothing in it. You have to downgrade the actual firmware package.

How to do it right?

karr · 2025-06-22 15:00:20

wget https://archive.archlinux.org/packages/l/linux-firmware/linux-firmware-20250613.12fe085f-5-any.pkg.tar.zst

sudo pacman -U ./linux-firmware-20250613.12fe085f-5-any.pkg.tar.zst

That didn't help me either. That didn't help me either. The screen is still black

Last edited by karr (2025-06-22 15:02:01)

seth · 2025-06-22 15:09:22

https://www.reddit.com/r/archlinux/comm … nd_amdgpu/
https://archive.archlinux.org/packages/ … kg.tar.zst

kantokana · 2025-06-22 15:23:51

intellq's solution worked for me. My problem computer also has a Radeon RX 9070.

karr, you may want the linux-firmware-amdgpu package instead of the linux-firmware one.

Something like:

wget https://archive.archlinux.org/packages/l/linux-firmware-amdgpu/linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst

sudo pacman -U ./linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst

Last edited by kantokana (2025-06-22 15:25:26)

karr · 2025-06-22 15:48:14

I had to completely remove linux-firmware*, then

wget https://archive.archlinux.org/packages/l/linux-firmware/linux-firmware-20250508.788aadc8-2-any.pkg.tar.zst

sudo pacman -U ./linux-firmware-20250508.788aadc8-2-any.pkg.tar.zst

Everything is working for me again. Now I understand well why there is no need to rush updates.

Last edited by karr (2025-06-22 15:49:56)

s8n · 2025-06-22 17:41:05

Same issue as everyone else, I have a Radeon RX 9070.
Fixed by booting with nomodeset and downgrading linux-firmware-amdgpu to 20250613.12fe085f-5.

karr · 2025-06-22 18:02:38

s8n wrote:

Same issue as everyone else, I have a Radeon RX 9070.
Fixed by booting with nomodeset and downgrading linux-firmware-amdgpu to 20250613.12fe085f-5.

You're right, this fixes the problem.

# pacman -Rdd linux-firmware

# pacman -Syu linux-firmware

wget https://archive.archlinux.org/packages/l/linux-firmware-amdgpu/linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst

sudo pacman -U ./linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst

seth · 2025-06-22 19:27:52

So the bug is in at least the -2 and -6 versions, but not the -5 one

LuxFerre · 2025-06-22 22:55:08

There's a new 7 version in core-testing with a fix.

a1ex · 2025-06-23 09:52:50

karr wrote:

s8n wrote:
Same issue as everyone else, I have a Radeon RX 9070.
Fixed by booting with nomodeset and downgrading linux-firmware-amdgpu to 20250613.12fe085f-5.
You're right, this fixes the problem.
# pacman -Rdd linux-firmware
# pacman -Syu linux-firmware
wget https://archive.archlinux.org/packages/l/linux-firmware-amdgpu/linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst
sudo pacman -U ./linux-firmware-amdgpu-20250613.12fe085f-5-any.pkg.tar.zst

Thank you. You can also ssh in to downgrade to -5

LuxFerre · 2025-06-23 12:33:47

linux-firmware-amdgpu 20250613.12fe085f-8 from core-testing is also fine. The version from core is still the broken one though...

oyvindsk · 2025-06-25 10:46:01

linux-firmware-amdgpu-20250613.12fe085f-9 works for me

czert · 2025-07-02 23:13:34

I'm having the same problem, but downgrading linux-firmware-amdgpu to 20250613.12fe085f-5 doesn't help. Upgrading to the current 20250627-1 doesn't help either. Not sure which GPU I have, lspci -k says this:

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev c6)
Subsystem: ASUSTeK Computer Inc. Device 12ad
Kernel modules: amdgpu

Relevant dmesg section:

[Thu Jul 3 00:55:09 2025] amdgpu: Virtual CRAT table created for CPU
[Thu Jul 3 00:55:09 2025] amdgpu: Topology: Add CPU node
[Thu Jul 3 00:55:09 2025] amdgpu 0000:03:00.0: probe with driver amdgpu failed with -22

With nomodeset, the system runs fine, but the screen glitches out quite a lot. Any ideas what to try next? Or should I file a bug report somewhere?

seth · 2025-07-03 06:06:41

People downgraded to 20250613.12fe085f-2 or all the way back to linux-firmware-20250508.788aadc8-2
What do the "irrelevant" dmesg lines look like?

czert · 2025-07-03 07:59:27

Not even downgrading to linux-firmware-20250508.788aadc8-2 (while removing all the new linux-firmware-* packages) works for me -- the screen still goes blank during systemd startup. dmesg says different things this time, though:

# dmesg -T | grep amdgpu
[Thu Jul  3 09:37:45 2025] [drm] amdgpu kernel modesetting enabled.
[Thu Jul  3 09:37:45 2025] amdgpu: Virtual CRAT table created for CPU
[Thu Jul  3 09:37:45 2025] amdgpu: Topology: Add CPU node
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 0 <soc15_common>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 1 <gmc_v9_0>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 2 <vega10_ih>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 3 <psp>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 4 <smu>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 5 <dm>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 6 <gfx_v9_0>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 7 <sdma_v4_0>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 8 <vcn_v2_0>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: detected ip block number 9 <jpeg_v2_0>
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
[Thu Jul  3 09:37:45 2025] amdgpu: ATOM BIOS: 13-CEZANNE-019
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: vgaarb: deactivate vga console
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: MODE2 reset
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[Thu Jul  3 09:37:45 2025] [drm] amdgpu: 512M of VRAM memory ready
[Thu Jul  3 09:37:45 2025] [drm] amdgpu: 7692M of GTT memory ready.
[Thu Jul  3 09:37:45 2025] amdgpu 0000:03:00.0: amdgpu: Found VCN firmware Version ENC: 1.24 DEC: 8 VEP: 0 Revision: 3
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: reserve 0x400000 from 0xf41f400000 for PSP TMR
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
[Thu Jul  3 09:37:46 2025] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[Thu Jul  3 09:37:46 2025] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[Thu Jul  3 09:37:46 2025] amdgpu: Virtual CRAT table created for GPU
[Thu Jul  3 09:37:46 2025] amdgpu: Topology: Add dGPU node [0x1638:0x1002]
[Thu Jul  3 09:37:46 2025] kfd kfd: amdgpu: added device 1002:1638
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 7
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: Runtime PM not available
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: amdgpu: [drm] Using custom brightness curve
[Thu Jul  3 09:37:46 2025] amdgpu 0000:03:00.0: [drm] Registered 4 planes with drm panic
[Thu Jul  3 09:37:46 2025] [drm] Initialized amdgpu 3.63.0 for 0000:03:00.0 on minor 1
[Thu Jul  3 09:37:46 2025] fbcon: amdgpudrmfb (fb0) is primary device
[Thu Jul  3 09:37:47 2025] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[Thu Jul  3 09:37:48 2025] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

Full log at http://0x0.st/80LR.txt

Last edited by czert (2025-07-03 09:07:45)

Arch Linux

#1 2025-06-22 11:51:57

The problem with the new update linux-firmware [SOLVED]

#2 2025-06-22 12:49:19

Re: The problem with the new update linux-firmware [SOLVED]

#3 2025-06-22 12:52:08

Re: The problem with the new update linux-firmware [SOLVED]

#4 2025-06-22 12:55:55

Re: The problem with the new update linux-firmware [SOLVED]

#5 2025-06-22 13:09:00

Re: The problem with the new update linux-firmware [SOLVED]

#6 2025-06-22 13:39:00

Re: The problem with the new update linux-firmware [SOLVED]

#7 2025-06-22 13:41:32

Re: The problem with the new update linux-firmware [SOLVED]

#8 2025-06-22 13:50:57

Re: The problem with the new update linux-firmware [SOLVED]

#9 2025-06-22 14:14:50

Re: The problem with the new update linux-firmware [SOLVED]

#10 2025-06-22 14:17:33

Re: The problem with the new update linux-firmware [SOLVED]

#11 2025-06-22 14:20:25

Re: The problem with the new update linux-firmware [SOLVED]

#12 2025-06-22 15:00:20

Re: The problem with the new update linux-firmware [SOLVED]

#13 2025-06-22 15:09:22

Re: The problem with the new update linux-firmware [SOLVED]

#14 2025-06-22 15:23:51

Re: The problem with the new update linux-firmware [SOLVED]

#15 2025-06-22 15:48:14

Re: The problem with the new update linux-firmware [SOLVED]

#16 2025-06-22 17:41:05

Re: The problem with the new update linux-firmware [SOLVED]

#17 2025-06-22 18:02:38

Re: The problem with the new update linux-firmware [SOLVED]

#18 2025-06-22 19:27:52

Re: The problem with the new update linux-firmware [SOLVED]

#19 2025-06-22 22:55:08

Re: The problem with the new update linux-firmware [SOLVED]

#20 2025-06-23 09:52:50

Re: The problem with the new update linux-firmware [SOLVED]

#21 2025-06-23 12:33:47

Re: The problem with the new update linux-firmware [SOLVED]

#22 2025-06-25 10:46:01

Re: The problem with the new update linux-firmware [SOLVED]

#23 2025-07-02 23:13:34

Re: The problem with the new update linux-firmware [SOLVED]

#24 2025-07-03 06:06:41

Re: The problem with the new update linux-firmware [SOLVED]

#25 2025-07-03 07:59:27

Re: The problem with the new update linux-firmware [SOLVED]

Board footer