On 04-08-18 19:46, Carlos E. R. wrote:
On 2018-08-04 17:25, Felix Miata wrote:
Andrei Borzenkov composed on 2018-08-04 17:08 (UTC+0300):
IIRC the only option is to switch to terminal before final stage and manually edit file on root. No success for me with such method: https://bugzilla.opensuse.org/show_bug.cgi?id=1101756 enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation
Or you can rename existing installation in advance - this is probably easier and makes sure it won’t accidentally conflict with future installs. Such has been the only reliable method for me. On host gb250, which is my only UEFI with RAM in it ATM, and as yet has only TW, I currently have:
BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0003,000A,000B,0007,0009 Boot0001* opensusetw Boot0002* debian Boot0003* tubuntu Boot0007* Hard Drive Boot0009* CD/DVD Drive Boot000A* ubuntu Boot000B* opensuse
After kernel installations I check with efibootmgr and usually find the order shuffled and so need to move my preference (opensusetw) back to first priority, and sometimes use -B on functional duplicates (as shown above, currently needed). Also I have reconfigured /etc/grub.d/ so that custom.cfg content is the first shown regardless which is actually controlling boot. Also I disable os-prober, since custom.cfg is doing all I need done.
Maybe this helps Carlos: <https://nwrickert2.wordpress.com/2017/12/19/handling-multiple-opensuse-version-with-uefi/> Thank you everybody :-)))
This link indicates several possibilities, and there is one that I like, similar to what others told here, but more detailed:
Edit "GRUB_DISTRIBUTOR=secondinstall" (for example), then run yast boot loader module touching something minor in the config that makes it write it all again :-)
[...]
/etc/default/grub:
GRUB_DISTRIBUTOR=openSUSE_aux
I run YaST "boot loader", change the "timeout" from 8 to 9 in the bootloader options, hit "OK", and then... I get:
linux-9wbs:/boot/efi # tree /boot/efi/ /boot/efi/ ├── BOOT │ └── BOOT.SDI └── EFI ├── Boot │ └── bootx64.efi ├── Microsoft │ ├── Boot │ │ ├── BCD │ │ ├── BCD.LOG ... ├── opensuse │ ├── MokManager.efi │ ├── boot.csv │ ├── grub.cfg │ ├── grub.efi │ ├── grubx64.efi │ └── shim.efi └── opensuse_aux <========= ├── MokManager.efi ├── boot.csv ├── grub.cfg ├── grub.efi ├── grubx64.efi └── shim.efi
50 directories, 155 files linux-9wbs:/boot/efi #
A new directory created at the proper place. And the entries:
linux-9wbs:~ # efibootmgr BootCurrent: 0002 Timeout: 2 seconds BootOrder: 0004,0002,0001,2001,0003,2002,2003 Boot0000* EFI USB Device (TOSHIBA TransMemory) Boot0001* Windows Boot Manager Boot0002* opensuse-secureboot Boot0003* openSUSE Boot0004* opensuse_aux-secureboot Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network linux-9wbs:~ #
What is strange is what would be the entry in non-secure boot mode. I efibootmgr -v The secureboot is loaded by shim.efi The non secureboot by grubx64.efi think it might be #3
Well, for the restored from backup system I have to do the same after chrooting to its root partition mounted from the "aux" system.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org