[Guide] Intel NUC7/NUC8 using Clover UEFI (NUC7i7Bxx,NUC8i7Bxx,etc)

[sakiv]

I replied to sakiv's post. His issue is to do with turbo boost. Way to fix it is change cooling profile from Balanced which is default to Quiet it makes the turbo boost and fan noise more conservative while not effecting temps. Do this Bios change first.
Boot your NUC. let it load everything and wait five minutes. Make sure nothing is open ie no triangles under your dock icons right click and close everything. Make sure to have rehabmans fakesmc hwmontioring kexts in the kexts/other folder so you can see cpu and other temps. download them from latest file here. Drag the hardware monitoring app into applications folder.

RehabMan / OS-X-FakeSMC-kozlek / Downloads — Bitbucket

bitbucket.org

If your base temps are at idol 35 to 40 celcius then your temps are ok. You will get spikes in temp up to 95 celcius if browsing the web etc that's normal. If that is ok then your problem is possiblly hardware related ie memory related but worth making sure base temps are ok first.

Thanks for the reply.
I tried this actually before I posted as i has seen it elsewhere. When you turn off turbo boost, my base temps are in the 30-50 range. With load it quickly shoots up to 100deg C. My other issue with the whole computer just randomly shutting off is still happening. Nothing in the logs to indicate why. As I was typing this reply to you, it happened with only this webpage open and at that time temps were not super high so now I really dont know what is causing my problem. I was totally stable on Mojave and now having these issues on Catalina.

 

[Cyberdude]

I don’t have anyway to test what I’m suggesting, there were missing kexts that should have enabled the wireless/ Bluetooth but I also noticed the ACPI/patched folder was empty and that could be part of it as well. The only reason you might have problems using Rehabmans original scripts is you will likely be installing a later version of Mojave than 14.2. The fix for that is using a later version of clover than he used so supposedly you can install, download his github content and run the scripts and then after that update Clover. Should work.

OK, so went through the Rehabman scripts and got my Wifi/BT issues worked out as well as accel. graphics. SO all is good. Honestly, i tried to walk back the changes to see what finally triggered the functionality, but couldn't figure it out. But it works, so...

I think I'll just leave my NUC7 on Mojave and stop screwing with it.

Thanks for all the help! I really appreciate it.

 

[PixelNot]

NUC8i7BEH doesn't like 64 GB! I have a fully working NUC following the instructions and EFI shared by LeesureOne. I decided to pull the trigger on 64 GB (2 * 32 GB) but it doesnt like it and refuses to boot. Enclosed is the output if I run the -V flag on boot. If I literally power it off and put the 32 GB back, it boots and runs no issue.

I realise 64 GB isn't offically supported via the Ark website but it does work no problems with Linux and Win 10 that I have run for several weeks without an issue.

 

[Leesureone]

OK, so went through the Rehabman scripts and got my Wifi/BT issues worked out. Honestly, i tried to walk back the changes to see what finally triggered the functionality, but couldn't figure it out. But it works, so...

I still can't seem to get the accel. graphics to work however, so any help on that front would be greatly appreciated.

Did you set up your bios to match:

These settings are important but are already set as needed by "Load Defaults"
- Devices->Video, "IGD Minimum Memory" set to 64mb or 128mb
- Devices->Video, "IGD Aperture Size" set to 256mb

NUC8i7BEH doesn't like 64 GB! I have a fully working NUC following the instructions and EFI shared by LeesureOne. I decided to pull the trigger on 64 GB (2 * 32 GB) but it doesnt like it and refuses to boot. Enclosed is the output if I run the -V flag on boot. If I literally power it off and put the 32 GB back, it boots and runs no issue.

I realise 64 GB isn't offically supported via the Ark website but it does work no problems with Linux and Win 10 that I have run for several weeks without an issue.

View attachment 435808

This has been brought up before by some other users, as far as I know they had to resign themselves to running 32 GBs.

 

[Escanor]

Hello everyone, I am just getting into hackintosh and ready to buy my first nuc8i7BEH2.. I was looking into the forum to understand which wifi/bt card is compatible with the system, does anyone used the M.2: BCM94350ZAE/DW1820A on the nuc? Should I buy the adaptor or is ready to be insert?

 

[Leesureone]

Hello everyone, I am just getting into hackintosh and ready to buy my first nuc8i7BEH2.. I was looking into the forum to understand which wifi/bt card is compatible with the system, does anyone used the M.2: BCM94350ZAE/DW1820A on the nuc? Should I buy the adaptor or is ready to be insert?

