Hi,
As Alexander pointed out, you don't miss anything. Let me elaborate a bit.
The Slint installer runs grub-install which among other things writes
an EFI OS
loader grubx64.efi in an EFI System Partition, that you can see from
Slint as
boot/efi/EFI/slint/grubx64.efi and a boot entry in the firmware menu,
which is
actually a link to grubx64.efi.
grubx64.efi looks for the grub configuration file grub.cfg in the /boot/grub
directory of the system from which grub-install ran (or or from the
directory
argument of the --boot-directory option of the grub-install command).
So if you really want a boot entry for Arch in the firmware's boot menu
you will
need to write an EFI OS loader able to boot Arch in ten EFI system
partition, to
which this boot entry would link to. This can be done several ways, but...
Why would you need that, as long as the GRUB menu built from Slint allows to
boot Arch?
As an aside, in Slint you can run grub-emu to display the grub menu that
will be
displayed at next boot and check the boot entries it includes.
This comes handy for blind users as the menu displayed by grub-emu is
accessible
to the blind, but not the menu displayed when booting.
Also I am guilty of something called EFI3M
https://github.com/DidierSpaier/EFI3M
Cheers,
Didier
On 26/05/2021 03:47, Linux for blind general discussion wrote:
I have 3 operating systems on the same disk. Windows, slint and, as of this morning, arch. Installed in just that order. The bios type is UEFI.
Slint runs grub, so I did not install it in arch.
After completing the arch install, I got back into slint and ran
update-grub
It found arch on /dev/sda7
When I ran
efibootmgr
Arch was not listed there, however.
What step did I miss?
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list