| 1 |
On Sunday, 10 July 2022 15:19:08 BST Peter Humphrey wrote: |
| 2 |
> Hello list, |
| 3 |
> |
| 4 |
> One of my machines uses bootctl to offer a choice of kernel to boot (I don't |
| 5 |
> use anything else from systemd); it has these files in |
| 6 |
> /boot/loader/entries: |
| 7 |
> |
| 8 |
> 08-gentoo-5.15.32-r1-rescue.conf |
| 9 |
> 09-gentoo-5.15.32-r1-rescue.nonet.conf |
| 10 |
> 30-gentoo-5.18.10.conf |
| 11 |
> 32-gentoo-5.18.10.nox.conf |
| 12 |
> 34-gentoo-5.18.10.nonet.conf |
| 13 |
> 40-gentoo-5.15.41.conf |
| 14 |
> 42-gentoo-5.15.41.nox.conf |
| 15 |
> 44-gentoo-5.15.41.nonet.conf |
| 16 |
> |
| 17 |
> Until a few days ago, the system offered the kernels cited in those .conf |
| 18 |
> files - in the same order as I've listed them. Also of course in ascending |
| 19 |
> numerical order. Both as expected. |
| 20 |
> |
| 21 |
> Now, though, they're offered in precisely the opposite order (with the two |
| 22 |
> other usual options below them as before: Windows and Enter UEFI setup). |
| 23 |
> |
| 24 |
> What might have caused this reversal? |
| 25 |
> |
| 26 |
> $ cat /boot/loader/entries/30*f |
| 27 |
> title Gentoo 5.18.10 |
| 28 |
> version 5.18.10-gentoo |
| 29 |
> linux vmlinuz-5.18.10-gentoo |
| 30 |
> initrd intel-uc.img |
| 31 |
> options root=/dev/nvme0n1p5 net.ifnames=0 raid=noautodetect pcie_aspm=off |
| 32 |
> |
| 33 |
> $ cat /boot/loader/loader.conf |
| 34 |
> timeout 5 |
| 35 |
> default 30-gentoo-5.18.10 |
| 36 |
> |
| 37 |
> $ ls /boot/vmlinuz-5.18.10-gentoo |
| 38 |
> /boot/vmlinuz-5.18.10-gentoo |
| 39 |
> |
| 40 |
> $ efibootmgr |
| 41 |
> BootCurrent: 0001 |
| 42 |
> Timeout: 1 seconds |
| 43 |
> BootOrder: 0001,0007,0011,0008,0000 |
| 44 |
> Boot0000* Windows Boot Manager |
| 45 |
> Boot0001* Gentoo Linux |
| 46 |
> Boot0007* UEFI OS |
| 47 |
> Boot0008* Hard Drive |
| 48 |
> Boot0011* CD/DVD Drive |
| 49 |
|
| 50 |
This is happening if the EFI firmware for some reason has re-scanned the |
| 51 |
attached block devices to find bootable UEFI images. I've seen something as |
| 52 |
simple as rebooting with, then without a bootable USB drive causing this. |
| 53 |
Since the images boot order is editable, in your case via bootctl, then it |
| 54 |
should be a fixable problem. |
Archives