-
Notifications
You must be signed in to change notification settings - Fork 119
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
Add support for the Raspberry Pi 5 #223
Comments
I'm happy to help testing on my freshly arrived Pi 5 once you're starting to work on it. |
My first Pi 5 arrived 🎉 When I just try to boot a current gokrazy installation, I get the following error message by the bootloader: When I set I would have checked the serial port, but I don’t get any output on the GPIO header. I ordered a Raspberry Pi Debug Probe to use the JST port. |
Exciting! Happy hacking, let us know how it goes :) |
The Debug Probe arrived, so now we can see the serial output of the entire boot process. For the attempt with I then tried dropping https://github.com/raspberrypi/firmware/blob/master/boot/bcm2712-rpi-5-b.dtb into the kernel directory. This made it go a whole lot further, in that the bootloader recognizes the installation as compatible, we see Linux kernel output, but then the boot hangs when it tries to find the root device: full serial output
So, my guess is that we need to sort out the following issues:
|
Looks like https://forums.raspberrypi.com/viewtopic.php?t=360653 is the most recent post regarding Pi 5 upstream work, and there is a patch series to try out, but ethernet and USB don’t work yet apparently. Seems like we need to be patient for a few more weeks at least… |
Status update: 6by9, the person working on upstream support for the Pi 5, reports that it will take quite a long time because of a DMA-related long-standing misunderstanding in the kernel that’s hard to fix: https://forums.raspberrypi.com/viewtopic.php?p=2202581&sid=d2fbe43c5b4e9f133bf7842210a19d7d#p2202581 |
Thanks for the update @stapelberg |
We have compression at the SquashFS level, so this extra layer of compression only means more complexity in userspace when loading modules. related to gokrazy/gokrazy#260 related to gokrazy/gokrazy#223
The files come from: https://github.com/RPi-Distro/firmware-nonfree/tree/223ccf3a3ddb11b3ea829749fbbba4d65b380897/debian/config/brcm80211/cypress This commit switches from regular files to a .tar archive so that we can use symbolic links: all the .txt files are just symlinks these days. Tested manually on the Raspberry Pi 3B, 3B+, 4B, 5B. related to gokrazy/gokrazy#223
Quick status update: over in #264, we now have an experimental Raspberry Pi kernel (not yet auto-updated), and I can successfully boot my Pi 5 with it, including fan control and encrypted WiFi. If anyone is eager to try it out, feel free to give it a go. |
The Pi 5 boots with a kernel command line that contains “reboot=w” which triggers a false-positive with the boot= check. related to gokrazy/gokrazy#223
Got a chance to verify the crypto acceleration is working (using Go’s Pi 4:
Pi 5:
At this point, once #264 is fixed, we can call the Pi 5 supported. |
related to gokrazy/gokrazy#223
This kernel has the broadest device compatibility (incl. Pi 5). related to gokrazy/gokrazy#223
Alright, I think all remaining work items have been completed by now. Give the https://github.com/gokrazy/kernel.rpi kernel (now the default) a shot if you have a Raspberry Pi 5 :) Please open new issues if something doesn’t work. |
This issue tracks the progress. Currently, the Pi 5 is not in stock.
Here’s some background info: https://www.jeffgeerling.com/blog/2023/answering-some-questions-about-raspberry-pi-5
First draft of a checklist:
aes pmull sha1 sha2
The text was updated successfully, but these errors were encountered: