agherzan
linux-firmware-rpidistro: Fix wireless error message on RPi
- What I did
Fix an error message generated when creating an image with brcmfmac enabled.
As #1396 describes, the brcmfmac driver generates an error message during boot, which can be seen by inspecting the log of the device. This error happens because several files in linux-firmware-rpidistro links to non-existing files. By updating the link of these files to the valid files in the target, this error message is fixed.
- How I did it
Create a patch file for the linux-firmware-rpidistro recipe, that changes the links of different rpi board firmware files from linking to non-existing files, to link to the file which exists in the system.
A similar change was already implemented for the base file - this PR do the same fix for all the rest of the RPi files, so no error message will be generated.
Fixes: #1396
Hi @omrisarig13, @kraj,
Based on my experience this is a good solution to fix:
[ 5.490148] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 5.500249] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2
Seems like the CI is blocking the merge of the PR for quite some time. Can you rebase and force push to trigger the checks again?
Thanks, Leon
@leon-anavi Thanks for looking at it, and @kraj , thanks for doing the rebase and pushing.
Let me know if there's anything more I can help with.
Hm, the CI failed again but the errors are not related to the change:
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/locales_2.35-0ubuntu3.9_all.deb 404 Not Found [IP: 185.125.190.81 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/s/setuptools/python3-pkg-resources_59.6.0-1.2ubuntu0.22.04.2_all.deb 404 Not Found [IP: 185.125.190.81 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/t/tzdata/tzdata_2025b-0ubuntu0.22.04_all.deb 404 Not Found [IP: 185.125.190.81 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc-dev-bin_2.35-0ubuntu3.9_amd64.deb 404 Not Found [IP: 185.125.190.81 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc6-dev_2.35-0ubuntu3.9_amd64.deb 404 Not Found [IP: 185.125.190.81 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc-devtools_2.35-0ubuntu3.9_amd64.deb 404 Not Found [IP: 91.189.91.83 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/s/setuptools/python3-setuptools_59.6.0-1.2ubuntu0.22.04.2_all.deb 404 Not Found [IP: 185.125.190.39 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
These URLs are indeed returning error 404. The file names are different, for example locales_2.35-0ubuntu3.9_all.deb is missing but there are locales_2.35-0ubuntu3.10_all.deb and locales_2.35-0ubuntu3_all.deb. Clearly an issue with the Docker container although it is supposed to run apt-get update.
Hi @kraj, could you please trigger the checks again? I believe this patch is still necessary, and the previous failure was not caused by it but by a “404 Not Found” error inside the container.
Hi @kraj, could you please trigger the checks again? I believe this patch is still necessary, and the previous failure was not caused by it but by a “404 Not Found” error inside the container.
CI machine is under maintenance @agherzan is upgrading ti, so it will have to wait
Thanks for merging this pull request. For the record, although the main issue has been solved, I am still seeing the following error -2 in dmesg:
[ 5.607778] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,5-model-b.bin failed with error -2
From what I understand from the Linux kernel commits, this missing file should be harmless on Raspberry Pi, because "TxCap blobs are additional data blobs used only on Apple devices".
@leon-anavi Is the follow-up PR https://github.com/agherzan/meta-raspberrypi/pull/1515 fixing the above?
@leon-anavi Is the follow-up PR #1515 fixing the above?
No, no or may just partially, with #1515 there is still the one error for txcap_blob. I believe it is harmless because "TxCap blobs are additional data blobs used on Apple devices". Here is the log from my test setup with Raspberry Pi 5:
root@raspberrypi5:~# dmesg | grep brcmfmac
[ 5.688060] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 5.689276] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 5.699680] usbcore: registered new interface driver brcmfmac
[ 5.999737] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 6.007580] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26 CY) FWID 01-b677b91b