I am now walking through the install step by step. Initially, it is suggested (in the Beginner's Guide) to test whether efivars is mounted. I ran mount -t efivarfs efivarfs /sys/firmware/efi/efivars And got this message: mount: mount point /sys.....efivars does not exist. I don't knolw whether this is good or bad news. I tested for UEFI in Windows. The result was positive. This is kind of what I mean, that there are so many shades and variations. On Thu, May 1, 2014 at 3:45 PM, Alan E. Davis <lngndvs@gmail.com> wrote:
What is the "EFISTUB bug"?
Alan
On Thu, May 1, 2014 at 3:42 PM, Alan E. Davis <lngndvs@gmail.com> wrote:
I'm staying tuned.
Alan
On Thu, May 1, 2014 at 3:41 PM, Delcypher <delcypher@gmail.com> wrote:
On 1 May 2014 23:35, Daniel Micay <danielmicay@gmail.com> wrote:
On 01/05/14 06:28 PM, Alan E. Davis wrote:
After already chrooting, during the Arch installation process, I saw some information that suggested to use a command, as follows:
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
You don't need to do this, so I'm not sure where you're getting this information. Adding an EFI entry is optional since it already installs itself as the fallback loader too. You can install an EFI loader without being booted via EFI.
It's at https://wiki.archlinux.org/index.php/UEFI#Mount_efivarfs
It's certainly a lot simpler than using grub... you don't seem to want it to work so obviously it's not going to work, since you're going out of your way to ignore the instructions.
It is unless you're one of the people effected by the EFISTUB bug like myself. So I'm currently using GRUB2.