Contribute
Register

Testing Thread: Skylake Platform in OS X

Status
Not open for further replies.
Same here ...
Edit: I've fixed that by changing FixOwnership in Clover's config.plist to true. Now it says "waiting for root device"

Look here: https://pikeralpha.wordpress.com/2015/11/06/appleapic-kext-binary-patch-for-skylake/

"Update

A few tips for folks who are still getting the dreadful: “Still waiting for root device“. First. Make sure that you have XHCI hand-off enabled in the BIOS and dropping ACPI tables like SaSsdt.aml may cause boot issues with SATA devices!"
 
All good now! Successfully booted to Mac OS X on my ASrock Z170 Extreme4 with a few glitches here and there. Also , changing the resolution will cause problems with the screen.
 
All good now! Successfully booted to Mac OS X on my ASrock Z170 Extreme4 with a few glitches here and there. Also , changing the resolution will cause problems with the screen.

A few tips for folks who are still getting the dreadful: “Still waiting for root device“. First. Make sure that you have XHCI hand-off enabled in the BIOS and dropping ACPI tables like SaSsdt.aml may cause boot issues with SATA devices!"



What did you do to fix the waiting for root device after doing the fix ownership?

What if we don't have the XHCI handoff setting in our BIOS?

I don't understand the line "and dropping ACPI tables like SaSsdt.aml may cause boot issues with SATA devices!"

Thanks!
 
Ok, I repartitioned my testing hdd, and made an installer partition using Unibeast 6.0.1. Now, I try to boot using a usb with Clover 3320 cause I was still getting the row of pluses but with 2 lines before it, so I am trying the hfs plus.efi thing. But now I am getting:

***********************************************
This version of Mac OS X is not supported on this platform!
***********************************************
Reason: Mac-DB15BD556843C820

I tried google, and I think is a SMBIOS thing, but I am not sure.
Any ideas?
 
If you get waiting for root, you need to add the APIC fix if you haven't already to your config.plist. See Post #1, Update #3.
 
What did you do to fix the waiting for root device after doing the fix ownership?

What if we don't have the XHCI handoff setting in our BIOS?

I don't understand the line "and dropping ACPI tables like SaSsdt.aml may cause boot issues with SATA devices!"

Thanks!
EDIT : Nervermind. Just add this FakeSMC.kext to \EFI\CLOVER\kexts\10.11
That fixed it for me. You could use my config.plist too if you want.

View attachment FakeSMC and config.plist .zip
 
If you get waiting for root, you need to add the APIC fix if you haven't already to your config.plist. See Post #1, Update #3.

I did the direct find/replace method that Pike recommended and used the config.plist edit both to no avail on GA-Z170-Gaming 5. I guess it's the same error for a different reason? I'm going to try the USB fix when I get home in about an hour.
 
Ok, I managed to replace the VBox...efi with the HFSPlus.efi in the drivers64UEFI folder in the efi partition, of the hdd with the installer that has been made with Unibeast 6.0.1, but I am still stuck at:

OsxAptioFixDRV: Starting Overrides for System\Library\CoreServices\boot.efi
using relocate block: no, hibernate wake: no
+++++++++++++++++++++++++++++++++++++

Edit:
I unplugged the GTX970 too.
Still the same.

Any ideas?
 
EDIT : Nervermind. Just add this FakeSMC.kext to \EFI\CLOVER\kexts\10.11
That fixed it for me. You could use my config.plist too if you want.

View attachment 161022

With your config.plist / FakeSMC.kext I'm getting a kernel panic before I can hit the installer with my ASUS H170 PLUS-D3 / i7-6700.
IMG_0174.jpgIMG_0175.jpg
Apologies if I'm missing something straightforward - any thoughts?
 
Status
Not open for further replies.
Back
Top