X299 - Open Core support

[tonyarnold]

even more with new (yesterday flashed) Vega64 rom.

What's this? Is there a firmware update for the Vega 64's?

 

[Lorengrin]

What's this? Is there a firmware update for the Vega 64's?

Yes, and the resolution on the initial screen is now appropriate on 4K screens on both MAC or Windows.

Asus X299 - Support

I tried to Install 10.15 and still try to use OC instead Clover (with 10.15 install and 10.14.6 in use everyday), maybe too much on the same time, but still I'm angry because I can't find what is missing, what I do wrong to stuck at this moment every time: I checked few downloaded EFI folders...

www.tonymacx86.com

 

[BavarianDNA]

​

The attached files were made for the ASUS Prime Deluxe (version I, not II), using the latest BIOS. You mentioned on another thread that there are not many of us using this mobo and it is probably true. I did find much greater stability in this PD1 mobo with the latest BIOS update.

OK, here's a basic EFI for CLOVER (missing themes, boot files, etc; this should be obvious).

Clover is easier than getting into various boot issues with OC and moving around ACPI and kext files. OC requires you to update the config file if you make any nomenclature changes to any ACPI or kext files.

However, if you wish to use OpenCore, I use the exact same files in OpenCore. I already provided a config.plist OC file in a previous post (here), so the OC version should be easy to construct.

Included are ACPIs, kexts and drivers. For specific BIOS settings, see previous threads by KGP. Power management files all work well, at least with Mojave. These same files will boot into Catalina. I can answer basic questions, but I'm not providing lots of support for it. It works well on my set-up.

Note:

1. ACPIs have associated slot numbers; you needs may vary, adjust accordingly.
2. ACPI patched folder has a GPU folder inside containing files for Radeon VII and Vega 56. Use one; if you have another GPU, then don't use either.
3. The kext/other folder has a PrimeX299DeluxeUSB.kext that will need adjusting depending on which USB ports you wish to use.
4. Similarly, the TSCAdjustReset-36threads.kext is set for a 9980XE with 18 cores. If you use another processor, you'll need to adjust this file.
5. The config file has no SNs; you'll need to complete the sections marked "Fill-in". (And again, see the previous post here for the OC version.)

*****

EDIT 9/22/19: Added latest BIOS (v1902) for ASUS X299 Prime Deluxe (version I) with a custom image.

Rather than place in this thread, I posted into the main ASUS X299 Support thread, here. See that post for the customized BIOS attachment.

Bro is this a plug and play, I have too the same Mobo and would love to test it out ans save myself the time. This is for clover and not OC, Right?

I have already my modified TSCAdjustReset-36threads.kext, another nobs question, with all your ssdt's, should include them in clover under ssdt list ?, So the clover shouldn't be touched except for the SMBIOS and System Parameters, right?

 

[rj510]

Bro is this a plug and play, I have too the same Mobo and would love to test it out ans save myself the time. This is for clover and not OC, Right?

I have already my modified TSCAdjustReset-36threads.kext, another nobs question, with all your ssdt's, should include them in clover under ssdt list ?, So the clover shouldn't be touched except for the SMBIOS and System Parameters, right?

Yes, Clover, not OC.

And yes, you're correct about needing to fill-in the missing data for the config-NoSN.plist file. Within these 3 sections, enter the proper data for each "Fill-in" (and rename the file 'config.plist'):

And make certain that your BIOS is v1902. There is a more current version, but only necessary for the latest CPUs. You also need to closely follow KGP's thread on how to set up the BIOS. This is critical for a successful boot; not a simple plug and play.

I only uploaded the basics; not a complete EFI. You'll need to supply the other EFI files and folders (CLOVERX64.efi, themes, etc). The folder arrangement is usual for Clover (≥5000). In parallel with the Clover folder is also the Boot folder; not supplied. Inside the Clover folder, the structure would look like this (patched folder inside ACPI):

Pay attention to the SSDT files that are labelled "slot" at the end. If you place the PCI cards into different slots, you'll maybe want to make some changes in those files. (If you don't know how to do this, they'll still work, but the slot positions will be incorrectly reported.)

Finally, these files are all good for Mojave. Catalina has some subtle differences in the power management SSDT files, which can be read about in other threads on this forum.

 

[BavarianDNA]

Yes, Clover, not OC.

And yes, you're correct about needing to fill-in the missing data for the config-NoSN.plist file. Within these 3 sections, enter the proper data for each "Fill-in" (and rename the file 'config.plist'):
View attachment 431088

And make certain that your BIOS is v1902. There is a more current version, but only necessary for the latest CPUs. You also need to closely follow KGP's thread on how to set up the BIOS. This is critical for a successful boot; not a simple plug and play.

I only uploaded the basics; not a complete EFI. You'll need to supply the other EFI files and folders (CLOVERX64.efi, themes, etc). The folder arrangement is usual for Clover (≥5000). In parallel with the Clover folder is also the Boot folder; not supplied. Inside the Clover folder, the structure would look like this (patched folder inside ACPI):

