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

[Leesureone]

Have anyone here had problem with CMOS checksum after updating Mac OS? I had this after updating to Catalina 10.15.6. Maybe it has anything to do with NVRAM. Don't know. I am using Clover EFI.

You get a bios error?

 

[Drfrag]

Latest commit to itlwm.kext for those using Intel WiFi.

 

[Drfrag]

You get a bios error?

No, just a message when first booting and needing to clear Nvram.

 

[Leesureone]

No, just a message when first booting and needing to clear Nvram.

There are a few reports of the same thing in other threads. One suggestion was to refresh the bios which apparently worked. Another was here but they also ended up refreshing the bios as well.

<< Solved >> - Catalina 10.15.4 Supplemental Update > Getting CMOS Checksum Errors on Every Boot

Getting CMOS Checksum errors on every boot after updating from 10.15.2 to 10.15.4 on the original 2011 CustoMacMini.

www.tonymacx86.com

 

[paniniham]

Latest commit to itlwm.kext for those using Intel WiFi.


View attachment 481802

Does it work with MacOS UI, or do we still have to enter name and pass through text file?

 

[Drfrag]

There are a few reports of the same thing in other threads. One suggestion was to refresh the bios which apparently worked. Another was here but they also ended up refreshing the bios as well.

<< Solved >> - Catalina 10.15.4 Supplemental Update > Getting CMOS Checksum Errors on Every Boot

Getting CMOS Checksum errors on every boot after updating from 10.15.2 to 10.15.4 on the original 2011 CustoMacMini.

www.tonymacx86.com

Updating Clover to latest version fixed CMOS checksum erros. Latest version has OcQuirks.efi that is a modern memory fix driver and I am now using it instead of OsxAptioFix3DRV.efi.
Tere was another error with CMOS. My clock was not recorded on BIOS after reboot or shutdown and I found the problem was with SSDT-RTC0.aml. On NUC8i7BEAH we don't need to fake a RTC, because DSDT already has it set up. We only need to shutdown AWAC and the real RTC will be up and running after that.
So we need SSDT-AWAC.aml and should not use SSDT-RTC0.aml

 

[Drfrag]

Does it work with MacOS UI, or do we still have to enter name and pass through text file?

Yes it does work if you use it with HeliPort. Install it to your Application folder.

 

[Leesureone]

Updating Clover to latest version fixed CMOS checksum erros. Latest version has OcQuirks.efi that is a modern memory fix driver and I am now using it instead of OsxAptioFix3DRV.efi.
Tere was another error with CMOS. My clock was not recorded on BIOS after reboot or shutdown and I found the problem was with SSDT-RTC0.aml. On NUC8i7BEAH we don't need to fake a RTC, because DSDT already has it set up. We only need to shutdown AWAC and the real RTC will be up and running after that.
So we need SSDT-AWAC.aml and should not use SSDT-RTC0.aml

Did you mean NUC8i7BEH? Never heard of the BEAH, also never had to use OsxAptioFix3DRV.efi instead of OsxAptioFixDrv.efi let alone OCQuirks. Haven't used clover for months and months, and from what I've been hearing its had it fair share of issues. My feeling at this point is if you have to resort to using OCQuirks might as well go all in and use OpenCore.

 

[Drfrag]

Did you mean NUC8i7BEH? Never heard of the BEAH, also never had to use OsxAptioFix3DRV.efi instead of OsxAptioFixDrv.efi let alone OCQuirks. Haven't used clover for months and months, and from what I've been hearing its had it fair share of issues. My feeling at this point is if you have to resort to using OCQuirks might as well go all in and use OpenCore.

Yes. NUC8i7BEH, sorry. I was using OsxAptioFix3DRV.efi and was not having any issue until last update. I tried to use Opencore but don't know why, even using your EFI, I had kernel panic during boot. Maybe something is wrong with my BIOS configuration or version.

 

[Leesureone]

Yes. NUC8i7BEH, sorry. I was using OsxAptioFix3DRV.efi and was not having any issue until last update. I tried to use Opencore but don't know why, even using your EFI, I had kernel panic during boot. Maybe something is wrong with my BIOS configuration or version.

Hmmm. The bios settings are the same for both and I haven’t found a bios version that made a difference in quite some time. I think some other i7 users have had success, maybe some will chime in. Thanks for keeping us updated on the wireless kext development as well as your other contributions here.