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

[spottsy]

Th

Page 89 now for whatever reason Monterey works with either 7.4 or 7.5 versions.

Thanks for the page number and your continued updating of opencore efi for us. I'll install Monterey now.

 

[MikiBroki]

Its from OpenCore, if you boot from the Windows Boot Manager that should resolve that.

Thing is I obtained the message from other computer after I started Windows from the NUC using Windows Boot Manager (with the Big Sur external disk disconnected).

In any case, I am not concerned with the message itself, but with other possible effects in terms of security that it may have. I will do a start repair from windows and see.

 

[Leesureone]

Thing is I obtained the message from other computer after I started Windows from the NUC using Windows Boot Manager (with the Big Sur external disk disconnected).

In any case, I am not concerned with the message itself, but with other possible effects in terms of security that it may have. I will do a start repair from windows and see.

In your config.plist under Platform/Generic doe you have advise features turned on or off? If it is on turn it off and try again or try resetting the NVRAM and then booting through Windows Boot Manager.

 

[MikiBroki]

In your config.plist under Platform/Generic doe you have advise features turned on or off? If it is on turn it off and try again or try resetting the NVRAM and then booting through Windows Boot Manager.

Yes, It's off and I have resetting NVRAM, but same occurs

EDIT: after trying many times and started session in my microsoft account, it's shows like a nuc again.

 

[cyonix]

Yes, the device properties might need to be changed but without the device I wouldn't be able to. I could suggest different ID's using Hackintool but instead I would recommend you follow the Dortania suggestions here. Other changes may also be necessary but again the guide should be able to help you.

Desktop Kaby Lake | OpenCore Install Guide

I managed to get it running on Monterey 12.0.1

NUC8i3BELS with Intel 8140u cpu.

AAPL,ig-platform-id: 00001659
device-id: 16590000

 

[greg-g]

I am using the excellent OpenCore Nuc8i7OC7.5 build on my 8i7BEH NUC posted by @Leesureone. My OS is: BigSur 11.6.1. Everything is working very well with one interesting exception. When I disable System Integrity Protection (SIP) in the config.plist, it does indeed disable SIP BUT the sound settings are changed and I can no longer use the headphone outputs (or any native HW outputs). Basically this kills sound for me. I have this down to a 1 character change in config.plist in the line below csr-active-config (see below). If the data is AAAAAA== then everything works fine but SIP is on (which is the default in the build). Sound outputs all good. If I disable SIP (as shown below), then sure enough SIP is disabled but then the HW sound output options go away.

For clarity the AAAAAA== is the text output of the Config.plist. The real hex values entered are shown below and correspond to values in opencore documentation: https://dortania.github.io/OpenCore...oting/extended/post-issues.html#disabling-sip

AAAAAA== Corresponds to 00000000 Hex
AwAAAA== Corresponds to FF0F0000 HEX

I have also tried HEX 03000000

I want SIP off because I would like to use a wifi driver that only works when SIP is disabled. Namely this one: https://github.com/chris1111/Wireless-USB-OC-Big-Sur-Adapter

All would be smooth sailing if this odd thing was not going on with sound. This has nothing to do with that wifi driver. This problem occurs with or without it. The issue is turning off SIP. As confirmed by many iterations and reboots. Does anybody have a clue whats going on? To me this a bit like adjusting the emergency brake and having problems with the door lock. I don't see or understand the connection between SIP and Sound ouputs?

Example text of config.plist with SIP disabled:

<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>ForceDisplayRotationInEFI</key>
<integer>0</integer>
<key>SystemAudioVolume</key>
<data>Rg==</data>
<key>boot-args</key>
<string>keepsyms=1</string>
<key>csr-active-config</key>
<data>AwAAAA==</data>
<key>prev-lang:kbd</key>
<string>en-US:0</string>
<key>run-efi-updater</key>
<string>No</string>
</dict>

Note that I reset NVRAM manually on the boatloader to minimize the config.plist changes and narrow down the root cause.

 

[Leesureone]

I am using the excellent OpenCor Nuc8i7OC7.5 build on my 8i7BEH NUC posted by #leesureone (BigSur 11.6.1). Everything is working very well with one interesting exception. When I disable SIP in the config.plist, it does indeed disable SIP BUT the sound settings are changed and I can no longer use the headphone outputs (or any native HW outputs). Basically this kills sound for me. I have this down to a 1 character change in config.plist in the line below csr-active-config (see below). If the data is AAAAAA== then everything works fine but SIP is on (which is the default in the build). Sound outputs all good. If I disable SIP (as shown below), then sure enough SIP is disabled but then the HW sound output options go away.

