* amdxdna: firmware <-> driver compatibility
@ 2026-03-20 16:26 Helmut Grohne
2026-03-23 16:25 ` Lizhi Hou
0 siblings, 1 reply; 3+ messages in thread
From: Helmut Grohne @ 2026-03-20 16:26 UTC (permalink / raw)
To: Min Ma, Lizhi Hou, dri-devel
Hello,
I recently attempted updating my linux-firmware. This included updating
amdnpu/17f0_10/npu.sbin.1.0.0.63 to amdnpu/17f0_10/npu.sbin.1.1.2.64.
Once loading the new firmware, I see the following messages on a Debian
6.19.6+deb14+1-amd64 kernel:
amdxdna 0000:66:00.1: enabling device (0000 -> 0002)
amdxdna 0000:66:00.1: [drm] *ERROR* aie2_check_protocol: Incompatible firmware protocol major 7 minor 2
amdxdna 0000:66:00.1: [drm] *ERROR* aie2_hw_start: firmware is not alive
amdxdna 0000:66:00.1: [drm] *ERROR* aie2_smu_exec: smu cmd 4 failed, 0xff
amdxdna 0000:66:00.1: [drm] *ERROR* aie2_smu_fini: Power off failed, ret -22
amdxdna 0000:66:00.1: [drm] *ERROR* aie2_init: start npu failed, ret -22
amdxdna 0000:66:00.1: [drm] *ERROR* amdxdna_probe: Hardware init failed, ret -22
amdxdna 0000:66:00.1: probe with driver amdxdna failed with error -22
This indicates that the updated firmware is incompatible with a 6.19
series kernel. A web search suggests that a 7.0+ kernel requires a npu
firmware >= 1.1. This is an ABI break. When the interface changes in
incompatible ways, the firmware filename should change to avoid such
confusion. The firmware upgrade should be supplying both firmware
versions as long as 6.19 remains supported.
Helmut
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: amdxdna: firmware <-> driver compatibility
2026-03-20 16:26 amdxdna: firmware <-> driver compatibility Helmut Grohne
@ 2026-03-23 16:25 ` Lizhi Hou
2026-03-23 16:58 ` Helmut Grohne
0 siblings, 1 reply; 3+ messages in thread
From: Lizhi Hou @ 2026-03-23 16:25 UTC (permalink / raw)
To: Helmut Grohne, Min Ma, dri-devel; +Cc: Mario Limonciello
Hi Helmut,
Thanks for reporting this. Does your linux-firmware have this change?
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/58cf579b98c0c4878deeda1acb5db70e699875b5
Under the same firmware directory, there should be npu_7.sbin which
links to npu.sbin.1.1.2.64. This is for the latest driver.
And npu.sbin still links to npu.sbin.1.0.0.63 which is for previous drivers.
Could you check if the symbol links are created as expected under
amdnpu/17f0_10/?
Thanks,
Lizhi
On 3/20/26 09:26, Helmut Grohne wrote:
> Hello,
>
> I recently attempted updating my linux-firmware. This included updating
> amdnpu/17f0_10/npu.sbin.1.0.0.63 to amdnpu/17f0_10/npu.sbin.1.1.2.64.
> Once loading the new firmware, I see the following messages on a Debian
> 6.19.6+deb14+1-amd64 kernel:
>
> amdxdna 0000:66:00.1: enabling device (0000 -> 0002)
> amdxdna 0000:66:00.1: [drm] *ERROR* aie2_check_protocol: Incompatible firmware protocol major 7 minor 2
> amdxdna 0000:66:00.1: [drm] *ERROR* aie2_hw_start: firmware is not alive
> amdxdna 0000:66:00.1: [drm] *ERROR* aie2_smu_exec: smu cmd 4 failed, 0xff
> amdxdna 0000:66:00.1: [drm] *ERROR* aie2_smu_fini: Power off failed, ret -22
> amdxdna 0000:66:00.1: [drm] *ERROR* aie2_init: start npu failed, ret -22
> amdxdna 0000:66:00.1: [drm] *ERROR* amdxdna_probe: Hardware init failed, ret -22
> amdxdna 0000:66:00.1: probe with driver amdxdna failed with error -22
>
> This indicates that the updated firmware is incompatible with a 6.19
> series kernel. A web search suggests that a 7.0+ kernel requires a npu
> firmware >= 1.1. This is an ABI break. When the interface changes in
> incompatible ways, the firmware filename should change to avoid such
> confusion. The firmware upgrade should be supplying both firmware
> versions as long as 6.19 remains supported.
>
> Helmut
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-03-24 9:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-20 16:26 amdxdna: firmware <-> driver compatibility Helmut Grohne
2026-03-23 16:25 ` Lizhi Hou
2026-03-23 16:58 ` Helmut Grohne
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.