Contribute
Register

ASUS Sabertooth P67, BIOS 3302 DSDT

Status
Not open for further replies.
Joined
May 29, 2012
Messages
887
Motherboard
Gigabyte Z390 Gaming X
CPU
i9-9900K
Graphics
RX 6900 XT
Mac
  1. iMac
  2. MacBook Pro
Classic Mac
  1. LC
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
I assembled my Hackintosh with a Core i7-2600K and P67 Sabertooth, basically following timelapser01's guide word for word.

viewtopic.php?f=54&t=56534&p=361644

Using Geekbench, I had a score in the 11000's.

He used EasyBeast, so I thought I could juice out a little more performance by using a DSDT, however, there is no DSDT in the database.

I followed samisnake's guide to making your own DSDT, using the P67 Sabertooth patch on Maldon's site. I kept getting 143 uncompilable errors. I tried all the workarounds, like booting with iBoot, rBoot, booting into Windows, etc. Same 143 errors.

It turned out that most of the errors originated from the HDEF patch and the SBUS patch. To fix the HDEF patch, I manually edited the P67 Sabertooth patch file following these instructions:

http://olarila.com/forum/viewtopic.php?f=19&t=1421

Similarly, I found someone with the same error in the SBUS patch using a ASUS P8Z68 mobo, and the fix was published.

I modified these sections of the Patch, then the final error was

_HID suffix must be all hex digits (GH)

I manually changed "ABDCEFGH" to "PNP0C15"

viewtopic.php?f=14&t=61284

The warnings I got were:

ResourceTag larger than Field (Tag: 64 bits, Field: 32 bits)

And the fix here was to change "CreateDWordField" to "CreateQWordField"

After these edits, it compiled without any errors! I installed the modified DSDT, repaired permissions, rebuilt the caches, then rebooted.

Cross my fingers….and it rebooted without problems! Using Geekbench, my new score was close to 13000, about a 15% increase!

Listed here are the specific fixes, and I am attaching the "Patched Patch", as well as my DSDT.

SBUS fix:

Change:

Code:
into device name_adr 0x001F0003 parent_label PCI0 remove_entry;
into device label PCI0 insert
begin
Device (SBUS)\n
{\n
    Name (_ADR, 0x001F0003)\n
    Device (BUS0)\n
    {\n
        Name (_CID, "smbus")\n
        Name (_ADR, Zero)\n
        Device (DVL0)\n
        {\n
            Name (_ADR, 0x57)\n
            Name (_CID, "diagsvault")\n
        }\n
    }\n
    Method (_DSM, 4, NotSerialized)\n
    {\n
        Store (Package (0x02)\n
            {\n
                "device-id", \n
                Buffer (0x04)\n
                {\n
                    0x30, 0x3A, 0x00, 0x00\n
                }\n
            }, Local0)\n
        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
        Return (Local0)\n
    }\n
}
end;

To:

Code:
into method label _DSM parent_adr 0x001F0003 remove_entry;
into device name_adr 0x001F0003 insert
begin
    Device (BUS0)\n
    {\n
        Name (_CID, "smbus")\n
        Name (_ADR, Zero)\n
        Device (DVL0)\n
        {\n
            Name (_ADR, 0x57)\n
            Name (_CID, "diagsvault")\n
        }\n
    }\n
    Method (_DSM, 4, NotSerialized)\n
    {\n
        Store (Package (0x02)\n
            {\n
                "device-id", \n
                Buffer (0x04)\n
                {\n
                    0x30, 0x3A, 0x00, 0x00\n
                }\n
            }, Local0)\n
        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
        Return (Local0)\n
    }
end;

HDEF fix

Change:

Code:
into device name_adr 0x001B0000 parent_label PCI0 remove_entry;
into device label PCI0 insert
begin
Device (HDEF)\n
{\n
    Name (_ADR, 0x001B0000)\n
    Method (_DSM, 4, NotSerialized)\n
    {\n
        Store (Package (0x04)\n
            {\n
                "layout-id", \n
                Buffer (0x04)\n
                {\n
                    0x0C, 0x00, 0x00, 0x00\n
                }, \n
                "PinConfigurations", \n
                Buffer (Zero) {}\n
            }, Local0)\n
        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
        Return (Local0)\n
    }\n
}
end;

to:

Code:
into method label _DSM parent_adr 0x001B0000 remove_entry;
into device name_adr 0x001B0000 insert
begin
    Method (_DSM, 4, NotSerialized)\n
    {\n
        Store (Package (0x04)\n
            {\n
                "layout-id", \n
                Buffer (0x04)\n
                {\n
                    0x0C, 0x00, 0x00, 0x00\n
                }, \n
                "PinConfigurations", \n
                Buffer (Zero) {}\n
            }, Local0)\n
        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
        Return (Local0)\n
    }
