On Sunday, 10 July 2022 15:19:08 BST Peter Humphrey wrote: > Hello list, > > One of my machines uses bootctl to offer a choice of kernel to boot (I don't > use anything else from systemd); it has these files in > /boot/loader/entries: > > 08-gentoo-5.15.32-r1-rescue.conf > 09-gentoo-5.15.32-r1-rescue.nonet.conf > 30-gentoo-5.18.10.conf > 32-gentoo-5.18.10.nox.conf > 34-gentoo-5.18.10.nonet.conf > 40-gentoo-5.15.41.conf > 42-gentoo-5.15.41.nox.conf > 44-gentoo-5.15.41.nonet.conf > > Until a few days ago, the system offered the kernels cited in those .conf > files - in the same order as I've listed them. Also of course in ascending > numerical order. Both as expected. > > Now, though, they're offered in precisely the opposite order (with the two > other usual options below them as before: Windows and Enter UEFI setup). > > What might have caused this reversal? > > $ cat /boot/loader/entries/30*f > title Gentoo 5.18.10 > version 5.18.10-gentoo > linux vmlinuz-5.18.10-gentoo > initrd intel-uc.img > options root=/dev/nvme0n1p5 net.ifnames=0 raid=noautodetect pcie_aspm=off > > $ cat /boot/loader/loader.conf > timeout 5 > default 30-gentoo-5.18.10 > > $ ls /boot/vmlinuz-5.18.10-gentoo > /boot/vmlinuz-5.18.10-gentoo > > $ efibootmgr > BootCurrent: 0001 > Timeout: 1 seconds > BootOrder: 0001,0007,0011,0008,0000 > Boot0000* Windows Boot Manager > Boot0001* Gentoo Linux > Boot0007* UEFI OS > Boot0008* Hard Drive > Boot0011* CD/DVD Drive
This is happening if the EFI firmware for some reason has re-scanned the attached block devices to find bootable UEFI images. I've seen something as simple as rebooting with, then without a bootable USB drive causing this. Since the images boot order is editable, in your case via bootctl, then it should be a fixable problem.
signature.asc
Description: This is a digitally signed message part.
