You are not logged in.
Pages: 1
Hi,
I got a very strange problem which I really can't resolve.
I decided for my config to use EFI with GPT partitionning.
I then installed grub2 correctly for this configuration using the wiki.
Here are the commands I used (I may miss some, because it was 2 weeks ago, and I continuesly tried to fix this since).
$ sudo modprobe dm_mod
$ sudo modprobe efivars
$ sudo grub-install --directory=/usr/lib/grub/x86_64-efi --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --boot-directory=/boot --recheck --debug
$ sudo cp /boot/efi/efi/arch_grub/grubx64.efi /boot/efi/shellx64.efi
$ sudo cp /boot/efi/efi/arch_grub/grubx64.efi /boot/efi/efi/shellx64.efi
$ sudo cp /boot/efi/efi/arch_grub/grubx64.efi /boot/efi/efi/shell/shellx64.efi
$ sudo grub-mkconfig -o /boot/grub/grub.cfg
But it seems that my the boot entry created can't boot.
Here is my boot entry, according to efibootmgr (and what appears in my bios as well)
$ sudo efibootmgr
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* arch_grub
Boot0001* Hard Drive
At each boot, I got an error message saying there is nothing to boot on my hard drive (which is normal).
But this message appears because the previous boot section isn't working properly.
And I have to go into the bios, launch the efi shell I previously set which redirect me to grub2.
-----
Edit: I got a workaround : I added a boot entry which point to the Shell.
So now, the boot seems fine, except it's not.
It should use the grub efi, and not the shell efi.
Also, at the very beginning, I remember having trouble with the --root-directory option which became --efi-directory :
Note: In GRUB2 2.00~beta4, the grub-install option --efi-directory replaces --root-directory and the latter is deprecated.
And then I updated grub to get the beta 4.
So my efi shell are grubx64.efi from beta 3 (they work).
And the grubx64.efi files from beta 4 don't seem to work.
------
Edit:
I might have done something wrong when creating the EFI partition, but it seems that any efi entry which refer to a file inside the EFI folder won't boot.
So, instead of EFI/arch_grub/grubx64.efi, I created a custom efi boot entry, and copyed a file in arch_grub/grubx64.efi
Last edited by gravitezero (2012-05-04 17:06:23)
Offline
Have you tried passing verbose to efibootmgr to see what it thinks is going on?
Have you reinstalled after updating grub?
Last edited by cfr (2012-05-06 03:47:02)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Pages: 1