Hi Fritz, On Thu, 16 Mar 2023, 15:35:11 +0100, Fritz Hudnut wrote:
[...] It may turn out to be "the solution" . . . but these days if I can just "move it around" to another OS that somehow seems easier . . . at the moment. I can face into the fact that "pilot error" is involved, but previously that error did not take up such huge swathes of time to . . . compensate. Seems like something has changed on the software side that has increased the magnitude of the "bonkerism" in regards to os-prober.
I might suggest/propose a different way to avoid running os-prober at all. As all UEFI Bios'es offer the way to boot a specific OS by selecting it from the list of OSes installed in the "EFI System" partition, it is probably as easy as choosing it from the Grub list generated by os-prober. Using Linux it's even possible to define the OS to be booted next, just for one go, leaving the "standard/default" OS as is: : Get the list of installed OSes: efibootmgr : Choose the next one: efibootmgr -n openSUSE-Tumbleweed The "standard/default" OS can be defined by moving its number to be front of the "BootOrder:" list: : Move Boot0002 to the front: efibootmgr -o 2,... # Replace ... with your actual values If you can live with this, you just need to add GRUB_DISABLE_OS_PROBER="true" to /etc/default/grub and re-generate your /boot/grub2/grub.cfg: grub2-mkconfig -o /boot/grub2/grub.cfg You might need to do similar stuff on all your other Linux installations. HTH, cheers. l8er manfred