From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "thomas.kuang" <ks002278@163.com>
Cc: alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [BUG] Lenovo ThinkBook 16 G7 QOY (Snapdragon X) - No soundcards detected
Date: Wed, 10 Jun 2026 15:52:49 +0200 [thread overview]
Message-ID: <5dce26c1-71ae-4c98-8010-037ff2cbccd6@oss.qualcomm.com> (raw)
In-Reply-To: <6aac2e60.9b61.19eb1bb6031.Coremail.ks002278@163.com>
On 6/10/26 3:31 PM, thomas.kuang wrote:
>
>
> when run
> sudo sh -c 'echo "start" > /sys/class/remoteproc/remoteproc0/state'
> sudo sh -c 'echo "start" > /sys/class/remoteproc/remoteproc1/state'
>
>
> dmesg is following:
> 625.929265] remoteproc remoteproc0: powering up adsp
> [ 625.929296] remoteproc remoteproc0: Direct firmware load for qcom/x1p42100/LENOVO/21NH/qcadsp8380.mbn failed with error -2
> [ 625.929299] remoteproc remoteproc0: request_firmware failed: -2
> [ 625.929302] remoteproc remoteproc0: Boot failed: -2
> [ 625.936529] remoteproc remoteproc1: powering up cdsp
> [ 625.936552] remoteproc remoteproc1: Direct firmware load for qcom/x1p42100/LENOVO/21NH/qccdsp8380.mbn failed with error -2
> [ 625.936555] remoteproc remoteproc1: request_firmware failed: -2
> [ 625.936557] remoteproc remoteproc1: Boot failed: -2
As the dmesg suggests, you're missing these firmware files and need
to supply them.
Konrad
prev parent reply other threads:[~2026-06-10 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 11:57 thomas.kuang
2026-06-09 9:24 ` Konrad Dybcio
2026-06-09 22:26 ` thomas.kuang
2026-06-10 10:32 ` Konrad Dybcio
2026-06-10 13:31 ` thomas.kuang
2026-06-10 13:52 ` Konrad Dybcio [this message]
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=5dce26c1-71ae-4c98-8010-037ff2cbccd6@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alsa-devel@alsa-project.org \
--cc=ks002278@163.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®