The latest from RPi-Distro should be good. Zero 2 W can have one of two chips and as I understand both should work as expected given latest firmware and sdio files.
https://github.com/RPi-Distro/firmware-nonfree/issues/23#issuecomment-1094877540
Joonas Kuorilehto (1ac9cc26) at 01 Apr 23:15
There is https://github.com/RPi-Distro/firmware-nonfree/issues/23 about the firmware too but I don’t think it affects Alpine because the current (not yet in Alpine) firmware should work on Zero 2 W with the other chip when used with wpa_supplicant.
@inklesspen you can get it to work by supplying the firmware files from RPi-Distro repo, probably as explained by @macmpi .
Hi @ncopa , thanks for merging alpine-conf!58 (merged) but as Nick Hanley pointed out the config.txt is duplicated across these two repositories so here's the same change for this one that wasn't merged yet?
Joonas Kuorilehto (c6bb8cfe) at 21 Mar 12:52
scripts/mkimg.arm.sh: add support for Raspberry Zero 2 W
... and 531 more commits
@ncopa I'd like to help get this in for the next release. Let me know if there's anything more I can do to help make it happen.
I have Machine model: Raspberry Pi Zero 2 W Rev 1.0
.
On Alpine Linux 3.15.1 I get brcmfmac43436s-sdio, and in gokrazy brcmfmac43430-sdio.
gokrazy
[ 38.584804] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 38.594067] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,model-zero-2-w.bin failed with error -2
[ 38.915752] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,model-zero-2-w.txt failed with error -2
[ 39.120984] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 39.148509] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766
alpine 3.15.1 aarch64 rpi
(edit config.txt to add pi02, setup-interfaces; no other action needed).
localhost:"# dmesg|grep brcm
15.148790] brcmfmac: brcm_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1
15.1492621 usbcore: registered new interface driver brcmfmac
15.1562461 brcmfmac mmc1:0001:1 : Direct firmware load for brcm/brcmfmac43436s-sdio.raspberrypi,nodel-zero-2-u.bin failed with error -2
15.1569321 brcmfmac mmc1:0001:1 : Direct firmuare load for brcm/brcmfmac43436s-sdio.bin failed with error -2
15.1569861 brcmfmac: bromf_fu_al loc_request: using bren/bronfnac43430-sdio for chip BOM43430/1
15.496738] brcmfmac: bremf _fu alloc request: using brcm/bremfmac43430-sdio for chip BCM43430/1
15.5053411 brcmfmac: bremf_c preinit_dends: Firnuare: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7496287 CY) FUID 01-32059766
37.5339341 brcmfmac: bromf_cfg80211 _set pouer_mgmt: pover save enabled
(apologies for typos due to OCR from photo here)
In both WiFi is working.
@inklesspen For Zero 2 W, I used 3.15 - as I understand the latest https://dl-cdn.alpinelinux.org/alpine/v3.15/releases/aarch64/alpine-rpi-3.15.1-aarch64.tar.gz is equivalent.
The steps to use it: Edit config.txt as per !31953 (diffs) - add section
[pi02]
kernel=boot/vmlinuz-rpi
initramfs boot/initramfs-rpi
For me this was sufficient to get working WiFi via normal Alpine setup.
@stapelberg Do you have other suggestions besides dmesg to identify the hardware?
@njhanley Wasn't clear if you meant I should create a merge request for that too so I did.
Maybe you can try as I did? Do you get the same dmesg as me? Very easy with 3.15.0.
On Sun 13. Mar 2022 at 15.15 Rose Davidson (@inklesspen) < gitlab@alpinelinux.org> wrote:
Rose Davidson https://gitlab.alpinelinux.org/inklesspen commented #13302 (comment 221977):
No, I absolutely did not. As I said upthread, I had to build my own image to include the firmware https://github.com/RPi-Distro/firmware-nonfree/tree/bullseye/debian/config/brcm80211/brcm, which is how I discovered #13408 (closed) #13408 (closed).
— Reply to this email directly or view it on GitLab #13302 (comment 221977).
You're receiving this email because of your account on gitlab.alpinelinux.org. If you'd like to receive fewer emails, you can unsubscribe https://gitlab.alpinelinux.org/-/sent_notifications/REDACTED/unsubscribe from this thread or adjust your notification settings.
-- Joonas Kuorilehto
@inklesspen Please confirm if you used alpine-rpi-3.15.0-aarch64.tar.gz with just config updated to use same kernel/initrd as 3B+?
I tested alpine-rpi-3.15.0-armhf.tar.gz too and it also works after my config.txt change in !31953 (merged) . Not sure what problem you have with WiFi - are there different revisions of Zero 2 W ? Do note that Zero 2 W only has 2.4 GHz WiFi, not 5 GHz.
armhf, pi0 should have matched Zero 2 W. However when I tried, the alpine-rpi-3.15.0-armhf.tar.gz did not boot on my Zero 2 W. After my change of adding the 3 lines to config.txt, it did boot successfully and connected to WiFi as well.
Edit: meaning, before the change neither armhf or aarch64 booted on Zero 2 W but after changes (manually to config.txt), both worked.
I created !31953 (merged) for the config.txt change.
Add support for Raspberry Zero 2 W.
I've only tested with alpine-rpi-3.15.0-aarch64.tar.gz. That didn't boot on Zero 2 W but when I added:
[pi02]
kernel=boot/vmlinuz-rpi
initramfs boot/initramfs-rpi
everything worked flawlessly.
Based on https://www.raspberrypi.com/documentation/computers/config_txt.html#model-filters , my understanding is that none of the existing device filters would match on Zero 2 W so we need to add new model filter for each architecture being built for Raspberry. I copied the kernel/initramfs as used on 3B+ as the Zero 2 W has 64bit ARM just like 3B+.
Joonas Kuorilehto (31515250) at 13 Mar 08:36
scripts/mkimg.arm.sh: add support for Raspberry Zero 2 W
... and 53302 more commits