Installation of Slackware and GRUB 2 on GPT with UEFI BIOS

Hello all,

I'm trying to install Slackware 14.1 on a GPT hard disk in a machine with Asus UEFI BIOS. I've had several problems with different fixes that I've tried. All of the problems boil down to me not being able to reboot to slackware even from the CD boot prompt. When I format the BIOS Boot partition as ef02 (bios boot partition) in gdisk, it can't be mounted to install grub, but when formatted as ef00, the partition can be mounted and installed to, but the /boot partition has a similar problem where it cannot be mounted (I've been formatting it as 8300 (Linux file system) in gdisk. The same issue also occurs with my root partition formatted to 8300. Any advice or tutorials would be appreciated!

The SlackDocs Project seems like a great place to start. EUFI support seems pretty robust.

I tried following this http://docs.slackware.com/howtos:sla...based_hardware tutorial and always got a "wrong fs type" error when mounting the usb stick but it was formatted to EFI System. And when I mounted the same type of file system on my boot drive, it could mount fine. But when booting from that drive, it simply brings me back to the same BIOS screen.

Also, when running the grub-install on the boot drive I get this error "Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables."

formatted to EFI System

I don't think the bootstick is supposed to formatted in anything other than VFAT, is it? The point is, the kernel can't read the EFI formating, it just needs to be told to load the efi modules.

I have my system partitioned this way:

gdisk /dev/sdx to make a new GPT setup on both disks, the cgdisk to make the partitions as follows:
/dev/sda1 ef00 (EFI) 100M
/dev/sda2 8300 (boot) 100M
/dev/sda3 8e00 (lvm) rest of disk

I made notes of my setup procedure on my LQ blog, see http://www.linuxquestions.org/questi...re-14-1-35788/

Hope that helps

Why make the /boot partition separate as you already have separate /dev/sda1 (EFI) partition that could be shared with other OS's (if you need to)?

Easiest answer: because that's the way the Slackware README_CRYPT.TXT suggested. Plus, the EFI has to be partitioned fat32, and is modified by the BIOS, which expects something called EFI. However, boot can be whatever one wants. I think it's cleaner this way. If you have an encrypted filesystem you'll have to have a separate /boot, and using something called EFI will probably eventually break something.

Ah yes, with encrypted filesystem that makes sense

thanks!