-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to WiFi on Raspberry Pi Zero 2 W (custom OS) #32
Comments
Just a quick note to say that I've seen this, but will be unable to investigate until the new year. No obvious causes spring to mind, but you might be able to get some insight by enabling the output of messages from the firmware to the kernel log. Add |
Thank you for your help in advance! dmesg (full): dmesg.txt |
Is there anything else to try in order to investigate the cause?
|
We are using the Raspberry Pi kernel and firmware to build Home Assistant OS, a custom built OS using buildroot. In our HAOS 8.5 release we have been using
brcmfmac43436-sdio.bin
with md5sum 5dcbec4e28e90a4f503c1117fc71bdd9 (from commit dcea7a3, version 9.88.4.65). This seemed to have worked well.With HAOS 9.x series we moved to
brcmfmac43436-sdio.bin
with md5sum c9ca5766578bcb603239de54737ede6a (from commit 28bad1e, version 9.88.4.77). With this version WiFi association seems to work, however NetworkManager is then unable to obtain a IP address via DHCP. The kernel prints the following error on each try:The kernel used is the same version as Raspberry Pi OS is using currently (built from tag
1.20221104
).The OS uses a fairly standard user space using wpa_supplicant v2.10 and NetworkManager v1.34.0.
I am using a original Raspberry Pi power supply (with 5.1V).
On the same hardware Raspberry Pi OS seems to work (using NetworkManager as well). So this must be some kind of user space configuration or race condition.
Is there a specific wpa_supplicant or NetworkManager patch/configuration required? I understand that this issue is probably beyond what Raspberry Pi supports. But maybe this issue has been seen previously and/or you have other insights which might help me get this problem resolved.
See also: home-assistant/operating-system#2220
The text was updated successfully, but these errors were encountered: