Tiny Core Base > Raspberry Pi
RPi5 wifi no longer works
(1/1)
Juanito:
I just updated firmware-rpi-wifi and regdb with the result that piCore64-16.x wifi stopped working:
--- Code: ---Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
--- End code ---
--- Code: ---dmesg
...
[ 43.155270] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 43.166079] Loaded X.509 cert 'benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
[ 43.166290] Loaded X.509 cert 'romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[ 43.168082] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 43.168293] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 43.168324] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 43.168327] cfg80211: failed to load regulatory.db
[ 43.179848] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 43.181060] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 43.181096] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,5-model-b.bin failed with error -2
[ 43.181107] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin failed with error -2
[ 43.181244] usbcore: registered new interface driver brcmfmac
[ 44.186273] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
--- End code ---
Something to do with moving from /lib/firmware to /usr/local/lib/firmware and/or too many symlinks?
Paul_123:
I’ll take a look.
Paul_123:
I just wrote a new card with piCore64-16, resized, installed firmware-rpi-wifi.tcz and wifi,tcz on a pi5.
wifi works just fine.
Are you sure you upgraded your rootfs to the 16.0.0 release. The release candidate rootfs did not have the symlink from /lib/firmware to /usr/local/lib/firmware.
Juanito:
The symlink is not there so I guess I must be using a pre-release version of rootfs-piCore64-16.0.gz (dated May 18)?
Juanito:
Confirmed - I overwrote rootfs-piCore64-16.0.gz (and everything else) and the symlink is there now.
Navigation
[0] Message Index
Go to full version