My UEFI mother board is set to only and it boots the VL64 ISO.My apple computers don't have a bios, only EFI, and they boot it as well.maybe my systems have some kind of backwards compatibility built in?

VL64-7.0.1-STD-FINAL.iso with an md5 checksum of a83ee1b1dae6ebbf6c1afa0aebcf3e7b.

When I examine the contents of the iso, I do not see the files I normally expect to find on a true UEFI-bootable disk. These would typically be one or more files with an .efi suffix, generally found in a directory named "EFI" or the like. The VL64 iso that I extracted contained no files of this nature that i could find.

I'm booting UEFI only (my MB offers Legacy BIOS, UEFI, or Both). This option has worked for numerous UEFI-capable boot disks that I've made from Linux installation ISOs.

Am I using the wrong file or something? I have a 64-bit machine. The machine, by the way, is a Thinkpad 420.

My motherboard will permit booting via BIOS (which it calls "Legacy") as well as EFI, but booting Legacy defeats the purpose, since my experience has been that an EFI installation requires booting the install disk or USB stick via EFI.

I'm encouraged that some of you have managed to boot VL's install disks using EFI; I'm wondering if I'm using a different iso or something. Please advise. Thanks.

As with most tech topics, UEFI is having its share of controversy (do a search on "UEFI secure boot"; also, the Pope -- I mean Linus -- apparently doesn't like it ). For my money, I like it because it boots faster. Also, a standard BIOS can't boot a hard drive of capacity greater than 2.1Tb (my little Thinkpad isn't there yet, but maybe some day ...).

I made the switch when I got an SSD. SSDs benefit from GPT formatting (superior partition alignment). I read that GPT is part of the UEFI specification (see Rod's Book link below), so I decided to convert to UEFI and GPT at the same time.

One reason UEFI Linux machines can boot faster is that, since kernel 3.3, an EFI boot stub has been built into the kernel itself. In other words, you don't even need a boot loader. The EFI firmware in your machine will boot the Linux kernel directly, if you want it to.

To facilitate sending kernel options to the kernel, though, a lot of people use a simple boot manager like rEFInd or gummiboot. You can use grub2, but, as somebody who mainly just needs to boot a kernel, perhaps with a simple kernel option or two, I find grub2 unnecessarily complex. I've gone with rEFInd, which works very well.

I've learned a great deal from reading the "Rod's Books" pages on UEFI, GPT, etc. Here's one example:

While I've spent a good bit of time fiddling with UEFI and GPT matters and trying to get various distros to install via UEFI, I'm really out of my depth to try to discuss the finer technical points. Still, I hope this helps a bit.

It has to be said that if you buy a new computer that comes preinstalled with Windows 8 Retail it Will Be using UEFI. This is a requirement of Microsoft or else the OEM's are not allowed to build the machine with Windows 8.

I searched for UEFI issues because I wanted to install Vector on my new computer to dual boot with Windows 8. That's not gonna happen anytime likely because I already have a ton of stuff on this machine i would have problems moving. Otherwise, my solution would be to wipe the drive, disable Secure Boot in bios ( this rather than the UEFI itself is the cause of all the trouble i understand) , switch to legacy Bios mode and reinstall Windows 8 under that. This is a pain in da butt i wish i had known about before i bought this PC.. and do warn all your friends of this also.