Hi Markus, The version of bootarm.efi that I have is able to boot from my MBR disk. I used the strings command you provided and it looks like it is looking for efiboot.plist. I still haven't found documentation on the allowable contents of efiboot.plist file anywhere. Sounds like the format was created by Apple? I might have to take a look at the source code to decipher what is possible... I guess I could put a empty file in /etc/efiboot.plist and see if bootarm.efi finds it.
-- George Morgan [email protected] On Sat, Jan 23, 2021, at 12:12 AM, Markus Kilbinger wrote: > Hi George, > > Am Sa., 23. Jan. 2021 um 00:16 Uhr schrieb George Morgan > <[email protected]>: > > [...] > > On which device / filesystem does the efiboot.plist or boot.cfg need to be > > created on? > > IIRC bootarm.efi uses the first netbsd / ffs partition to search for > that file, but maybe it's limited to gpt partitions (efi means gpt > normally; I haven't tried / used mbr oder disklabel for that). > > Maybe you can try / see that at the bootarm.efi prompt where you type > 'ls', 'dev' etc. to find out what was found by / is available for > bootarm.efi (if none, migrating mbr to gpt on the sata disk would be > an option). > > 'strings bootarm.efi | grep boot' should show you whether > '/etc/efiboot.plist' or boot.cfg would be used. > > Markus. >
