ASUS X99 Boards - Big Sur (Not Compatible)

[hellowe]

@hellowe I have read other people do it, but I personally wouldn't do it. If I was in your place, I would clean install on a separate SSD and test any functionality I need, then move all my data over once I am satisfied. It's the longer route but since we have hackintoshes, I'd rather be safe than sorry and lose all my data. I have a real Mac mini and that one is not even behaving properly after I upgraded to Monterey lol...

@xsiborg definitely agree your suggestion, and I think I will take your approach to test it firstly.

 

[ozamal]

Hi all

I got my X99 Asus deluxe II with a 6950x 64gb RAM, RX Vega 64 LC, NVMe boot drive all working with full DSDT and SSDT implementation. Everything works including thunderbolt hot swap SSDT workaround that was used by KGP on previous built. With this EFI a lot of the KGP X99 SSDTs can be used. Like the Vega 64 and the thunderbolt PCIe card for example.

My motherboard has a modified bios the register and nvram unlocked.

One thing though is that I cannot update to 11.6. It goes through the whole install and then once it boots back up into the OS i get the "some updates could not be installed" notification and I'm stuck at 11.2.3

I've got my USB ports mapped with a Kext and USBlimit set to false in the config file... Any idea how I could get the update working?

 

[ozamal]

Hi all

I got my X99 Asus deluxe II with a 6950x 64gb RAM, RX Vega 64 LC, NVMe boot drive all working with full DSDT and SSDT implementation. Everything works including thunderbolt hot swap SSDT workaround that was used by KGP on previous built. With this EFI a lot of the KGP X99 SSDTs can be used. Like the Vega 64 and the thunderbolt PCIe card for example.

My motherboard has a modified bios the register and nvram unlocked.

One thing though is that I cannot update to 11.6. It goes through the whole install and then once it boots back up into the OS i get the "some updates could not be installed" notification and I'm stuck at 11.2.3

I've got my USB ports mapped with a Kext and USBlimit set to false in the config file... Any idea how I could get the update working?

Managed to fix the issues. USB mapping was the problem. Re did my usb map and then could update to 11.6.1 no problem

 

[The Veterant]

Managed to fix the issues. USB mapping was the problem. Re did my usb map and then could update to 11.6.1 no problem

Christmas in the making:

Here is my EFI working 100% on BigSur and Monterey my CPU its a Xeon e5 2696v4 you have to do nothing maybe don't know but I will advice to try it first it has a coustome DSDT for my system since we have the same vega I dont see any reason not to work, also serial and MLB has to input your self one cause mine its private also on bootFlags dont touch anything untill you try it first and when you at the PICKER screen hit the button to clear NVRAM twice then do what you need it to do. Now if anything works well for you I need a trade in return, and that its the 2101 bios mod of yours also does it has the latest microcode for XEONS that you know of, enjoy and thanks if you decide to share the mod bios. That is OpenCore 0.7.6 BootLoader enjoy.

 

[Feartech]

Christmas in the making:

Here is my EFI working 100% on BigSur and Monterey my CPU its a Xeon e5 2696v4 you have to do nothing maybe don't know but I will advice to try it first it has a coustome DSDT for my system since we have the same vega I dont see any reason not to work, also serial and MLB has to input your self one cause mine its private also on bootFlags dont touch anything untill you try it first and when you at the PICKER screen hit the button to clear NVRAM twice then do what you need it to do. Now if anything works well for you I need a trade in return, and that its the 2101 bios mod of yours also does it has the latest microcode for XEONS that you know of, enjoy and thanks if you decide to share the mod bios. That is OpenCore 0.7.6 BootLoader enjoy.

shouldn't use a DSDT.aml in opencore, also shouldn't be using a DSDT from another motherboard

 

[The Veterant]

Why is that at less explained the reasons or consequences of the implementation cause other wise the it’s been upgrading from the apps store all the way from 11.04 but thanks for your observation and recommendation.

I posted a EFI for other to try it not for other critic about it. thanks anyway for the advice

 

[Feartech]

Why is that at less explained the reasons or consequences of the implementation cause other wise the it’s been upgrading from the apps store all the way from 11.04 but thanks for your observation and recommendation.

I posted a EFI for other to try it not for other critic about it. thanks anyway for the advice

because you said:
I dont see any reason not to work

and I was explaining why it won't work

 

[dj_adam21]

Guys need your help I m stuck at PCI configuration begins BIG SUR, latest open core and unlocked bios tried a bunch of boot flags none of them work.
If anyone has any ideas please let me know
Thanks!!!

 

[jmacie]

Guys need your help I m stuck at PCI configuration begins BIG SUR, latest open core and unlocked bios tried a bunch of boot flags none of them work.
If anyone has any ideas please let me know
Thanks!!!

I was successful with stripping out all unnecessary kexts. You have both usbinjectall and usbmaps checked at the same time. I removed the usbmap kext also remove the cpufrienddataprovider and innie kext. Lilu is supposed to be the 1st kext move intelmausi down below lilu. Don't need cpufriend or cputscsync or hibernationfixup. You need to add back your personal platformID's ,you have "Unlikely" written in System UUID. Anyway try this EFI, you also have no wifi or bluetooth kexts, can't help with the limited info you have provided

 

[dj_adam21]

I was successful with stripping out all unnecessary kexts. You have both usbinjectall and usbmaps checked at the same time. I removed the usbmap kext also remove the cpufrienddataprovider and innie kext. Lilu is supposed to be the 1st kext move intelmausi down below lilu. Don't need cpufriend or cputscsync or hibernationfixup. You need to add back your personal platformID's ,you have "Unlikely" written in System UUID. Anyway try this EFI, you also have no wifi or bluetooth kexts, can't help with the limited info you have provided

Thanks for the help but unfortunately the same pci config begins