Re: Potential UEFI boot.cfg bug

On Mon, 18 May 2026 21:40:48 +0100
Sad Clouds <[email protected]> wrote:

> > Not really, if it is as I suspect, it is more a (mostly undocumented)
> > limitation in the protocol between the boot program and the kernel.
> 
> Thanks for the info, this probably explains it. I used similar wedges
> names on Raspberry Pi and did not remember noticing the issue. But I
> guess different ports use different boot protocols.
> 
> cat /boot/cmdline.txt
> root=NAME=NetBSD-root console=fb
> #root=NAME=NetBSD-diag console=fb
> 
> I will shorten the names and test again.

I think I may just give up boot.cfg as I can't get it to work reliably
with multiple root partitions.

I reduced the names of root partitions, to make sure "NAME=<label>"
fits within 15 chars. It still refuses to boot from the correct
partition when using boot.cfg. Manually typing "boot NAME=root-main:"
at the bootloader prompt does boot from the correct partition.

# gpt show -l ld0
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34       2014         Unused
       2048     262144      1  GPT part - boot-efi
     264192    2097152      2  GPT part - root-diag
    2361344    4194304      3  GPT part - root-main
    6555648  127660032      4  GPT part - cgd
  134215680       2015         Unused
  134217695         32         Sec GPT table
  134217727          1         Sec GPT header

# cat /boot-efi/efi/netbsd/boot.cfg 
# Boot into NetBSD diagnostic environment
menu=Boot root-diag:rndseed /var/db/entropy-file;boot NAME=root-diag:
menu=Boot root-diag single user:rndseed /var/db/entropy-file;boot NAME=root-diag: -s

# Boot into NetBSD main environment
menu=Boot root-main:rndseed /var/db/entropy-file;boot NAME=root-main:
menu=Boot root-main single user:rndseed /var/db/entropy-file;boot NAME=root-main: -s

menu=Drop to boot prompt:prompt
default=3
timeout=5
clear=1