-
Notifications
You must be signed in to change notification settings - Fork 115
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
Document state of Raspberry Pi 400 #188
Comments
I guess the 4B and 400 are nearly identical, except when it comes to the wifi. The 4B has BCM43455: "2.4 GHz and 5.0 GHz IEEE 802.11ac" When using wifi on the rpi400 with Debian, I see:
I have no clue how any of this works, but taking notes in case it helps anybody. My gokrazy image contains,
I guess we'd need https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/bullseye/debian/config/brcm80211/brcm/brcmfmac43456-sdio.txt in there, which I see some people naming like I haven't tried that, and not sure what else would be needed after. But looking at gokrazy/wifi@e6db8b8 that seems like maybe all that's needed? Oh, probably the other two binaries as well:
|
Just to note: Raspbian is not the same as Debian, in particular they have different WiFi drivers. I don’t have a Pi 400 to test, so you’ll need to try out the WiFi firmware files yourself. But yeah, maybe getting the right files in place with the right name is all you need :) |
Well, my naive attempt (bradfitz/gokrazy-wifi@46162e7) didn't work. Maybe this means something to you: lsmod says:
And
This part of the above looks suspect:
How's it thinking this is Debian/Raspbian on that same hardware shows:
|
@bradfitz I've been attempting to identify the parts of the plain Debian Installer that don't quite work with the RPi 400, and the To attempt to answer your question:
I'm learning this stuff, but I think it'd be worth figuring out the 'flattened device tree' (.dtb) file that's being loaded by Roughly speaking: Devicetree provides an alternative to ACPI to describe the names and configuration properties of hardware, and the kernel frequently uses those properties when building firmware filepaths to request. In the case of the
Those As for the As of recently there is a license and firmware available, as distributed (license in the Separately, I'm also trying to figure out whether the BCM43455 and BCM43456 are in fact the same device with different regulatory/calibration parameters.. but I'm not particularly sure how to go about doing that. |
Thanks for sharing your findings!
You could try asking the Raspberry Pi employees, see e.g. RPi-Distro/firmware-nonfree#23 for a successful escalation of a WiFi issue in the past. |
Thank you, @stapelberg - I'll follow up on a separate issue thread there (it may take me a while to get around to that and to write the question, but will do). |
Platform
I’m using:
Observed behavior
The Raspberry Pi 400 seems to mostly work. Everything except wifi.
I moved one of my SD cards from a Raspberry Pi 3B+ to a RPi 400 and it booted fine, but only got DHCP on wired ethernet, not wifi. Then moved it to another RPi 400 (because I'd previously taken apart the first 400 and broke parts of its keyboard), to confirm it wasn't a hardware problem, and same on the second RPi 400: ethernet works, but no wifi.
Expected behavior
Documentation on https://gokrazy.org/platforms/ about the state of Raspberry Pi 400 (ethernet works, no wifi)
Extra bonus: fix wifi on 400 too, so I can convert my kids' Sonos controller jukebox to gokrazy :)
I'm willing to dedicate (and/or locally host) one of my three RPi 400s as a CI machine if needed.
The text was updated successfully, but these errors were encountered: