[arch-general] UEFI madness

Mike Cloaked mike.cloaked at gmail.com
Sat Mar 2 13:29:27 EST 2013

On Sat, Mar 2, 2013 at 9:26 AM, David Benfell <benfell at parts-unknown.org>wrote:

> On 03/02/2013 10:32 AM, Mike Cloaked wrote:
> >
> > which works really beautifully and needs no manual intervention when new
> > kernels arrive.  However it did take me some time with a lot of help from
> > Rod Smith to get it all set up correctly.
> >
> > Basic steps were:
> > 1) Format disks with GPT instead of MSDOS
> > 2) Make sure that there is a /boot/efi/EFI ESP which is formatted FAT32
> > 3) Since I also wanted /boot to contain initial ramdisk and kernel I had
> > /boot as a directory in my root (/) partition which is ext4.
> > 4) In order to get it to work I made sure that the rEFInd config files
> were
> > set up in the ESP as well as the required files in /boot (and including
> the
> > ext4 rEFInd driver files in the ESP so that rEFInd can read the initrd
> and
> > kernel files unde ext4 in /boot (and include the rEFInd driver files in
> > those directories also.
> > 5) In my system I found that the standard method to write the nvram
> entries
> > failed to work - so I had to boot to the efi shell from the arch install
> > iso on usbkey and write the nvram entries from the shell.
> >
> > If you want more details I can post more tomorrow.
> >
> > I hope this helps.
> >
> Of these, step 4 seems to me to be undocumented. And I'm assuming I
> don't need to worry about step 5 unless it bites me? How will I know?
> Thanks!

The thread on the forum where I got the information that led me to my
working system is at:


This may help - you will see in that thread what led to me needing to use
the efi shell.

I hope this helps.

mike c

More information about the arch-general mailing list