There is no way to get UEFI 2.0 on that board. I know it did support RHEL 5.1 64-bit and SuSE 10 64-bit, so I'm thinking there has to be some way to boot a 64-bit OS off the old EFI 1.1.
There is, I'm currently running Arch Linux x64 on it, but without access to EFI runtime services, and via a detour (EFI Shell). Booting via legacy BIOS seems impossible, which I find rather weird.
I'm trying to do the exact same thing (same machine and distro). I only got the machine yesterday, so I haven't had much time to work with it, but if I find a good solution, I'll post here. Meanwhile, I'm all ears if anyone else has a good solution; I'm not at all used to EFI (I very much preferred Open Firmware and don't understand why we're subjected to this EFI crap when there was a perfectly good solution already present).
I managed to get it to boot as a normal BIOS GRUB install (on an MBR partition, not a GUID partition). Some caveats:
- I am using the SAS active hotswap backplane (ASR1500SASBP), not the passive backplane. Since that means I'm booting using an option ROM, that may affect how willing the machine is to boot off it; however, since the board claims to be able to run DOS 6.22, I'm willing to bet that you'd be able to run from the built-in SATA controllers using either the fixed drive option or the passive backplane. If you're looking to get a nice upgrade, the active backplane is available cheaply on eBay; I got it and the AXXSASIOMOD (the 4x external SAS I/O module that fits the header underneath the PCIe riser) from the same seller (kalleyomalley) for $25 each and combined shipping. They both install quite easily and quickly.
- The older firmware on the SAS controllers (both the backplane and the I/O module) was quite buggy and was interfering with the boot process. Fortunately, for all of EFI's faults, it makes it quite easy to do things like firmware upgrades from a USB stick with no OS. I downloaded this package, unzipped it and stuck it on a USB flash drive and ran the appropriate scripts from the EFI shell. Note the instruction that says you need to disable the SAS backplane when updating the I/O module and vice versa.
Once everything was set, I was able to set the appropriate drive on the backplane as the primary boot device. GRUB (installed as the regular GRUB version, not the EFI version) runs fine at boot now, though it seems some of the UUIDs for the drives changed (I'm not sure why, since I don't know where the UUIDs are stored or from what they're calculated).
Feel free to post back if none of this helps; I may be forgetting something else I did.
Well, I now realize I haven't tried installing or booting an OS using an MBR-partitioned hard drive (slaps himself in the face). My personal default is always GPT. I'm using the active backplane too, but thanks for the suggestion. I'm actually looking for the Intel RMM module, but I assume I'll get it from eBay some time in the future.
Thanks for your feedback.
Also, it occurs to me that there may be a way to do it with a GPT disk, since there are MBR compatibility modes which allow for sector 0 to be used as a boot block. I didn't play much with it, though, since it seems the compatibility with 32-bit EFI 1.1 doesn't give me much benefit, and my boot drive is only 80GB (the data drives can have whatever partition table format I want, obviously).