For clarity the AAAAAA== is the text output of the Config.plist. The real hex values entered are shown below and correspond to values in opencore documentation: https://dortania.github.io/OpenCore...oting/extended/post-issues.html#disabling-sip

AAAAAA== Corresponds to 00000000 Hex
AwAAAA== Corresponds to FF0F0000 HEX

I have also tried HEX 03000000

I want SIP off because I would like to use a wifi driver that only works when SIP is disabled. Namely this one: https://github.com/chris1111/Wireless-USB-OC-Big-Sur-Adapter

All would be smooth sailing if this odd thing was not going on with sound. This has nothing to do with that wifi driver. This problem occurs with or without it. The issue is turning off SIP. As confirmed by many iterations and reboots. Does anybody have a clue whats going on?

Example text of config.plist with SIP disabled:

<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>ForceDisplayRotationInEFI</key>
<integer>0</integer>
<key>SystemAudioVolume</key>
<data>Rg==</data>
<key>boot-args</key>
<string>keepsyms=1</string>
<key>csr-active-config</key>
<data>AwAAAA==</data>
<key>prev-lang:kbd</key>
<string>en-US:0</string>
<key>run-efi-updater</key>
<string>No</string>
</dict>

I'm not sure I can help you with your SIP related sound issues. My recommendation would always be to run with it enabled, not disabled unless it is a total deal breaker. Any reason you can't use the onboard intel wireless/ bluetooth my EFI is configured to use? You wouldn't need USB Wifi and could run with SIP turned on.

 

[greg-g]

I'm not sure I can help you with your SIP related sound issues. My recommendation would always be to run with it enabled, not disabled unless it is a total deal breaker. Any reason you can't use the onboard intel wireless/ bluetooth my EFI is configured to use? You wouldn't need USB Wifi and could run with SIP turned on.

Well, you pose a great question! Back in the day (2 years ago) when I first built this Hackintosh with Clover/Majove those internal Intel WiFi and BT were useless with Hackintosh technology as it was. Furthermore, I put the system in a metal/fanless case (heat sink case by Akasa) and the recommendation then was to just pull the antennas because A) The metal case blocked the signal and B) Drivers did not work back then anyway. Since then I was using USB BT and Wifi and even turned those off in the Bios. I guess I need to go back and see how to rig those antennas (or appropriate replacements) and try to put Humpty Dumpty together again. I still have the original antennas.

Just curious did you get AirDrop working? That was always the miracle and I admit I have had my head in the sand for 2 years. I am just now updating everything. As I understood it the only way to pull that off is to rejigger the hardware with a special hardware mod. Anyway, you have performed one miracle, I might as well see if you performed two! Thanks!

PS In your response regarding SIP you asked does it need to be turned off? The answer is Yes. To use that driver SIP needs to be turned off. However, you have given me another better way to skin this cat.

 

[Leesureone]

Well, you pose a great question! Back in the day (2 years ago) when I first built this Hackintosh with Clover/Majove those internal Intel WiFi and BT were useless with Hackintosh technology as it was. Furthermore, I put the system in a metal/fanless case (heat sink case by Akasa) and the recommendation then was to just pull the antennas because A) The metal case blocked the signal and B) Drivers did not work back then anyway. Since then I was using USB BT and Wifi and even turned those off in the Bios. I guess I need to go back and see how to rig those antennas (or appropriate replacements) and try to put Humpty Dumpty together again. I still have the original antennas.

Just curious did you get AirDrop working? That was always the miracle and I admit I have had my head in the sand for 2 years. I am just now updating everything. As I understood it the only way to pull that off is to rejigger the hardware with a special hardware mod. Anyway, you have performed one miracle, I might as well see if you performed two! Thanks!

PS In your response regarding SIP you asked does it need to be turned off? The answer is Yes. To use that driver SIP needs to be turned off. However, you have given me another better way to skin this cat.

I don't think Airdrop works, you'd need a natively recognized wireless adapter/ Truthfully all I did was follow the developments of the OpenIntelWireless gang over at Github (like so many of us). Hopefully that Cat is skinned!

 

[Feartech]

I don't think Airdrop works, you'd need a natively recognized wireless adapter/ Truthfully all I did was follow the developments of the OpenIntelWireless gang over at Github (like so many of us). Hopefully that Cat is skinned!

yes, you will need a compatible card for airdrop