On Sat, 23 May 2026, Robert Elz wrote:
Another thing to check is that the boot.cfg file is being used at all. Put a distinctive banner in it, so when it gets read, it is obvious that it is really being used. It is possible that nothing you put there is being seen.
Yeah, I scratched my head a bit for the correct boot.cfg when I experimented with RootFS-on-RAID-over-wedges some time back: https://www.unitedbsd.com/d/1479-using-some-kind-of-raid0stripe-for-root-filesystem/7 There, only the boot.cfg in EFI:/efi/netbsd/ mattered. The one written by sysinst(8) inside the RAID root wedge didn't matter. And, of course, here, only the /boot.cfg in the `Root1' wedge mattered. The others are not read by the bootloader.
On my system, I haven't yet made efiboot find a boot.cfg file (not on the root filesys, not any of those, nor in the EFI partition, any plausible path) - but finding out why hasn't been a priority (I just dispensed boot.cfg files all over the place, each with a banner saying which one was found - none ever appeared, just the default boot netbsd flag banner).
Is there any kind of RAID/CCD/CGD involved in your setup? -RVP
