6 replies to this topic

[EvilMacMongo]

Ok so I've been doing some research but still can't find out the answer i'm looking for.

If no dsdt was needed to install and run SL up to 10.6.8 would making a dsdt for my hack improve anything?  Simple question I think but if I didn't need one, what is the point of it and would it improve things like speed?

[Gringo Vermelho]

DSDT patching is not a magic box of tricks that make your PC fast. For the most part, you patch your DSDT in order to fix very specific issues, for example to get an unmodified Apple driver to load and/or work properly with hardware that's already compatible. A nudge here, a tickle there.
The most common edits are Intel and vanilla kernel specific, done to fix issues with sleep/wake, power management stuff.
Years ago people were patching their DSDT to enable native CPU power management, but thankfully the Chameleon boot loader made most of that obsolete early in the 2.0 RC5 dev cycle: http://www.insanelym...howtopic=225766

DSDT editing is close to pointless if you're not using an Intel CPU because you can never have native power management. This is also the reason why it doesn't matter much which model identifier you use in smbios.plist - the power management profiles (both CPU and GPU) in OS X match with entire Mac models rather than separate bits of hardware. But you're not invited to the party.

Your patched kernel 'blacklists' certain kernel extensions that doesn't work with AMD hardware (and older Intel CPUs such as the Pentium 4 and the Pentium D). This effectively shuts down native power management (you couldn't use it anyway) which is in turn why you need Hackintosh specific kernel extensions like sleepenabler, VoodooPower.kext etc.

As an example, you could fix your HPET device code but it would be pointless since AppleHPET.kext never loads on your system in the first place, AFAIK its only client is AppleIntelCPUPowerManagement.kext which obviously never loads either. And you can't make use of device ID patches to your USB controller or LPC device because your hardware is nowhere near anything that ever shipped in a Mac.

[EvilMacMongo]

that explains alot.  Thank you

[LatinMcG]

gringo vermelho.. u should sticky that answer as a DSDT FAQ

[ammoune78]

hi every one! sorry for my english ! But my question is: i have an asus P5Q-E motherboard and ATI powercolor hd 4870 512m, so the graphics are recognised but not completely, and i'll need to put graphics injection to my DSDT.aml.
can any one help me please ? But there is a little problem on my DSDT i have that :
Name (MBIF, Package (0x08)
{
0x03,
"P5Q-Deluxe", ======> my board is P5Q-E not the first one
0x01010201,
0x01000100,
0xE0000000,
Zero,
Zero,
Zero
})
please help me to do it    
Thanks

[Gringo Vermelho]

It doesn't matter that it says P5Q-Deluxe in your DSDT, it's just ASUS recycling the same DSDT code across the P5Q series. Just ignore it, besides that whole section of code is not used at all by OS X anyway.

Use IORegistryExplorer to find where to insert your GFX0 device code. The example below is from a P5Q-E board with an Nvidia card in the PCI-E x16 slot - this is P0P2 in your DSDT.
 P5Q-E_P0P2.png   178.53K   36 downloads

[ammoune78]

Thank you Gringo! But excuse me, how to put it, because I don't know the place and the script where i'll put it in the DSDT!

I am very grateful to you as far as possible to show me how to do it

Here is my attached original DSDT.aml extracted form Windows 7 and the picture of ATI informations from Aida64.

 acpi_dsdt.zip   15.94K   3 downloads  ATI RADEON PowerColor HD AX4870.png   91.44K   14 downloads