Firmware issue with wifi-chip on Zero2w with *some* access-points #279
Comments
|
Can confirm I have the same issue. zero1w works, pi4 works, zero2w doesn't work. Same AP, same wifi settings. Gave up and using a very thirsty pi4 instead. |
lianergoist
changed the title
|
I believe this is being looked in to @ Pi |
|
Please can you post the output of Regarding:
You don't say upgraded from what. The problem may appear to have started happening on an upgrade to bookworm if the previous distro had a different version of firmware compared to bookworm. FYI the tip of bullseye currently has the same version of firmware as bookworm for these chips. |
I have attached the output file...
I have not upgraded myself, but I have seen this thread: https://forums.raspberrypi.com/viewtopic.php?p=2130615#p2147719 ...and it looks like I misunderstood something. They were upgrading bullseye, not upgrading to Bookworm. But it still looks like there have been a problem with the firmware for a while. |
|
Thanks for the log. Unfortunately, it does not appear to show an attempt at association/connection to an AP. I would expect to see If you'd like to try a more 'hands on' approach to connect manually, you could try the following steps while retaining the modprobe settings: Create /etc/wpa_supplicant/wpa_supplicant.conf if it doesn't exist, for example: Start the supplicant: Then use wpa_cli to connect: ...where the '0' is the network number returned from add_network. It may be greater than 0 for you. It should have tried to connect at this point, so hopefully you'll be able to see sign of an error in dmesg / journalctl -k. You can trigger the following using wpa_cli, although this obviously only helps if you can connect initially: |
I am happy to help. Just ask [...]
This fails. Or rather, it don'tfinish, and I had to Ctrl-z and kill it. This is the output. I kill it at "EAPOL: External notification - portValid=0".
That not working, because wpa_supplicant is not loaded. dmesg after all this: |
You'll need to use a different shell to run wpa_cli in unless wpa_supplicant is invoked with |
Okay, I have been running the wpa_cli commands. After that this is dmesg: and this is journalctl - k -b -0 (only latest boot): Hope you can use it, and please let me know if you want me do try other things. |
|
Thanks. That's what I needed. If you append |
No, I am sorry. |
|
I think my typo confused things. Your recent journalctl log still shows the feature (PSK offload) as enabled. I'm guessing the syntax in your modprobe conf file is incorrect. Try this: You can confirm the feature is disabled if you don't see the following in the log when attempting to connect: I suspect disabling this feature will allow you to connect to your AP, but let's see. |
YES!! Now it's working! :-) |
Hello, Any chance you could help me address my issue as well? I've been in the same boat trying to use my hotspot on my iphone as a connection I've setup with networkmanager and while my older setups work just fine, I'm having issues with Bookworm in trying to connect to it. Unfortunately, the two lines in brcmfmac.conf aren't solving it. I put the following code in /etc/modprobe.d/brcmfmac.conf If I run dmesg | grep brcmfmac and search for the |
|
Hi. Can you attach your entire kernel boot log encapsulating the failed association with (1) only the |
Do you normally debug this with a wired network connection? This disconnects me from ssh session as I would expect I'm running headless so I connected to a display to continue, and added I included the -B so it would run in the background, but it only works with -B before -d and -c I see my usual network to connect to when I run however, I don't see my hotspot after toggling it on and running scan, scan_results. There are about 5 results of the 12 or so that don't have ssid so I don't know if that would be one of them. Would you like me to connect to my usual network or are am I supposed to be attempting the following add network command with the hotspot? Forgive the noob question, but if successfully connected to something, am I then supposed to ssh again so I can run dmesg and journalctl so I can get you the outputs? I'm running a headless setup so I'm not sure how else to provide you with the outputs. I thought I was running Bullseye on one of them but they're all Bookworm. I forgot to mention I set up a pi5 the other day with Bookworm and no problems with the hotspot. |
Yes. I use a USB OTG cable attached to the zero2w and have a USB-Ethernet adapter plugged into it. |
|
Oh boy, I goofed. Yeah, on my phone, there's an option to Maximize Compatibility and toggling that on did it. Ugh lol. Any harm in keeping that brcmfmac.conf file in there? Don't quite understand still what that does. |
It just makes the brcmfmac driver output extra debug. If nothing needs debugged, you don't need it. Removing it will prevent lots of debug being written to disk and spamming your kernel log. |
|
Do I understand correctly, that adding |
|
Correct. It's considered a workaround. |
|
Not sure if related, but I'm getting a similar error message with RPOS Bookworm (32bit lite) on a Zero 2 W when starting a hotspot running on the Zero: The hotspot worked fine before I created and started a bridge with nmcli. bringing the bridge down and then starting the hotspot gives the same result. Output of The workaround has no effect here. EDIT: |
This seems like a different issue. There is no evidence to suggest that it's caused by the zero2 wlan firmware related problem this ticket is intended to track.
At a guess, maybe network manager has reused an existing connection which did not require security, but now does. Try cleaning out your NM connections and starting afresh. |
|
I have the same issue. New image didn't solve the problem either. tried nmtui and nmcli but no luck |
Which? The hotspot or the PSK offload timeout? I'd prefer to keep this ticket specifically for the latter. |
|
I had the same issue with my Raspberry Pi Zero 2W and Mikrotik hap ax2 router. Create file /etc/modprobe.d/brcmfmac.conf with Will it be fixed in next distro release? |
|
Any update on this? |
|
It has proven somewhat tricky to track down exactly where the issue is, or rather specifically what triggers the 4-way handshake to fail when that transaction is offloaded to the firmware. There is some evidence to suggest that's AP related. |
|
Oh okay, I got 2 Pi Zero 2Ws, I can't get them to work with the official Raspberry Pi OS Bookworm. I had to use Ubuntu images. On Ubuntu WIFI is very stable. But Ubuntu doesn't have rpicam-apps, which sucks for my use case. |
|
Do you have different wlan firmware between Ubuntu and RPiOS? |
|
[ 17.866354] brcmfmac: F1 signature read @0x18000000=0x1541a9a6 |
|
Is that for both distros? |
this is for ubuntu 24.04 |
|
This is from my Pi Zero 2W running Ubuntu. I cannot get the data from Pi Zero 2W running Bookworm as I cannot SSH into it. |
|
I have a PiKVM, WiFi starting to work with Mikrotik router only after applying a fix Here is my data: sudo dmesg | grep brcmfmac sudo wpa_supplicant -v uname -a |
|
Installed Ubuntu 24.01 LTS via Pi imager -> the same issue with WiFi, not able to connect to mikrotik router without a fix. So the is no difference between Ubuntu and Raspberry Pi OS. |
|
I am unable to connect to wifi with this. |
Then you have another issue not related to this thread. @learmj Is any way how we can troubleshoot this issue with connecting some router? It is a very annoying to add a fix every time when install new image. |
|
Same problem here. I tried connecting from different pi zero w/w 2 devices to different mikrotik devices. Connecting to my phone as a hotspot works. Connecting to mikrotik APs doesn't. After adding the workaround and rebooting I get a working wifi connection to the mikrotik devices. |
|
Thanks @SergeyRim
Good to know. That's what I had hoped.
I hear you. I've only reproduced it with a Mikrotik hAP ac lite so far, but I'm sure there must be interop problems with other APs. If you're able to get any logging output from the AP itself when the connection fails, that might be useful (you can get syslog output from a Mikrotik for example). I'm running version RouterOS Curious - have you adjusted any settings on your Mikrotik (eg changed security profile/config since factory defaults)? Obviously restoring to factory defaults may be undesirable in many cases, but if you were able to zap it back to defaults I'd be interested to know if the problem persists (or has persisted since day 1 with the factory default security profile). |
|
@learmj Here are my logs collected on a mAP lite runnning routeros 7.16.1: I got exactly the same issue with a hAP ax3 als running 7.16.1. My wireless configuration is completely custom so I don't know the difference to a factory default setup. In case it would really help narrowing down the issue I could reset the mAP lite to factory defaults. |
|
Thanks. I'd say this is a 4-way handshake error, indicative what I've seen with my mikrotik. As you pointed out, disabling the 4-way handshake in the wlan firmware prevents the problem from occurring. |
|
Same here with mikrotik ax3. |
|
Just reporting that I also see this issue. Latest RaspiOS Lite release (22.Oct.2024), on a Zero 2 W. (Also tested the non-lite and earlier releases) I could see all all SSID (sudo nmcli d wifi list), but could connect to none of them ("Error ... Secrets were required, but not provided.") I disabled power-save, fixed some oddities with the locale config, tried to set up WiFi manually. Disabled and re-enabled WPA3 and PMF on my AP. Nothing seemed to help until I today found this issue/thread. I modified the brcmfmac.conf (only needed the "options brcmfmac feature_disable=0x2000" line) Let me know if there is anything I can to to aid the debugging process. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a problem with the firmware in Bookworm for the wifi-chip on Zero2w. It is a known problem for many users, and it has been discussed in the raspberry pi forum: https://forums.raspberrypi.com/viewtopic.php?t=366155
It has been a problem for a while, when people has upgraded to Bookworm. And it still exist in both 32 and 64 bit versions. But, apparently only on some APs... I can connect to the AP on my android phone, but not to the router from my ISP.
I don't have the skills to narrow down the exact problem, but a user has reported: "The router logs show that RPi is trying to connect, but everything ends with a Handshake error".
The reason why I think it is a firmware problem in Bookworm for the wifi-chip on Zero2ws:
I create the sd-card in rpi-imager app (32 or 64 bit). It does not matter if I choose to configure wifi in rpi-imager or do it later in raspi-config. If I configure in rpi-manager (set ssid and password) there is simply no network after logging in. If I use raspi-config, it tries to connect, but fails.
If I move that sd-card to a Zero1w (only the 32-bit OS of course) and boot up, there are no problems.
If I use a wifi-dongle, there are no problems.
So, there is only a problem when I use the wifi-chip on Zero2w. And again, only on some APs...
I hope someone will look into it.
I am not looking for a workaround. I simply will report a problem some users have, that should be fixed.
The text was updated successfully, but these errors were encountered: