You are not logged in.
Pages: 1
For a bit of context I’m doing this on a Laptop and got to the Grub installation stage however when performing the following:
grub-install —target=x86_64-efi —bootloader-id=grub_uefi —recheck
It prints an error which reads the following:
Could not prepare Boot variable: No space left on device. Grub-install: error: efibootmgr failed to register the boot entry: I/O error.
I tried using the efibootmgr command which gave me the following boot order
BootOrder: 0001, 0002, 0000
Boot0000* Windows Boot Manager
Boot0001* UEFI DISK 3.0
Boot0002* UEFI DISK 3.0 PMAP, Partition 2
I’m not sure if the Windows Boot Manager is somehow messing the GRUB installation or if it’s user error on my part, I looked up info on it but all I came up on were on how to erase Grub and install Windows Boot Manager to restore or otherwise Dual-Boot Windows which I’m not trying to do
Last edited by Svoxala (2020-05-25 09:23:14)
Offline
Not unlikely to be buggy firmware, you could try using --removable and setting your firmware to boot the default payload instead.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
If your firmware won't load the fallback location then redirect the Windows NVRAM entry to Arch's GRUB by running this command from an Administrator prompt in Windows:
bcdedit /set "{bootmgr}" path "\EFI\grub_uefi\grubx64.efi"Jin, Jîyan, Azadî
Offline
Pages: 1