-
Notifications
You must be signed in to change notification settings - Fork 455
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
RPI ZERO 2W: don't works, needs patch for firmware 7.45.96.s1 #619
Comments
We are not related to Raspberry Pi nor Kali Linux - but if you want to get this to work I suggest you to first get Kali Linux to correctly load the original firmware. Once this works, you can think about adding monitor mode. On Raspberry Pi OS they do this by creating a corresponding symlink, see: |
I just want to get working monitor mode, since it don't works on raspi-os, this is why I installed Kali Linux. With RPI4 it works ok (with some minor issues, but it can be ignored), but RPI4 uses different chip BCM4345/6. With RPI Zero 2w it don't works at all on Kali Linux (no WiFi with OEM firmware and no WiFi with nexmon patched firmware) because RPI Zero 2w uses chip BCM43430/1. Original raspi-os uses firmware 7.45.96.s1 for this BCM43430/1 chip. I tried to compile nexmon, but there is no patch for firmware 7.45.96.s1. Original raspi-os-bookworm 6.6.31+rpt-rpi-v8 running on rpi2w uses this symlink Here is log file from raspi-os-bookworm with working firmware:
Unfortunately there is no patch for firmware 7.45.96.s1. Kali Linux for some unknown reason loads I'm not sure - how the system determines which chip type is installed and which firmware needs to be loaded? It seems that there is some issue in Kali Linux to determine which firmware should be loaded, because it loads brcmfmac43436-sdio instead of brcmfmac43430-sdio. I tried to replace brcmfmac43436-sdio with a copy of brcmfmac43430-sdio, it loads brcmfmac43430-sdio firmware, but it also don't works. PS: also it's not clear why original raspi-os-bookworm loads
|
Well, if it doesn't matter what OS you are using, I suggest to go for Raspberry Pi OS then. From the log output I can see that on Raspberry Pi OS, other than you suggested, Regarding the confusion about what file is to be loaded, there are a couple of discussions there: https://github.com/RPi-Distro/firmware-nonfree/issues However, all of the above has nothing to do with |
Why brcmfmac43436s-sdio??? When I boot into original Raspi OS with working wifi firmware it shows in the log that the chip is
Currently I'm trying to setup clean Raspi-OS Lite and make the patch. If I understand correctly there is needs to build |
The log says: |
just checked, yes -
Thanks , I wrote you mail about it. |
@alexzaporozhets no, adding patch for 7.45.96.s1 is a paid service. But I found old firmware BCM43430/1 version 7.45.41.46 (r666254 CY) which was supplied for RPI3 also works for RPI02W. And there is a patch in nexmon for this firmware version. You can found original 7.45.41.46 firmware version in this package: http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_0.43+rpi6_all.deb This firmware has some bug which sometimes may lead to not responding state. But this is better than nothing. |
Any steps or guide on how to execute it? |
Any updates? I have the same problem with the same version of firmware. |
like @qrp73 suggested, first download rpi os lite, downgrade the firmware, then setup nexmon. |
New RPI ZERO 2W uses chip BCM43430/1 with firmware 7.45.96.s1 (gf031a129). It appears that there is no patch for this firmware...
Here is original firmware which works ok, but don't have monitor mode:
With this RPI ZERO 2W WiFi don't works at all on latest Kali Linux (for both OEM and nexmon firmware).
I tried to compile
patches/bcm43430a1/7_45_41_46/nexmon
andpatches/bcm43436b0/9_88_4_65/nexmon/
but it don't works. And Kali Linux loadsbrcmfmac43436s-sdio
for some unknown reason. I tried to copybrcmfmac43430-sdio
andbrcmfmac43436-sdio
tobrcmfmac43436s-sdio
, but it also fails to load with error:The text was updated successfully, but these errors were encountered: