Contribute
Register

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

I am using monterey. Is the link you provided a github link? I got a 404 when I tried it. It may take me a while before I can try any of these options you mentioned, but I'll give it a try when I get a chance.

I didn't try Hackintool or The Port Mapping tool before. Are those still options that I can try while running monterey? I'm hoping to not have to go through the process of swapping out the nvme drive to try Catalina or Windows.

Thanks again
The link I provided was to ****** which has a link to Github which as I explained was appeared to be down for the time being. You can try whatever method you like but if the headers don't show up then you can't map the ports. You can also try IORegistryExplorer app to see if the show but I've tried it with the same negative result.

You may also may be able to use an external thunderbolt enclosure and install to it if changing out the internal drives seems like a hassle otherwise I don't know how to help you.
 
Last edited:
Or try this version of 7.9, you’d have to add back the NVRAM option again
have not tried the new version...strangely enought after two or three day the audio issue resolved its self...makes no sense but all is good.

and in regards to video from the thunderbolt port, I see there are a number of reports of issues with external video/usb-c video with 12.3. I dont know I can fairly assume this is a OC issue now that I see that. but will keep an eye peeled
 
have not tried the new version...strangely enought after two or three day the audio issue resolved its self...makes no sense but all is good.

and in regards to video from the thunderbolt port, I see there are a number of reports of issues with external video/usb-c video with 12.3. I dont know I can fairly assume this is a OC issue now that I see that. but will keep an eye peeled
Maybe you can post a link to the Thunderbolt Display issues you are talking about in 12.3. I know users with newer AMD cards took a hit with that update but that affected even real Mac users as well. I rolled back to 12.2 and am waiting for a fix from Apple.
 
Maybe you can post a link to the Thunderbolt Display issues you are talking about in 12.3. I know users with newer AMD cards took a hit with that update but that affected even real Mac users as well. I rolled back to 12.2 and am waiting for a fix from Apple.
 
I did a fresh install of Monterey 12.3 via OC 7.6 (the zip from Leesureone) on my NUC8i7BEH from a blank partition after the random lockups I was experiencing. So far things are working well, except for what I assume are strange power management issues.
Sleep/Wake works fine. But some mornings after putting the NUC to sleep the power LED is on and the NUC is totally unresponsive - no video, no input, no ping, nothing. I have to do a hard power reset to recover it.
Any suggestions or logs I could look at? FWIW I had the same issue under Monterey 12.2 but not under Big Sur. Thanks all.

Edit:

macOS called out a kernel panic that seems to be a conflict from the ethernet kext (com.insanelymac.IntelMausiEthernet). Seems like a good place to start troubleshooting. Curious if others have seen similar KPs on their Monterey based NUC8?

