Hi, thanks for the recipe. >4) Pull a copy down of the armv7.img.gz or build the earmv7hf release. If all you need this for, is the bootarm.efi file, you can get that from https://cdn.NetBSD.org/pub/NetBSD/NetBSD-9.0/evbarm-earmv7hf/installation/misc/bootarm.efi or corresponding for the release you want to spin up. >6) There are a couple of ways to proceed at this point.. if you can get > the FFS mounted from the armv7.img and rpi.img images you can create the > needed parts from those (I was not able to do this from a amd64 box, > BTW, but YMMV). If that doesn't work for whatever reason, create a > image with a MSDOS MBR on it that has a 80MB 32bit FAT and a FFS format > 1 filesystem for the rest of the disk (newfs -O1 ....). Don't forget to > put a MBR on it with fdisk and make the MS-DOS filesystem active. I managed to do this part on NetBSD/amd64 8.0 by using a vnd device: vnconfig -c /dev/vnd0d rpi.img fdisk vnd0 disklabel vnd0 mount -t msdos /dev/vnd0e /mnt ... umount /mnt mount -t ffs /dev/vnd0a /mnt ... umount /mnt vnconfig -u vnd0 I do not yet have liftoff in my effort to boot an armv6 kernel yet, though; I'm hitting a kernel assert in config_vsearch() in subr_autoconf.c: KASSERT(ifattr || cfdriver_iattr_count(parent->dv_cfdriver) <2); fires for me. I mistakenly built from a 9.99.92 tree, though, so I'm reverting my tree and re-trying with 9.0. Regards, - Håvard