You are not logged in.
Some interesting experiments here with a raspberry pi 3b+ I was given. Some of this may well apply to other models. It's a different way from the usual dd of someone else's image, or compilation>dd from e.g. rpi-image-builder https://github.com/pyavitz/rpi-img-builder (thanks c0rnelius).
Early days so far and I didn't document everything very well.
The sd card was partitioned, using a Devuan system, with a small fat32 "boot" partition. To this was copied (not dd'd) the "virtual" uefi from here https://github.com/pftf/RPi3 .. Other files needed were EFI/boot/bootaa64.efi (simple to make and the bootloader found it automatically) and boot/grub with the usual (arm64) layout and a custom grub.cfg ..
The rest was formatted ext2 containing Devuan Daedalus loaded via mmdebstrap (superior IMO to debootstrap), then built up in chroot, complete with standard kernel.
On boot the grub menu appears and behaves normally. Everything seems to work including wireless. Bluetooth sound was more challenging, now working with alsa only + bluez-alsa. No xserver for now.
Interestingly I can chain the grub to another grub on a usb pen which (sdcard) grub always detects as /dev/sda. Other distributions are installed there, including another Daedalus and Ceres. Alternative kernels are installed there including a self-compiled mainline 6.13 (used default arm64 defconfig) and one compiled as a deb package using rpi-image-builder. Apparently 6.13 has improved pi support but they all work. A normal update-grub enables them all in the secondary grub menu.
Another revelation: I can boot a custom live image from iso. I never saw that done for arm64.
Anyone else here tried a pi setup like that? Multiboot with uefi, grub, no uboot, no image dd. Pure Devuan except in this case some maybe unnecessary firmware. Maybe you found something I missed or have better or different ideas. If something similar was posted here before either I never found it or it's way outdated.
Last edited by dzz (2025-02-27 19:14:02)
Offline