panic(cpu 3 caller 0xffffff8009dd38e3): Kernel trap at 0xffffff800de677ad, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffffd03b586008, CR3: 0x000000000ffea000, CR4: 0x00000000003626e0 RAX: 0x0000000000000000, RBX: 0xffffffa0437f5000, RCX: 0xffffffd061de3e70, RDX: 0x0000000000000100 RSP: 0xffffffd061de3cc0, RBP: 0xffffffd061de3d40, RSI: 0xffffff9044020000, RDI: 0xffffffa0437f5000 R8: 0x0000000000000000, R9: 0xffffff80436ec6f0, R10: 0xffffffd03b53ef90, R11: 0xffffff950daa0000 R12: 0xffffffa0437f5000, R13: 0x0000000000000000, R14: 0xffffffd03b586000, R15: 0x0000000000000000 RFL: 0x0000000000010246, RIP: 0xffffff800de677ad, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffffd03b586008, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1 Panicked task 0xffffff951020f670: 217 threads: pid 0: kernel_task Backtrace (CPU 3), panicked thread: 0xffffff950daa0000, Frame : Return Address 0xffffffd061de3670 : 0xffffff8009c83e1d mach_kernel : _handle_debugger_trap + 0x41d 0xffffffd061de36c0 : 0xffffff8009de3ca6 mach_kernel : _kdp_i386_trap + 0x116 0xffffffd061de3700 : 0xffffff8009dd34fd mach_kernel : _kernel_trap + 0x51d 0xffffffd061de3750 : 0xffffff8009c23a60 mach_kernel : _return_from_trap + 0xe0 0xffffffd061de3770 : 0xffffff8009c841ed mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffd061de3890 : 0xffffff8009c839a6 mach_kernel : _panic_trap_to_debugger + 0x2b6 0xffffffd061de38f0 : 0xffffff800a5164af mach_kernel : _panic + 0x84 0xffffffd061de39e0 : 0xffffff8009dd38e3 mach_kernel : _sync_iss_to_iks + 0x2c3 0xffffffd061de3b60 : 0xffffff8009dd35d2 mach_kernel : _kernel_trap + 0x5f2 0xffffffd061de3bb0 : 0xffffff8009c23a60 mach_kernel : _return_from_trap + 0xe0 0xffffffd061de3bd0 : 0xffffff800de677ad com.insanelymac.IntelMausiEthernet : __ZN10IntelMausi11rxInterruptEP18IONetworkInterfacejP11IOMbufQueuePv + 0x3b 0xffffffd061de3d40 : 0xffffff800de68164 com.insanelymac.IntelMausiEthernet : __ZN10IntelMausi16pollInputPacketsEP18IONetworkInterfacejP11IOMbufQueuePv + 0xe 0xffffffd061de3d60 : 0xffffff800c575eb6 com.apple.iokit.IONetworkingFamily : __ZN19IONetworkController20executeCommandActionEP8OSObjectPvS2_S2_S2_ + 0x38 0xffffffd061de3d90 : 0xffffff800a448a54 mach_kernel : __ZN13IOCommandGate9runActionEPFiP8OSObjectPvS2_S2_S2_ES2_S2_S2_S2_ + 0xb4 0xffffffd061de3df0 : 0xffffff800c575f2e com.apple.iokit.IONetworkingFamily : __ZN19IONetworkController14executeCommandEP8OSObjectPFiPvS2_S2_S2_S2_ES2_S2_S2_S2_S2_ + 0x60 0xffffffd061de3e50 : 0xffffff800c57a2f7 com.apple.iokit.IONetworkingFamily : __ZN18IONetworkInterface19if_input_poll_gatedEP7__ifnetjjPP6__mbufS4_PjS5_ + 0xcd 0xffffffd061de3ed0 : 0xffffff800a3786db mach_kernel : _netif_rxpoll_compat_thread_func + 0x2cb 0xffffffd061de3fa0 : 0xffffff8009c2318e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IONetworkingFamily(3.4)[62888EF4-277C-35B5-B9FA-DF8008BC5D28]@0xffffff800c56b000->0xffffff800c581fff com.insanelymac.IntelMausiEthernet(2.4.1d1)[88E228F4-3264-385C-84E9-3B7F99112336]@0xffffff800de64000->0xffffff800de8afff dependency: com.apple.iokit.IONetworkingFamily(3.4)[62888EF4-277C-35B5-B9FA-DF8008BC5D28]@0xffffff800c56b000->0xffffff800c581fff dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff800c803000->0xffffff800c82efff
 
Last edited:
I did a fresh install of Monterey 12.3 via OC 7.6 (the zip from Leesureone) on my NUC8i7BEH from a blank partition after the random lockups I was experiencing. So far things are working well, except for what I assume are strange power management issues.
Sleep/Wake works fine. But some mornings after putting the NUC to sleep the power LED is on and the NUC is totally unresponsive - no video, no input, no ping, nothing. I have to do a hard power reset to recover it.
Any suggestions or logs I could look at? FWIW I had the same issue under Monterey 12.2 but not under Big Sur. Thanks all.

Edit:

macOS called out a kernel panic that seems to be a conflict from the ethernet kext (com.insanelymac.IntelMausiEthernet). Seems like a good place to start troubleshooting. Curious if others have seen similar KPs on their Monterey based NUC8?

