Re: boot.cfg dev command not working

[RVP <rvp%SDF.ORG@localhost>]

On Sun, 23 Mar 2025, Paul Goyette wrote:

> >  What do I use for NNNN ?

The efi(8) man-page explains this:

     Many efi options require a number (####) indicating which ``Boot####''
     argument to modify.  Many options take this as an argument, but it can
     also be set with the -b option.  Note that the boot number is a hexadeci-
     mal in the range of 0 to 0xFFFF.  It need not have a leading `0x' prefix
     and it need not be zero padded to 4 hexdigits.

> Here's my current info - what would you want me to try?  And if the
> wrong thing gets deleted, how do I recover?
>
> # efi -v
> Boot0004* UEFI OS 
> HD(1,GPT,143a1b62-7eee-4032-adf8-dfe20a383bdb,0x800,0x6400000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
> Boot0005* UEFI OS 
> HD(1,GPT,adb5c6c6-f9fa-45b7-a332-5f52a4e7c0a5,0x800,0x19000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

If those 2 entried don't correspond to NetBSD's ESP partition, delete them:

efi -B -b 4
efi -B -b 5

> Boot0006* UEFI:CD/DVD Drive     BBS(Reserved(0x81),0x0000,)
> Boot0007* UEFI:Removable Device BBS(Reserved(0x82),0x0000,)
> Boot0008* UEFI:Network Device   BBS(Reserved(0x83),0x0000,)

These 3 have been created by the BIOS, based on your boot-order config. settings.
You can leave these in place (unless it confuses efi(8) and crashes it; in which
case just delete them--the firmware'll auto-create them, usually).

> And if the wrong thing gets deleted, how do I recover?

You can create entries like this, and each entry thus created moved to the
head of the `BootOrder':

efi -c -L NetBSD -d /dev/rld0 -p 1 -l '\EFI\BOOT\BOOTX64.EFI'

where,

-L	specifies the label
-d	is the disk on which the BIOS should look, for
-p	the EFI partn. (use `gpt show ...' for this) which contains
-l	the specified EFI bootloader executable file.

-RVP