Hi Diederik,
changes were made to the Kernel so now each of the files is requested board-specifc first, in your case:
brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.bin
brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.clm_blob
and if not existent, falling back to the regular ones:
brcm/brcmfmac43455-sdio.bin (symbolic link to
cypress/cyfmac43455-sdio.bin)
brcm/brcmfmac43455-sdio.txt (not existing -> different topic)
brcm/brcmfmac43455-sdio.clm_blob
(symbolic link to
cypress/cyfmac43455-sdio.clm_blob
currently only the board-specific .txt files (NVRAM settings) are available in the bullseye / bullseye-backports packages, see:
based on the popularity of the Raspberry Pi models, the missing symbolic links might be added sooner or later.
for the time being you can add them manually:
cd /lib/firmware/brcm/
sudo ln -s ../cypress/cyfmac43455-sdio.bin
brcmfmac43455-sdio.raspberrypi,3-model-b-plus.bin
sudo ln -s
../cypress/cyfmac43455-sdio.clm_blob
brcmfmac43455-sdio.raspberrypi,3-model-b-plus.clm_blob
(both files, even if your Kernel 6.0.0-3 only requests per-board .bin files)
With the recent Kernel version
firmware_request_nowarn() is used for the
board-specifc files, so those errors shouldn't be logged.
-> I will do some testing with fallback files to verify this.
In my case it's a bit more complicated involving a bug with space characters in the debian-installer and a nonexistent
clm_blob file for brcmfmac43340, see #1030519
commits in the Kernel:
per-board bin files (
2021-08-01 13:26:59 +0300):
per-board clm_blob files (
2022-09-19 12:59:33 +0300):