Contribute
Register

[Guide] Intel Kaby Lake NUC7 using Clover UEFI (NUC7i7BNH, NUC7i5BNK, NUC7i3BNH, etc)

Status
Not open for further replies.
Joined
Jun 14, 2017
Messages
11
Motherboard
Intel NUC7i5BNK
CPU
Intel® Core i5-7260U
Graphics
Intel® Iris™ Plus 640
Mac
  1. MacBook Air
  2. Mac mini
Mobile Phone
  1. iOS
Thanks a lot for the guide. Using it I created my first Hackintosh last weekend. But I had a few problems which I wanted to share. I use NUC7I5BNH with Samsung NVMe SSD 960 EVO 250GB and Crucial 2x 8GB RAM.

I created two USB-sticks using both options (MBR and GPT).

First issue (Installation):
During installation the SSD was not recognised in Disk Utility which caused me to use "diskutil" in Terminal. For me as a Hackintosh (and Linux) novice it took some time to learn how to use it and to create EFI and HFS+ partitions which then had been replace to APFS during High Sierra installation. But finally it worked out fine. Surprisingly I didn't see any comments/problems/help like this in the thread.

Second issue (Post Install):
Finally, 'make install_nuc7', mounts the EFI partition, and copies the built files where they can be loaded by Clover (to EFI/Clover/ACPI/patched).

The final step "make install_nuc7" didn't work properly and din't mount the EFI partition. I had to mount it manually. After that copying the built files didn't work either. So I had to copy them manually using the Finder. I though that the created USB-Stick was the issue so I tried two times using different created USB-sticks. Same issue with both USB-sticks.

Finally it all works out fine and the Hackintosh is working. But w/o manual extra tasks I would have been in trouble. I'm really glad to have a new performant "2017 Mac mini" which I use as a Media PC (Kodi, etc.). Thanks again for the great work to create that guide and your support.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
184,623
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
First issue (Installation):
During installation the SSD was not recognised in Disk Utility which caused me to use "diskutil" in Terminal. For me as a Hackintosh (and Linux) novice it took some time to learn how to use it and to create EFI and HFS+ partitions which then had been replace to APFS during High Sierra installation. But finally it worked out fine. Surprisingly I didn't see any comments/problems/help like this in the thread.

Should be no problem provided you place apfs.efi and HFSPlus.efi in drivers64UEFI as per guide.

The final step "make install_nuc7" didn't work properly and din't mount the EFI partition. I had to mount it manually.
After that copying the built files didn't work either.

You will need to provide details.
For example, output from mount_efi.sh, 'diskutil list', etc.
 
Last edited:
Joined
Jun 14, 2017
Messages
11
Motherboard
Intel NUC7i5BNK
CPU
Intel® Core i5-7260U
Graphics
Intel® Iris™ Plus 640
Mac
  1. MacBook Air
  2. Mac mini
Mobile Phone
  1. iOS
apfs.efi and hfsplus.efi were in the right folder as per guide. The SSD was recognised with "diskutil status" via Terminal. The Disk Utility app is not working properly for the Samsung 960 EVO. I tried another Samsung 960 EVO but it failed as well. My recommendation is just to add a comment in the guide to use diskutil in Terminal in that case. Maybe with the instructions (syntax) to create the HFS+ and EFI partitions. Just to be on the safe side.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
184,623
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
apfs.efi and hfsplus.efi were in the right folder as per guide. The SSD was recognised with "diskutil status" via Terminal. The Disk Utility app is not working properly for the Samsung 960 EVO. I tried another Samsung 960 EVO but it failed as well. My recommendation is just to add a comment in the guide to use diskutil in Terminal in that case. Maybe with the instructions (syntax) to create the HFS+ and EFI partitions. Just to be on the safe side.

For that specific issue (I assume this is the uninitialized disk problem), we'll just wait for Apple to fix their problem.
Easy work around is to initialize the disk in Windows... (eg. diskpart.exe)

Also, I wonder if people are just missing the "View" menu options in Disk Utility...

But what was your issue with mount_efi.sh?
 
Joined
Jun 14, 2017
Messages
11
Motherboard
Intel NUC7i5BNK
CPU
Intel® Core i5-7260U
Graphics
Intel® Iris™ Plus 640
Mac
  1. MacBook Air
  2. Mac mini
Mobile Phone
  1. iOS
But what was your issue with mount_efi.sh?

I just followed your guide and everything worked fine w/o any errors or warnings until the last step. There was an error message that the build files had not been copied. Without the right final config.plist the system didn't boot from "Macintosh HD" of course. So I copied the build files by hand (Finder). After that it booting worked.
I just started the last script "make install_nuc7" again to see whether the copying works >> which works after the manual EFI mount. The mistake was only in the EFI mount instructions (the mount_efi.sh I used is attached). I didn't look into your scripts because I can't understand those. Almost all works here w/o understanding the tasks thanks to your great tools and guides.

For me the issue is closed because there is a work around (manual mount of EFI partition). I just wanted to mention my experience in case someone else has the same issue.
 

Attachments

  • mount_efi.sh.zip
    1.8 KB · Views: 62

RehabMan

Moderator
Joined
May 3, 2012
Messages
184,623
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
I just followed your guide and everything worked fine w/o any errors or warnings until the last step. There was an error message that the build files had not been copied. Without the right final config.plist the system didn't boot from "Macintosh HD" of course. So I copied the build files by hand (Finder). After that it booting worked.
I just started the last script "make install_nuc7" again to see whether the copying works >> which works after the manual EFI mount. The mistake was only in the EFI mount instructions (the mount_efi.sh I used is attached). I didn't look into your scripts because I can't understand those. Almost all works here w/o understanding the tasks thanks to your great tools and guides.

For me the issue is closed because there is a work around (manual mount of EFI partition). I just wanted to mention my experience in case someone else has the same issue.

You will need to provide the error messages/failure details.
I cannot guess.
And I'm not clairvoyant.
./mount_efi.sh and 'make install_nuc7' is working just fine here.

Note: "make install_nuc7" does NOT copy the final config.plist. That is a separate step, as per post #1 guide.
 
Joined
Jul 31, 2012
Messages
113
Motherboard
ASUS STRIX Z370G
CPU
i7-8700K
Graphics
Vega 64
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
After you purchase a USB-C->DP, report back here.

4k60 works when selecting "default for display" and using a USB-C to DP cable. Curiously, connector-type still reports 00 04 00 00:

Screen Shot 2017-12-05 at 5.34.53 PM.png

while About This Mac now reports DisplayPort (previously HMDI or DVI):

IMG_9487.JPG
 

Attachments

  • ioreg-dp.ioreg.zip
    598.9 KB · Views: 69
Last edited:
Joined
Jan 21, 2013
Messages
81
Motherboard
SA25GG
CPU
2620m
Graphics
6630m
Mobile Phone
  1. iOS
Hi Rehabman,

Do you think apple thunderbolt display can be used with a usb-c -> thunderbolt connector? Can all of the video, audio and usb data work with just one usb-c port?

Cheers

Peng
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
184,623
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
4k60 works when selecting "default for display" and using a USB-C to DP cable. Curiously, connector-type still reports 00 04 00 00:

View attachment 297518

while About This Mac now reports DisplayPort (previously HMDI or DVI):

View attachment 297523

What I find strange about this report is that the display is still connected to @0.
Expected that with using the USB-C port, that it would be different from the HDMI port (your previous ioreg, that was supposedly using the HDMI port, was also connected to @0).
Are you sure the ioreg files you attached accurately represent display connected to HDMI (then) and DP (now)?
 
Status
Not open for further replies.
Top