View attachment 431089

Pay attention to the SSDT files that are labelled "slot" at the end. If you place the PCI cards into different slots, you'll maybe want to make some changes in those files. (If you don't know how to do this, they'll still work, but the slot positions will be incorrectly reported.)

Finally, these files are all good for Mojave. Catalina has some subtle differences in the power management SSDT files, which can be read about in other threads on this forum.

Yeah, I have been paying attention to the KGP instruction, and I've successfully installed and ran Mojave as a primary drive and Catalina as a test drive so far.

I'm currently trying to figure out a solution for my ASUS Strix Vega 64 fans. I will try login windows and use ASUS software to turn the fans on always and see if this will work also when booting into Mojave.

 

[tsrattan]

Catalina was working properly before and suddenly it starts getting stucks here for minute or two and then screeen goes black where as mojave boots properly. When i use clover catalina boots properly

 

[zhangdiming]

Yes, Clover, not OC.

And yes, you're correct about needing to fill-in the missing data for the config-NoSN.plist file. Within these 3 sections, enter the proper data for each "Fill-in" (and rename the file 'config.plist'):
View attachment 431088

And make certain that your BIOS is v1902. There is a more current version, but only necessary for the latest CPUs. You also need to closely follow KGP's thread on how to set up the BIOS. This is critical for a successful boot; not a simple plug and play.

I only uploaded the basics; not a complete EFI. You'll need to supply the other EFI files and folders (CLOVERX64.efi, themes, etc). The folder arrangement is usual for Clover (≥5000). In parallel with the Clover folder is also the Boot folder; not supplied. Inside the Clover folder, the structure would look like this (patched folder inside ACPI):

View attachment 431089

Pay attention to the SSDT files that are labelled "slot" at the end. If you place the PCI cards into different slots, you'll maybe want to make some changes in those files. (If you don't know how to do this, they'll still work, but the slot positions will be incorrectly reported.)

Finally, these files are all good for Mojave. Catalina has some subtle differences in the power management SSDT files, which can be read about in other threads on this forum.

Greetings，rj510. could you tell me how to modify SSDT-X299-ASUS-PD1-ARPT-Slot5.aml, because my card is BCM943602CDP. Thanks for your help!

 

[rj510]

Yeah, I have been paying attention to the KGP instruction, and I've successfully installed and ran Mojave as a primary drive and Catalina as a test drive so far.

I'm currently trying to figure out a solution for my ASUS Strix Vega 64 fans. I will try login windows and use ASUS software to turn the fans on always and see if this will work also when booting into Mojave.

The guide I've studied for Vega 64 is this one here. You should be able to start with one of KGP's SSDT for the Vega 64 and go from there.

 

[rj510]

Greetings，rj510. could you tell me how to modify SSDT-X299-ASUS-PD1-ARPT-Slot5.aml, because my card is BCM943602CDP. Thanks for your help!

Basically, you want to run your computer without this SSDT and use Hackintool. During this same boot, use Hackintool and look at the PCI tab and generate data for PCI. From this information, you'll be able open the ARPT-Slot5 SSDT file and edit the fields concerning device-id, vendor-id, etc. that differ from the values between Hackintool and what are in the SSDT file. The slot number is easily substituted by replacing the "5" value with the slot number that you're presently using. (The slot number is cosmetic only.)

An alternative way that may a little easier and work just as well for you is: create a new copy of the SSDT file and then edit it by deleting those same values from the SSDT file, and then try booting with that version. Often the computer will accurately populate those fields in the System Report/Hardware/PCI section without them being present in the SSDT file. (The main job of the SSDT files are to re-label the devices, which you can see when using IORegistryExplorer.)

By tinkering around with these SSDT files like this, you'll better learn their ins and outs and be more comfortable doing your own edits.

 

[zhangdiming]

Basically, you want to run your computer without this SSDT and use Hackintool. During this same boot, use Hackintool and look at the PCI tab and generate data for PCI. From this information, you'll be able open the ARPT-Slot5 SSDT file and edit the fields concerning device-id, vendor-id, etc. that differ from the values between Hackintool and what are in the SSDT file. The slot number is easily substituted by replacing the "5" value with the slot number that you're presently using. (The slot number is cosmetic only.)

An alternative way that may a little easier and work just as well for you is: create a new copy of the SSDT file and then edit it by deleting those same values from the SSDT file, and then try booting with that version. Often the computer will accurately populate those fields in the System Report/Hardware/PCI section without them being present in the SSDT file. (The main job of the SSDT files are to re-label the devices, which you can see when using IORegistryExplorer.)

By tinkering around with these SSDT files like this, you'll better learn their ins and outs and be more comfortable doing your own edits.

Thanks very much! I have modified 2 ssdt files based on your advice. My wifi+bt and 5700xt works fine now!