X299 Big Sur Support

[dny87]

You're gonna need the latest OpenCore for Big Sur.

I‘ve got opencore 0.6.5.

 

[jaspercat5]

Use the new RestrictEvents kext and it will fix your memory configuration errors. No need to add anything to the config.plist anymore. (Make sure Custom Memory is disabled in the plist).

Note this is for MacPro7,1 SMBIOS.




Go to System Preferences > Startup Disk > Unlock and pick your macOS disk and lock the tab again, it will bless macOS to be the default OS.

If you get some type of NVRAM error, you need to fix that.

Thanks @izo1 for the pointer on the RestricEvents kext - will have a look at this when I get some time.

The changes in System preferences for boot disk selection were the standard means of setting defaults but there is something different about the NVRAM on the EVGA X299 Dark resulting in any changes made in SP not sticking.

 

[jaspercat5]

Does anyone know why Intel Power Gadget is not reporting the Power draw accurately on the X299 (temps/frequency etc. seem 0k) IPG works 'out of the box' on the Z390's I have.

 

[Loloflatsix]

Does anyone know why Intel Power Gadget is not reporting the Power draw accurately on the X299 (temps/frequency etc. seem 0k) IPG works 'out of the box' on the Z390's I have.

View attachment 504618

Specific HW sensors were developed for our X299 system, they were part of FakeSMC. kext and pluggings like CPUsensors and HWsensors or SuperIOsensors see on Github @interferenc HWsensorsX299.

At that time, we were using Clover as bootloader.

Now with OPenCore boatloader I don't know if there are specifics sensors for X299 on SMCProcessor.kext or SMCSuperIO.kext
So this should explain some restrictions with Intel Power Gadget.

It seems possible to compile with Xcode the kext "HWsensors X299" and attach them to the OC EFI, but its just my idea and i don't know if it will work and if better.

 

[jaspercat5]

Thanks for that. When I get some time I'll have a look and report back with any updates.

 

[Ellybz]

@dny87
You should not have any issues with any of the EFIs for Gigabyte X299 reported in this forum thread. they're all validated to work @100% with Big Sur. Note that during the install, if the activity led of your Hack is still blinking, it means that it's working, so be patient & let it do his thing. ( it might give you the idea it has frozen )

If you're a beginner with Open Core, I suggest you to do more readings or try the Dortania guide, it's a good way to start. The first posts by @Loloflatsix in this thread are also a "MUST" read.

Lastly, If you have tried all the Gigabyte EFIs reported by @Loloflatsix or myself in this thread, and none are working, your issue comes from somewhere else. ( Bios, GPU or hardware).

Don't forget to clean your NVRAM before the Install ( Boot picker option in OpenCore )

 

[Loloflatsix]

EFI OC 0.6.5 Asus Rampage R6EE :
- SMBIOS MacPro7,1 with CustomMemory.plist ( To adapt for other configs with appropriate USBmap.kext, DeviceProperties, Custom SSDTs ( GPU, Thunderbolt, etc...), Serial Number, SMUUID, CustomMemory.plist, etc...)

 

[jaspercat5]

EFI OC 0.6.5 Asus Rampage R6EE :
- SMBIOS MacPro7,1 with CustomMemory.plist ( To adapt for other configs with appropriate USBmap.kext, DeviceProperties, Custom SSDTs ( GPU, Thunderbolt, etc...), Serial Number, SMUUID, CustomMemory.plist, etc...)

Here is my EFi for the X299 Dark based on Opencore 0.6.5.

I had posted a detailed guide for @dny87 which actually took me a long time but unfortunately it didn't pass moderation! No idea why.

Thanks for all who helped me on this platform particularly Loloflatsix.

Good luck with your builds.

Ian

 

[jaspercat5]

sorry forgot to attach the EFI.....

Should be on page 135

 

[dny87]

thanks i will try my best,
if i get it to work i will let you know