Guix also works fine on Pine64 boards. The Pinebook works (at least somewhat), but the RockPro RK3399 do well. These are all relatively cheap but you might have to figure out some of the quirks as you go (: I guess similar to @theesm 's reply most RISC-V boards ought to work (though I have not tested any of that in a while)
I guess the best board for you primarily depends on how you intend to use it!
Can I get a hint at what one can use as a starting point? I see snippets of config here and there and mention of having to do something with uboot, but what is everyone starting with to bootstrap? Are you starting from some other Linux with the guix package manager installed? Is there a minimal guix boot disk somewhere that can be booted on arm? The mnt reform link above points at hardware much like what I have, but I’m not sure where to start.
I eventually had to settle with Armbian. I can’t recall why I had to give up, but the motherboard really needs UEFI support if one wants to run Guix on an ARM board.
u may get risc v single board computers here… thats in the price range
The extlinux.conf approach matches what I’ve seen discussed for rk3588 boards generally: stock U-Boot scans /boot/extlinux, so passing u-boot-bootloader in the bootloader-configuration is what makes Guix cooperate instead of expecting to write the bootloader itself. For the Orange Pi 5+, the practical check is whether its DTS is upstreamed in the kernel tree you mentioned; if it is, the same layout should hold, and if not you’re building a custom kernel package around it. Keeping the Guix partitions offset from the eMMC U-Boot region is worth planning before you partition.
The distinction between stock U-Boot actually finding extlinux.conf versus Armbian’s install scripts overwriting the boot chain is the part that clicks for me. On the Orange Pi 5+, the main thing I’d verify before assuming a direct port is whether its upstream DTS is already in mainline; the bootloader-configuration approach only helps if the kernel can describe the board. If the DTS is still out-of-tree, you’d be maintaining a custom kernel package regardless of U-Boot. Worth confirming that first, since it determines how much effort this really costs.