On Thu, 16 May 2019 12:12:52 +0200 "Carlos E. R." <robin.listas@gmx.es> wrote:
On 16/05/2019 11.38, Stephen Berman wrote: [...]
I have this output, so I changed GRUB_DISTRIBUTOR to 'ostw', went to the YaST bootloader module, changed the bootloader from GRUB2 to GRUB2 for EFI, but on saving got an error that no EFI partition was found. So I added /boot/efi to TW's fstab, went back to the bootloader module, and this time saved without error. However, doing that rewrote /etc/default/grub and unset GRUB_DISTRIBUTOR again. Nevertheless, /boot/grub2/grub.cfg showed both TW and Leap (in that order). Then I rebooted into Leap, where GRUB_DISTRIBUTOR was still set to 'osleap', ran the bootloader module, changed GRUB2 to GRUB2 for EFI, saved, and again this unset GRUB_DISTRIBUTOR, but again, on rebooting, both Leap and TW were listed (now in that order).
Maybe the setting was deleted because you changed to grub2 for efi and that is considered a major change, but perhaps it is a bug. I would try to set distributor again, and this time in yast only change the "timeout in seconds", which is a known trick to force yast to write again its files.
Ah, that worked! linux-pjgr:~ # efibootmgr -v BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0001,0000 Boot0000* opensuse HD(1,GPT,b925e952-4899-46a4-b68a-40d92b7b9d34,0x800,0x100000)/File(\EFI\OPENSUSE\GRUBX64.EFI) Boot0001* ostw HD(1,GPT,b925e952-4899-46a4-b68a-40d92b7b9d34,0x800,0x100000)/File(\EFI\ostw\grubx64.efi) steve@linux-pjgr:~> tree /boot/efi/ /boot/efi/ `-- EFI |-- opensuse | `-- grubx64.efi `-- ostw `-- grubx64.efi 3 directories, 2 files
On Wed, 15 May 2019 18:36:58 -0400 Felix Miata <mrmazda@earthlink.net> wrote:
Carlos E. R. composed on 2019-05-15 21:56 (UTC+0200):
The same EFI partition can be mounted in as many operating systems you install. It should have different directories inside for each.
It /should/, but don't count on it, unless you are exercising oversight of GRUB_DISTRIBUTOR= on each (making each unique).
As described above, this didn't work for me, and no separate directories were created (where should they be, under /boot/efi ?); did I do something wrong? Do the directories need to be created manually?
No, yast creates them: [...] Legolas:~ # tree --si -D /boot/efi/EFI/opensuse* /boot/efi/EFI/opensuse ├── [1.2M Aug 4 2018] MokManager.efi ├── [ 58 Aug 4 2018] boot.csv ├── [ 155 Aug 4 2018] grub.cfg ├── [1.1M Aug 4 2018] grub.efi ├── [124k Aug 4 2018] grubx64.efi └── [1.2M Aug 4 2018] shim.efi /boot/efi/EFI/opensuse_aux ├── [1.2M Aug 4 2018] MokManager.efi ├── [ 66 Aug 4 2018] boot.csv ├── [ 155 Aug 4 2018] grub.cfg ├── [1.1M Aug 4 2018] grub.efi ├── [124k Aug 4 2018] grubx64.efi └── [1.2M Aug 4 2018] shim.efi /boot/efi/EFI/opensuse_main ├── [1.2M May 9 14:12] MokManager.efi ├── [ 68 May 9 14:12] boot.csv ├── [ 155 May 9 14:12] grub.cfg ├── [1.1M May 9 14:12] grub.efi ├── [124k May 9 14:12] grubx64.efi └── [1.2M May 9 14:12] shim.efi
0 directories, 18 files Legolas:~ #
How did grub.cfg and the other files get there? I only have grubx64.efi and grub.cfg is in /boot/grub2 as before. After rebooting Leap, setting GRUB_DISTRIBUTOR="osleap" again and changing the timeout in the bootloader module, I now have this: steve@linux-tuxedo:~> tree /boot/efi/ /boot/efi/ `-- EFI |-- opensuse | `-- grubx64.efi |-- osleap | `-- grubx64.efi `-- ostw `-- grubx64.efi 4 directories, 3 files linux-tuxedo:~ # efibootmgr -v BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0002,0001,0000 Boot0000* opensuse HD(1,GPT,b925e952-4899-46a4-b68a-40d92b7b9d34,0x800,0x100000)/File(\EFI\OPENSUSE\GRUBX64.EFI) Boot0001* ostw HD(1,GPT,b925e952-4899-46a4-b68a-40d92b7b9d34,0x800,0x100000)/File(\EFI\OSTW\GRUBX64.EFI) Boot0002* osleap HD(1,GPT,b925e952-4899-46a4-b68a-40d92b7b9d34,0x800,0x100000)/File(\EFI\osleap\grubx64.efi)
The "opensuse" directory is now an orphan, doesn't belong to any OS. Ie, yast created the new directory but did not delete the old - it had no way of knowing which one was the old, anyway, distributor was not changed inside yast.
Is there any reason not to manually delete the "opensuse" directory?
Also, although "Use graphical console" is checked in the Kernel Parameters tab of the bootloader module (and GRUB_TERMINAL="gfxterm" is in /etc/default/grub in both Leap and TW), the boot screen is in textmode. Other than that, I haven't noticed any problems.
I don't know about that :-?
You mean you have a graphical boot screen with GRUB2 for EFI? I wonder why I don't... Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org