Wednesday, April 24, 2024

[fedora-arm] Re: Lenovo X13s Firmware Load Issues on Kernel 6.8.7-300

Thanks Dennis,

I created the file with the following contents

install_items+=" /lib/firmware/qcom/sc8280xp/LENOVO/21BX/qcdxkmsuc8280.mbn /lib/firmware/qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn /lib/firmware/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn /lib/firmware/qcom/sc8280xp/LENOVO/21BX/qcvss8280.mbn "

The last one is the video firmware described here ( which I manually added from the windows cabs. Not sure if this is needed for mainline kernel or just for the WIP branches but included just incase.

I think I could have included the firmware in compressed xz form but extracted it (unxz) as was unsure exactly how compressed firmware is handled. And then ran dracut --force to regenerate.

USB devices were partially working without the firmware, but as I wasn't booting from USB device I don't know if they were being reset during boot.

Thanks again for your help. Battery level is back working (and so is external monitor).

Andrew Spooner

From: Dennis Gilmore <>
Sent: 23 April 2024 20:29
To: Andrew Spooner <>
Cc: <>
Subject: Re: [fedora-arm] Lenovo X13s Firmware Load Issues on Kernel 6.8.7-300
The move from dracut 059 to 060 led to some additional modules being
in the initrd. A workaround is to add a dracut config snippet that
includes the firmware in the initrd. after putting the file in
/etc/dracut.conf.d/ you will need to rebuild the initrd. ideally the
driver should try and reload the firmware once the root filesystem
becomes available. a side effect of the modules being included in the
initrd is that USB booting should work without the need blacklist
qcom_q6v5_pas as it is what has been included and works here. What is
not clear to me currently is if usb would work correctly without the


On Tue, Apr 23, 2024 at 11:28 AM Andrew Spooner
<> wrote:
> Hi all,
> I have been using Fedora 40 Beta on my Lenovo X13s (followed instructions on, thanks for those, very helpful).
> However, last couple of kernel updates have brought regressions which I think are due to failing to load firmware.
> dmesg has lines like : -
> [    2.596550] remoteproc remoteproc0: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn failed with error -2
> [    2.606506] remoteproc remoteproc1: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn failed with error -2
> This has the impact that the power monitor doesn't seem to be able to pull battery status (pd-mapper is installed and running)
> Rebooting and selecting kernel 6.8.4-300.fc40.aarch64 and this issue disappears. Is this happening to any other X13s owner? Any help a debugging the issue/resolving it without downgrading kernel would be appreciated.
> Thanks
> Andrew Spooner
> --
> _______________________________________________
> arm mailing list --
> To unsubscribe send an email to
> Fedora Code of Conduct:
> List Guidelines:
> List Archives:
> Do not reply to spam, report it:

No comments:

Post a Comment