OPNsense aarch64 firmware repository

Started by Maurice, September 06, 2023, 07:28:35 PM

Previous topic - Next topic
You have to extract the bzip2-compressed VM image first.
You don't have to resize it. During first boot, the root partition and its file system automatically grow to fill the SD card.
Don't copy the entire VM image to the SD card. It contains two partitions (esp and rootfs). Copy these to the SD card (in addition to the "uboot" partition).
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).

February 27, 2025, 04:49:58 AM #136 Last Edit: February 27, 2025, 06:43:36 AM by Nordom
Quote from: Maurice on February 27, 2025, 02:02:58 AMDon't copy the entire VM image to the SD card. It contains two partitions (esp and rootfs). Copy these to the SD card (in addition to the "uboot" partition).

I extracted the bzip VM image. How do I access the esp and rootfs? From the .qcow2 file what steps are needed so I can see the ESP and RootFS folders?

Edit: I just had thought that I can use the DD command burn the .raw to my / partition that I created .I am trying that now.

Edit2: the DD command did work, but  EDK2 is unable to locate the opnsense img. Using Virtual Machine Manager I was able to create a VM using freeBSD14.2 and aarch64 archecture from the raw I created. It is just unfortunate EDK2 cannot detect it. I suspect the format is not correct for EDK2 see it. However EDK2 does try to boot my created partition and it does say its trying to loading /EFI/BOOT/BOOTAA64.EFI, however it doesn't seem like it can see any other file or folder.

OPNsense 25.1.2 aarch64 packages and sets released.
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).

OPNsense 25.1.3 aarch64 packages and sets released.
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).