X299 Big Sur Support

[P1LGRIM]

Interestingly on this board it simply won't boot past the picker if the NPCI=0x2000 argument is not present.

Boot arguments are case sensitive, NPCI=0x2000 is nonsense and will have no effect.
It should be npci=0x2000 (or npci=0x3000).

 

[jaspercat5]

Boot arguments are case sensitive, NPCI=0x2000 is nonsense and will have no effect. It should be npci=0x2000 (or npci=0x3000).

Of course, just a typo as you’ll see from my config.plist.

I’ll nip back and edit it as we’re supposed to be helping, not misleading, folks on this platform.

 

[pieropontra]

Thank you for your feedback @pieropontra,
1. Prolly will when I get home today... and see what happens...
2. So, I have used UEFI and bootstrap, and have disabled traditional BIOS selection, Ideally I'd move the MS EFI somewhere else, just don't know how.
3. I've already logged into my AppleID account and it (Apple) knows about this machine. This new build replaced a failed 2009 MacPro5,1 firmware from 4,1. Not sure if I log out of my Apple ID and try iMacPro1,1 and see what happens, testing performance does give you a clue to if things are working right...
4. agree
5. I've tinkered with it last night, but I plug things in and the thumb drive mounts the volume, but is invisible to Hackintool, so more to come on that oddity... prolly remove USBInjectAll.kext and see what shows up...

2 Just use the bios to choose which OS to boot and delete MS folder in OC EFI
3 I've switched smbios many times, it will simply show as a new device in iCloud, just log out from the old one

 

[djlild7hina]

Unable to install BS on Asus Rampage VI Extreme using OC.
I created the USB following the dortania guide for the Skylake-x.
USB boots and installer loads successfully.
But after selecting the destination device for the OS install. The screen closes and went back to installer landing page.

My rig configuration is following:
MB: Asus Rampage Extreme IV
Bios: Currently 3105. (Altough I also tested with 2002 and 3600. But faced same issue).
CPU: 7940x
SSD (to install BS): Transcend 250 GB
GPU: Vega 64 (in first PCI-e slot)
Ram: Corsair Dominator 16x4
Casing: Corsair 1000D

I used both USB-C and USB 3 flash devices to install the BS. But same issue.
Even created the Catalina installer with OC. But faced the same issue.

Bios configuration is same as mentioned in the kgp mojave guide. (Except TB3 is disabled and 4G encoding is enabled).

Here is my EFI folder.

Any help?

Try this with BIOS 3201 or 3301. Make sure Above 4G Encoding is Enabled and MSR lock is Disabled in the BIOS. Also I copied your serial from your EFI folder but I would use a new serial.

 

[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?