Supporting Debian Raspberry Bookworm?

[reubenmiller]

I've currently be trying to use use the latest Raspberry image which is based on Debian Bookworm and brings in support for Raspberry Pi 5 (rpi5), however the image does not boot when applying the image to a Raspberry Pi 4 (rpi4).

Looking at the related Raspberry Pi release notes for 2023-10-10-raspios-bookworm-arm64-lite.img.xz, it hints at potential root causes:

• /boot mount point moved to /boot/firmware

In addition, the rugpi-bakery bake command includes the rpi4 eeproms, however I have been experimenting with excluding the eeproms from the image, however the image was still not bootable.

So here comes the main point questions/info (and hence why I'm posting in the discussion and not in the issues):

• Is the project open to PR's?
• I can offer testing support or information support about rp5 (if that would help)

[koehlma]

Regarding the EEPROM files: The reason for including those files is that we require the A/B partition firmware features which only have been introduced recently. On first boot, the files will lead the Pi 4 to update its firmware. Without those files, an off-the-shelf Pi 4 with an old firmware would not boot. I am not sure what the effects of these files on a Pi 5 are, though.

I just implemented an option for rugpi-bakery.toml to disable the placement of firmware files in the image (6a55cdb):

include_firmware = "none"

Regarding the switch to /boot/firmware: This does not make any difference. In fact, the /boot mount point is not even included in /etc/fstab right now. Also, Rugpi Bakery does correctly find the files as they are (still) on the first partition.

Presumably, the issues with Bookworm are because it comes with an initramfs by default, which interferes with Rugpi's initialization process. I just implemented a fix (0ce8cd0). Rugpi Bakery will now disable the respective option in config.txt.

I also pushed some other smaller fixes required for Bookworm to work. At least it works for me now. ;)

Can you confirm that these fixes solved your problems? (Please make sure to wait for the latest Docker images to become available and pull them in before trying it again.)

Is the project open to PR's?

Yes, we very much welcome PRs.

I can offer testing support or information support about rp5 (if that would help)

This would be great. We are also trying to get our hands on one.

[reubenmiller]

Sounds promising I'll test it out shortly.

Regarding the EEPROM for rp5, I'm assuming it would be destructive but that is only a guess, the files are slightly different, and the folder structure has changed, I was playing around with adding an option (like you did) on my fork. Changes would be fairly trivial (and happy to create a PR as well).

This would be great. We are also trying to get our hands on one.

Just a tip, since it looks like you're in Germany as well, the following site might have stock (one of the very few):

• https://shop.funk24.net/Raspberry-Pi/Raspberry-Pi-5/Pi-5-Bundles/

[reubenmiller]

To test it out I built the docker image locally, however building a new image with Debian bookworm worked perfectly on a Raspberry Pi 4 (5 still needs to be tested):

Below is the proof for Raspberry Pi 4:

And the proof of which OS version it is running:

FYI: I'm testing rugpi integration with the project that I'm involved with thin-edge.io

[koehlma]

I am glad that it worked out.

Thanks for the tip with the Pi 5 – I just ordered one.

FYI: I'm testing rugpi integration with the project that I'm involved with thin-edge.io

I know. Very exciting. Please let me know if you need anything to make this happen. In case you are interested, maybe we could also work out some sort of collaboration?

[reubenmiller]

And I can confirm the image works on Raspberry Pi 5.