http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 http://bugzilla.opensuse.org/show_bug.cgi?id=1101756#c1 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com --- Comment #1 from Neil Rickert --- I'll just add some history of this, to the best of my recollection. This is based on my experience. With openSUSE 12.3, the distributor could be set in Yast bootloader. But it did not work in an installation. The installer only used "opensuse". I could use Yast bootloader on the installed system to change the distributor, and that worked. I think the "/etc/default/grub" that is saved during install did not use what was set for distributor during install. In 13.1, I think it worked for install. But I'm not completely sure of that. And it might have been 13.2. Some time later, probably during the 13.2 cycle, the distributor field was removed from Yast bootloader. There's probably an earlier bug report where I complained about that. You had to directly edit "/etc/default/grub" to change it. Using "distributor" would probably not work with Ubuntu. Although I have not tested it, I am under the impression that the Ubuntu "shim" is hard coded to use the directory "\EFI\ubuntu" in the EFI partition. Hmm, I actually have tested it. I currently have "deepin" installed for testing. It used the Ubuntu shim (in "\EFI\deepin"). But that Ubuntu shim depends on the files "grubx64.efi" and "grub.cfg" that are in "\EFI\ubuntu". For myself, I am now doing things in a way that does not depend on using distributor. However, I'm expecting your bug report to not get much traction. You should be able to create the "opensuse150" entry that you want by manually editing "/etc/default/grub" and setting GRUB_DISTRIBUTOR . And then make some small change in Yast bootloader (maybe a timeout change), and it should reinstall as you want. But I think the last that I tested this was when running Leap 42.1. For completeness, here's some output: # efibootmgr BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0002,0005,0008,000B,0001,0003,000F,000E,000A,0006,0007,0009 Boot0000* opensuse-secureboot Boot0001* ubuntu Boot0002* betasuse-secureboot Boot0003* deepin Boot0005* UEFI OS Boot0006* Generic Usb Device Boot0007* CD/DVD Device Boot0008* mageia Boot0009* Generic Usb Device Boot000A* CD/DVD Device Boot000B* systemd-boot Boot000E* UEFI OS Boot000F* ubuntu Both of those "ubuntu" entries boot to "deepin", because the "deepin" install put some of its boot files in the "ubuntu" directory. If I restore the original ubuntu boot files, then booting to the "deepin" entry will boot ubuntu. The "betasuse-secureboot" entry was created with manual editing of "/etc/default/grub" and then using Yast bootloader. It currently boots to 42.3, but with a menu that allows me to boot other systems. It's my backup in case the main boot entry fails. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 http://bugzilla.opensuse.org/show_bug.cgi?id=1101756#c3 --- Comment #3 from Neil Rickert ---

This bug is about not needing to do so ...

Yes. But that's hopeless. Too much depends on the firmware. On the box that I referred to above, the firmware changes the boot order unless I go into firmware settings and set the order there. And if I delete a UEFI boot entry, the firmware puts it back unless I also delete the associated ".efi" files. What I do is use "/etc/grub.d/40_custom" to make sure that every system can boot every other system. I usually do this via a grub "configfile" command, so it just uses the native grub configuration for that other system.

Choosing 2 or 5 from the BIOS UEFI menu produces only a grub> prompt.

You should be able to change what happens for 2 (the UEFI OS entry). That just boots with "\EFI\Boot\bootx64.efi". So copy to the boot files from your preferred system to "\EFI\Boot" in the EFI partition. When you install openSUSE, it will put its boot files there if it sees that no other system is using that directory. Otherwise openSUSE doesn't touch it. However, Ubuntu, deepin and Solus all ignore what is there and put there own boot files there regardless. What it amounts to, is that UEFI is a mess. There's no consistency between vendors or between operating systems. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 http://bugzilla.opensuse.org/show_bug.cgi?id=1101756#c6 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #6 from Josef Reidinger --- I worry that working with ESP partition is done a layer lower then yast2-bootloader. Yast2 just checks that there is ESP partition, but do not modify it. It only calls grub2-install and grub2-mkconfig. But I agree that this change of GRUB_DISTRIBUTOR is a bug that should be fixed. So your manual edit of default/grub should be respected. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 http://bugzilla.opensuse.org/show_bug.cgi?id=1101756#c8 --- Comment #8 from Neil Rickert --- This issue may be indirectly related to bug 1175906 and I'll add a comment to that this week (and switch it to 15.3). It is looking as if Leap 15.3 will be using the SUSE shim instead of the openSUSE shim. In my experiments, I have an EFI boot entry for "opensuse" that is used for 15.3, and an entry for "tumbleweed" that is used for Tumbleweed. This allows me to select which "shim" I am using for booting. -- You are receiving this mail because: You are on the CC list for the bug.