I've had my Skull Canyon working as my primary computer for about a week now. Thanks, RehabMan for all your work on the Intel NUC's and the NVMe SSD's.
I just wanted to share some problems I encountered along the way. In doing a Google search I couldn't find people who had these issues with these specific causes, so hopefully by putting it here, it may help somebody else.
1) In trying to start the install from Clover, I got the message:
OsxAptioFixDrv: Starting overrides for \.IABootFiles\boot.efi
Using reloc block: no, hibernate wake: no
+++++++++++++++++++++++++++++++++++++++++++++++++++
There could be numerous causes for this, what happened in my case was that the BIOS setting "Execute Disable Bit" was disabled where it should have been enabled (must have read the instructions incorrectly).
2) Also, in starting the install from Clover, in verbose mode, messages fly quickly on the screen, a kernel panic occurs (only discernible if you can read quickly or take a picture) and the Clover screen re-appears.
Again, there could be numerous causes. In my case, I have the Samsung 960 (had the Evo, it died and replaced it with the Pro) and I created the SSDT_NVMe-Pcc.aml from what's been posted on this site. If you do that, the SSD has to be in the first slot (middle of the computer). Putting in the other slot is the wrong slot and caused the kernel panic.
3) I created the HackrNVMeFamily on my 10.11.6 (up-to-date the security updates) computer, tried to install from a recent AppStore download of El Capitan. It wouldn't recognize the 960 Evo. The App Store gave me the base 10.11.6 despite me downloading it in early May 2017. I'm guessing (RehabMan, feel free to comment) that me using HackrNVMeFamily created from an updated El Capitan with the base 10.11.6 installer was the problem. Given the choice of either installing the base 10.11.6 and updating it on the Skull Canyon or installing Sierra (10.12.4 at the time) on an external disk on one of my computers (I hadn't installed Sierra yet on any of my other Mac), I just decided to install Sierra and that worked.
4) I was having an issue whereby coming out of waking the display would freeze the Skull Canyon. (I followed the directions and computer sleep is disabled). Before trying to wake, I could ssh into the Skull Canyon and it was working. Trying to wake the display would make the computer freeze (ssh, ping would not work, obviously the display wasn't working as well). This happened numerous times but once was there a message in one of the logs:
Assertion failed: (false && "10 seconds of continuous GPU Driver unreadiness, relaunching WindowServer"), function void IMGGraphicsStackReadinessFailure(), file Server/Windows/Updater.cc, line 2864.
In the BIOS settings, go to:
Performance -> Graphics -> RC6 (Render Standby) -> Disable
While there were still problems with the display waking, the computer no longer would freeze when trying to wake the display. It should be noted that these display wake problems would not happen for short sleep periods - I would test it after a few minutes of sleep and it would wake (thinking I had solved the problem), but always when the sleep was were 30 minutes or longer, there would be a problem. I don't know what the threshold is.
(I think the display sleep issue is with my monitor, the Nixeus NX-Vue27 - 4-1/2 years old, using DisplayPort; I no longer have the issue when using HDMI - I didn't try this early on because the specs for the monitor say that 2560x1440 is only supported by DisplayPort and DVI, but it turns out that it works for HDMI. Please don't suggest a different cable - the cable I have is VESA compliant and has pin-20 disconnected and in any case, I hope to be getting a new monitor in the next few months.)