On Monday, 19 October 2020 13:08:35 BST Peter Humphrey wrote: > On Sunday, 11 October 2020 23:21:49 -00 pe...@prh.myzen.co.uk wrote: > > Can anyone please tell me precisely where 'efibootmgr -c ...' writes a > > boot > > record, or whatever it's called? My machine seems unable to store what I > > give it, and I suspect that the BIOS ROM has failed. Big expense if so. > > I have a bootable system again. > > In one line: I need Windows as part of my system maintenance. > > Yes, I did mean to write that. Let me explain. > > Every attempt of mine to write bootable images failed. I still don't know > why, but while I was trying everything I could think of, I ran Windows (on > /dev/ sdb) to restore a system image (from /dev/sda; /root is on > /dev/nvme0n1). On rebooting, lo! and behold! there was a boot menu! It was > an old one, dating from when I created the system image in Windows, but > after booting from USB and adding the right kernels and /boot/loader/ > structure, and running 'bootclt update', a reboot showed me the proper boot > menu. > > A kernel upgrade arrived today, so after installing it and updating the > /boot/ loader config, I ran Windows again to create a new system image. > > So on my machine, efibootmgr is no use. I have to use bootctl from > systemd-boot to manage my bootable images. And Windows to preserve them. > > I've attached a shot of the boot menu I've been referring to in this thread. > It's not pretty, but there's only so much I can do with a curved screen and > a hand-held phone.
I am confused ... Are you saying calling 'efibootmgr -v' lists a different UEFI boot menu? o_O
signature.asc
Description: This is a digitally signed message part.
