beta992, on 24 September 2012 - 10:06 AM, said:
UEFI-booting is not working:
...
You are fast. I think you should not have any problems with UEFI boot on your mobo.
Notes:
1. If UEFI booting ML with OsxAptioFixDrv driver, you MUST add slide=0 in config.plist in boot args
<key>boot-args</key>
<string>-v slide=0</string>
2. You can use the same stick for BIOS Clover boot and UEFI boot. The Clover setup difference between BIOS and UEFI boot for me is only in drivers. BIOS Clover boot will use drivers from /EFI/Drivers64/ and UEFI Clover boot will use /EFI/Drivers64UEFI/.
3. For BIOS Clover boot you probably do not need any drivers. So /EFI/Drivers64 can be empty. You can add FSInject-64.efi in there if there is a need to block kernelcache and load with kernel+kexts.
4. For UEFI Clover boot you need in /EFI/Drivers64UEFI:
- some HFS+ driver (HFSPlus.efi or VBoxHFS.efi) - to allow Clover to read HFS+ volumes
- OsxFatBinaryDrv-64.efi - to add support for fat binary (multi-architecture binaries) .efi files (Apple's boot.efi is such file)
- OsxAptioFixDrv-64.efi - to overcome some UEFI memory problems on our mobos
- optionally FSInject-64.efi
Do not forget slide=0. Good luck.
Edit:
5. If UEFI booting from FAT32 USB stick, you can boot directly to Clover by copying /EFI/Boot/CloverX64.efi into /EFI/Boot/BootX64.efi. BootX64.efi is default app that will be started when the stick is selected for UEFI boot.