-
Notifications
You must be signed in to change notification settings - Fork 104
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
Raspberry Pi Zero 2 W: BCM43430/2 firmware stuck when switching between mesh endpoints #27
Comments
Am I right in thinking you were actually running |
need to check the same. But there is no need to update right now. I was only noticing that it was running fine and the last rpi-update seem to have broken my wifi functionality in the mentioned aspect. I can run rpi-update again, it tells me it can update but i'd expect it will pull the problematic 9.88.4.77 again (which i manually replaced with 9.88.4.65 currently). For further tests and if its needed i can update again to provide more details in debugging and so on. Shall I? |
|
oki thought the first will grab the lastest FW from all repositories needed while apt only gets the released bundle packages officially released |
can report the wifi is stable since 20h now and with a 100 mesh switches inbetween (while it was barely stable 3 min before). Works like expected so far i can tell andn o "reboot" via script required to get it online again. If it helps to solve the issue, I can switch to the latest fw again and provide any debug logs or outputs if someone tells me what i need to upload or export. Thanks for help |
I was running "rpi-update" on my Pi Zero 2 and it seems like its not able to reconnect to the wifi when it is one once. My Pi is driving over my place and switching between three AP with a AVM mesh.
Problematic FW:
Syslog
https://cloud.krautmaster.de/index.php/s/esWJoemFiKzpqys
Moving back to FW:
seem to fix the problem of loosing the ability to do a auto reconnect and switches normally between the APs in the mesh with ony a short outage.
The text was updated successfully, but these errors were encountered: