Asus X299 - Support

[Stork]

OpenCore on the X299 motherboards is discussed in this thread >

X299 - Open Core support

This thread is meant to be support/discussion for users that are experimenting/using OpenCore. Users that are using Clover please refer to the original X299 support thread. NOTE: This post will no longer be updated, please refer to new X299 Support thread and this post

www.tonymacx86.com

Let's keep this thread focused on Clover, UniBeast/MultiBeast and/or kgp's methods.

 

[lennip]

Hi there!

I'm another victim of the stupid BIOS v.3006 update here.

I had a build based on kgp's tutorial that has been working fine under Mojave for several months, but I experienced weird problems with the BIOS (v. 802) randomly showing a blank screen when accessing it. So I tried to fix it by updating the BIOS to the latest version (3006).
Now the BIOS seems to work better, but I cannot boot to Mojave anymore, neither from my M.2 SSD nor from my recovery / setup USB stick: whatever I try, it hangs after "End randomseed+++++++". Even in safe mode...

Of course after updating the BIOS I configured it again as it was before (same settings as in kgp's tutorial for the Prime Deluxe).

So nothing has changed besides the BIOS version. I understand from reading this thread that it needs to be either rolled back, or patched... Unfortunately I tried flashing it back to 802 but it did not work.

So, my question is, does anyone have a patched BIOS v.3006 for the Asus x299 Prime Deluxe II (X299D2.CAP) and the corresponding cascadelakefix.aml SSDT, and would be kind enough to share them here? Since for now I can't boot into my Mac system so I can't use UEFIPatch to do it myself.

Thank you in advance for your help!

 

[K-Onix]

Hello lennip,
Your Mobo have the USB BIOS Flashback system, so you can easily return to previous BIOS.
If you have problems with 802 you can also try with 703 or 603.
My Mobo doesn't have the USB BIOS Flashback (Asus TUF X299 Mark2). It seems to be the only Asus MB without this functionality. The manual delivered with my MB was for the Mark1 who have the USB BIOS Flashback system.
So I was sure I could roll back...

 

[lennip]

Hello lennip,
Your Mobo have the USB BIOS Flashback system, so you can easily return to previous Bios.

EDIT: Solved!!! I originally replied that I tried to flashback yesterday but failed because I wasn't sure if I had performed the flashback the correct way. I now have found out that I had not formatted the USB drive properly, which is why it didn't work. I know how to do it correctly now.

Turns out I did not even need to flash back to 802 because I finally managed to patch the BIOS v.3006 from another computer using UEFIPatch.exe for Windows. And I was able to mount and open the EFI partition of my Mojave install USB stick from my Ubuntu 18 laptop and add the cascadelakefix.aml SSDT that SC1lla provided in a previous message.
After that I was finally able to boot again to my existing Mojave build using the USB stick.

I am currently in the process of editing the EFI folder of my M2 drive so it can boot on its own, and I still have to fix a minor issue with the DisplayPort not working anymore (I had to switch to HDMI to get the signal from the video card). Otherwise, I am happy and relieved I managed to make it work again.

Thanks everyone for your help!

 

[LeleTuratti]

For all those who have problems with the boot after the BIOS update, try to use my EFI folder on a USB stick.

BEFORE:
Remember to modify TSCAdjustReset.kext according to the number of your cores, and insert it in Kext/Others
And enable the correct USB patches in KextsToPach for your system (Mojave or Catalina).

Once booted, copy the ACPI Patch into your Clover/ACPI/DSDT section and remove my EFI folder.

Let's keep this thread focused on Clover, UniBeast/MultiBeast and/or kgp's methods.

Hi @Stork! Do you know if there is any way to make sleep work on the X299 chipset?
Currently my computer goes to sleep, but at the moment of the wake it restarts and I get a panic report that blames the apple XHCI controller.
I know it's a common problem in the X299 platform, but it's unclear if there is a solution...

 

[Stork]

Hi @Stork! Do you know if there is any way to make sleep work on the X299 chipset?
Currently my computer goes to sleep, but at the moment of the wake it restarts and I get a panic report that blames the apple XHCI controller.
I know it's a common problem in the X299 platform, but it's unclear if there is a solution...

No, unfortunately. I recommend this thread and the X299 OpenCore thread for advice.

 

[K-Onix]

For all those who have problems with the boot after the BIOS update, try to use my EFI folder on a USB stick.
BEFORE:
Remember to modify TSCAdjustReset.kext according to the number of your cores, and insert it in Kext/Others
And enable the correct USB patches in KextsToPach for your system (Mojave or Catalina).

Thanks LeleTuratti for your help.
So...
- I grab your EFI and put it on an USB Stick
- Change IOCPnumber in TSCAdjustReset.kext (you have 12 cores I presume) put it in Kext/Others
- Enable 2 USB patchs for Catalina in KextsToPatch (by editing with the config.plistClover configurator)
> When I boot on this USB stick first I discover the beautiful wallpaper of your Clover menu.
Then I select my drive and get the same thing again
#LOG:EXITBS:START

I also add in config plist /boot args : -v , keepsyms=1 , debug=0x100

 

[LeleTuratti]

Thanks LeleTuratti for your help.
So...
- I grab your EFI and put it on an USB Stick
- Change IOCPnumber in TSCAdjustReset.kext (you have 12 cores I presume) put it in Kext/Others
- Enable 2 USB patchs for Catalina in KextsToPatch (by editing with the config.plistClover configurator)
> When I boot on this USB stick first I discover the beautiful wallpaper of your Clover menu.
Then I select my drive and get the same thing again
#LOG:EXITBS:START

I also add in config plist /boot args : -v , keepsyms=1 , debug=0x100

Do you have Above4GDecoding enabled on the Bios? Try to disable it.
And try to update clover to the latest version

 

[K-Onix]

Above4GDecoding is disabled, and always was on my machine.
I have update clover (with multibeast 12, I don't know another way) and now version is 5107.
Your version was 5108.
I also try with Above4GDecoding enabled.
Still same result.

 

[LeleTuratti]

Above4GDecoding is disabled, and always was on my machine.
I have update clover (with multibeast 12, I don't know another way) and now version is 5107.
Your version was 5108.
I also try with Above4GDecoding enabled.
Still same result.

Open Config.plist with Clover Configurator, and select Install/Update clover in the Tools on the left.
On Clover installer select the usb stik --> Customize --> and select: "install for UEFI booting only" and on drivers, the drivers that are already present in your EFI/Driver folder.