- Joined
- Oct 23, 2013
- Messages
- 6
- Mac
- Classic Mac
- Mobile Phone
Even though I have a working Clover USB drive now, I still have some questions about Clover. I am going to try a Clover UEFI reinstall and see how it works compared to tonymacx86's tools (which have worked great). Rather than start a new thread, I'll post them here.
I have a Gigabyte H87-wifi.
I know I need to install drivers for my 892 audio and Atheros/Intel ethernet. With Multibeast, this is incredibly easy. How would I go about doing this with a Clover UEFI install? Can I use Multibeast on a Clover UEFI install?
My understanding is that Gigabyte boards with Hybrid UEFI doesn't need OsxAptioFixDrv-64.efi (I quote slice below with his explanation). If I leave it out, however, the boot goes nowhere. It doesn't even get to the point where it would kernel panic with a bad config. Any idea why?
Chimera's config file and Clover's config.plist are very similar, correct? In order to get a perfect config.plist, could I just emulate Chimera's settings into Clover's format?
I have a Gigabyte H87-wifi.
I know I need to install drivers for my 892 audio and Atheros/Intel ethernet. With Multibeast, this is incredibly easy. How would I go about doing this with a Clover UEFI install? Can I use Multibeast on a Clover UEFI install?
My understanding is that Gigabyte boards with Hybrid UEFI doesn't need OsxAptioFixDrv-64.efi (I quote slice below with his explanation). If I leave it out, however, the boot goes nowhere. It doesn't even get to the point where it would kernel panic with a bad config. Any idea why?
Chimera's config file and Clover's config.plist are very similar, correct? In order to get a perfect config.plist, could I just emulate Chimera's settings into Clover's format?
I'll repost some info regarding UEFI boot from there:
When trying UEFI boot, try with following combination of drivers in /EFI/Drivers64UEFI folder:
1. HFSPlus.efi, OsxFatBinaryDrv-64.efi
if this does not work, then
2. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxLowMemFixDrv-64.efi
and then if this does not work then
3. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi (with slide=0 in boot args in config.plist)
and if even this does not work, then try:
4. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi (with slide=0 in boot args in config.plist), EmuVariableRuntimeDxe.efi (from here)
More about it:
1. HFSPlus.efi, OsxFatBinaryDrv-64.efi
This works on boards with Gigabyte Hybrid EFI. This is the best option for UEFI boot, in the sense that no special fixes are required. Any OSX should boot fine, unless some big change happens that will stop working boot here.
2. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxLowMemFixDrv-64.efi
This works on Insyde H2O UEFI. Some small memory issue will be fixed by LowMemFix, and then everything should be equal to case 1.
3. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi (with slide=0 for ML)
This works for all other boards ... well, where works. This is not so good solution because it depends on current functioning of boot.efi and current structures that are passed between boot.efi (boot loader) and kernel, like boot args and device tree. Meaning: if structure of boot args changes, like it changed when Lion came out, which caused Chameleon to fail to boot Lion, this will again break Chameleon and UEFI boot with AptioFix - until somebody fixes it. This is the most annoying thing to me because the major point for having UEFI boot is to use boot.efi as bootloader and to avoid such things. Well, if this happens, the first solution will be to fall back to standard Clover until the thing is resolved. The small issue is that standard Clover is also dependent on kernel boot args when kernel and kext patching or kext injection is used - this would also need to be turned off in that case.
4. HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi, EmuVariableRuntimeDxe.efi
This works on Dell Vostro, some ThinkPad's - some laptops with Phoenix UEFI. All mentioned in 3. is applicable here.
All other drivers may or may not be needed. Drivers listed above are required minimum. The best way to test if the driver is needed or not is to try without it - if the thing still works, then it is not needed. Well, more or less ... since for example normal boot works without FSInject, but that one can be needed sometimes.