Share this post

Link to post

Share on other sites

Thanks for the pointers. I'll run through the SSDT from the MBP5,1 I have and compare them to mine for the OST and PDC fields.

The following lines from yours:

Processor (CPU1, 0x01, 0x00000810, 0x06)

{

OperationRegion (STBL, SystemMemory, 0xCFF8E0D0, 0x01D2)

What memory addresses are they referring to from your SSDT tables? The CST or IST?

In this case it is referring to my computers IST table, but OperationRegion can be used for anything, including yours below, but there is no need to replace them.

I did put in my own PDC and OST but that made no difference (been playing with wireless routers all day and this is the first sit down I've had). As mentioned I'll look through the SSDT-1 from an MBP5,1 and see what they are doing to load the CST and IST from SSDT...

Actually those are identical, and IST0 is loaded to HI0 and CST0 to HC0...

The second argument in a Load() statement is a handle (see ACPI programmers manual) which can be used to release the table. Actually, you can see that yourself by reading the second argument like this: HI0 refers to Handle IST 0 and HC0 refers to Handle CAP 0

Code snippet -> from _OST for the Dell

Store (0x06, STS0)

Store (0x0A, STS0)

For the MBP5,1

Store (0x06, Index (STS0, 0x00))

Store (0x0A, Index (STS0, 0x00))

Just the way the Store is done is different between the two SSDT's... Not sure if that is significant at all or not, thoughts?

Yes, that is different. The first call simply replaced STS0 with 0x06 while the second call replaces only the nth argument – in this case 0 – with 0x06/0x0a.

p.s. If you do happen to have SSDT tables, then by all means use that and don't go looking for anything else. Assuming that you don't have to change anything in it of course

And like I said before, that table is your key to success. Here's an example:

To anyone wondering about why there are two tables in _PSS, one called SPSS and the other NPSS; Take a look at this example:

Now check the table I proved to in post #71 to find this: If set, the OSPM supports the C1 "I/O then Halt" FFH sequence for multi-processor configurations. And you'll find other use of it throughout the DSDT/SSDT.

n.b. TYPE in this example is probably called differently in yours, like PDC0 for example.

You should see a similar check in method _PCT() in your SSDT – which is one of the three Performance Control objects (_PCT, _PSS and _PPC) – to differentiate between FFixedHW and SystemIO et all.

Share this post

Link to post

Share on other sites

The data for the P-states listed in the NPSS and SPSS methods appeared to match up with my processor's capabilities, so I left it alone. As for the C-State latency, that's pretty neat but I don't have any IST tables or c-states from my motherboard. How would I go about adapting the tables from the Mac Pro to work with my system?

Share this post

Link to post

Share on other sites

Really stumped here. DSDT.aml fixed everything LAN, Video, Audio, CMOS reset, USBEHCI and power button on GA-EP45-DS3R+Q9550. In Leopard 10.5.7 the same DSDT.aml allows AppleIntelCPUPowerManagement to initialize correctly and I do see temps higher by 10 deg. Centigrade. But the same DSDT.aml in SnowLeopard 10.6 causes kernel panic on boot. I have to put back the NullCPUPowermanagement.kext to get booted. everything Else is working.

Can anyone please shed some light on this.

On my way to DSDT Vanilla Speedstep, so need help please.

Thank you.

Share this post

Link to post

Share on other sites

The data for the P-states listed in the NPSS and SPSS methods appeared to match up with my processor's capabilities, so I left it alone. As for the C-State latency, that's pretty neat but I don't have any IST tables or c-states from my motherboard. How would I go about adapting the tables from the Mac Pro to work with my system?

Share on other sites

The question is if we add _cst to the DSDT correctly - will it work?!!

D.

Exactly!

BTW: The version of CPU-i that I compiled for Snow Leopard (32-bit) works here – unlike that ugly MSRTools tools thing. Even for my computer, which still shows up as: "P5K PRO" in System Profiler (I changed the ACPI plugin Info.plist). And not only that. because the 7.5 multiplier (0x4720 in my _PSS) works too!!! I am however still looking for the value for the 6.5 multiplier; the reported value in CPU-i (0x461C) doesn't seem to work here (no 6.5 showing up in CPU-i).

Hi,

Really stumped here. DSDT.aml fixed everything LAN, Video, Audio, CMOS reset, USBEHCI and power button on GA-EP45-DS3R+Q9550. In Leopard 10.5.7 the same DSDT.aml allows AppleIntelCPUPowerManagement to initialize correctly and I do see temps higher by 10 deg. Centigrade. But the same DSDT.aml in SnowLeopard 10.6 causes kernel panic on boot. I have to put back the NullCPUPowermanagement.kext to get booted. everything Else is working.

Can anyone please shed some light on this.

On my way to DSDT Vanilla Speedstep, so need help please.

Thank you.

I take it that the unmodified dsdt.dsl works with Snow Leopard? As in it fails after your changed it? Then attach both the original (working) and modified dsdt.dsl because how else should anyone here help you?

I tried your suggestions but it didn't work

whatever I tried led me to the same result -->multiplier X6 and stock voltage (1.25) not changing.

What kind of "Model Identifier:" do you see in System Profiler?

Mine still reports: "P5K PRO" and thus I modified ACPI_SMC_PlatformPlugin.kext (I simply replaced MacPro3,1" and "MacPro4,1" with "P5K PRO" in the Info.plist) to get P-stepping working.