Lrwxrwxrwx 1 root root 44 Aug 16 13:43 brcmfmac43430-sdio.raspberrypi,model-zero-w.txt -> brcmfmac43430-sdio.raspberrypi,3-model-b.txt Lrwxrwxrwx 1 root root 22 Aug 16 13:33 brcmfmac43430-sdio.raspberrypi,3-model-b.txt -> brcmfmac43430-sdio.txt Lrwxrwxrwx 1 root root 36 Aug 16 13:43 brcmfmac43430-sdio.clm_blob ->. Ls -la /lib/firmware/brcm/brcmfmac4343* lrwxrwxrwx 1 root root 31 Aug 16 13:43 brcmfmac43430-sdio.bin ->. brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436-sdio for chip BCM43430/2 brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43436-sdio.raspberrypi,model-zero-2-w.bin failed with error -2 usbcore: registered new interface driver brcmfmac Here are some details from 8.5 (sorry for the long quotes…):ĭmesg | grep brcm brcmfmac: F1 signature read 7.634232] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436-sdio for chip BCM43430/2 I suspect the cause is the firmware blob bundled in the OS image. I have no issues running HAOS 8.5, but upgrading to 9.x broke the network connections. I know, it is strongly discouraged, but it’s perfect for my taste: strong enough to handle my automation needs for 4 HVAC devices via MQTT. I’m using Raspberry Pi Zero 2 W running HAOS.
I run HomeAssistant for some years, but as I had no problems, I didn’t sign up to the forum earlier.
0 kommentar(er)
