All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Grohne <helmut@subdivi.de>
To: Min Ma <mamin506@gmail.com>, Lizhi Hou <lizhi.hou@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: amdxdna: firmware <-> driver compatibility
Date: Fri, 20 Mar 2026 17:26:34 +0100	[thread overview]
Message-ID: <20260320162634.GA1515@subdivi.de> (raw)

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


             reply	other threads:[~2026-03-23  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 16:26 Helmut Grohne [this message]
2026-03-23 16:25 ` amdxdna: firmware <-> driver compatibility Lizhi Hou
2026-03-23 16:58   ` Helmut Grohne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260320162634.GA1515@subdivi.de \
    --to=helmut@subdivi.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lizhi.hou@amd.com \
    --cc=mamin506@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.