Richard Owlett composed on 2025-12-28 10:23 (UTC-0600):
> As root I get
>> root@debian12:/home/richard# efibootmgr
>> bash: efibootmgr: command not found
> Thankfully all signs point to BIOS.
Don't rush to thankfulness. UEFI is more robust. A standard Trixie installation
on
MBR will usurp boot control from Bookworm without enabling it in its own boot
menu. From a default installation you'd have to edit Trixie's /etc/default/grub
file to include
GRUB_DISABLE_OS_PROBER="false"
and regenerate /boot/grub/grub.cfg before Bookworm would again be bootable. Then
on next Bookworm update that includes a Grub update, it would usurp boot control
back from Trixie, unless you'd disabled Bookworm's Grub from rewriting boot
code,
or uninstalled its Grub. It's been a very long time since this issue has
presented
here. All my PCs are multiboot. I block installation of, remove, or otherwise
disable Grub from all but the one installation I wish to retain boot control.
So,
I'm not sure whether a simple new kernel installation will also trigger
usurpation
at the same time grub.cfg is regenerated for the new kernel.
In some configurations (fewer than 5 partitions on a disk), an MBR partitioned
disk may be convertible to GPT, in which case MBR booting could be converted to
UEFI booting without existing installation destruction. But you need to know
whether that Latitude supports UEFI before contemplating using UEFI. A 2010
Core-iX processor on a Latitude E6410 would suggest UEFI support could be
present.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
