I’m still in the process of getting familiar with setting things up under UEFI instead of CMS. I have a Lenovo T420 which has Windows 10, MX 19.1, and EOS. While testing the new ISO, I installed a second copy of EOS, using the online installer. Used Plasma instead of my normal Xfce. Didn’t like Plasma much, and since I wanted to do a normal Arch install using UEFI boot, I decided to wipe the EOS Plasma install and put a pure Arch install in its place.
Basic install went fine, installed Grub and rebooted. Which is where the strangeness starts…
When the machine rebooted, I got boot options for Win10, and EndevourOS. Nothing for MX or for the new Arch install. When I selected EOS, I ended up in the new Arch install, just to really confuse me. Attempting to rerun grub-mkconfig did nothing except lose me the Windows 10 option.
When I looked at the firmware boot option, I could see entries for Win, Arch, EOS and MX. Both the Arch and EOS entry boot the new Arch install. Booting MX gets me the MX grub, which gives me a working entry for EOS. So I have no idea what is going on…
As a temporary step, I installed reFind, which gives me Win, EOS, MX and a Grub entry. EOS starts the pure Arch install, as does the Grub entry. MX gives me the normal MX grub selections, which does allow me to boot to EOS. So I’m not at all sure that I know what is going on.
I’m just wondering if it is the way I installed grub to the new Arch install that is causing the problem. This is the command I used (pretty well straight from the Arch Wiki):
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
I’m wondering if the confusion has been caused by my using “GRUB” as the bootloader-id rather than something like “Arch”, though I’m far from sure that could do it. Since the second EOS install seems to have used the existing /boot/efi/EFI/EndevourOS directory, which would have pointed to the partition on which I’ve now installed Arch, could that cause this sort of problem?
As another question, is there a safe way to delete the copy of Grub that I installed for Arch (so I can reinstall it using Arch as the bootloader-id? In the past I’ve had some problems removing boot entries from NVRAM after making changes to Grub installations in a UEFI environment.
I guess its one way of learning, but it is taking a bit more time than I’d hoped…