Pat
I submit to your more advanced Knowledge, HOWEVER
When I built my new system
AsRock Z77 Extreme4 MB
Kingston 120GB SSD
2 TB HD
32 GB ram
used DVD Player

I plugged the system in and after a few seconds a slackware 13.37 dvd started to boot. Here the used dvd I installed had a disk it. I quickly swapped the disk for 64-14.0 and went through a normal install including lilo. Prior to setup using gdisk I made sda1 an efi partition mounted at /boot/efi, sda2 mounted at /, sda3 mounted at /home, sda4 swap. Then did a standard full install accepting all defaults including installing lilo.
System booted from lilo fine.
To get UEFI working I first had to format /boot/efi as fat32 then find and install the (Intel I Believe) Shellx64.efi onto my /boot/efi partition. I also found and installed Dell's efibootmgr. You need not even install this just copy it to your /boot/efi partition it is completely self contained so is elilo.efi. Also copy vmlinuz-huge-3.2.29 to /boot/efi/bzImage.efi
Now the good part took a while to figure out
Boot the system press [DELETE] or whatever gets you into the UEFI manager screen
On mine I had to go to the BOOT page on the manager screen and select boot the Shellx64.efi remember we just put this in our /boot/efi partition. Whole bunch of shit flys by and finally you will get a prompt
at the prompt type
fs0:> bzImage.efi root = /dev/sda2 ro ( it could also be fs1 or even fs2)
this will boot your kernel in UEFI mode
once in efi mode I followed the slackdocs instructions on installing elilo.efi and elilo.conf
Then type /boot/efi/efibootmgr -c
this will create an UEFI boot point called Linux at /dev/sda1 which will launch elilo.efi
On next boot hit [DELETE] go to boot menu and select "Linux" as the default boot image.
And Bob's your uncle. Every reboot after this will be Slackware
Sorry no help for you Windows guys.

Installing UEFI was the most fun I've had since my original Slackware install and on top of that I get to help you. GREAT DAY
John

EDIT: the initial bzImage.efi copied to /boot/efi was the huge kernel. After installing elilo.efi you can boot anything you put in elilo.conf.
Sorry my notes are not very good

2 members found this post helpful.

Ah, that explains it. I was talking about booting a disc while in UEFI mode. UEFI in legacy boot mode (which yours was or LILO wouldn't have worked) should be able to boot our ISOs fine.

I can say it does. I just got an new MoBO (to me) the other day, an ASUS M5A97LE R2.0. It has that UEFI bios. My Slackware 14 booted on it in the legacy mode (I had other troubles but *NONE* were to do with the UEFI) just fine.

Just out of curiosity, does it really matter to the user whether you use UEFI or legacy mode to boot the system?

I'm not trying to start a flame war or anything. Nor am I suggesting that development stop on a permanent working solution as I'm sure at some point manufacturers will stop putting legacy mode in. Just wondering if you lose some functionality by installing and using legacy mode.

Dan

1 members found this post helpful.

You could have a look to the links I posted here.

Sometimes I am not very good at communications so here is a working example
My efi partition is /dev/sda1 formatted "mkdosfs -F 32" and mounted at /boot/efi
note bzImage is the huge kernel from the 14.0 dvd
with lilo installed in the gpt "protected mbr" and an error in the above the UEFI firmware will default to a mbr boot. This way you have a working os to fix your problem. Without lilo installed in the protective mbr you get a blank screen to work from.
Which would you rather have?
Pretty interesting that the kernel can be loaded and run from sda while sdb has the root OS as in my rescue and build installs.
This is posted in the hope it will help someone. This UEFI stuff is not really complicated even thought most of the literature seems to make it appear that way. IMHO elilo is simpler than lilo.
thanks
john

1 members found this post helpful.

It only matters if you got Windows 8 preinstalled, have no media to reinstall it in legacy mode, and would like to keep it to dual boot. Otherwise, if the machine supports legacy mode, that's probably the better way to go at this point. I've heard that some video drivers rely on BIOS calls to set things up and are not accelerated when the OS is booted under UEFI, and there are likely to still be other bugs lurking.

3 members found this post helpful.

How does one test their video card/driver? On my other (older, non-UEFI) MoBo, with my nvidia gt-520 and the nvidia driver from nvidia, with 'gears' I would get 6000 fps.

I just did 'gears' on this new mobo (UEFI), the same card and driver and only get 59 fps.

I can at least tell you that "gears" has not been a good benchmark for quite some time (if it ever was). What it returns is usually the same as the vertical refresh rate.

I was thinking this very same thing this morning. It is less risky [since it doesn't need to be installed to the MBR] and is certainly easier to tinker with.

What ruins it for me is this 'secure boot' thing. I'm not sure that we should be supporting it, given the amount of power it hands certain vendors. I'd rather disable it. I want to be in control of my hardware.

The question I have is: How did we let it get to this point?

Thanks for the answers. They were all informative. I should have pointed out that I don't dual boot any of my computers. My PC and laptop run Slackware only, my wife's laptop runs XP. If I find I absolutely have to do something in Windows I borrow the wife's.

Any plans on adding something automated to the installer?

Yes. This is just information for the people who want to brick their Samsung laptops now.

2 members found this post helpful.

http://blog.hansenpartnership.com/linux-foundation-secure-boot-system-released

small video demo: http://youtu.be/1fNhQYRIjD8

So what it is is actually the Microsoft Secure Boot System provided by MS to the LF. It may work but it's still unacceptable IMO.