Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - napyk

#1
I finally got a working opnsense on my espressobin v7. I used the img from @tsgan as a base image but wasnt able to autoboot out of the box.

I found someone in the freebsd forum who managed to get a working u-boot version with UEFI support and a FreeBSD version that works.

https://forums.FreeBSD.org/threads/freebsd-for-espressobin-marvell-armada-3700.70910/post-470496

So I used the u-boot version described in the forum and installed the 12.1 stable kernel to the image of @tsgan and my espressobin autoboots fine now.
#2
Quote from: tsgan on January 03, 2020, 10:08:42 AM
pfsense works on this device:

https://www.netgate.com/solutions/pfsense/sg-1100.html

As for OPNsense, you can try my image (it is not official one):

https://people.freebsd.org/~ganbold/OPNsense-201912171639-OpenSSL-arm-aarch64.img.xz

It works for me on espressobin.

I recently received my Espressobin v7 from Amazon and got it working with some modifications. I moved dtb/marvell/armada-3720-espressobin.dtb to efi/boot on the FAT partition and applied the following settings to u-boot (according to freebsd forum):


setenv fdt_name 'efi/boot/armada-3720-espressobin.dtb'
setenv image_name 'efi/boot/bootaa64.efi'
setenv bootmmc 'mmc dev 0; fatload mmc 0:1 $kernel_addr $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr $fdt_addr'
run bootmmc


To enable autoboot I added:

setenv bootcmd 'mmc dev 0; fatload mmc 0:1 $kernel_addr $image_name;fatload mmc 0:1 $fdt_addr $fdt_name; bootefi $kernel_addr $fdt_addr'


My only problem is that i get the following error on startup:

Startup error in /boot/lua/loader.lua:
LUA ERROR: cannot open /boot/lua/loader.lua: invalid argument.

can't load 'kernel'


So I have to run the following code in EFI console on every startup to boot into OPNsense:

set currdev=disk0p2
boot


I tried to add a variable for rootdev under System>>Settings>>Tunables but got the same error on a reboot. Did u have the same problem? How did u fix it?