Contribute
Register

10.11.4+ Skylake Starter Guide

@wildwillow,

This makes no sense my SSD is Samsung 850 Pro AHCI non NVme yet I get the same issue as this one post #51. I will try genericNVme to see what happens. I also have the IOAPIC clover patch for the Skylake MB's and that did not help. After that last line line in post #51 I keep waiting and I see the message Still Waiting for Root Device, then the screen text becomes shattered and unreadable with the prohibited sign.

This Post:

http://www.tonymacx86.com/threads/10-11-4-skylake-starter-guide.193628/page-6#post-1274123

My System:

Asus Maximus VIII Hero Alpha (Latest Bios 1902 same problem in v1702)
Corsair Vengeance 64 GB on Asus's QVL memory list
Evga GTX 770 4Gb
Samsung SSD (AHCI) 850 Pro
EC 10.11.6
 
Last edited:
@wildwillow,

This makes no sense my SSD is Samsung 850 Pro AHCI non NVme yet I get the same issue as this one post #51. I will try genericNVme to see what happens. I also have the IOAPIC clover patch for the Skylake MB's and that did not help. After that last line line in post #51 I keep waiting and I see the message Still Waiting for Root Device, then the screen text becomes shattered and unreadable with the prohibited sign.

This Post:

http://www.tonymacx86.com/threads/10-11-4-skylake-starter-guide.193628/page-6#post-1274123

My System:

Asus Maximus VIII Hero Alpha (Latest Bios 1902 same problem in v1702)
Corsair Vengeance 64 GB on Asus's QVL memory list
Evga GTX 770 4Gb
Samsung SSD (AHCI) 850 Pro
EC 10.11.6
Apologies for the late reply. Where are you with this installation? Waiting for root means its looking for the OS/installer. Installing the GenericNVMe.kext will do nothing for your issue with a SATA device. The post you read required the user to install the NVMe driver due to the fact that was what he was using. The IOAPIC patch is no longer required in later version of El Capitan.
 
Hi Ammulder,
Thanks for your outstanding and detailed work here. I have a skylake system and I have followed you usb procedure with general success. I have 14 listed in the IO registry, however I can't seem to get power to my lacie USB 3 drive through any of these ports. Wondering if I have made a blunder somewhere or am missing something. Would appreciate your input.
 
Hi all thanks for this unfortunately whenever I load these settings my machine works perfectly for exactly two days then starts playing up again. Is there something I am doing wrong? It also does not store my multibeast settings when I try to relead the build it says file corrupted. I have tried reloading multibeast but got the same results.

Thanks in anticipation.
Alan
 
Hi, SeasideMike! Thanks for your input. I have re downloaded MultiBeast and re done the build. The latest build is a bit worse as it does not pick up sound system now. Any other advice would be greatly appreciated.
 
I am FINALLY getting my new build here Monday/Tuesday next week. I will have a GTX 1080 and a i7-6700K in my build using the Z170 model of this motherboard. It seems like most people have been able to go through this build using the Z170 WIFI model just fine, but with the GTX 1080, I am a little worried.

Should I leave GPU unplugged while using macOS? Or would it be ok to plug it in have two HDMI cables plugged into the computer, so that one would be plugged in to the GTX 1080 and the other would be plugged into the motherboard its self.

Ultimately, if I am using macOS with a GTX 1080, what steps do I need to do to hopefully avoid errors? I plan on dual booting the computer with TWO separate drives, so that macOS is on one SSD and Windows is on another SSD. Is there any guide on how to do this safely?
 
My iHack:
iMac17,1 - Asus H170M-PLUS, Intel Core i5-6500@3,20GHz (Skylake), Intel HD Graphics 530, i219-V, Crucial 2x8GB DDR4-2133, 2SSDs + HDD, VH2453MH 24'', El Capitan 10.11.6 (SSD2 - Ubuntu MATE 16.04 + Windows 10), Clover 3944.
 
Last edited:
B150M-DS3H
Success: Booted from USB -> Installed El Capitan -> trying to use Multibeast...
.. cannot make display work
.. retrying Multibeast (-x) : log says: msdodfs.kext failed to load operation not allowed..
.. cant mount ESP partition disk1s1

How do I patch your patches? Text edit?
 
TextEdit can lead to problems with your config.plist if you are not very careful. We recommend patching .plist files with Xcode or Plist Edit Pro.
 
Back
Top