first of all I want to thank you for the great work and all your attainments regarding to Clover! I was testing some stuff and ran into different issues, so for that reason I really need your help.
So let's beginn with my system specs:
- CPU: Intel i5 3570K
- Motherboard: Gigabyte GA-H77-DS3H latest F7 AMI Alaska UEFI Bios
- GPU: Onboard Intel HD 4000
- OS: Only Mountain Lion 10.8.2 (12C54)
- Identifier: Mac Book Pro 9.2 because of the Chipset - Also tried iMac12.2 but it gave me AGPM issues
- Custom DSDT: Yes
First I've installed the non UEFI version for testing and everything seemed to work flawless. I could boot into OS X, had full CI/QE etc. Then I've tested my USB 3.0 ports but they were not working properly. When I plugged in a USB 2.0 device, nothing happened at all. Setting the ports to USB 2.0 in Bios lets them work in 2.0 mode at least.
This would be ok for me, because I don't own any USB 3.0 products at this time. The more annoying thing is that my screen won't wake up when I set the machine to sleep and try to wake it up if I'm using my custom DSDT. What surprises me very much, is the fact that this is not happening every time!
For example: I can go to sleep for about ten times without any issues. Then, the eleventh time the screen won't wake up from sleep. Without DSDT sleep seems to work well. By the way, I'm running into the same issues using the latest version of Chameleon and don't have ANY idea how to solve it!
So far so good. After the whole testing I decided to install the UEFI version. Unfortunately it isn't even booting.
I have the following stuff in "drivers64UEFI":
- VBoxHfs.64.efi - also tried HFSPlus.efi, but it has no effect.
I've attached Clover's config.plist, my custom DSDT and the preboot.log. So if anybody could help me to solve my problems, especially the sleep issue, I would be the happiest man on Planet Earth!
Many thanks in advance!
By the way... is there any quiet boot option in Clover and is it possible to wake the system via keyboard?
Adding "darkwake=0" into <key>boot-args</key> isn't changing anything.