Le 24 janvier 2026 16:09:06 GMT+01:00, David Lecompte <[email protected]> a écrit : >I now tried on a Rockpi 4, after installing u-boot on the SPI flash >following instructions at >https://ixypsilon.net/rock-pi-4-blobless-bootloader/ > >The outcome is very similar: > >U-Boot TPL 2024.10 (Jan 24 2026 - 14:37:36) >lpddr4_set_rate: change freq to 400MHz 0, 1 >Channel 0: LPDDR4, 400MHz >BW=32 Col=10 Bk=8 CS0 Row=15 CS=1 Die BW=16 Size=1024MB >Channel 1: LPDDR4, 400MHz >BW=32 Col=10 Bk=8 CS0 Row=15 CS=1 Die BW=16 Size=1024MB >256B stride >lpddr4_set_rate: change freq to 800MHz 1, 0 >Trying to boot from BOOTROM >Returning to boot ROM... > >U-Boot SPL 2024.10 (Jan 24 2026 - 14:37:36 +0100) >Trying to boot from SPI >## Checking hash(es) for config config-1 ... OK >## Checking hash(es) for Image atf-1 ... sha256+ OK >## Checking hash(es) for Image u-boot ... sha256+ OK >## Checking hash(es) for Image fdt-1 ... sha256+ OK >## Checking hash(es) for Image atf-2 ... sha256+ OK >## Checking hash(es) for Image atf-3 ... sha256+ OK >## Checking hash(es) for Image atf-4 ... sha256+ OK >load_simple_fit: Skip load 'atf-5': image size is 0! > > >U-Boot 2024.10 (Jan 24 2026 - 14:37:36 +0100) > >SoC: Rockchip rk3399 >Reset cause: POR >Model: Radxa ROCK Pi 4A >DRAM: 2 GiB >PMIC: RK808 >Core: 304 devices, 33 uclasses, devicetree: separate >MMC: mmc@fe320000: 1, mmc@fe330000: 0 >Loading Environment from SPIFlash... SF: Detected xt25f32 with page size 256 >Bytes, erase size 4 KiB, total 4 MiB >*** Warning - bad CRC, using default environment > >In: serial,usbkbd >Out: serial,vidconsole >Err: serial,vidconsole >Model: Radxa ROCK Pi 4A >Net: eth0: ethernet@fe300000 > >Hit any key to stop autoboot: 0 >Scanning for bootflows in all bootdevs >Seq Method State Uclass Part Name Filename >--- ----------- ------ -------- ---- ------------------------ -------- >-------- >Scanning global bootmeth 'efi_mgr': >Card did not respond to voltage select! : -110 >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 > 0 efi_mgr ready (none) 0 <NULL> >** Booting bootflow '<NULL>' with efi_mgr >Loading Boot0000 'mmc 0' failed >EFI boot manager: Cannot load any image >Boot failed (err=-14) >Scanning bootdev '[email protected]': >Card did not respond to voltage select! : -110 >Scanning bootdev '[email protected]': >rockchip_pcie pcie@f8000000: PCIe link training gen1 timeout! >rockchip_pcie pcie@f8000000: PCIe link training gen1 timeout! >scanning bus for devices... >Bus usb@fe380000: USB EHCI 1.00 >Bus usb@fe3c0000: USB EHCI 1.00 >Bus usb@fe800000: Register 2000140 NbrPorts 2 >Starting the controller >USB XHCI 1.10 >Bus usb@fe900000: Register 2000140 NbrPorts 2 >Starting the controller >USB XHCI 1.10 >scanning bus usb@fe380000 for devices... 2 USB Device(s) found >scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found >scanning bus usb@fe800000 for devices... 1 USB Device(s) found >scanning bus usb@fe900000 for devices... 1 USB Device(s) found >Scanning bootdev 'usb_mass_storage.lun0.bootdev': > 1 efi ready usb_mass_ 2 usb_mass_storage.lun0.boo >/EFI/BOOT/BOOTAA64.EFI >** Booting bootflow 'usb_mass_storage.lun0.bootdev.part_2' with efi >Booting /\EFI\BOOT\BOOTAA64.EFI >GC Warning: pthread_getattr_np or pthread_attr_getstack failed for main >thread >GC Warning: Could not open /proc/stat >Welcome, this is GNU's early boot Guile. >Use 'gnu.repl' for an initrd REPL. > >loading kernel modules... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >waiting for partition '31393730-3031-3031-3139-313133333833' to appear... >ice-9/boot-9.scm:1685:16: In procedure raise-exception: >failed to resolve partition "31393730-3031-3031-3139-313133333833" > >Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue. >GNU Guile 3.0.9 >Copyright (C) 1995-2023 Free Software Foundation, Inc. > >Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'. >This program is free software, and you are welcome to redistribute it >under certain conditions; type `,show c' for details. > >Enter `,help' for help. >scheme@(guile-user)> > >Any advice on how to boot Guix would be highly appreciated ! > >Cheers, >David. >
Hi David, I think the issue is that you're booting the image from a USB stick, but the kernel and initramfs don't have an appropriate driver. So it cannot mount the root filesystem. On my rockpi, I had to add a few modules (specifically sdhci, sdhci-pltfm, phy-rockchip-usb and phy-rockchip-inno-usb2) before I switched to the linux-libre-arm64-generic kernel, which contains these drivers. The arm64 installer is probably built with linux-libre which does not have them. You could boot another linux distro and use the manual installation procedure to work around this issue.
