OPNsense Forum

English Forums => Hardware and Performance => Topic started by: senser on December 29, 2025, 08:33:52 PM

Title: which coreboot payload
Post by: senser on December 29, 2025, 08:33:52 PM
I want to switch from AMI Bios to coreboot on my Topton N150 box, which is currently running opnsense 25.7 (barebone).

So I am configuring coreboot (v25.12) for my mainboard (Topton ADL: TWL (X2E_N150)) on a fedora box and I am currently stuck at figuring out what payload I should choose.
This is what gpart sais about my nvme disk containing opnsense:
$ gpart show
=>       40  488397088  nda0  GPT  (233G)
         40     532480     1  efi  (260M)
     532520       1024     2  freebsd-boot  (512K)
     533544        984        - free -  (492K)
     534528   16777216     3  freebsd-swap  (8.0G)
   17311744  471085056     4  freebsd-zfs  (225G)
  488396800        328        - free -  (164K)


AFAIK, I can not use seabios payload as it requires an MBR partition...or does it? Do I have one? Maybe it is hidden?
Sorry if this is a stupid question - but when I flash this coreboot.rom I'd REALLY like my router to boot up again... :)
Title: Re: which coreboot payload
Post by: Maurice on December 29, 2025, 09:36:16 PM
OPNsense GPT installations are hybrid. They have a GPT + ESP ("efi" partition) as well as an MBR + traditional second-stage boot loader ("freebsd-boot" partition). So the same disk can be booted using either UEFI or legacy BIOS.

Cheers
Maurice
Title: Re: which coreboot payload
Post by: senser on December 29, 2025, 10:21:45 PM
So we can chose either edk2 OR seabios payload and we should be re-booting fine?
So what should I choose? :)
Title: Re: which coreboot payload
Post by: Maurice on December 29, 2025, 10:28:27 PM
Not sure what the benefits of legacy BIOS would be, but maybe I'm not seeing the full picture.
Title: Re: which coreboot payload
Post by: senser on December 29, 2025, 10:46:18 PM
Legacy BIOS (seabios) has fewer coreboot configuration options and is probably the safest option? For UEFI (edk2) there is the choice of mrchromebox fork or original for example.

But using ,,current" (UEFI) solutions seems like a good idea. :) Should I just choose the default selection for UEFI (which is: edk2 - mrchromebox fork)?