end;
 

Attachments

  • P67 Sabertooth HDEF SBUS fix.txt
    7.4 KB · Views: 542
  • Sabertooth P67 DSL - patched - HDEF fix SBUS fix.dsl
    46.8 KB · Views: 595
Hi tedyun

In your HDEF dsdt, you assigned 'layout-id' to '0C 00 00 00'.

AFAIK sabertooth p67 has ALC892 and it could be '7C 03 00 00' (wrote in Toleda's ALC 8xx guide).

Anyway do you have audio sound work? If it does, which method or kext do you use?
 
I will take a look. In the original patch, it is listed as '0C 00 00 00' so I did not change that. I'm not a coder, so I don't really understand what is going on :crazy: I just modified the original patch file so that it would compile.

I'll play around with it, but I've spent the last couple of days trying to get the Speedstepping patches to work to no avail, so I probably will just give up optimizing this system because it is working pretty much the way I want.

For audio, I am using my SB Audigy2 ZS Platinum Pro. An oldie but it has the inputs and outputs I need for my use. I use the kX Audio Driver for this.

I just checked my onboard audio and I don't have sound coming out. If I have time, I'll futz around with trying to get the ALC892 to work and I will report back here.

So sleep doesn't work and audio doesn't work. But USB3 and Firewire work no prob.

theroot said:
Hi tedyun

In your HDEF dsdt, you assigned 'layout-id' to '0C 00 00 00'.

AFAIK sabertooth p67 has ALC892 and it could be '7C 03 00 00' (wrote in Toleda's ALC 8xx guide).

Anyway do you have audio sound work? If it does, which method or kext do you use?
 
tedyun said:
So sleep doesn't work and audio doesn't work. But USB3 and Firewire work no prob.

For your system configuration, MultiBeast's AppleIntelCPUPowerManagement would be helpful. Or have you tried it already?

1. Sleep
- Drivers & Bootloaders -> Kexts & Enablers -> Miscellaneous -> Patched AppleIntelCPUPowerManagement

2. SpeedStep - SSDT
http://tonymacx86.blogspot.com/2012/05/ ... ridge.html
 
I tried patching my own using AICPMPatch:

http://www.osx86.net/view/2543-aicpmpatch.html

But when I replaced the vanilla version, and removed NullCPUPowerManagement, I got Kernel Panics.

I'm still running Snow Leopard, so I didn't have that option for the version of Multibeast I used.


theroot said:
tedyun said:
So sleep doesn't work and audio doesn't work. But USB3 and Firewire work no prob.

For your system configuration, MultiBeast's AppleIntelCPUPowerManagement would be helpful. Or have you tried it already?

1. Sleep
- Drivers & Bootloaders -> Kexts & Enablers -> Miscellaneous -> Patched AppleIntelCPUPowerManagement

2. SpeedStep - SSDT
http://tonymacx86.blogspot.com/2012/05/ ... ridge.html
 
I also have an ASUS Sabertooth P67 I would like to try a Hackintosh build with. I would be happy to help with this (creating the DSDT) and help with testing if that might help us get one posted in the database.

Thanks
 
Hi, I'm having issue generate dsdt.aml from your dsl file. When I try to open the dsl file in DSDT editor, it give me error about brackets. Can you please help. Thank you very much.
 
I would like to use your .dsl file to install a DSDT, but how do i do it? It's a .dsl file and not a .aml?
 
Hi, I'm having issue generate dsdt.aml from your dsl file. When I try to open the dsl file in DSDT editor, it give me error about brackets. Can you please help. Thank you very much.

Looks like it was mistakenly saved as a .dsl file. Rename to .aml and it should open just fine.
 
Hello friends!
I also have the Sabertooth P67 BIOS 3302
I installed the Mountain Lion but am not getting my machine to work properly ... I already tried different alternatives, but nothing works.
I downloaded the DSDT that our friend tedyun posted, but it did not work.
What should I do, any alternative?
Despois that I install Multibeast not connect my machine anymore, so I restart from scratch, install again the Mountain Lion and make another attempt ... I already reinstalled the system more than 20 times! (But I will not give up hehe)
Could someone help me?
What are the options which you guys selected in multibeast?
Could someone give me some help?
From already thank you very much!
I do not know speak English very well, I'm using google translator to communicate, sorry for some grammar errors. lol
 
Status
Not open for further replies.
Back
Top