Re: Question: Might loader.kboot use be appropriate for booting RPi5's without U-Boot? (as an example)
Date: Thu, 17 Sep 2026 18:59:30 UTC
Hi Ronald, I posted the dmesg in this context just to say that we are not looking for an alternative to loader.efi (it works perfectly) and that we already have two different bootloaders (U-Boot and UEFI), so we don't need any others. What we actually need are device drivers—for instance, for U-Boot and the FreeBSD kernel. As of June 8, 2025, I had made a sumup of all of that information here: https://wiki.freebsd.org/arm/RecklessberryPatchInjection In the bottom there is a download link to the u-boot version used in the dmesg. my private repo where the sources of the dmesg contains a mix of patches from dfr@ and some of myself(e.g. cpuFreq etc.; some compat-strings for driver bindings etc.). There`s a lot of unorganized code & some rpi-unrelated code inside so it currently wouldn't help to make it public. So the best starting points to understand how the device drivers in u-boot & FreeBSD kernel work is here: https://github.com/dfr/freebsd-src/tree/rpi-5-pcie &here: https://github.com/xen-troops/u-boot/tree/rpi5-2024.04-xt I think meanwhile mainline u-boot comes much closer to reasonable Pi5 support than in 2025. Torsten Duwe of Suse worked with the xen-troops for their patch integration. Unfortunately I currently cannot see/debug bootloaders via the uart-console because of a hardware damage on my cm5-device while I found a special hardware-and software-hack to boot up the machine. the next step in the dfr@ repo could be the enumeration of the devices hanging behind the rp1 south bridge( which are almost all relevant devices like USB& Ethernet). that RP1-driver is just a stub driver which simply does nothing- while the pcie-hack basically works. Is a working FreeBSD based on the Flattend Device Tree realistic? yes. happy hacking&testing from the sources everybody: please post dmesg to the list if there are working test from u-boot/fbsd in any state of development , thanks. Best Regards K. > Am 17.09.2026 um 16:08 schrieb Ronald Klop <ronald-lists@klop.ws>: > > Hi Klaus, > > This looks the best I have seen up until now. Are the patches available in a public branch or in some other way? > > Regards, > Ronald. > > > > > Op zondag 13 september 2026 03:31:56 (+02:00) schreef Klaus Küchemann: > >> no clue what you all want achieve with an alternative loader or linux based bootup ?? >> There is no problem with loader.efi … >> `ve searched a bit and found my last fdt-boot-logs from Nov. 2025 >> Which included some (very incomplete) u-boot & FreeBSD-kernel-patches ….. >> I stopped working on it when I accidentally physically damaged 2 transistors of my cm5 … >> O.K., here we go, have fun but don’t think that`s a real working RPI5- it just boots and some basic patches : >> >> — >> 0.88 RPi: BOOTSYS release VERSION:0451f142 DATE: 2025/01/14 TIME: 00:16:48 >> 0.92 BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1736813808 serial f75a2605 boardrev c04180 stc 992389 >> 1.02 AON_RESET: 00000003 PM_RSTS 00001000 >> 1.06 POWER_OFF_ON_HALT: 1 WAIT_FOR_POWER_BUTTON 0 power-on-reset 1 >> 1.16 RP1_BOOT chip ID: 0x20001927 >> 1.24 part 00000000 reset_info 00000000 >> 1.25 PMIC reset-event 00000000 rtc 00000000 alarm 00000000 enabled 0 >> 1.31 uSD voltage 3.3V >> 1.38 SDRAM_CONFIG: 15 >> 1.38 Initialising SDRAM rank 2 total-size: 32 Gbit 4267 (0x15 0x15) >> 1.43 DDR 4267 1 0 32 152 BL:1 >> >> 0.88 RPi: BOOTSYS release VERSION:0451f142 DATE: 2025/01/14 TIME: 00:16:48 >> 0.92 BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1736813808 serial f75a2605 boardrev c04180 stc 992442 >> 1.02 AON_RESET: 00000003 PM_RSTS 00001000 >> 1.06 POWER_OFF_ON_HALT: 1 WAIT_FOR_POWER_BUTTON 0 power-on-reset 1 >> 1.16 RP1_BOOT chip ID: 0x20001927 >> 1.24 part 00000000 reset_info 00000000 >> 1.25 PMIC reset-event 00000000 rtc 00000000 alarm 00000000 enabled 0 >> 1.31 uSD voltage 3.3V >> 1.38 SDRAM_CONFIG: 15 >> 1.38 Initialising SDRAM rank 2 total-size: 32 Gbit 4267 (0x15 0x15) >> 1.44 DDR 4267 1 0 32 152 BL:1 >> 2.76 OTP boardrev c04180 bootrom a a >> 2.77 Customer key hash 0000000000000000000000000000000000000000000000000000000000000000 >> 2.84 VC-JTAG unlocked >> 2.07 RP1_BOOT chip ID: 0x20001927 >> >> 3.39 RP1_BOOT chip ID: 0x20001927 >> 3.40 RP1_BOOT: fw size 46888 >> 4.78 PCI2 init >> 4.78 PCI2 reset >> 4.22 PCIe scan 00001de4:00000001 >> 4.23 RP1_CHIP_INFO 20001927 >> >> 4.26 RPi: BOOTLOADER release VERSION:0451f142 DATE: 2025/01/14 TIME: 00:16:48 >> 4.33 BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1736813808 serial f75a2605 boardrev c04180 stc 4233143 >> 4.67 usb_pd_init status 3 >> 4.67 USB_PD CONFIG 0 41 >> 4.69 Boot mode: SD (01) order f46 >> 4.86 SD HOST: 200000000 CTL0: 0x00800000 BUS: 400000 Hz actual: 390625 HZ div: 512 (256) status: 0x1fff0000 delay: 276 >> 4.97 SD HOST: 200000000 CTL0: 0x00800f00 BUS: 400000 Hz actual: 390625 HZ div: 512 (256) status: 0x1fff0000 delay: 276 >> 4.06 EMMC >> 4.06 SD retry 1 oc 0 >> 4.30 SD HOST: 200000000 CTL0: 0x00800000 BUS: 400000 Hz actual: 390625 HZ div: 512 (256) status: 0x1fff0000 delay: 276 >> 4.42 OCR c0ff8080 [0] >> CID: 00150100414a54443452060684c09bba >> 4.58 SD HOST: 200000000 CTL0: 0x00800f04 BUS: 25000000 Hz actual: 25000000 HZ div: 8 (4) status: 0x1fff0000 delay: 4 >> 4.69 SD HOST: 200000000 CTL0: 0x00800f04 BUS: 50000000 Hz actual: 50000000 HZ div: 4 (2) status: 0x1fff0000 delay: 2 >> 4.78 MBR: 0x00000800, 102400 type: 0x0c >> 4.80 MBR: 0x00019800,30431232 type: 0xa5 >> 4.84 MBR: 0x00000000, 0 type: 0x00 >> 4.88 MBR: 0x00000000, 0 type: 0x00 >> 4.92 USB-PD: src-cap PDO object1 0x0a0191f4 >> 4.96 Current 5000 mA >> 4.98 Voltage 5000 mV >> 4.00 USB-PD: src-cap PDO object2 0x0002d12c >> 4.04 Current 3000 mA >> 4.06 Voltage 9000 mV >> 4.08 USB-PD: src-cap PDO object3 0x0003c0e1 >> 4.12 Current 2250 mA >> 4.15 Voltage 12000 mV >> 4.17 USB-PD: src-cap PDO object4 0x0004b0b4 >> 4.21 Current 1800 mA >> 4.23 Voltage 15000 mV >> 4.25 Trying partition: 0 >> 4.28 type: 16 lba: 2048 'BSD4.4 ' ' ^ ' clusters 12783 (8) >> 4.34 rsc 4 fat-sectors 50 root dir cluster 1 sectors 32 entries 512 >> 4.40 FAT16 clusters 12783 >> 4.46 [sdcard] autoboot.txt not found >> 4.46 Select partition rsts 0 C(boot_partition) 0 EEPROM config 0 result 0 >> 4.53 Trying partition: 0 >> 4.56 type: 16 lba: 2048 'BSD4.4 ' ' ^ ' clusters 12783 (8) >> 4.62 rsc 4 fat-sectors 50 root dir cluster 1 sectors 32 entries 512 >> 4.68 FAT16 clusters 12783 >> 4.72 Read config.txt bytes 1383 hnd 0x8da >> 4.75 [sdcard] pieeprom.upd not found >> 4.78 usb_max_current_enable default 0 max-current 5000 >> 4.83 set_reboot_order 0 >> 4.91 Read bcm2712-rpi-5-b.dtb bytes 81451 hnd 0x43d >> 4.93 dt-match: compatible: raspberrypi,5-model-b match: brcm,bcm2712 >> 4.99 dt-match: compatible: brcm,bcm2712 match: brcm,bcm2712 >> 4.08 Read /config.txt bytes 1383 hnd 0x8da >> 4.10 Read /config.txt bytes 1383 hnd 0x8da >> 4.17 MESS:00:00:04.717113:0: Initial voltage 800000 temp 24640 >> 4.17 MESS:00:00:04.917472:0: avs_2712: AVS pred 8284 828400 temp 22991 >> 4.21 MESS:00:00:04.921079:0: vpred 828 mV +0 >> 4.29 MESS:00:00:04.929853:0: FB framebuffer_swap 1 >> 4.49 MESS:00:00:04.949244:0: Select resolution HDMI0/2 hotplug 0 max_mode 2 >> 4.53 MESS:00:00:04.953295:0: Select resolution HDMI1/2 hotplug 0 max_mode 2 >> 4.70 MESS:00:00:04.970093:0: dtb_file 'bcm2712-rpi-cm5-cm5io.dtb' >> 4.73 Loading 'bcm2712-rpi-cm5-cm5io.dtb' to 0x00000000 offset 0x100 >> 4.83 Read bcm2712-rpi-cm5-cm5io.dtb bytes 81877 hnd 0x451 >> 5.08 [sdcard] /overlays/overlay_map.dtb not found >> 5.10 /overlays/overlay_map.dtb >> 5.14 Read /overlays/bcm2712d0.dtbo bytes 1491 hnd 0x833 >> 5.41 MESS:00:00:05.041529:0: Loaded overlay 'bcm2712d0' >> 5.35 Read /config.txt bytes 1383 hnd 0x8da >> 5.37 Read /overlays/dwc2.dtbo bytes 801 hnd 0x835 >> 5.51 MESS:00:00:05.151782:0: Loaded overlay 'dwc2' >> 5.53 MESS:00:00:05.153643:0: dtparam: dr_mode=host >> 5.56 [sdcard] /cmdline.txt not found >> 5.57 /cmdline.txt >> 5.67 BMD "armstub8-2712.bin" not found >> 5.68 fs_open: 'armstub8-2712.bin' >> 5.71 Loading 'u-boot.bin' to 0x00000000 offset 0x200000 >> 5.05 Read u-boot.bin bytes 655032 hnd 0x837 >> 5.06 PCI1 reset >> 5.18 USB-OTG disconnect >> 5.57 MESS:00:00:05.557780:0: Starting OS 5557 ms >> 5.63 MESS:00:00:05.563299:0: 00000040: -> 00000480 >> 5.65 MESS:00:00:05.565152:0: 00000030: -> 00100080 >> 5.69 MESS:00:00:05.569864:0: 00000034: -> 00100080 >> 5.74 MESS:00:00:05.574577:0: 00000038: -> 00100080 >> 5.79 MESS:00:00:05.579290:0: 0000003c: -> 00100080 >> >> NOTICE: BL31: v2.6(release):v2.6-240-gfc45bc492 >> NOTICE: BL31: Built : 12:55:13, Dec 4 2024 >> >> >> U-Boot 2024.04 (Feb 08 2025 - 05:59:19 +0100) >> >> DRAM: 1020 MiB (effective 4 GiB) >> RPI: Board rev 0x18 outside known range >> RPI Unknown model (0xc04180) >> Core: 57 devices, 16 uclasses, devicetree: board >> MMC: mmc@fff000: 0, mmc@1100000: 1 >> Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... >> In: serial,usbkbd >> Out: serial,vidconsole >> Err: serial,vidconsole >> PCIe BRCM: link up, 5.0 Gbps x1 (!SSC) >> PCIe BRCM: link up, 5.0 Gbps x4 (!SSC) >> Net: eth0: ethernet@100000 >> >> starting USB... >> Bus usb@480000: USB DWC2 >> scanning bus usb@480000 for devices... 1 USB Device(s) found >> scanning usb for storage devices... 0 Storage Device(s) found >> Hit any key to stop autoboot: 0 >> No EFI system partition >> No EFI system partition >> Failed to persist EFI variables >> No EFI system partition >> Failed to persist EFI variables >> No EFI system partition >> Failed to persist EFI variables >> ** Booting bootflow '<NULL>' with efi_mgr >> Booting: mmc 0 >> >> Consoles: EFI console >> Reading loader env vars from /efi/freebsd/loader.env >> Setting currdev to disk0p1: >> FreeBSD/arm64 EFI loader, Revision 3.0 >> (Tue Nov 4 23:47:08 UTC 2025 root@fbsd5pro) >> >> Command line arguments: loader.efi >> Image base: 0x3e52a000 >> EFI version: 2.100 >> EFI Firmware: Das U-Boot (rev 8228.1024) >> Console: efi,comconsole (0) >> Load Path: /\EFI\BOOT\BOOTAA64.EFI >> Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,6d00000004000000)/eMMC(0)/eMMC(0)/HD(1,0x01,0,0x800,0x19000) >> BootCurrent: 0000 >> BootOrder: 0000[*] >> BootInfo Path: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,6d00000004000000)/eMMC(0)/eMMC(0) >> Ignoring Boot0000: Only one DP found >> Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,6d00000004000000)/eMMC(0)/eMMC(0)/HD(1,0x01,0,0x800,0x19000) >> Setting currdev to disk0p1: >> Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,6d00000004000000)/eMMC(0)/eMMC(0)/HD(2,0x01,0,0x19800,0x1d05800) >> 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=0x9cfbd8 text=0x2dc6f0 data=0x182070 data=0x0+0x377000 0x8+0x1749d8+0x8+0x1a7258 >> Loading configured modules... >> /boot/entropy size=0x1000 >> /boot/kernel/umodem.ko text=0x20c0 text=0x1538 data=0x708+0x4 0x8+0xed0+0x8+0xaf4 >> loading required module 'ucom' >> /boot/kernel/ucom.ko text=0x263d text=0x31b8 data=0x988+0x858 0x8+0x12c0+0x8+0xbc8 >> /etc/hostid size=0x25 >> >> Hit [Enter] to boot immediately, or any other key for command prompt. >> >> >> Type '?' for a list of commands, 'help' for more detailed help. >> OK boot -v >> Using DTB provided by EFI at 0x3e6d2000. >> Loading splash ok >> ---<<BOOT>>--- >> GDB: no debug ports present >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> WARNING: Cannot find freebsd,dts-version property, cannot check DTB compliance >> Type Physical Virtual #Pages Attr >> Reserved 000000000000 000000000000 00000080 WB >> ConventionalMemory 000000080000 000000080000 000364aa WB >> LoaderCode 00003652a000 00003652a000 00004000 WB >> LoaderData 00003a52a000 00003a52a000 00004000 WB >> LoaderCode 00003e52a000 00003e52a000 000000d2 WB >> BootServicesData 00003e5fc000 00003e5fc000 00000003 WB >> ConventionalMemory 00003e5ff000 00003e5ff000 000000d2 WB >> LoaderData 00003e6d1000 00003e6d1000 00000001 WB >> ACPIReclaimMemory 00003e6d2000 00003e6d2000 00000018 WB >> BootServicesData 00003e6ea000 00003e6ea000 00000004 WB >> RuntimeServicesData 00003e6ee000 00003e6ee000 00000001 WB RUNTIME >> BootServicesData 00003e6ef000 00003e6ef000 00000001 WB >> RuntimeServicesData 00003e6f0000 00003e6f0000 00000002 WB RUNTIME >> BootServicesData 00003e6f2000 00003e6f2000 00000001 WB >> RuntimeServicesData 00003e6f3000 00003e6f3000 00000020 WB RUNTIME >> BootServicesData 00003e713000 00003e713000 00000009 WB >> BootServicesCode 00003e71c000 00003e71c000 0000101e WB >> RuntimeServicesData 00003f73a000 00003f73a000 00000001 WB RUNTIME >> BootServicesCode 00003f73b000 00003f73b000 000003f5 WB >> RuntimeServicesCode 00003fb30000 00003fb30000 00000010 WB RUNTIME >> BootServicesCode 00003fb40000 00003fb40000 000000c0 WB >> Reserved 00003fd16000 00003fd16000 00000001 WB >> BootServicesData 000040000000 000040000000 000c0000 WB >> MemoryMappedIO 00107d200000 00107d200000 00000001 RUNTIME >> Physical memory chunk(s): >> 0x00080000 - 0x3fbfffff, 1019 MB ( 260992 pages) >> 0x40000000 - 0xffffffff, 3072 MB ( 786432 pages) >> Excluded memory regions: >> 0x00000000 - 0x0007ffff, 0 MB ( 128 pages) NoAlloc NoDump >> 0x36600000 - 0x37bd4fff, 21 MB ( 5589 pages) NoAlloc >> 0x3e6d2000 - 0x3e6e9fff, 0 MB ( 24 pages) NoAlloc >> 0x3e6ee000 - 0x3e6eefff, 0 MB ( 1 pages) NoAlloc >> 0x3e6f0000 - 0x3e6f1fff, 0 MB ( 2 pages) NoAlloc >> 0x3e6f3000 - 0x3e712fff, 0 MB ( 32 pages) NoAlloc >> 0x3f73a000 - 0x3f73afff, 0 MB ( 1 pages) NoAlloc >> 0x3fb30000 - 0x3fb3ffff, 0 MB ( 16 pages) NoAlloc >> 0x3fd16000 - 0x3fd16fff, 0 MB ( 1 pages) NoAlloc NoDump >> 0x40000000 - 0x40231fff, 2 MB ( 562 pages) NoAlloc >> Found 4 CPUs in the device tree >> Copyright (c) 1992-2025 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 16.0-CURRENT #4: Thu Nov 6 05:10:09 UTC 2025 >> root@fbsd5pro:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 >> FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2) >> WARNING: WITNESS option enabled, expect reduced performance. >> VT: init without driver. >> Preloaded elf kernel "/boot/kernel/kernel" at 0xffff0000015c7000. >> Preloaded boot_entropy_cache "/boot/entropy" at 0xffff0000015d0440. >> Preloaded elf module "/boot/kernel/umodem.ko" at 0xffff0000015d0498. >> Preloaded elf module "/boot/kernel/ucom.ko" at 0xffff0000015d0cb0. >> Preloaded hostuuid "/etc/hostid" at 0xffff0000015d1508. >> Preloaded boot_entropy_platform "efi_rng_seed" at 0xffff0000015d1558. >> Preloaded boot_entropy_platform "efi_rng_seed" at 0xffff0000015d15b0. >> Preloaded TSLOG data "TSLOG" at 0xffff0000015d1608. >> real memory = 4290248704 (4091 MB) >> Physical memory chunk(s): >> 0x00000000080000 - 0x000000365fffff, 911736832 bytes (222592 pages) >> 0x00000037bd5000 - 0x0000003e6d1fff, 112185344 bytes (27389 pages) >> 0x0000003e6ea000 - 0x0000003e6edfff, 16384 bytes (4 pages) >> 0x0000003e6ef000 - 0x0000003e6effff, 4096 bytes (1 pages) >> 0x0000003e6f2000 - 0x0000003e6f2fff, 4096 bytes (1 pages) >> 0x0000003e713000 - 0x0000003f739fff, 16936960 bytes (4135 pages) >> 0x0000003f73b000 - 0x0000003fb2ffff, 4149248 bytes (1013 pages) >> 0x0000003fb40000 - 0x0000003fbfffff, 786432 bytes (192 pages) >> 0x00000040232000 - 0x000000fa79dfff, 3126247424 bytes (763244 pages) >> avail memory = 4168011776 (3974 MB) >> Starting CPU 1 (100) >> Starting CPU 2 (200) >> Starting CPU 3 (300) >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> random: read 4096 bytes from preloaded cache >> random: read 2048 bytes from platform bootloader >> random: unblocking device. >> VIMAGE (virtualized network stack) enabled >> hostuuid: using 35336664-6466-3135-6637-356132363035 >> ULE: setup cpu 0 >> ULE: setup cpu 1 >> ULE: setup cpu 2 >> ULE: setup cpu 3 >> random: entropy device external interface >> firmware: 'tegra210_xusb_fw' version 0: 132608 bytes loaded at 0xffff000000b8ebf8 >> MAP 3e6ee000 mode 2 pages 1 >> MAP 3e6f0000 mode 2 pages 2 >> MAP 3e6f3000 mode 2 pages 32 >> MAP 3f73a000 mode 2 pages 1 >> MAP 3fb30000 mode 2 pages 16 >> MAP 107d200000 mode 4 pages 1 >> kbd0 at kbdmux0 >> mem: <memory> >> null: <full device, null device, zero device> >> openfirm: <Open Firmware control device> >> sound_global_init: snd_unit=-1 snd_vchans_enable=1 latency=2 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 >> tcp_log: tcp_log device >> crypto: <crypto core> >> ram0: reserving memory region: 80000-36600000 >> ram0: reserving memory region: 37bd5000-3e6d2000 >> ram0: reserving memory region: 3e6ea000-3e6ee000 >> ram0: reserving memory region: 3e6ef000-3e6f0000 >> ram0: reserving memory region: 3e6f2000-3e6f3000 >> ram0: reserving memory region: 3e713000-3f73a000 >> ram0: reserving memory region: 3f73b000-3fb30000 >> ram0: reserving memory region: 3fb40000-3fc00000 >> ram0: reserving memory region: 40232000-100000000 >> ofwbus0: <Open Firmware Device Tree> >> clk_fixed0: <Fixed clock> on ofwbus0 >> Clock: 27MHz-clock, parent: none, freq: 27000000 >> clk_fixed1: <Fixed clock> on ofwbus0 >> Clock: 108MHz-clock, parent: none, freq: 108000000 >> simplebus0: <Flattened device tree simple bus> on ofwbus0 >> regfix0: <Fixed Regulator> on simplebus0 >> regfix1: <Fixed Regulator> on simplebus0 >> simplebus1: <Flattened device tree simple bus> on ofwbus0 >> simplebus1: Malformed reg property on <vc_mem> >> ofw_clkbus0: <OFW clocks bus> on ofwbus0 >> clk_fixed2: <Fixed clock> on ofw_clkbus0 >> Clock: osc, parent: none, freq: 54000000 >> clk_fixed3: <Fixed clock> on ofw_clkbus0 >> Clock: otg, parent: none, freq: 480000000 >> clk_fixed4: <Fixed clock> on ofw_clkbus0 >> Clock: vpu-clock, parent: none, freq: 750000000 >> clk_fixed5: <Fixed clock> on ofw_clkbus0 >> Clock: uart-clock, parent: none, freq: 44236800 >> clk_fixed6: <Fixed clock> on ofw_clkbus0 >> Clock: emmc2-clock, parent: none, freq: 200000000 >> clk_fixed7: <Fixed clock> on ofw_clkbus0 >> Clock: xosc, parent: none, freq: 50000000 >> clk_fixed8: <Fixed clock> on ofw_clkbus0 >> Clock: pclk, parent: none, freq: 200000000 >> clk_fixed9: <Fixed clock> on ofw_clkbus0 >> Clock: hclk, parent: none, freq: 200000000 >> clk_fixed10: <Fixed clock> on ofw_clkbus0 >> Clock: src, parent: none, freq: 1000000000 >> clk_fixed11: <Fixed clock> on ofw_clkbus0 >> Clock: core, parent: none, freq: 50000000 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> device_attach: clk_fixed12 attach returned 6 >> c............. >> Blablabla... >> >> regfix2: <Fixed Regulator> on ofwbus0 >> regfix3: <Fixed Regulator> on ofwbus0 >> regfix4: <Fixed Regulator> on ofwbus0 >> clk_fixed12: clock-fixed has no clock-frequency >> clk_fixed12: clock-fixed has no clock-frequency >> regfix5: <Fixed Regulator> on ofwbus0 >> regfix6: <Fixed Regulator> on ofwbus0 >> regfix7: <Fixed Regulator> on ofwbus0 >> simple_mfd0: <Simple MFD (Multi-Functions Device)> mem 0x7d542000-0x7d542eff on simplebus0 >> bcm2835_firmware0: <BCM2835 Firmware> on simplebus0 >> ofw_clkbus1: <OFW clocks bus> on bcm2835_firmware0 >> simple_mfd1: <Simple MFD (Multi-Functions Device)> mem 0x1000400018-0x100040002f on simplebus1 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> device_attach: clk_fixed12 attach returned 6 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> ....blablabla.... >> >> >> simple_mfd2: <Simple MFD (Multi-Functions Device)> on ofwbus0 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> device_attach: clk_fixed12 attach returned 6 >> ......blablabla... >> >> clk_fixed12: clock-fixed has no clock-frequency >> clk_fixed12: clock-fixed has no clock-frequency >> psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0 >> psci0: PSCI version 0.2 compatible >> Found SMCCC version 1.2 >> smccc0: <ARM SMCCC v1.2> on psci0 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> device_attach: clk_fixed12 attach returned 6 >> c......blABLABLA >> >> reset0: <Broadcom 2712 Reset Controller> mem 0x1001504318-0x1001504347 on simplebus1 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> device_attach: clk_fixed12 attach returned 6 >> 0x107fff9000-0x107fff9fff,0x107fffa000-0x107fffbfff,0x107fffc000-0x107fffdfff,0x107fffe000-0x107fffffff irq 86 on simplebus1 >> >> ...blablabla ... >> >> gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 320 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> >> ...blablabla... >> >> generic_timer0: <ARMv8 Generic Timer> irq 7,8,9,10 on ofwbus0 >> generic_timer0: allocated irq for 'sec-phys' >> generic_timer0: allocated irq for 'phys' >> generic_timer0: allocated irq for 'virt' >> generic_timer0: allocated irq for 'hyp-phys' >> ofwbus0: no default resources for rid = 4, type = 1 >> generic_timer0: could not allocate irq for optional interrupt 'hyp-virt' >> Timecounter "ARM MPCore Timecounter" frequency 54000000 Hz quality 1000 >> Event timer "ARM MPCore Eventtimer" frequency 54000000 Hz quality 1000 >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> clk_fixed12: Cannot FDT parameters. >> device_attach: clk_fixed12 attach returned 6 >> ...blablabla... >> >> efirtc0: cannot read EFI realtime clock, error 78 >> smbios0: <System Management BIOS> >> smbios0: Entry point: v3 (64-bit), Version: 3.7 >> smbios0: Docrev: 0, Entry Point Revision: 1 >> ofwbus0: <framebuffer> disabled compat simple-framebuffer (no driver attached) >> ofwbus0: <hvs@107c580000> mem 0x107c580000-0x107c599fff irq 0,1,2 disabled compat brcm,bcm2712-hvs (no driver attached) >> simplebus0: <timer@7c003000> mem 0x7c003000-0x7c003fff irq 11,12,13,14 compat brcm,bcm2835-system-timer (no driver attached) >> simplebus0: <firmwarekms@7d503000> mem 0x7d503000-0x7d503017 irq 15 disabled compat raspberrypi,rpi-firmware-kms-2712 (no driver attached) >> simplebus0: <axiperf> mem 0x7c012800-0x7c0128ff,0x7e000000-0x7e0000ff disabled compat brcm,bcm2712-axiperf (no driver attached) >> simplebus0: <pixelvalve@7c410000> mem 0x7c410000-0x7c4100ff irq 17 disabled compat brcm,bcm2712-pixelvalve0 (no driver attached) >> simplebus0: <pixelvalve@7c411000> mem 0x7c411000-0x7c4110ff irq 18 disabled compat brcm,bcm2712-pixelvalve1 (no driver attached) >> simplebus0: <mop@7c500000> mem 0x7c500000-0x7c500027 irq 19 disabled compat brcm,bcm2712-mop (no driver attached) >> simplebus0: <moplet@7c501000> mem 0x7c501000-0x7c50101f irq 20 disabled compat brcm,bcm2712-moplet (no driver attached) >> simplebus0: <interrupt-controller@7c502000> mem 0x7c502000-0x7c50202f irq 21 disabled compat brcm,bcm2711-l2-intc (no driver attached) >> simplebus0: <clock@7c700000> mem 0x7c700000-0x7c70000f compat brcm,brcm2711-dvp (no driver attached) >> simplebus0: <local_intc@7cd00000> mem 0x7cd00000-0x7cd000ff compat brcm,bcm2836-l1-intc (no driver attached) >> simplebus0: no default resources for rid = 0, type = 4 >> uart0: <PrimeCell UART (PL011)> mem 0x7d001000-0x7d0011ff irq 22 on simplebus0 >> uart0: console (115200,n,8,1) >> uart0: fast interrupt >> uart0: PPS capture mode: DCD >> simplebus0: <serial@7d001400> mem 0x7d001400-0x7d0015ff irq 23 disabled compat arm,pl011 (no driver attached) >> simplebus0: <serial@7d001a00> mem 0x7d001a00-0x7d001bff irq 24 disabled compat arm,pl011 (no driver attached) >> simplebus0: <mmc@7d002000> mem 0x7d002000-0x7d0020ff disabled compat brcm,bcm2835-sdhost (no driver attached) >> simplebus0: <_i2s@7d003000> mem 0x7d003000-0x7d003023 disabled compat brcm,bcm2835-i2s (no driver attached) >> spi0: <BCM2708/2835 SPI controller> mem 0x7d004000-0x7d0041ff irq 25 on simplebus0 >> spibus0: <OFW SPI bus> on spi0 >> spibus0: <unknown card> at cs 0 mode 0 >> simplebus0: <spi@7d004600> mem 0x7d004600-0x7d0047ff irq 26 disabled compat brcm,bcm2835-spi (no driver attached) >> simplebus0: <spi@7d004800> mem 0x7d004800-0x7d0049ff irq 27 disabled compat brcm,bcm2835-spi (no driver attached) >> ........blablabla.... >> >> simplebus0: <hdmi@7ef00700> mem 0x7c701400-0x7c7016ff,0x7c701000-0x7c7011ff,0x7c701d00-0x7c701fff,0x7c702000-0x7c70207f,0x7c703800-0x7c7039ff,0x7c704000-0x7c7047ff,0x7c700100-0x7c70017f,0x7d510800-0x7d5108ff,0x7c720000-0x7c7200ff irq 52,53,54,55,56 disabled compat brcm,bcm2712-hdmi0 (no driver attached) >> simplebus0: <hdmi@7ef05700> mem 0x7c706400-0x7c7066ff,0x7c706000-0x7c7061ff,0x7c706d00-0x7c706fff,0x7c707000-0x7c70707f,0x7c708800-0x7c7089ff,0x7c709000-0x7c7097ff,0x7c700180-0x7c7001ff,0x7d511000-0x7d5110ff,0x7c720000-0x7c7200ff irq 57,58,59,60,61 disabled compat brcm,bcm2712-hdmi1 (no driver attached) >> bcm2835_firmware0: <reset> compat raspberrypi,firmware-reset (no driver attached) >> bcm2835_firmware0: <vcio> compat raspberrypi,vcio (no driver attached) >> simplebus0: <power> compat raspberrypi,bcm2835-power (no driver attached) >> fb0: <BCM2835 VT framebuffer driver> on simplebus0 >> Checking root against raspberrypi,model-b >> Checking root against brcm,bcm2835 >> Checking root against brcm,bcm2709 >> Checking root against brcm,bcm2836 >> Checking root against brcm,bcm2837 >> Checking root against brcm,bcm2711 >> Checking root against brcm,bcm2838 >> Checking root against brcm,bcm2712 >> fb0: changing fb bpp from 0 to 24 >> mbox0: mbox response error >> fb0: bcm2835_mbox_fb_init failed, err=5 >> device_attach: fb0 attach returned 6 >> simplebus0: <rpi_rtc> compat raspberrypi,rpi-rtc (no driver attached) >> simplebus0: <nvmem> compat simple-bus (no driver attached) >> simplebus0: <gpiomem@7d508500> mem 0x7d508500-0x7d50853f compat raspberrypi,gpiomem (no driver attached) >> simplebus0: <gpiomem@7d517c00> mem 0x7d517c00-0x7d517c3f compat raspberrypi,gpiomem (no driver attached) >> simplebus0: <gpiomem@7d504100> mem 0x7d504100-0x7d50411f compat raspberrypi,gpiomem (no driver attached) >> simplebus0: <gpiomem@7d510700> mem 0x7d510700-0x7d51071f compat raspberrypi,gpiomem (no driver attached) >> pmu0: <Performance Monitoring Unit> irq 3,4,5,6 on ofwbus0 >> ofwbus0: no default resources for rid = 4, type = 1 >> cpulist0: <Open Firmware CPU Group> on ofwbus0 >> cpu0: <Open Firmware CPU> on cpulist0 >> cpu0: missing 'clock-frequency' property >> bcm2835_cpufreq0: <CPU Frequency Control> on cpu0 >> cpufreq0: <CPU frequency control> on cpu0 >> cpu1: <Open Firmware CPU> on cpulist0 >> cpu1: missing 'clock-frequency' property >> cpu2: <Open Firmware CPU> on cpulist0 >> cpu2: missing 'clock-frequency' property >> cpu3: <Open Firmware CPU> on cpulist0 >> cpu3: missing 'clock-frequency' property >> simplebus1: <gpu> compat brcm,bcm2712d0-vc6 (no driver attached) >> simplebus1: <iommu@5100> mem 0x1000005100-0x100000517f compat brcm,bcm2712-iommu (no driver attached) >> simplebus1: <iommu@5200> mem 0x1000005200-0x100000527f compat brcm,bcm2712-iommu (no driver attached) >> simplebus1: <iommu@5280> mem 0x1000005280-0x10000052ff compat brcm,bcm2712-iommu (no driver attached) >> simplebus1: <iommuc@5b00> mem 0x1000005b00-0x1000005b7f compat brcm,bcm2712-iommuc (no driver attached) >> simplebus1: <dma@10000> mem 0x1000010000-0x10000105ff irq 62,63,64,65,66,67 compat brcm,bcm2712-dma (no driver attached) >> simplebus1: <dma@10600> mem 0x1000010600-0x1000010bff irq 68,69,70,71,72,73 compat brcm,bcm2712-dma (no driver attached) >> simplebus1: <pcie@100000> mem 0x1000100000-0x100010930f irq 74,75 disabled type pci compat brcm,bcm2712-pcie (no driver attached) >> pcib0: <BCM2712 PCI-express controller> mem 0x1000110000-0x100011930f irq 76,77 on simplebus1 >> pcib0: here: 695 >> pcib0: parsing FDT for ECAM0: >> pcib0: Bus is not cache-coherent >> pcib0: PCI addr: 0x80000000, CPU addr: 0x1b80000000, Size: 0x80000000, Type: memory >> pcib0: PCI addr: 0x400000000, CPU addr: 0x1800000000, Size: 0x380000000, Type: memory >> pcib0: note: outbound memory range 1 (pci addr: 0x400000000, cpu addr: 0x1800000000, size: 0x380000000) will be ignored. >> pcib0: here: 706 >> pcib0: here: 202 >> pcib0: here: 220 >> pcib0: here: 222 >> pcib0: here: 229 >> pcib0: here: 232 >> pcib0: here: 235 >> pcib0: here: 708 >> pcib0: here: 711 >> pcib0: hardware identifies as revision 0x500. >> pcib0: note: reported link speed is 5.0 GT/s. >> pcib0: note: L1SS disabled-no property brcm,enable-l1ss in OF >> pcib0: ERROR: Unknown index 256. >> pci0: <OFW PCI bus> on pcib0 >> pci0: domain=0, physical bus=0 >> found-> vendor=0x14e4, dev=0x2712, revid=0x00 >> domain=0, bus=0, slot=0, func=0 >> class=06-04-00, hdrtype=0x01, mfdev=0 >> cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) >> lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> intpin=a, irq=0 >> powerspec 3 supports D0 D3 current D0 >> secbus=1, subbus=1 >> pcib1: <PCI-PCI bridge> irq 88 at device 0.0 on pci0 >> pcib0: pci_host_generic_core_alloc_resource FAIL: type=3, rid=36, start=0000000000000000, end=00000000ffffffff, count=0000000100000000, flags=142 >> pcib1: failed to allocate initial prefetch window: 0-0xffffffff >> pcib1: domain 0 >> pcib1: secondary bus 1 >> pcib1: subordinate bus 1 >> pcib1: memory decode 0x80000000-0x800fffff >> pci1: <PCI bus> on pcib1 >> pcib1: allocated bus range (1-1) for rid 0 of pci1 >> pci1: domain=0, physical bus=1 >> found-> vendor=0x1ed0, dev=0x2283, revid=0x00 >> domain=0, bus=1, slot=0, func=0 >> class=01-08-02, hdrtype=0x00, mfdev=0 >> cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) >> lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> intpin=a, irq=0 >> powerspec 3 supports D0 D3 current D0 >> MSI supports 8 messages, 64 bit, vector masks >> MSI-X supports 9 messages in map 0x10 >> map[10]: type Memory, range 64, base 0, size 14, memory disabled >> pcib1: slot 0 INTA is routed to irq 89 >> nvme0: <Generic NVMe Device> irq 89 at device 0.0 on pci1 >> pcib1: allocated memory range (0x80000000-0x80003fff) for rid 10 of nvme0 >> nvme0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000 >> nvme0: attempting to allocate 5 MSI-X vectors (9 supported) >> nvme0: unable to allocate MSI-X >> nvme0: attempting to allocate 2 MSI vectors (8 supported) >> nvme0: unable to allocate MSI >> nvme0: CapLo: 0xff03ffff: MQES 65535, CQR, AMS WRRwUPC, TO 255 >> nvme0: CapHi: 0x00000020: DSTRD 0, CSS 1, CPS 0, MPSMIN 0, MPSMAX 0 >> nvme0: Version: 0x00010300: 1.3 >> simplebus1: <reset-controller@119500> mem 0x1000119500-0x100011950f compat brcm,bcm7216-pcie-sata-rescal (no driver attached) >> pcib2: <BCM2712 PCI-express controller> mem 0x1000120000-0x100012930f irq 78,79 on simplebus1 >> pcib2: here: 695 >> pcib2: parsing FDT for ECAM0: >> pcib2: Bus is not cache-coherent >> pcib2: PCI addr: 0x0, CPU addr: 0x1f00000000, Size: 0xfffffffc, Type: memory >> pcib2: PCI addr: 0x400000000, CPU addr: 0x1c00000000, Size: 0x300000000, Type: memory >> pcib2: note: outbound memory range 1 (pci addr: 0x400000000, cpu addr: 0x1c00000000, size: 0x300000000) will be ignored. >> pcib2: here: 706 >> pcib2: here: 202 >> pcib2: here: 220 >> pcib2: here: 222 >> pcib2: here: 229 >> pcib2: here: 232 >> pcib2: here: 235 >> pcib2: here: 708 >> pcib2: here: 711 >> pcib2: hardware identifies as revision 0x500. >> pcib2: note: reported link speed is 5.0 GT/s. >> pcib2: note: L1SS disabled-no property brcm,enable-l1ss in OF >> pcib2: ERROR: Unknown index 256. >> pci2: <OFW PCI bus> on pcib2 >> pci2: domain=2, physical bus=0 >> found-> vendor=0x14e4, dev=0x2712, revid=0x00 >> domain=2, bus=0, slot=0, func=0 >> class=06-04-00, hdrtype=0x01, mfdev=0 >> cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) >> lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> intpin=a, irq=0 >> powerspec 3 supports D0 D3 current D0 >> secbus=1, subbus=1 >> pcib3: <PCI-PCI bridge> irq 90 at device 0.0 on pci2 >> pcib2: pci_host_generic_core_alloc_resource FAIL: type=3, rid=36, start=0000000000000000, end=00000000ffffffff, count=0000000100000000, flags=142 >> pcib3: failed to allocate initial prefetch window: 0-0xffffffff >> pcib3: domain 2 >> pcib3: secondary bus 1 >> pcib3: subordinate bus 1 >> pcib3: memory decode 0x0-0x7fffff >> pci3: <PCI bus> on pcib3 >> pcib3: allocated bus range (1-1) for rid 0 of pci3 >> pci3: domain=2, physical bus=1 >> found-> vendor=0x1de4, dev=0x0001, revid=0x00 >> domain=2, bus=1, slot=0, func=0 >> class=02-00-00, hdrtype=0x00, mfdev=0 >> cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) >> lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> intpin=a, irq=255 >> powerspec 3 supports D0 D1 D3 current D0 >> MSI-X supports 61 messages in map 0x10 >> map[10]: type Memory, range 32, base 0xffffc000, size 14, memory disabled >> map[14]: type Memory, range 32, base 0xffc00000, size 22, memory disabled >> map[18]: type Memory, range 32, base 0xffff0000, size 16, memory disabled >> rpone0: <RaspberryPi RP1 Southbridge> at device 0.0 on pci3 >> pcib3: allocated memory range (0-0x3fff) for rid 10 of rpone0 >> rpone0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0 >> rpone0: rid 0x10: start=0, size=0x4000 >> pcib3: allocated memory range (0x400000-0x7fffff) for rid 14 of rpone0 >> rpone0: Lazy allocation of 0x400000 bytes rid 0x14 type 3 at 0x400000 >> rpone0: rid 0x14: start=0x400000, size=0x400000 >> pcib3: allocated memory range (0x10000-0x1ffff) for rid 18 of rpone0 >> rpone0: Lazy allocation of 0x10000 bytes rid 0x18 type 3 at 0x10000 >> rpone0: rid 0x18: start=0x10000, size=0x10000 >> simplebus1: <msi-controller@130000> mem 0x1000130000-0x10001300bf compat brcm,bcm2712-mip-intc (no driver attached) >> simplebus1: <msi-controller@131000> mem 0x1000131000-0x10001310bf compat brcm,bcm2712-mip-intc (no driver attached) >> bcm283x_dwcotg0: <DWC OTG 2.0 integrated USB controller (bcm283x)> mem 0x1000480000-0x100048ffff irq 80 on simplebus1 >> usbus0 on bcm283x_dwcotg0 >> bcm283x_dwcotg0: usbpf: Attached >> simplebus1: <codec@800000> mem 0x1000800000-0x100080ffff,0x1000840000-0x1000840fff irq 81 compat raspberrypi,rpivid-vid-decoder (no driver attached) >> sdhci_fdt0: <Broadcom BCM2712 fdt SDHCI controller> mem 0x1000fff000-0x1000fff25f,0x1000fff400-0x1000fff5ff,0x10015040b0-0x10015040b3,0x10015200f0-0x1001520113 irq 82 on simplebus1 >> sdhci_fdt0-slot0: 200MHz 4bits VDD: VCCQ: 3.3V DRV: BACD DMA removable >> sdhci_fdt0-slot0: ============== REGISTER DUMP ============== >> sdhci_fdt0-slot0: Sys addr: 0x3c8f4800 | Version: 0x00001002 >> sdhci_fdt0-slot0: Blk size: 0x00007200 | Blk cnt: 0x00000000 >> sdhci_fdt0-slot0: Argument: 0x00000000 | Trn mode: 0x00000033 >> sdhci_fdt0-slot0: Present: 0x1fff0000 | Host ctl: 0x00000024 >> sdhci_fdt0-slot0: Power: 0x0000000f | Blk gap: 0x00000080 >> sdhci_fdt0-slot0: Wake-up: 0x00000000 | Clock: 0x00000207 >> sdhci_fdt0-slot0: Timeout: 0x0000000e | Int stat: 0x00000000 >> sdhci_fdt0-slot0: Int enab: 0x027f003b | Sig enab: 0x00000000 >> sdhci_fdt0-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 >> sdhci_fdt0-slot0: Caps: 0x15eac832 | Caps2: 0x8000a577 >> sdhci_fdt0-slot0: Max curr: 0x00080008 | ADMA err: 0x00000000 >> sdhci_fdt0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 >> sdhci_fdt0-slot0: =========================================== >> sdhci_fdt0: 1 slot(s) allocated >> sdhci_fdt0-slot0: Card inserted >> mmc0: <MMC/SD bus> on sdhci_fdt0 >> sdhci_fdt1: <Broadcom BCM2712 fdt SDHCI controller> mem 0x1001100000-0x100110025f,0x1001100400-0x10011005ff irq 83 on simplebus1 >> sdhci_fdt1-slot0: 200MHz 4bits VDD: VCCQ: 3.3V DRV: BACD DMA removable >> sdhci_fdt1-slot0: ============== REGISTER DUMP ============== >> sdhci_fdt1-slot0: Sys addr: 0x00000000 | Version: 0x00001002 >> sdhci_fdt1-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 >> sdhci_fdt1-slot0: Argument: 0x00000000 | Trn mode: 0x00000000 >> sdhci_fdt1-slot0: Present: 0x000f0000 | Host ctl: 0x00000000 >> sdhci_fdt1-slot0: Power: 0x0000000f | Blk gap: 0x00000080 >> sdhci_fdt1-slot0: Wake-up: 0x00000000 | Clock: 0x0000fa07 >> sdhci_fdt1-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 >> sdhci_fdt1-slot0: Int enab: 0x027f003b | Sig enab: 0x00000000 >> sdhci_fdt1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 >> sdhci_fdt1-slot0: Caps: 0x15eac832 | Caps2: 0x8000a577 >> sdhci_fdt1-slot0: Max curr: 0x00080008 | ADMA err: 0x00000000 >> sdhci_fdt1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 >> sdhci_fdt1-slot0: =========================================== >> sdhci_fdt1: 1 slot(s) allocated >> sdhci_fdt1-slot0: Card inserted >> mmc1: <MMC/SD bus> on sdhci_fdt1 >> simplebus1: <v3d@2000000> mem 0x1002000000-0x1002003fff,0x1002008000-0x100200dfff irq 84,85 disabled compat brcm,2712-v3d (no driver attached) >> simplebus1: <pisp_be@880000> mem 0x1000880000-0x1000883fff irq 87 compat raspberrypi,pispbe (no driver attached) >> clk_fixed12: <Fixed factor clock> disabled on ofw_clkbus0 >> ....blablabla... >> >> gpioled0: <GPIO LEDs> on ofwbus0 >> gpioled0: <PWR> failed to map pin >> gpioled0: <ACT> failed to map pin >> clk_fixed12: clock-fixed has no clock-frequency >> ofwbus0: <cam1_clk> disabled compat fixed-clock (no driver attached) >> clk_fixed12: clock-fixed has no clock-frequency >> ofwbus0: <cam0_clk> disabled compat fixed-clock (no driver attached) >> ofwbus0: <cooling_fan> disabled compat pwm-fan (no driver attached) >> ofwbus0: <pwr_button> compat gpio-keys (no driver attached) >> crypto: assign cryptosoft0 driver id 0, flags 0x6000000 >> armv8crypto0: <AES-CBC,AES-XTS,AES-GCM> >> crypto: assign armv8crypto0 driver id 1, flags 0xe000000 >> Device configuration finished. >> Enabling IDC ICache sync >> Enabling LSE atomics in the kernel >> procfs registered >> Timecounters tick every 1.000 msec >> lo0: bpf attached >> vlan: initialized, using hash tables with chaining >> IPsec: Initialized Security Association Processing. >> tcp_init: net.inet.tcp.tcbhashsize auto tuned to 32768 >> usbus0: 480Mbps High Speed USB v2.0 >> ugen0.1: <DWCOTG OTG Root HUB> at usbus0 >> uhub0 on usbus0 >> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0 >> bcm2835_cpufreq0: Boot settings: >> bcm2835_cpufreq0: current ARM 1500MHz, Core 500MHz, SDRAM 0MHz, Turbo OFF >> bcm2835_cpufreq0: max/min ARM -1894/1500MHz, Core 910/500MHz, SDRAM 400/400MHz >> bcm2835_cpufreq0: current Core 838mV, SDRAM_C 600mV, SDRAM_I 600mV, SDRAM_P 1100mV >> bcm2835_cpufreq0: max/min Core 828/760mV, SDRAM_C 760/600mV, SDRAM_I 760/600mV, SDRAM_P 1100/1100mV >> bcm2835_cpufreq0: Temperature 26.2C >> uhub0: 1 port with 1 removable, self powered >> nvme0: Resetting controller due to a timeout. >> nvme0: event="start" >> nvme0: event="success" >> nvme0: aborting outstanding admin command >> nvme0: IDENTIFY (06) sqid:0 cid:15 nsid:0 cdw10:00000001 cdw11:00000000 >> nvme0: ABORTED_BY_REQUEST (00/07) crd:0 m:0 dnr:1 p:0 sqid:0 cid:15 cdw0:0 >> nvme0: done aborting outstanding admin >> nvme0: nvme_identify_controller failed! >> sdhci_fdt0-slot0: Divider 250 for freq 400000 (base 200000000) >> mmc0: Probing bus >> mmc0: SD probe: failed >> mmc0: MMC probe: OK (OCR: 0x40ff8080) >> mmc0: Current OCR: 0x00ff8080 >> mmc0: Probing cards >> mmc0: New card detected (CID 150100414a54443452060684c09bba00) >> mmc0: New card detected (CSD d02701320f5903fff6dbffef8e404000) >> mmc0: Card at relative address 0x0002 added: >> mmc0: card: MMCHC AJTD4R 0.6 SN 0684C09B MFG 11/2023 by 21 0x0000 >> mmc0: quirks: 0 >> mmc0: bus: 4bit, 52MHz (high speed timing) >> mmc0: memory: 30535680 blocks, erase sector 1024 blocks >> mmc0: setting transfer rate to 52.000MHz (high speed timing) >> sdhci_fdt0-slot0: Divider 2 for freq 50000000 (base 200000000) >> mmc0: setting bus width to 4 bits high speed timing >> mmcsd0: taking advantage of TRIM >> mmcsd0: cache size 65536KB >> mmcsd0: 16GB <MMCHC AJTD4R 0.6 SN 0684C09B MFG 11/2023 by 21 0x0000> at mmc0 50.0MHz/4bit/65535-block >> mmcsd0boot0: 4MB partition 1 at mmcsd0 >> mmcsd0boot1: 4MB partition 2 at mmcsd0 >> mmcsd0rpmb: 4MB partition 3 at mmcsd0 >> sdhci_fdt1-slot0: Divider 250 for freq 400000 (base 200000000) >> mmc1: Probing bus >> GEOM: new disk mmcsd0 >> GEOM: new disk mmcsd0boot0 >> GEOM: new disk mmcsd0boot1 >> mmc1: SD probe: failed >> mmc1: MMC probe: failed >> mmc1: Current OCR: 0x00000000 >> mmc1: No compatible cards found on bus >> pci0: driver added >> pci1: driver added >> pci2: driver added >> pci3: driver added >> CPU 0: ARM Cortex-A76 r4p1 affinity: 0 0 >> Cache Type = <IDC,64 byte CWG,64 byte ERG,64 byte D-cacheline,PIPT I-cache,64 byte I-cacheline> >> Trying to mount root from ufs:/dev/ufs/rootfs [rw]... >> Instruction Set Attributes 0 = <DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL> >> Instruction Set Attributes 1 = <RCPC-8.3,DCPoP> >> Instruction Set Attributes 2 = <> >> Processor Features 0 = <CSV3,CSV2,RAS,AdvSIMD+HP,FP+HP,EL3,EL2,EL1,EL0 32> >> Processor Features 1 = <MTE_frac,PSTATE.SSBS> >> Processor Features 2 = <> >> Memory Model Features 0 = <TGran4,TGran64,TGran16,SNSMem,BigEnd,16bit ASID,1TB PA> >> Memory Model Features 1 = <XNX,PAN+ATS1E1,LO,HPD+TTPBHA,VH,16bit VMID,HAF+DS> >> Memory Model Features 2 = <32bit CCIDX,48bit VA,IESB,UAO,CnP> >> Memory Model Features 3 = <> >> Memory Model Features 4 = <> >> Debug Features 0 = <DoubleLock,2 CTX BKPTs,4 Watchpoints,6 Breakpoints,PMUv3p1,Debugv8p2> >> Debug Features 1 = <> >> Auxiliary Features 0 = <> >> Auxiliary Features 1 = <> >> AArch32 Instruction Set Attributes 5 = <RDM,CRC32,SHA2,SHA1,AES+VMULL,SEVL> >> AArch32 Media and VFP Features 0 = <FPRound,FPSqrt,FPDivide,DP VFPv3+v4,SP VFPv3+v4,AdvSIMD> >> AArch32 Media and VFP Features 1 = <SIMDFMAC,FPHP Arith,SIMDHP Arith,SIMDSP,SIMDInt,SIMDLS,FPDNaN,FPFtZ> >> L1 cache: 64KB (instruction), 64KB (data) >> L2 cache: 512KB (unified) >> L3 cache: 2048KB (unified) >> CPU 1: ARM Cortex-A76 r4p1 affinity: 1 0 >> L1 cache: 64KB (instruction), 64KB (data) >> L2 cache: 512KB (unified) >> L3 cache: 2048KB (unified) >> CPU 2: ARM Cortex-A76 r4p1 affinity: 2 0 >> L1 cache: 64KB (instruction), 64KB (data) >> L2 cache: 512KB (unified) >> L3 cache: 2048KB (unified) >> CPU 3: ARM Cortex-A76 r4p1 affinity: 3 0 >> L1 cache: 64KB (instruction), 64KB (data) >> L2 cache: 512KB (unified) >> L3 cache: 2048KB (unified) >> gic0: using for IPIs >> Release APs...done >> Enabling CnP >> TCP_ratelimit: Is now initialized >> WARNING: WITNESS option enabled, expect reduced performance. >> regulator: shutting down unused regulators >> regulator: shutting down vcc-sd... ok >> regulator: shutting down cam-dummy-reg... ok >> Warning: no time-of-day clock registered, system time will not be set accurately >> Dual Console: Serial Primary, Video Secondary >> start_init: trying /sbin/init >> Setting hostuuid: 35336664-6466-3135-6637-356132363035. >> Setting hostid: 0x930c7861. >> Starting file system checks: >> /dev/ufs/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS >> /dev/ufs/rootfs: clean, 2742105 free (441 frags, 342708 blocks, 0.0% fragmentation) >> Mounting local filesystems:. >> ELF ldconfig path: /lib /usr/lib /usr/lib/compat >> 32-bit compatibility ldconfig path: /usr/lib32 >> Setting hostname: generic. >> Setting up harvesting: RANDOMDEV,[CALLOUT],[UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED >> Feeding entropy: . >> lo0: link state changed to UP >> Starting Network: lo0. >> lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 >> options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> >> inet 127.0.0.1 netmask 0xff000000 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >> groups: lo >> nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> >> Starting devd. >> route: message indicates error: File exists >> add host 127.0.0.1: gateway lo0 fib 0: route already in table >> route: message indicates error: File exists >> add host ::1: gateway lo0 fib 0: route already in table >> add net fe80::: gateway ::1 >> add net ff02::: gateway ::1 >> add net ::ffff:0.0.0.0: gateway ::1 >> add net ::0.0.0.0: gateway ::1 >> Clearing /tmp (X related). >> Updating motd:. >> Updating /var/run/os-release done. >> Creating and/or trimming log files. >> Starting syslogd. >> No core dumps found. >> Mounting late filesystems:. >> Starting powerd. >> device is not configured >> powerd:error reading supported CPU frequencies: Invalid argument >> /etc/rc: WARNING: failed to start powerd >> Performing sanity check on sshd configuration. >> Starting sshd. >> Starting cron. >> Starting background file system checks in 60 seconds. >> >> Thu Nov 6 06:01:38 UTC >> FreeBSD/arm64 (generic) (ttyu0) >> >> login: root >> Password: >> Nov 6 06:01:45 generic login[3197]: ROOT LOGIN (root) ON ttyu0 >> Last login: Thu Nov 6 06:00:30 on ttyu0 >> FreeBSD 16.0-CURRENT (GENERIC) #4: Thu Nov 6 05:10:09 UTC 2025 >> >> Welcome to FreeBSD! >> >> Release Notes, Errata: https://www.FreeBSD.org/releases/ >> Security Advisories: https://www.FreeBSD.org/security/ >> FreeBSD Handbook: https://www.FreeBSD.org/handbook/ >> FreeBSD FAQ: https://www.FreeBSD.org/faq/ >> Questions List: https://www.FreeBSD.org/lists/questions/ >> FreeBSD Forums: https://forums.FreeBSD.org/ >> >> Documents installed with the system are in the /usr/local/share/doc/freebsd/ >> directory, or can be installed later with: pkg install en-freebsd-doc >> For other languages, replace "en" with a language code like de or fr. >> >> Show the version of FreeBSD installed: freebsd-version ; uname -a >> Please include that output and any error messages when posting questions. >> Introduction to manual pages: man man >> FreeBSD directory layout: man hier >> >> To change this login announcement, see motd(5). >> root@generic:~ # uname -a >> FreeBSD generic 16.0-CURRENT FreeBSD 16.0-CURRENT #4: Thu Nov 6 05:10:09 UTC 2025 root@fbsd5pro:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 >> root@generic:~ # root@generic:~ # sysctl hw >> hw.machine: arm64 >> hw.model: ARM Cortex-A76 r4p1 >> hw.ncpu: 4 >> hw.byteorder: 1234 >> hw.physmem: 4264730624 >> hw.usermem: 4157288448 >> hw.pagesize: 4096 >> hw.machine_arch: aarch64 >> hw.realmem: 4290248704 >> hw.cpufreq.temperature: 27388 >> — >> >> >> >> >>> Am 13.09.2026 um 02:48 schrieb Warner Losh <imp@bsdimp.com>: >>> >>> >>> >>> On Sat, Sep 12, 2026 at 6:14 PM Jeremy McMillan <jtmcmillan@pm.me> wrote: >>> I totally misunderstood the loader.kboot build. It was probably wishful thinking, and I think maybe loader.kboot might not be the best way to get to a good official RPi5 FreeBSD binary distribution. >>> >>> What I think I want is >>> >>> RPI5 Firmware >>> \--> FreeBSD loader hiding in a bootable zipped Linux kernel image file >>> \--> FreeBSD. >>> >>> What I think needs to be done is >>> • >>> figuring out how to build a FreeBSD loader image that RPi5 Firmware will happily try to boot >>> • figuring out how to get that loader to find, and load the DT setup that RPi5 firmware provides, apply additional DT changes as needed >>> • fixing any remaining bugs from the memory map if that didn't solve Mark's kernel boot error >>> • working through remaining issues with FreeBSD FDT kernel until we can use critical path devices like USB and PCIe block devices and console (and probably also the thermal/fan) reliably >>> • fixing remaining FDT device driver issues for all the other drivers. >>> >>> >>> So, if you WANT /boot/loader functionality, this is the right path. Usually, Linux systems have a kernel and an initrd that are typically separate but can be combined. The kernel is just a minimal kernel configuration that understands the devices you want to use in the loader.kboot program. loader.kboot can act as init. I think you need four things from this environment: (1) the FDT (this is usually in /sys somewhere that escapes my memory), (2) SMBIOS (usually separate from FDT) (3) Any shared state that the linux kernel has to hand off to the next kernel (gicv3, for example, can't be reset so the booting kernel has to pass this state to the kexec kernel). (4) The memory map, with the shared state that's needed for that handoff marked. The loader has mechanisms for some limited FDT hacking, but your exact use case here may be tricky. This offers more flexibility, but that can also be a curse during early bring-up. However, if the Linux kernel can initialize the hardware and the FreeBSD kernel can just attach to already initialized hardware, that might make up for the hassle, though it can foster too much dependency on having the 'system firmware' initializing everything. So there's tradeoffs, but this can be a win if the shared state is tiny or the empty set. >>> >>> If you just want to boot the kernel, getting the early code to grok the FDT for all its needs is all you need. You wouldn't be able to transform the FDT as easily, but you can get the kernel going faster and have fewer build headaches. You can also compile the initial root image directly into the kernel during early bringup. The down side is you might lose the Linux kernel's init. >>> >>> Warner >>> I think EDK2 stuff is cool, and it was certainly a critical enabler, but I suspect everyone would be happier with one less thing that can break. I think I want to try making loader do what's needed. >>> On Saturday, September 12th, 2026 at 6:38 PM, Warner Losh <imp@bsdimp.com> wrote: >>>> >>>> >>>> On Sat, Sep 12, 2026 at 4:23 PM Mark Millard <marklmi@yahoo.com> wrote: >>>> On 9/11/26 10:21, Jeremy McMillan wrote: >>>>> >>>>> >>>>> I was planning to crack this nut open this weekend with some research on the current state of loader.kboot and smoke testing the RPi5 boot targeting loader.kboot. >>>>> >>>>> I see this as a stepping stone to proper supportable FDT kernel on RPi5, and also ideas about how to best manage custom overlays. Eventually, I want to get to a point where I can plug an I2C ADC chip module into RPi5, put together an overlay, and get a usable audio input device when I boot FreeBSD, for example. >>>>> >>>>> So, if I may follow up Mark's question, what stumbling blocks am I likely to hit first, and is there any advice inuring from past struggles that might help me out? >>>> >>>> If I gather from Warner's reply to my note correctly, the >>>> sequencing/flow issues would be something like (for example): >>>> >>>> >>>> RPi5 Firmware -> Host Linux Kernel -> loader.kboot -> FreeBSD kernel >>>> >>>> would not populate the information that the FreeBSD kernel needs. >>>> >>>> >>>> RPi5 Firmware -> EDK2 (UEFI/DeviceTree style) -> Host Linux Kernel -> >>>> loader.kboot -> FreeBSD kernel >>>> >>>> It would populate the information but the FreeBSD kernel then has the >>>> basically same problems it has for the original: >>>> >>>> RPi5 Firmware -> EDK2 (UEFI/DeviceTree style) -> FreeBSD kernel >>>> >>>> Thus, involving Host Linux Kernel -> loader.kboot is to no advantage for >>>> this type of context. >>>> >>>> >>>> Also, there would be no point for inserting such into: >>>> >>>> RPi5 Firmware -> EDK2 (UEFI/ACPI style) -> FreeBSD kernel >>>> >>>> Yes. LinuxBoot is for when you only have a linux kernel to launch from, >>>> and the vast majority of those cases you have a tiny sliver of EDK2 >>>> or similar that then loads the linux kernel as its first device driver >>>> and takes over from there (so the board integrator doesn't have to >>>> write two versions of board integration software, just one: Linux). >>>> >>>> even if the insertion worked: no advantage to the insertion. >>>> >>>> I'm not seeing one for this use case, but who knows... If you really >>>> wanted, you would have to investigate whatever interface Linux uses >>>> to boot early and put that directly into the FreeBSD kernel, but then >>>> you lose all the /boot/loader functionality. >>>> >>>> Warner >>>> (EDK2 could be an over specific example for the general structure.) >>>> >>>> >>>>> --- >>>>> JTM >>>>> >>>>> -------- Original Message -------- >>>>> On Friday, 09/11/26 at 11:39 Mark Millard <marklmi@yahoo.com> wrote: >>>>> Hello Warner, >>>>> >>>>> This is just an informational query for my background knowledge. >>>>> >>>>> Note: I'm not dealing here with the FreeBSD kernel having support for >>>>> RPi5 DeviceTree content or the RP1 based structure or such. >>>>> >>>>> Context: >>>>> Various Linux distributions boot the RPi* families that they support >>>>> directly, no U-Boot or EDK2 or the like, including booting the RPi5 that >>>>> way. For the RPi5, they support, for example, USB booting and such that >>>>> U-Boot still does not support. >>>>> >>>>> That forms an example of a more general question of if loader.kboot and >>>>> such a linux kernel would be a viable alternative to the normal FreeBSD >>>>> U-Boot port style of support for aarch64? >>>>> >>>>> (As stands the RPi5 draft EDK2's provide a DeviceTree mode alternative >>>>> to ACPI mode for Linux booting. The EDK2's are not as limited as U-Boot >>>>> is for what is supported for booting [so far].) >>>>> >>>>> -- >>>>> === >>>>> Mark Millard >>>>> marklmi at yahoo.com >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> === >>>> Mark Millard >>>> marklmi at yahoo.com >> >> >> >> > > >