panic(cpu 3 caller 0xffffff8009dd38e3): Kernel trap at 0xffffff800de677ad, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffffd03b586008, CR3: 0x000000000ffea000, CR4: 0x00000000003626e0 RAX: 0x0000000000000000, RBX: 0xffffffa0437f5000, RCX: 0xffffffd061de3e70, RDX: 0x0000000000000100 RSP: 0xffffffd061de3cc0, RBP: 0xffffffd061de3d40, RSI: 0xffffff9044020000, RDI: 0xffffffa0437f5000 R8: 0x0000000000000000, R9: 0xffffff80436ec6f0, R10: 0xffffffd03b53ef90, R11: 0xffffff950daa0000 R12: 0xffffffa0437f5000, R13: 0x0000000000000000, R14: 0xffffffd03b586000, R15: 0x0000000000000000 RFL: 0x0000000000010246, RIP: 0xffffff800de677ad, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffffd03b586008, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1 Panicked task 0xffffff951020f670: 217 threads: pid 0: kernel_task Backtrace (CPU 3), panicked thread: 0xffffff950daa0000, Frame : Return Address 0xffffffd061de3670 : 0xffffff8009c83e1d mach_kernel : _handle_debugger_trap + 0x41d 0xffffffd061de36c0 : 0xffffff8009de3ca6 mach_kernel : _kdp_i386_trap + 0x116 0xffffffd061de3700 : 0xffffff8009dd34fd mach_kernel : _kernel_trap + 0x51d 0xffffffd061de3750 : 0xffffff8009c23a60 mach_kernel : _return_from_trap + 0xe0 0xffffffd061de3770 : 0xffffff8009c841ed mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffd061de3890 : 0xffffff8009c839a6 mach_kernel : _panic_trap_to_debugger + 0x2b6 0xffffffd061de38f0 : 0xffffff800a5164af mach_kernel : _panic + 0x84 0xffffffd061de39e0 : 0xffffff8009dd38e3 mach_kernel : _sync_iss_to_iks + 0x2c3 0xffffffd061de3b60 : 0xffffff8009dd35d2 mach_kernel : _kernel_trap + 0x5f2 0xffffffd061de3bb0 : 0xffffff8009c23a60 mach_kernel : _return_from_trap + 0xe0 0xffffffd061de3bd0 : 0xffffff800de677ad com.insanelymac.IntelMausiEthernet : __ZN10IntelMausi11rxInterruptEP18IONetworkInterfacejP11IOMbufQueuePv + 0x3b 0xffffffd061de3d40 : 0xffffff800de68164 com.insanelymac.IntelMausiEthernet : __ZN10IntelMausi16pollInputPacketsEP18IONetworkInterfacejP11IOMbufQueuePv + 0xe 0xffffffd061de3d60 : 0xffffff800c575eb6 com.apple.iokit.IONetworkingFamily : __ZN19IONetworkController20executeCommandActionEP8OSObjectPvS2_S2_S2_ + 0x38 0xffffffd061de3d90 : 0xffffff800a448a54 mach_kernel : __ZN13IOCommandGate9runActionEPFiP8OSObjectPvS2_S2_S2_ES2_S2_S2_S2_ + 0xb4 0xffffffd061de3df0 : 0xffffff800c575f2e com.apple.iokit.IONetworkingFamily : __ZN19IONetworkController14executeCommandEP8OSObjectPFiPvS2_S2_S2_S2_ES2_S2_S2_S2_S2_ + 0x60 0xffffffd061de3e50 : 0xffffff800c57a2f7 com.apple.iokit.IONetworkingFamily : __ZN18IONetworkInterface19if_input_poll_gatedEP7__ifnetjjPP6__mbufS4_PjS5_ + 0xcd 0xffffffd061de3ed0 : 0xffffff800a3786db mach_kernel : _netif_rxpoll_compat_thread_func + 0x2cb 0xffffffd061de3fa0 : 0xffffff8009c2318e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IONetworkingFamily(3.4)[62888EF4-277C-35B5-B9FA-DF8008BC5D28]@0xffffff800c56b000->0xffffff800c581fff com.insanelymac.IntelMausiEthernet(2.4.1d1)[88E228F4-3264-385C-84E9-3B7F99112336]@0xffffff800de64000->0xffffff800de8afff dependency: com.apple.iokit.IONetworkingFamily(3.4)[62888EF4-277C-35B5-B9FA-DF8008BC5D28]@0xffffff800c56b000->0xffffff800c581fff dependency: com.apple.iokit.IOPCIFamily(2.9)[03565C8B-2960-3B32-92FD-E6E86917FE61]@0xffffff800c803000->0xffffff800c82efff
Its never been mentioned here before, besides the kernel panic, the behavior you describe sounds more like a USB port mapping error. What works for me in my upload may need to be changed to work for you. It gets a little more complicated to do after Catalina. I found that Monterey broke some of the port mapping I thought was fine because it had worked in Big Sur.
 
Its never been mentioned here before, besides the kernel panic, the behavior you describe sounds more like a USB port mapping error. What works for me in my upload may need to be changed to work for you. It gets a little more complicated to do after Catalina. I found that Monterey broke some of the port mapping I thought was fine because it had worked in Big Sur.

Thanks, a google showed that this KP is a known issue after an OS upgrade: https://github.com/Mieze/IntelMausiEthernet/issues/21

After cleaning the caches I haven't seen any further occurrences (fingers crossed). USB-wise all ports seem to report properly and recognize devices without issue.
 
Last edited:
Hello, did anyone try to use Sidecar on a Nuc8i5? So far I do not have the symbol even. I tried the latest EFI folder by @Leesureone but it did not change anything. The "idiots guide to Lilu" is helpful but I might have missed something in my Bios setup aswell. Good to know if someone can use this function. I use OpenCore 7.7 and latest macOS. Perhaps @Leesureone have the answer?
 
Last edited:
Hello, did anyone try to use Sidecar on a Nuc8i5? So far I do not have the symbol even. I tried the latest EFI folder by @Leesureone but it did not change anything. The "idiots guide to Lilu" is helpful but I might have missed something in my Bios setup aswell. Good to know if someone can use this function. I use OpenCore 7.7 and latest macOS. Perhaps @Leesureone have the answer?
There are lots of issues trying to get SideCar running on a hackintosh. You can try this, I haven't yet but it seems promising.

 
Back
Top