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

[eichi]

has anyone tried to get Big Sur public beta to work with the clover files from @Leesureone ?

 

[Drfrag]

has anyone tried to get Big Sur public beta to work with the clover files from @Leesureone ?

Yes, NUC8OC6.0EFI.zip worked just fine for me. Thanks @Leesureone !!

 

[markfultonncl]

I was able to get my NUC8i7BEH running Catalina using the latest OC EFI zip on page 90. It's also working on the latest BIOS as well, so its good to see that BIOS compatibility issues seem to be a thing of the past.
Thanks to @Leesureone this was a walk in the park compared to the last time I dabbled in hackintosh.

That said, the SD card reader doesn't seem to work. Is there a way to get this working? Based on previous posts there seems to be mixed results on this.

Another factoid: if I boot my NUC with an SD card inserted into the card reader, it panics:

panic(cpu 0 caller 0xffffff80072471ec): "Double fault at 0xffffff7f87b43082, registers:\n" "CR0: 0x000000008001003b, CR2: 0xffffff83b68c7ff8, CR3: 0x000000000c5e6000, CR4: 0x00000000003626e0\n" "RAX: 0xffffff7f87b4307e, RBX: 0xffffff8045319800, RCX: 0x0000000000000040, RDX: 0xffffff83b68c8020\n" "RSP: 0xffffff83b68c8000, RBP: 0xffffff83b68c8000, RSI: 0xffffff8045319800, RDI: 0xffffff8045198140\n" "R8:  0xffffff80452c7320, R9:  0x0000000000000005, R10: 0xaaaaaaaaaaaaaaab, R11: 0x0000000000000002\n" "R12: 0xffffff8045319800, R13: 0x0000000045319801, R14: 0xffffff8045198140, R15: 0xffffff8045198140\n" "RFL: 0x0000000000010282, RIP: 0xffffff7f87b43082, CS:  0x0000000000000008, SS:  0x0000000000000000\n" "Error code: 0x0000000000000000\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.1/osfmk/i386/trap_native.c:168
Backtrace (CPU 0), Frame : Return Address
0xffffff8006f51310 : 0xffffff800711a65d mach_kernel : _handle_debugger_trap + 0x49d
0xffffff8006f51360 : 0xffffff8007254a75 mach_kernel : _kdp_i386_trap + 0x155
0xffffff8006f513a0 : 0xffffff80072465fe mach_kernel : _kernel_trap + 0x4ee
0xffffff8006f513f0 : 0xffffff80070c0a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8006f51410 : 0xffffff8007119d27 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff8006f51510 : 0xffffff800711a117 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff8006f51560 : 0xffffff80078c1abc mach_kernel : _panic + 0x54
0xffffff8006f515d0 : 0xffffff80072471ec mach_kernel : _sync_iss_to_iks_unconditionally + 0x13c
0xffffff8006f516c0 : 0xffffff80078c1c08 mach_kernel : _panic_double_fault64 + 0x27
0xffffff8006f516d0 : 0xffffff80070c12bf mach_kernel : _hndl_double_fault + 0xf
0xffffff83b68c8000 : 0xffffff7f87b430a8 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice18matchPropertyTableEP12OSDictionary + 0x2a
0xffffff83b68c8050 : 0xffffff7f87b430a8 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice18matchPropertyTableEP12OSDictionary + 0x2a
0xffffff83b68c80a0 : 0xffffff7f87b430a8 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice18matchPropertyTableEP12OSDictionary + 0x2a
0xffffff83b68c80f0 : 0xffffff7f87b430a8 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice18matchPropertyTableEP12OSDictionary + 0x2a

I will have a go at debugging this.

So I'm not sure why this is panicking. I validated that Sinetek-rtsx.kext is in my Kexts folder on the EFI partition, and within its Info.plist the correct PCI device is represented with what I see reported by Hackintool for the card reader in the NUC8i7BEH. (Vendor: 0x10EC, Device: 0x522A; and IOPCIMatch includes 0x522A10EC). Also made sure the kext is enabled in conflg.plist for OC.

 

[Leesureone]

The develo

So I'm not sure why this is panicking. I validated that Sinetek-rtsx.kext is in my Kexts folder on the EFI partition, and within its Info.plist the correct PCI device is represented with what I see reported by Hackintool for the card reader in the NUC8i7BEH. (Vendor: 0x10EC, Device: 0x522A; and IOPCIMatch includes 0x522A10EC). Also made sure the kext is enabled in conflg.plist for OC.

The developers of opencore suggest forgoing use of card readers, finger print scanners and other similar devices. If you really need to access card memory there are some awesome USB versions out there for cheap.

 

[markfultonncl]

The develo

The developers of opencore suggest forgoing use of card readers, finger print scanners and other similar devices. If you really need to access card memory there are some awesome USB versions out there for cheap.

Just got this working by upgrading Sinetek-rtsx.kext to the latest (a simple replacement of the kext in the EFI partition was all that was needed). From the thread the devs moved over from the using the freebsd driver as a base in favor of the superior Linux driver (in terms of compatibility).

Full read+write access, and no more kernel panics with an inserted SD card on boot.

Kext link (in case its worth updating the EFI zips): https://github.com/cholonam/Sinetek-rtsx/releases/tag/Releases/v2.3

 

[mitoda]

Do you guys know how to clear the NUC off open core completely? in recently installed windows and on hardware it says acidanthera, windows won't load drivers for wifi, BT on the NUC natively.

 

[Leesureone]

Do you guys know how to clear the NUC off open core completely? in recently installed windows and on hardware it says acidanthera, windows won't load drivers for wifi, BT on the NUC natively.

If you have windows installed on a seperate drive boot from that drive. Select "windows boot manager" in the bios under the boot tab

 

[mitoda]

I actually don’t have have a windows boot manager, it’s very odd I wonder if everything got installed under the open core environment that’s why it’s showing as acidanthera hardware may have to re install windows again. It’s installed on a separate drive.

 

[Leesureone]

I actually don’t have have a windows boot manager, it’s very odd I wonder if everything got installed under the open core environment that’s why it’s showing as acidanthera hardware may have to re install windows again. It’s installed on a separate drive.

Thats happened to me before. It was there and then it wasn’t. I think there’s a way to restore the boot manager files without reinstalling if thats not a good option for you.

 

[markfultonncl]

Do you guys know how to clear the NUC off open core completely? in recently installed windows and on hardware it says acidanthera, windows won't load drivers for wifi, BT on the NUC natively.

I use OC with Windows and don't have any issues. What I found was that the Intel all in one driver utility doesn't work as it fails hardware detection, but if you download and install the drivers separately that should work.