Re: FreeBSD-16.0-CURRENT-arm64-aarch64-RPI-20260525-490c53e9353f-286096.img won't boot rpi5
Mark Millard <[email protected]> Mon, 1 Jun 2026 12:00:26 -0700
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On 6/1/26 11:27, void wrote: > Tried again with https://github.com/worproject/rpi5-uefi/releases/download/v0.3/RPi5_UEFI_Release_v0.3.zip and this time with 15.0-RELEASE D0 is targeted by: https://github.com/NumberOneGit/rpi5-uefi/releases/ that has a RPI5-D0v1 Pre-release dating back to 2025-May-7. (There are more recent changes but the author is depending on folks building from source to experiment with such.) Pre-D0 is targeted by (dating back to 2024-Mar-15): https://github.com/worproject/rpi5-uefi/releases/ The author of this one stopped working on it some time ago. The D0 one started from this one. As far as I know, FreeBSD does not have (many of?) the kernel changes for general device tree support for the RPi5 (pre-D0 or D0). The required additions are extensive based on the different way BCM2712's work for a lot of things. (By contrast, OpenBSD has DeviceTree based operation and does not deliberately work with ACPI, as I understand.) The widest general-operation support combination with the FreeBSD OS involved that I'm aware of is to use the ACPI style instead. Otherwise you wait for kernel work to progress. It may be possible to just use microsd card media in the slot without the ACPI style of booting, for all I know. For ACPI use, configuring correctly for Graphical vs. Serial includes doing the right thing in the likes of /boot/loader.conf to match. > > Got to the uefi shell, selected device tree, saved. The booting process gets as far as here: > > Consoles: EFI console > Reading loader env vars from /efi/freebsd/loader.env > Setting currdev to disk0p1: > FreeBSD/arm64 EFI loader, Revision 3.0 > > Command line arguments: loader.efi > Image base: 0x37b4e000 > EFI version: 2.70 > EFI Firmware: worproject (rev 1.00) > Console: efi (0x1000) > Load Path: \EFI\BOOT\BOOTAA64.EFI > Load Device: VenHw(0D51905B-B77E-452A-A2C0-ECA0CC8D514A,00F0FF001000000000)/S > D(0x0)/HD(1,MBR,0x00000000,0x800,0x19000) > BootCurrent: 0001 > BootOrder: 0000 0001[*] 0002 > BootInfo Path: VenHw(0D51905B-B77E-452A-A2C0-ECA0CC8D514A,00F0FF001000000000) > /SD(0x0) > Ignoring Boot0001: Only one DP found > Trying ESP: VenHw(0D51905B-B77E-452A-A2C0-ECA0CC8D514A,00F0FF001000000000)/SD(0x > 0)/HD(1,MBR,0x00000000,0x800,0x19000) > Setting currdev to disk0p1: > Trying: VenHw(0D51905B-B77E-452A-A2C0-ECA0CC8D514A,00F0FF001000000000)/SD(0x0)/H > D(2,MBR,0x00000000,0x19800,0x9E6800) > Setting currdev to disk0p2: > Loading /boot/defaults/loader.conf > Loading /boot/defaults/loader.conf > Loading /boot/device.hints > Loading /boot/loader.conf > Loading /boot/loader.conf.local > Loading kernel... > /boot/kernel/kernel text=0x318 text=0xa62b58 text=0x281508 data=0x16b460 data=0x > 0+0x2c3000 0x8+0x160938+0x8+0x189ef1 > Loading configured modules... > can't find '/boot/entropy' > /boot/kernel/umodem.ko text=0x20c0 text=0x1538 data=0x708+0x4 0x8+0xed0+0x8+0xaf > 4 > loading required module 'ucom' > /boot/kernel/ucom.ko text=0x257c text=0x387c data=0x958+0x858 0x8+0x11a0+0x8+0xa > fd > can't find '/etc/hostid' > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Using DTB provided by EFI at 0x3a0db000. > Loading splash ok > EFI framebuffer information: > addr, size 0x3f400000, 0x7e9000 > dimensions 1920 x 1080 > stride 1920 > masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 > x0: 0xffff00000103afa0 > x1: 0x0000000000000001 > x2: 0x0000000000000017 > x3: 0x0000000000000064 > x4: 0x0000000000000076 > x5: 0x0000000000000000 > x6: 0x1103120000000000 > x7: 0x0000000000120311 > x8: 0xffff000000e61b20 > x9: 0xffff0000010b4000 > x10: 0xffff0000010b0000 > x11: 0x0101010101010101 > x12: 0x000000000000002b > x13: 0x0000000000000003 > x14: 0x1103120000000000 > x15: 0x0000000000000020 > x16: 0x0000000000000020 > x17: 0x0000000000000000 > x18: 0xffff000000e61970 > x19: 0xffff00000103afa0 > x20: 0xffff000000e5e000 > x21: 0xffff00000110de80 > x22: 0x0000000000000038 > x23: 0x0000000037e70018 > x24: 0xffff000001114000 > x25: 0xffffa00000000000 > x26: 0xffffa0003b3d0018 > x27: 0xffff00000110d000 > x28: 0xffff00000110d000 > x29: 0xffff000000e61aa0 > sp: 0xffff000000e61970 > lr: 0xffff0000009193b4 > elr: 0xffff0000009193c8 > spsr: 0x00000000800002c9 > far: 0xfffffffdffdff5ff > esr: 0x00000000be000011 > panic: Unhandled System Error > cpuid = 0 > time = 1 > KDB: stack backtrace: > #0 0xffff0000005710ac at ??+0 > #1 0xffff00000051a100 at ??+0 > #2 0xffff000000519f5c at ??+0 > #3 0xffff00000093668c at ??+0 > #4 0xffff00000090b958 at ??+0 > Uptime: 1s > Rebooting... > cpu_reset failed > > > -- === Mark Millard marklmi at yahoo.com