The M.2: BCM94350ZAE/DW1820A may or may not work, its proven to be problematic in that apparently there are different variations of the card. The best recommendation is to use the Dell DW1560 although they are trending between $60 to $140 on Ebay or Amazon USA. You will also need an adapter and cables as documented here:

GitHub - sarkrui/NUC8i7BEH-Hackintosh-Build: [GUIDE] Installing macOS Mojave (10.14.x) on Intel NUC8i7BEH using Clover UEFI

[GUIDE] Installing macOS Mojave (10.14.x) on Intel NUC8i7BEH using Clover UEFI - GitHub - sarkrui/NUC8i7BEH-Hackintosh-Build: [GUIDE] Installing macOS Mojave (10.14.x) on Intel NUC8i7BEH using Clov...

github.com

Unless you need the connectivity features of OSX its recommended you take advantage of the M2 slot using a NVME SSD and using wired internet or purchasing a wireless or Bluetooth USB adapter (they do not make one that does both for OSX)

 

[Escanor]

The M.2: BCM94350ZAE/DW1820A may or may not work, its proven to be problematic in that apparently there are different variations of the card. The best recommendation is to use the Dell DW1560 although they are trending between $60 to $140 on Ebay or Amazon USA. You will also need an adapter and cables as documented here:

GitHub - sarkrui/NUC8i7BEH-Hackintosh-Build: [GUIDE] Installing macOS Mojave (10.14.x) on Intel NUC8i7BEH using Clover UEFI

[GUIDE] Installing macOS Mojave (10.14.x) on Intel NUC8i7BEH using Clover UEFI - GitHub - sarkrui/NUC8i7BEH-Hackintosh-Build: [GUIDE] Installing macOS Mojave (10.14.x) on Intel NUC8i7BEH using Clov...

github.com

Unless you need the connectivity features of OSX its recommended you take advantage of the M2 slot using a NVME SSD and using wired internet or purchasing a wireless or Bluetooth USB adapter (they do not make one that does both for OSX)

I just discover the guide that shows the ram are compatible with 2400mhz and I bought the 2666 one's. Good start though.. I will give it a try to the problematic one cause I found it at 15 euro.. Living in europe sucks with those components cause are really hard to find. I just have to wait till tomorrow that I will receive the components and start to call all the saints in the sky to help me

 

[WillMac]

I am suspecting it is my Asus USB bluetooth dongle to blame, but unfortunately this has to stay connected since I am using my Apple BT Keyboard/Mouse. It is a real shame that no solution for the inbuilt bluetooth firmware issue has been found (yet, fingers crossed).

I'm using Apple BT keyboard and mouse as well, with embedded NUC Intel BT. I have to use Linux workaround - boot to Linux to allow it to init BT properly (upload firmware) and then reboot to MacOS. BT works fine then as long as you don't poweroff the NUC (works fine after wake up from sleep). It survives reboots too. I only have to do is when I power it off, which is like once a week. It's not practical, but doable. I do however notice that my keyboard loses charge much faster than before (than with MacBook Pro).

 

[Nemphys]

I'm using Apple BT keyboard and mouse as well, with embedded NUC Intel BT. I have to use Linux workaround - boot to Linux to allow it to init BT properly (upload firmware) and then reboot to MacOS. BT works fine then as long as you don't poweroff the NUC (works fine after wake up from sleep). It survives reboots too. I only have to do is when I power it off, which is like once a week. It's not practical, but doable. I do however notice that my keyboard loses charge much faster than before (than with MacBook Pro).

Yes, I considered going this route, but I take my NUC to my office every day, so I would have to do that at least twice a day. I think it survives a simple power off, though, as long as you don't disconnect the power cable; I don't remember if I have tested this on my NUC, but it definitely applies to my wife's NUC7i3BNH.
It would be nice if some kext guru found a way to solve the firmware upload issue, though

 

[Leesureone]

Yes, I considered going this route, but I take my NUC to my office every day, so I would have to do that at least twice a day. I think it survives a simple power off, though, as long as you don't disconnect the power cable; I don't remember if I have tested this on my NUC, but it definitely applies to my wife's NUC7i3BNH.
It would be nice if some kext guru found a way to solve the firmware upload issue, though

All I'm going to say is wishful thinking. Ever considered a bluetooth dongle? There are quite a few that work with OSX without drivers.