| 1 |
On Tuesday, 1 October 2019 18:47:25 BST Mick wrote: |
| 2 |
|
| 3 |
> As I understand it this ID must be the ID bootctl itself reports. |
| 4 |
> However, earlier bootctl versions do not have this set-default ID |
| 5 |
> subcommand. If you run bootctl with no arguments does it show up? |
| 6 |
|
| 7 |
No, it behaves the same as 'bootctl status'. |
| 8 |
|
| 9 |
> > Bootctl and efibootmgr seem to operate orthogonally, at least in some |
| 10 |
> > respects, which doesn't help me to uderstand what's going on. |
| 11 |
> |
| 12 |
> If you follow the UEFI spec and store one kernel per EFI/ |
| 13 |
> subdirectory, the UEFI firmware will pick them up on its own and the |
| 14 |
> efibootmgr will list them. |
| 15 |
> |
| 16 |
> I would think bootctl will also pick them up and add them in its own menu. |
| 17 |
|
| 18 |
My impression is that efibootmgr only picks up what it's written itself, and |
| 19 |
what the BIOS has filled in. Bootctl does do as you say, though. |
| 20 |
|
| 21 |
> If you use a suitable alphanumeric nomenclature to elevate the |
| 22 |
> subdirectory of your kernel of choice, it should be selected as the |
| 23 |
> default (hopefully). |
| 24 |
|
| 25 |
Nope: |
| 26 |
|
| 27 |
# tree /boot/EFI |
| 28 |
/boot/EFI |
| 29 |
├── BOOT |
| 30 |
│ └── BOOTX64.EFI |
| 31 |
├── systemd |
| 32 |
│ └── systemd-bootx64.efi |
| 33 |
└── TestSys |
| 34 |
└── BOOT |
| 35 |
└── bootX64.efi |
| 36 |
|
| 37 |
# ls /boot/loader/entries |
| 38 |
08-gentoo-4.19.66-rescue.conf 40-gentoo-4.19.66.conf |
| 39 |
09-gentoo-4.19.66-rescue.nonet.conf 42-gentoo-4.19.66.nox.conf |
| 40 |
30-gentoo-4.19.72.conf 44-gentoo-4.19.66.nonet.conf |
| 41 |
32-gentoo-4.19.72.nox.conf 90-testsys-4.19.72.conf |
| 42 |
34-gentoo-4.19.72.nonet.conf 92-testsys-4.19.72.nonet.conf |
| 43 |
|
| 44 |
Bootctl has picked the test system as its default (90-testsys-4.19.72), and |
| 45 |
the boot menu comes up with it selected; that's why I want to change bootctl's |
| 46 |
default selection. The two files bootx64.efi (modulo case) are identical |
| 47 |
kernel images except for CONFIG_LOCALVERSION="<...>". |
| 48 |
|
| 49 |
> Meanwhile, assuming you have set the systemd-boot timeout to a value |
| 50 |
> greater than 0, you could try pressing 'd' after you move the cursor |
| 51 |
> to the desired kernel image. I think it sets the selected image as a |
| 52 |
> default, but I don't have a systemd-boot available to see if it merely |
| 53 |
> boots the existing default setting. |
| 54 |
|
| 55 |
That's it! I didn't know about that - where is it documented? |
| 56 |
|
| 57 |
Thank you for your own patience, Mick. :) |
| 58 |
|
| 59 |
-- |
| 60 |
Regards, |
| 61 |
Peter. |
Archives