You are not logged in.
Pages: 1
I installed this Arch system 3 years ago, then installed Ubuntu along side it. In the process, it seems that Ubuntu's GRUB install overtook my gummiboot install as the bootloader. I have config files for both in /boot. I don't really understand how this happened or why one bootloader would take priority over another. This makes me hesitant to try to resolve the situation (I'll also be getting rid of the Ubuntu install).
So I'd like to remove Grub and back to systemd-boot without making my machine unbootable in the process.
The ubuntu fstab has sda1/boot/EFI mounting as boot (referenced by UUID, but I'll use dev/sdX designations)
The Arch fstab has sda1/boot mounting as boot.
Looking at /boot/*, it seems that I've got both Grub and Gummiboot/systemd-boot config files.
#ls - R /boot
(kernal images, etc)
./EFI:
Boot gummiboot ubuntu
./EFI/gummiboot:
gummibootx64.efi
./EFI/ubuntu:
grub.cfg grubx64.efi MokManager.efi shimx64.efi
./loader:
entries loader.conf
./loader/entries:
arch.conf arch-lts.confSo how does the BIOS/UEFI know which bootloader config file to use? (It currently uses GRUB, IIRC).
And how do I remove GRUB and just use gummiboot/systemd-boot?
Thanks
Offline
Not an Installation issue, moving to NC...
Offline
The ubuntu fstab has sda1/boot/EFI mounting as boot (referenced by UUID, but I'll use dev/sdX designations)
The Arch fstab has sda1/boot mounting as boot.
This makes no sense. Directories can't be mounted, only partitions can.
Do you mean in ubuntu you mount sda1 on /boot/EFI/ and in arch you mount sda1 as /boot/?
how do I remove GRUB and just use gummiboot/systemd-boot?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Unified_Extensible_Firmware_Interface#efibootmgr The firmware if it uses efivars will use the boot order stored in efivars to determine which method it should use.
If the firmware does not use efivars it may use hardcoded locations instead and whatever bootloader is at that location would be used.
Installing Systemd-boot#Installation should make it the default bootloader if the firmware uses efivars.
If that worked you would then need to remove all the files under /boot/EFI that systemd-boot has not just added and remove the firmware entries using efibootmgr for the old boot loaders.
Offline
Pages: 1