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

[RehabMan]

This guide has been moved to the High Sierra guides forum:

https://www.tonymacx86.com/threads/...efi-nuc7i7bnh-nuc7i5bnk-nuc7i3bnh-etc.233241/

 

[rustyshelf]

Nice guide! I got my nuc7 (i5 model) working great based on this. Obviously WiFi and BT don't work but a cheap USB dongle fixed BT for me. The last problem I have is that iTunes won't play DHCP content, which I haven't been able to find a workaround for. I followed various guides for things like Shiki but iTunes still pops up a DHCP error if I try and play any HD movies I purchased from Apple. I don't suppose you've had any luck here or know of things I could try?

 

[RehabMan]

Nice guide! I got my nuc7 (i5 model) working great based on this. Obviously WiFi and BT don't work but a cheap USB dongle fixed BT for me. The last problem I have is that iTunes won't play DHCP content, which I haven't been able to find a workaround for. I followed various guides for things like Shiki but iTunes still pops up a DHCP error if I try and play any HD movies I purchased from Apple. I don't suppose you've had any luck here or know of things I could try?

Shiki.kext + Lilu.kext is supposed to solve the DRM problem.
I don't use DRM protected content, so it is not an issue for me...

 

[ralle12345]

Hello RehabMan

first of all thanks for your guide. I got my first hackintosh with El Cap (10.11.6) running thanks to your work. The system is a NUC7i5bnh. It had BIOS Version 042 when it came out of its box and I have since upgraded it to version 046.

The boot disk is on a Samsung 950 EVO NVMe, therefor I changed your SSDT-NUC7.aml to include the class-code spoof.
Other than that I followed your guide (at least I think i did )

Still there are two problems left that I wasn't able to solve myself.

* Graphics


As far as I understood from reading posts on the site there should be a kext loaded for the graphics.

Also, there seems to be no audio. In the system settings panel there are no audio devices.

Could you please take a look at my debug infos? I hope I'm not wasting your time with some really obvious mistake.

 

[RehabMan]

Hello RehabMan

first of all thanks for your guide. I got my first hackintosh with El Cap (10.11.6) running thanks to your work. The system is a NUC7i5bnh. It had BIOS Version 042 when it came out of its box and I have since upgraded it to version 046.

The boot disk is on a Samsung 950 EVO NVMe, therefor I changed your SSDT-NUC7.aml to include the class-code spoof.
Other than that I followed your guide (at least I think i did )

Still there are two problems left that I wasn't able to solve myself.

* Graphics
View attachment 254456

As far as I understood from reading posts on the site there should be a kext loaded for the graphics.

Also, there seems to be no audio. In the system settings panel there are no audio devices.

Could you please take a look at my debug infos? I hope I'm not wasting your time with some really obvious mistake.

If you made the NVMe changes to SSDT-NUC, why do you have a separate SSDT_NVMe-Pcc.aml?

I can't look in detail ATM, but seems like a potential for duplicate.

Edit: Just checked. That is your mistake... your edit to SSDT-NUC7.aml invalidates the entire thing becuase SSDT_NVMe_Pcc.aml is loading first.

Suggestion: Don't modify SSDT-NUC7 (use github version). You can simply add the NVMe SSDT (as you already have).

 

[ralle12345]

.
Edit: Just checked. That is your mistake... your edit to SSDT-NUC7.aml invalidates the entire thing becuase SSDT_NVMe_Pcc.aml is loading first.

Suggestion: Don't modify SSDT-NUC7 (use github version). You can simply add the NVMe SSDT (as you already have).

Thanks for looking at my problem.

I tried different ways to boot my system now.

* the github version of SSDT-NUC7.aml with the NVMe SSDT
* only my modified version of SSDT-NUC7

Both result in the same behavior. The system boots with the apple on the screen and the progress bar halfway through, then the graphics scramble and the system reboots. I tried booting in verbose mode but due to the scrambled graphics I can't see where it stumbles.

 

[RehabMan]

Thanks for looking at my problem.

I tried different ways to boot my system now.

* the github version of SSDT-NUC7.aml with the NVMe SSDT
* only my modified version of SSDT-NUC7

Both result in the same behavior. The system boots with the apple on the screen and the progress bar halfway through, then the graphics scramble and the system reboots. I tried booting in verbose mode but due to the scrambled graphics I can't see where it stumbles.

Read post #1, "Problem Reporting"

Note: For initial boot, you may need to disable "hda-gfx" injection as per post #1. After you get AppleHDA in cache, you can then re-enable it.

 

[the_trit]

How does this gen compare to the previous in terms of fan noise? Would you consider it a worthwhile purchase over skylake?

 

[RehabMan]

How does this gen compare to the previous in terms of fan noise? Would you consider it a worthwhile purchase over skylake?

I think it is similar... similar fan design, so under similar loads, similar noise levels.
A quieter system would require a form factor redesign.

 

[ralle12345]

Read post #1, "Problem Reporting"

Note: For initial boot, you may need to disable "hda-gfx" injection as per post #1. After you get AppleHDA in cache, you can then re-enable it.

At least graphics works now:



At first I noticed in the clover options during booting that inject intel was not checked. When I checked it then intel graphics was detected and used. Inspection of the config.plist showed this line:

https://github.com/RehabMan/Intel-NUC-DSDT-Patch/blob/master/config_nuc7.plist#L170

When set to </true> graphics is loaded just fine.

For the record here are the two versions of clover config that I tried. clover-notworking1.zip is the one with the github version of config.plist and my NVMe .aml and clover-notworking2.zip is the one with my patched version of your SSDT. Both result in a non-booting system with the progress-bar going half-way through and then rebooting.