Contribute
Register

Asus X299 - Catalina Support

Status
Not open for further replies.
Rehabman version worked, attached! Acidanthera one didn't work.

OK fine :
For exemple :

I see on your previous EFI / ACPI / SSDTs attached:

SSDT EC -USBX :

It's not good :


Code:
        Device (EC)
        {
            Name (_HID, "ACID0001")  // _HID: Hardware ID
            Method (_STA, 0, NotSerialized)  // _STA: Status

Your EC is :

Code:
   Scope (_SB.PC00.LPC0)
    {
        Device (EC0)
        {
            Name (_HID, EisaId ("PNP0C09"))  // _HID: Hardware ID
            Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
            {

For me the SSDT-SBUS-MCHC is not useful .

I'll go on and share the minimum SSDTs based on your system later.
 
OK fine :
For exemple :

I see on your previous EFI / ACPI / SSDTs attached:

SSDT EC -USBX :

It's not good :


Code:
        Device (EC)
        {
            Name (_HID, "ACID0001")  // _HID: Hardware ID
            Method (_STA, 0, NotSerialized)  // _STA: Status

Your EC is :

Code:
   Scope (_SB.PC00.LPC0)
    {
        Device (EC0)
        {
            Name (_HID, EisaId ("PNP0C09"))  // _HID: Hardware ID
            Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
            {

For me the SSDT-SBUS-MCHC is not useful .

I'll go on and share the minimum SSDTs based on your system later.

Ok, I’ll wait. But how am I able to boot with wrong SSDTs? :crazy:
 
OK fine :
For exemple :

I see on your previous EFI / ACPI / SSDTs attached:

SSDT EC -USBX :

It's not good :


Code:
        Device (EC)
        {
            Name (_HID, "ACID0001")  // _HID: Hardware ID
            Method (_STA, 0, NotSerialized)  // _STA: Status

Your EC is :

Code:
   Scope (_SB.PC00.LPC0)
    {
        Device (EC0)
        {
            Name (_HID, EisaId ("PNP0C09"))  // _HID: Hardware ID
            Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
            {

For me the SSDT-SBUS-MCHC is not useful .

I'll go on and share the minimum SSDTs based on your system later.

Note that these SSDTs were from dracoflar. Notes from his github:

SSDT-EC-USBX-X299

  • Creates a fake EC and fixes USB power. Note I do not power off the original EC, reason for this is due to a huge mess around sleep and _GPE. Turning off this EC makes waking a pain without hacky fixes
  • SSDT-PLUG-X299
    • Sets Plugin-type=1 to SB.SCK0.CP00 allowing for proper CPU power management
  • SSDT-SBUS-MCHC
    • Creates SMBus device allowing AppleSMBus to load
 
Note that these SSDTs were from dracoflar. Notes from his github:
SSDT-EC-USBX-X299
  • Creates a fake EC and fixes USB power. Note I do not power off the original EC, reason for this is due to a huge mess around sleep and _GPE. Turning off this EC makes waking a pain without hacky fixes
  • SSDT-PLUG-X299
    • Sets Plugin-type=1 to SB.SCK0.CP00 allowing for proper CPU power management
  • SSDT-SBUS-MCHC
    • Creates SMBus device allowing AppleSMBus to load
Thanks !
You're pointing in the right direction for OC :
You're right for EC : the system may reboot after sleep and on my EFI OC , my SSDT PLUG seems wrong I have this :

Code:
  Scope (\_SB.CP00)
    {
        Method (DSM, 4, NotSerialized)
        {
            Store ("Writing plugin-type to Registry!", Debug)
 
Well... it seems you're taking care of me :) am I supposed to do something or just wait? just asking...
 
Well... it seems you're taking care of me :) am I supposed to do something or just wait? just asking...

Yes @djlild7hina provide useful recommendations ( thanks :clap:) so we may continue on the X299 OC thread. ;)

Here are your system SSDTs and for the OC SSDTs on the OC thread
NB : the SSDTs are from Kgp repo but adapted for some to your system
 

Attachments

  • SYSTEM SSDT .zip
    10.9 KB · Views: 86
Yes @djlild7hina provide useful recommendations ( thanks :clap:) so we may continue on the X299 OC thread. ;)

Here are your system SSDTs and for the OC SSDTs on the OC thread
NB : the SSDTs are from Kgp repo but adapted for some to your system

So I have to inject all of them in ACPI folder/config.plist of Opencore? I suppose I have to leave EC-USBX + PLUG + RTC0 + SBUS as they previously are in my EFI?

Thanks for your work, really appreciated. Hope someone else with Prime x299-a will enjoy this.
 
So I have to inject all of them in ACPI folder/config.plist of Opencore? I suppose I have to leave EC-USBX + PLUG + RTC0 + SBUS as they previously are in my EFI?

Thanks for your work, really appreciated. Hope someone else with Prime x299-a will enjoy this.

Yes put this on ACPI and you must edit your OC config.plist ( with Xcode or TextMate) but you will also add the SSDTs linked by @djlild7hina
SSDT-EC-USBX-X299
SSDT-PLUG-X299
SSDT-SBUS-MCHC ( required for OC)
SSDT-DTGP
(With the Titan Ridge I also add SSDT-XOSI)

And after we will meet us on the X299 OC thread ;) TYA (Exciting the X299 system)
 
Last edited:
Yes put this on ACPI and you must edit your OC config.plist ( with Xcode or TextMate) but you will also add the SSDTs linked by @djlild7hina
SSDT-EC-USBX-X299
SSDT-PLUG-X299
SSDT-SBUS-MCHC ( required for OC)
SSDT-DTGP
(With the Titan Ridge I also add SSDT-XOSI)

And after we will meet us on the X299 OC thread ;) TYA (Exciting the X299 system)

Note that you don't need SSDT-DTGP if you have SSDT-SBUS-MCHC. the DTGP method is already included :) So make sure SSDT-SBUS-MCHC is first in your config.plist, since other SSDTs may reference that method. Also this thread is kinda like a second OC thread since mostly everyone moved to OC. :lol:
 
Status
Not open for further replies.
Back
Top