Contribute
Register

[Guide] Intel Skylake NUC6 (and Skull Canyon) using Clover UEFI (NUC6i5SYK, NUC6i7KYK, etc)

Status
Not open for further replies.
E.g. Arctic Silver is safe. Assuming that all liquid metal based pasted contain gallium is a bit overkill.

Yes Arctic Silver is safe because it isn't liquid metal.

There's a marked difference in their thermal conductivity values -

Arctic Silver 5 - 8.7 W/(m·K)
Thermal Grizzly Conductonaut - 73 W/(m·K)

Liquid metal pastes (Thermal Grizzly Conductonaut, Coollaboratory Liquid Pro/Ultra etc) are gallium-based alloys.

In the end I opted for Thermal Grizzly Kryonaut and temps are still settling but happy to report I'm also seeing a ~10°C drop.
 
Hi Rehabman,

I've installed High Sierra (10.13.1) following your guide as closely as possible on a NUC6i7KYK. For some reason USB3 devices are not detected after installation, unless they are behind a USB 2.0 hub. I've tried several things but couldn't figure out the reason for this behaviour. Any help/suggestions would be appreciated.

All the requested information is attached to this post:

1) Kextstate etc output:
sh-3.2# kextstat|grep -y acpiplat
15 1 0xffffff7f82220000 0xa5000 0xa5000 com.apple.driver.AppleACPIPlatform (6.1) 33FE0184-9235-32DF-8BC2-0B2B11971EDB <14 13 12 11 7 6 5 4 3 1>
sh-3.2# kextstat|grep -y appleintelcpu
sh-3.2# kextstat|grep -y applelpc
sh-3.2# kextstat|grep -y applehda
91 1 0xffffff7f81e27000 0x1f000 0x1f000 com.apple.driver.AppleHDAController (280.12) 55162F3D-B7E9-315C-A7E1-C5C4C02F03EC <90 89 88 12 7 6 5 4 3 1>
117 0 0xffffff7f81fbb000 0xb7000 0xb7000 com.apple.driver.AppleHDA (280.12) 7FC2BABA-4D4F-34FC-93E2-3E3244DEB73D <116 99 91 90 89 88 6 5 4 3 1>
sh-3.2# ls -l /System/Library/Extensions/AppleHDA.kext/Contents/Resources/*.zml.zlib
-rw-r--r-- 1 root wheel 4583 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/Platforms.zml.zlib
-rw-r--r-- 1 root wheel 1836 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout1.zml.zlib
-rw-r--r-- 1 root wheel 1828 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout2.zml.zlib
sh-3.2# md5 /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA
MD5 (/System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA) = c8991bd6637c2bb8471c235dd3408939
sh-3.2#

2) Touch & Kextcache output:
sh-3.2# kextstat|grep -y acpiplat
15 1 0xffffff7f82220000 0xa5000 0xa5000 com.apple.driver.AppleACPIPlatform (6.1) 33FE0184-9235-32DF-8BC2-0B2B11971EDB <14 13 12 11 7 6 5 4 3 1>
sh-3.2# kextstat|grep -y appleintelcpu
sh-3.2# kextstat|grep -y applelpc
sh-3.2# kextstat|grep -y applehda
91 1 0xffffff7f81e27000 0x1f000 0x1f000 com.apple.driver.AppleHDAController (280.12) 55162F3D-B7E9-315C-A7E1-C5C4C02F03EC <90 89 88 12 7 6 5 4 3 1>
117 0 0xffffff7f81fbb000 0xb7000 0xb7000 com.apple.driver.AppleHDA (280.12) 7FC2BABA-4D4F-34FC-93E2-3E3244DEB73D <116 99 91 90 89 88 6 5 4 3 1>
sh-3.2# ls -l /System/Library/Extensions/AppleHDA.kext/Contents/Resources/*.zml.zlib
-rw-r--r-- 1 root wheel 4583 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/Platforms.zml.zlib
-rw-r--r-- 1 root wheel 1836 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout1.zml.zlib
-rw-r--r-- 1 root wheel 1828 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout2.zml.zlib
sh-3.2# md5 /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA
MD5 (/System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA) = c8991bd6637c2bb8471c235dd3408939
sh-3.2#

Thanks,
Roel
 

Attachments

  • ioreg_NUC6i7KYK.zip
    510.4 KB · Views: 68
  • RehabMan_folder.zip
    51.6 KB · Views: 75
  • CLOVER.zip
    1.7 MB · Views: 88
Hi Rehabman,

I've installed High Sierra (10.13.1) following your guide as closely as possible on a NUC6i7KYK. For some reason USB3 devices are not detected after installation, unless they are behind a USB 2.0 hub. I've tried several things but couldn't figure out the reason for this behaviour. Any help/suggestions would be appreciated.

All the requested information is attached to this post:

