I have found a way to fix the issue with one small problem. I have to apply the fix each time I reboot.
Further testing was done to see if I could narrow down the issue further than just two versions of Raspberry Pi OS as being the problem. If it was entirely an OS issue there would be a lot more people complaining.
Further steps taken.
1) Took one of the Pi Zero 2 W over to a friend's house. It connects to his router just fine with Bullseye and Bookworm.
2) Brought the Pi back home and used two different relatively newer cellphones as hot spots and the Pi connected with Bullseye and Bookworm.
3) Since the Argon40 Pod case adds full size USB ports I tried connecting with an Edimax USB wireless adapter. This connects fine with Bullseye and Bookworm. This makes no sense. I would suspect an issue with the onboard wireless if it was just one Pi Zero 2 W but 4 of them?
4) Disconnected new router and fired up the old router. It connects fine with Bullseye and Bookworm. Problem with my new router? About 8 months old versus the at least 10 year old router that the Pi connects to.
Not believing it is a router issue since everything else in the house connects from old cellphones and laptops to new cellphones and laptops. Everything connects but the 4 different Pi Zero 2 Ws. I tried a few other things.
5) Tried to install Armbian XFCE and Cinnamon. Neither get to the desktop. Tried Fedora 40 and couldn't get the Pi to boot to the desktop.
6) Installed DietPi and had the same issue as Bullseye and Bookworm. Interesting. Since DietPi is based on Raspberry Pi OS maybe it is something strange in the OS from upstream. DietPi does not use the same network manager as Raspberry Pi OS. Network configurations can be done using the tool dietpi-config which is command line based. This is where I got the hint that sent me on a search for the solution.
DietPi shows the error "CTRL-EVENT-ASSOC-REJECT status_code=16" when trying to connect. Turns out this issue has been around for years but is very random which would explain why it still causes problems.
I got the fix from here. https://iwd.wiki.kernel.org/offloading and this gives details about IWD. https://iwd.wiki.kernel.org
On DietPi I run the below commands and wireless connects right away and works fine.
sudo rmmod brcmfmac
sudo modprobe brcmfmac feature_disable=0x82000
On Raspberry Pi OS I run the below commands and wireless also works.
sudo rmmod brcmfmac_wcc
sudo rmmod brcmfmac
sudo modprobe brcmfmac feature_disable=0x82000
Here is the last step I need to figure out. How do I get these changes to be permanent? Each time I reboot I have to run the above commands again before wireless will connect.
Further testing was done to see if I could narrow down the issue further than just two versions of Raspberry Pi OS as being the problem. If it was entirely an OS issue there would be a lot more people complaining.
Further steps taken.
1) Took one of the Pi Zero 2 W over to a friend's house. It connects to his router just fine with Bullseye and Bookworm.
2) Brought the Pi back home and used two different relatively newer cellphones as hot spots and the Pi connected with Bullseye and Bookworm.
3) Since the Argon40 Pod case adds full size USB ports I tried connecting with an Edimax USB wireless adapter. This connects fine with Bullseye and Bookworm. This makes no sense. I would suspect an issue with the onboard wireless if it was just one Pi Zero 2 W but 4 of them?
4) Disconnected new router and fired up the old router. It connects fine with Bullseye and Bookworm. Problem with my new router? About 8 months old versus the at least 10 year old router that the Pi connects to.
Not believing it is a router issue since everything else in the house connects from old cellphones and laptops to new cellphones and laptops. Everything connects but the 4 different Pi Zero 2 Ws. I tried a few other things.
5) Tried to install Armbian XFCE and Cinnamon. Neither get to the desktop. Tried Fedora 40 and couldn't get the Pi to boot to the desktop.
6) Installed DietPi and had the same issue as Bullseye and Bookworm. Interesting. Since DietPi is based on Raspberry Pi OS maybe it is something strange in the OS from upstream. DietPi does not use the same network manager as Raspberry Pi OS. Network configurations can be done using the tool dietpi-config which is command line based. This is where I got the hint that sent me on a search for the solution.
DietPi shows the error "CTRL-EVENT-ASSOC-REJECT status_code=16" when trying to connect. Turns out this issue has been around for years but is very random which would explain why it still causes problems.
I got the fix from here. https://iwd.wiki.kernel.org/offloading and this gives details about IWD. https://iwd.wiki.kernel.org
On DietPi I run the below commands and wireless connects right away and works fine.
sudo rmmod brcmfmac
sudo modprobe brcmfmac feature_disable=0x82000
On Raspberry Pi OS I run the below commands and wireless also works.
sudo rmmod brcmfmac_wcc
sudo rmmod brcmfmac
sudo modprobe brcmfmac feature_disable=0x82000
Here is the last step I need to figure out. How do I get these changes to be permanent? Each time I reboot I have to run the above commands again before wireless will connect.
Statistics: Posted by yakkoTDI — Sun Jun 16, 2024 7:53 am