X299 Big Sur Support

[djlild7hina]

Here is an updated BASE-EFI 0.6.5 for ASUS X299 boards. I haven't tested it yet but it should work

Some notes:

1. Recommended to use one of the latest BIOS (From Nov 2020 recent)
2. Enable 4G Encoding, Disable CSM, Disable MSR Lock
3. Config.plist
   1. Contains MacPro7,1 and iMacPro1,1 config.plist (rename SMBIOS selection to just 'config.plist' (For example 'config.plist-MacPro7,1' to 'config.plist' and delete other 'config.plist...')
      1. MacPro7,1 - Added RestricEvents.kext to disable the MacProMemoryNotification Error
   2. Updated to CPUTscSync.kext so no need to manually specify amount of threads
   3. agdpmod=pikera is Enabled in boot-args for NAVI GPUs
   4. USBInjectAll and XhciPortLimit is enabled.

 

[rustEswan]

I've got to ask this because I see all the time things like "I use MacPro7,1 because it most closely matches my hardware" or "I don't use iMacPro1,1 because its 2 years old" when referring to an X299 build.

I always understood it was best to pick an SMBIOS of a machine that most closely matches your hardware and CPU architecture, and well, all X299 builds, regardless of 7th, 9th or 10th gen CPU's are basically based on Skylake-X. Even 10th gen CascadeLake-X is much closer to Skylake-X than it is CascadeLake-W in the MacPro, despite its name, and we have 4 vs 6 channel amongst other things which is definitely most closely matching the 2017 iMac Pro - should we not be primarily using iMacPro1,1 with X299?

I mean I'm no expert on what MacOS actually does with SMBIOS and how it affects performance, stability hardware support etc, this is a genuine question of curiosity as it just doesn't seem to make sense to me based on my historical understanding of best-practice (if there is such a thing with a Hackintosh).

Actually what I'd really love is if someone could explain exactly how and what MacOS does with the SMBIOS variable - that would be super interesting if anyone knows!

 

[ol2003]

Here is an updated BASE-EFI 0.6.5 for ASUS X299 boards. I haven't tested it yet but it should work

Some notes:

1. Recommended to use one of the latest BIOS (From Nov 2020 recent)
2. Enable 4G Encoding, Disable CSM, Disable MSR Lock
3. Config.plist
   1. MacPro7,1 SMBIOS
   2. Edit TSCAdjustReset.kext with (# of Threads - 1) Currently set to 35 for 7980XE, 9980XE, 10980XE
   3. Added RestricEvents.kext to disable the MacProMemoryNotification Error
   4. agdpmod=pikera is Enabled in boot-args
   5. USBInjectAll and XhciPortLimit is enabled.

a small note to 3.2: you can also change to "CpuTscSync.kext", so you don't need to edit anything, cause the kext knows your cpu and do the things o its own... (you will find it on acidanthera). Works for me perfect.

 

[Loloflatsix]

a small note to 3.2: you can also change to "CpuTscSync.kext", so you don't need to edit anything, cause the kext knows your cpu and do the things o its own... (you will find it on acidanthera). Works for me perfect.

We have already discussed this point here : #1,143

The TSCAdjustReset.kext more specific four our X299 platform see on Github TSCAdjustReset.
Provided by interferenc : "On x299 and Skylake-X, the CPU has an invariant TSC, meaning it will NOT get out of sync. The problem with x299/Sklylake-X is that something (probably the BIOS, or even the CPU itself) writes to the TSC of some of the cores, and thus the TSCs are not in sync upon cold or warm boot. The IA32_TSC_ADJUST MSR holds the value of how much each core was adjusted. Writing 0 this register rolls back any previous changes. So TSCAdjustReset.kext does exactly that. It can even be unloaded after it did its job."

But if your choice does the trick ... you are free with it.

 

[djlild7hina]

a small note to 3.2: you can also change to "CpuTscSync.kext", so you don't need to edit anything, cause the kext knows your cpu and do the things o its own... (you will find it on acidanthera). Works for me perfect.

I've always been used to using TSCAdjustReset from kgp's days but updated the EFI for CpuTscSync.

 

[pieropontra]

I've always been used to using TSCAdjustReset from kgp's days but updated the EFI for CpuTscSync.

And how it goes?

 

[djlild7hina]

And how it goes?

So far I haven't notice any differences. But like @Loloflatsix mentioned, this was discussed in previous posts

X299 Big Sur Support

Okay ... it's little to complicated for me. Are we sure that "CpuTscSync.kext" doesn't do the same thing ? Or How can we verified that "CpuTscSync.kext" isn't working properly or as "TSCAdjustReset.kext" is ? Thanks I wouldn't waste my time with that (humor on :)) and simply use...

www.tonymacx86.com

1,143 to 1,148

 

[tucoboy]

Hey everyone, just updated to the "newest" 11.2 (full version) today and after restarting it a couple of times, everything works still. Again, no problems at all. Still having issues with Kensington TrackballWorks app that doesn't work at all. Just had to get SteerMouse (for $20). Oh well. At least everything else is kickin' it!

 

[oli.mathieu]

I've always been used to using TSCAdjustReset from kgp's days but updated the EFI for CpuTscSync.

Same for me,
it works

 

[Loloflatsix]

So far I haven't notice any differences. But like @Loloflatsix mentioned, this was discussed in previous posts

X299 Big Sur Support

Okay ... it's little to complicated for me. Are we sure that "CpuTscSync.kext" doesn't do the same thing ? Or How can we verified that "CpuTscSync.kext" isn't working properly or as "TSCAdjustReset.kext" is ? Thanks I wouldn't waste my time with that (humor on :)) and simply use...

www.tonymacx86.com

1,143 to 1,148

Same for me,
it works

Of course CpuTscSync.kext works : it's the rebranded and actualised version of VoodooTSCSync.kext by the Acidanthera team.
TSCAdjustReset.kext is also a version of VoodooTSCSync.kext with appropriate adjustments for X299 processors.
At the beginning I tried RehabMan's VoodooTSCSync.kext and It worked fine too.
I'm old school and like the "medocs" ( Google it, it's French word) I prefer the Magic Potion