1) Kextstate etc output:
sh-3.2# kextstat|grep -y acpiplat
15 1 0xffffff7f82220000 0xa5000 0xa5000 com.apple.driver.AppleACPIPlatform (6.1) 33FE0184-9235-32DF-8BC2-0B2B11971EDB <14 13 12 11 7 6 5 4 3 1>
sh-3.2# kextstat|grep -y appleintelcpu
sh-3.2# kextstat|grep -y applelpc
sh-3.2# kextstat|grep -y applehda
91 1 0xffffff7f81e27000 0x1f000 0x1f000 com.apple.driver.AppleHDAController (280.12) 55162F3D-B7E9-315C-A7E1-C5C4C02F03EC <90 89 88 12 7 6 5 4 3 1>
117 0 0xffffff7f81fbb000 0xb7000 0xb7000 com.apple.driver.AppleHDA (280.12) 7FC2BABA-4D4F-34FC-93E2-3E3244DEB73D <116 99 91 90 89 88 6 5 4 3 1>
sh-3.2# ls -l /System/Library/Extensions/AppleHDA.kext/Contents/Resources/*.zml.zlib
-rw-r--r-- 1 root wheel 4583 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/Platforms.zml.zlib
-rw-r--r-- 1 root wheel 1836 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout1.zml.zlib
-rw-r--r-- 1 root wheel 1828 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout2.zml.zlib
sh-3.2# md5 /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA
MD5 (/System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA) = c8991bd6637c2bb8471c235dd3408939
sh-3.2#

2) Touch & Kextcache output:
sh-3.2# kextstat|grep -y acpiplat
15 1 0xffffff7f82220000 0xa5000 0xa5000 com.apple.driver.AppleACPIPlatform (6.1) 33FE0184-9235-32DF-8BC2-0B2B11971EDB <14 13 12 11 7 6 5 4 3 1>
sh-3.2# kextstat|grep -y appleintelcpu
sh-3.2# kextstat|grep -y applelpc
sh-3.2# kextstat|grep -y applehda
91 1 0xffffff7f81e27000 0x1f000 0x1f000 com.apple.driver.AppleHDAController (280.12) 55162F3D-B7E9-315C-A7E1-C5C4C02F03EC <90 89 88 12 7 6 5 4 3 1>
117 0 0xffffff7f81fbb000 0xb7000 0xb7000 com.apple.driver.AppleHDA (280.12) 7FC2BABA-4D4F-34FC-93E2-3E3244DEB73D <116 99 91 90 89 88 6 5 4 3 1>
sh-3.2# ls -l /System/Library/Extensions/AppleHDA.kext/Contents/Resources/*.zml.zlib
-rw-r--r-- 1 root wheel 4583 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/Platforms.zml.zlib
-rw-r--r-- 1 root wheel 1836 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout1.zml.zlib
-rw-r--r-- 1 root wheel 1828 Nov 1 23:00 /System/Library/Extensions/AppleHDA.kext/Contents/Resources/layout2.zml.zlib
sh-3.2# md5 /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA
MD5 (/System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA) = c8991bd6637c2bb8471c235dd3408939
sh-3.2#

Thanks,
Roel

Your config.plist is wrong.
Read post #1, "Final config.plist".
 
Your config.plist is wrong.
Read post #1, "Final config.plist".

My apologies for wasting your time with such a basic mistake.
 
Hi,

For anybody who wants to use Thunderbolt devices. You'll need to set the Thunderbolt Security Level to 'legacy' and enable 'Thunderbolt Boot' (Thunderbolt USB boot isn't required). After this Thunderbolt devices will work as long as they have been plugged in since powering on your NUC. If you do not enable 'Thunderbolt Boot', Thunderbolt devices will only work after rebooting MacOS after the initial powering up of the NUC.

Thanks,
Roel
 
Hi, I'm having issues with the initial USB install using 10.13.1. It stops after "Still waiting for root device" and then I get the circle with the line through it. I seem to get the same with or without the 950Pro so it does not seem to be a NVMe spoofing problem. The USB passes that point if I exclude any kext (but of course, doesn't boot either).
 

Attachments

  • IMG_3974.jpg
    IMG_3974.jpg
    3.4 MB · Views: 110
  • IMG_3975.jpg
    IMG_3975.jpg
    2.4 MB · Views: 117
  • CLOVER.zip
    1.8 MB · Views: 66
I faced a similar issue. Booting off a different (USB 2.0) flash drive fixed it for me. Edit: although given that kexts affect progress this might well be a useless suggestion!
 
Last edited:
Hi, I'm having issues with the initial USB install using 10.13.1. It stops after "Still waiting for root device" and then I get the circle with the line through it. I seem to get the same with or without the 950Pro so it does not seem to be a NVMe spoofing problem. The USB passes that point if I exclude any kext (but of course, doesn't boot either).

Make sure you're using the correct USB port as per post #1.
And USBInjectAll.kext is not recommended for installation (it will likely cause USB3 to not work, due to lack of correct configuration). A USB2 stick will probably work with or without USBInjectAll.kext. Post-install we use a custom configuration for USBInjectAll such that all the USB ports work correctly, but that is not in place pre-install.
 
I faced a similar issue. Booting off a different (USB 2.0) flash drive fixed it for me. Edit: although given that kexts affect progress this might well be a useless suggestion!
OK. USB2.0 drive worked. That's a really strange problem. I only used the (yellow) left one for USB3.0 and USB2.0 and the problem went away with the slower drive.

Thanks for that hint.
 
OK. USB2.0 drive worked. That's a really strange problem. I only used the (yellow) left one for USB3.0 and USB2.0 and the problem went away with the slower drive.

Thanks for that hint.

The reason your USB3 drive did not work is because you made the mistake of using USBInjectAll.kext (the guide does not call for it during installation).
 
Status
Not open for further replies.
Back
Top