You are not logged in.
Hi.
Maybe it's a dumb question, but I can't find an answer.
When I was installed the Gummiboot to finish the Arch instalation, I saw I've disabled the UEFI boot in the BIOS before to boot the Arch's CD. So, I abled this, reboot the CD and retried. But now, when I run gummiboot install, it returns:
Failed to create EFI Boot variable entry: No such file or directory
What is this, and how can I solve?
Thanks!
Last edited by Uchiha (2013-11-10 03:24:06)
Linux user #519886
Offline
Most likely, you are not booted with UEFI. To use efibootmgr (which gummiboot uses to make the firmware entry), you need to be.
Offline
Hi.
Maybe it's a dumb question, but I can't find an answer.
When I was installed the Gummiboot to finish the Arch instalation, I saw I've disabled the UEFI boot in the BIOS before to boot the Arch's CD. So, I abled this, reboot the CD and retried. But now, when I run gummiboot install, it returns:
Failed to create EFI Boot variable entry: No such file or directory
What is this, and how can I solve?
Thanks!
Offline
Most likely, you are not booted with UEFI. To use efibootmgr (which gummiboot uses to make the firmware entry), you need to be.
Gummiboot setup (/usr/bin/gummiboot) is independent of efibootmgr. It does not use efibootmgr or efivar library at all. All other boot managers except gummiboot, do not include a setup script and instead rely on efibootmgr for entry creation. Even grub-install calls efibootmgr, it does not include its own tool like gummiboot setup.
Offline
Most likely, you are not booted with UEFI. To use efibootmgr (which gummiboot uses to make the firmware entry), you need to be.
But I'm in UEFI mode. The efivars -l returns the variables list.
After chroot, the efivars -l doesn't return the list. This command neither exists. It seems the UEFI mode is disabled after chroot.
Linux user #519886
Offline
After chroot, the efivars -l doesn't return the list. This command neither exists. It seems the UEFI mode is disabled after chroot.
https://wiki.archlinux.org/index.php/Un … t_efivarfs
Last edited by the.ridikulus.rat (2013-11-09 17:56:40)
Offline
Uchiha wrote:After chroot, the efivars -l doesn't return the list. This command neither exists. It seems the UEFI mode is disabled after chroot.
I've already tried this, but it returns mount: unknow filesystem type 'efivars', into and out of chroot.
Out of chroot, modprobe efivars does not exists.
I've read this page and so many others.
Last edited by Uchiha (2013-11-09 19:02:58)
Linux user #519886
Offline
I told it was a dumb question. I was typing:
mount -t efivars efivars /sys/firmware/efi/efivars
instead of:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Sorry.
Linux user #519886
Offline
I had the same problem.. I've spent so much time looking for an answer
Offline
efivarfs will be mounted in the chroot starting with the December ISO: https://projects.archlinux.org/arch-ins … 8d174ffc44
Offline