On Sat, 12 Jun 2021 11:47:16 +0000 "Andrew M.A. Cater" <amaca...@einval.com> wrote:
> On Sat, Jun 12, 2021 at 07:09:29AM -0400, songbird wrote: > > Joe wrote: > > ... > > > It doesn't help that the BIOS is broken, that it does not honour > > > the EFI DefaultBoot, and always rewrites entry 0000 if I change > > > it. Fortunately, it does honour NextBoot, or I'd never be able to > > > get it booted into buster. But it worked with stretch. I could > > > try installing stretch again and take a disc image, but it's a > > > fair bit of work when I have no guarantee that whatever is > > > missing will get replaced, and I do have a workaround which > > > works. > > > > after grub has updates i have to run a script which > > resets the boot order in uefi. > > > > > > # > > # efibootmgr > > > > BootCurrent: 0001 > > Timeout: 1 seconds > > BootOrder: 0001,0000,0006,0007,0005 > > > > > > # efibootmgr -o 0,1,5,6,7 > > BootCurrent: 0001 > > Timeout: 1 seconds > > BootOrder: 0000,0001,0005,0006,0007 > > > > > > songbird > > > > These sound like either: broken versions of UEFI / broken > installations or, exceptionally, a broken manufacturer somewhere. Yes, no question about that. Failing to honour DefaultBoot is definitely a no-no, along with the rewriting of the boot order. The thing is, the stretch installer took a Win10 installation and an empty second drive, and made a fully-working dual boot system with grub in charge. Stretch knows something about EFI booting that buster doesn't. > > It may be worth revisiting installations when Bulleseye comes out to > get something that works and is supportable for the next few years. > Yes. But at the moment, I need to use suspend rather than shutdown, and I only just about trust stable to do suspend properly. Even stable occasionally freaks out and goes dead, and I have to do the four second power button thing. It would be bearable if there was a trivial way to get Win10 to set NextBoot, but that involves booting it into Safe Mode and some Registry editing, which is more trouble than using a rescue USB and efibootmgr in chroot. I suppose I could try running efibootmgr under Win10, but I've never had any luck doing really low-level system stuff under emulation. -- Joe
