DSDT - Vanilla Speedstep - Generic Scope (_PR)

kdawg · November 17, 2009

I was - I only ran the fixed voodoopstate-v4 yesterday and I get:

Which is what I'm using now.

Note: I'm only Oclocked to 3.36GHz

So it's pulling the motherboard's overclock settings to calculate FID/VIDs, I see.

leslieking · November 17, 2009

FormerlyKnownAs: sorry for the OT! Why does this happen?

86:Desktop zoliky$ ./iasl -ta zoliky.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20080926 [Oct  4 2008]
Copyright © 2000 - 2008 Intel Corporation
Supports ACPI Specification Revision 3.0a


Maximum error count (200) exceeded
Bus error

FKA · November 17, 2009

FormerlyKnownAs: sorry for the OT! Why does this happen?

86:Desktop zoliky$ ./iasl -ta zoliky.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20080926 [Oct  4 2008]
Copyright © 2000 - 2008 Intel Corporation
Supports ACPI Specification Revision 3.0a


Maximum error count (200) exceeded
Bus error

It's not off topic mate.

Firstly check the file is saved as plain text format (I'm on XP at work ATM so may have saved as unicode by mistake!!)

Second use the latest IASLME that mitch_de posted here its the NOv_2009 one you want.

D.

So it's pulling the motherboard's overclock settings to calculate FID/VIDs, I see.

I presume voodoopstate just see's whatever FSB you have set in BIOS and works it's way down?!

Sort of!!!

FKA · November 17, 2009

I have attached my dsdt. thanks in Advance - Liquid_ic

Hi Liquid

Try this - assuming your FID/VID's where correct in the DSDT you posted this should work.

Please double chheck FID VID with fixed voodoopstate and pstatechanger - linked first post.

liquid_ic_dsdt.zip

Note you will NOT need DropSSDT=y with this code

D

Liquid Ice · November 17, 2009

Hi Liquid

Try this - assuming your FID/VID's where correct in the DSDT you posted this should work.

Please double chheck FID VID with fixed voodoopstate and pstatechanger - linked first post.

liquid_ic_dsdt.zip

Note you will NOT need DropSSDT=y with this code

D

Thanks I will give it a try.

leslieking · November 17, 2009

Thanks mate! Works for me

Ive corrected -MY- mistakes in this scope PR.

Try this zoliky.zip

Also the values highlighted in red below, are they the same as your origional, untouched Scope (PR) ?

You'll need to change them if they're not.
Scope (_PR)
   {
       Processor (CPU0, 0x00, 0x00000[b][color="#ff0000"]410[/color][/b], 0x06) {}
       Processor (CPU1, 0x01, 0x00000[b][color="#ff0000"]410[/color][/b], 0x06) {}
       Processor (CPU2, 0x02, 0x00000[b][color="#ff0000"]410[/color][/b], 0x06) {}
       Processor (CPU3, 0x03, 0x00000[b][color="#ff0000"]410[/color][/b], 0x06) {}
   }
D.

Liquid Ice · November 17, 2009

Hi Liquid

Try this - assuming your FID/VID's where correct in the DSDT you posted this should work.

Please double chheck FID VID with fixed voodoopstate and pstatechanger - linked first post.

liquid_ic_dsdt.zip

Note you will NOT need DropSSDT=y with this code

D

I dropped dropSSDT, and used the new dsdt.aml.

Seem that i have p-states. but CPU temperature is at 58 degrees. (Looks like no c-states). cpu status is fixed at

2.83ghz at 1.244 volts. No stepping. I don't have restart and shutdown working anymore since i removed EvOreboot.

here is my code for smbios.plist: maybe you can see what I am missing. looks like an error with MacPro3,1 not being recognized.

Note: My Q9550 only has C1E and EIST. No c2 or c4. I double checked with Intel this morning.

Thanks in advance. Hope we can find a solution.

<plist version="1.0">
<dict>
<key>SMUUID</key>
<string>637AD9F8-993C-3473-94AE-906240BF8EA7</string>
<key>SMbiosvendor</key>
<string>Apple Inc.</string>
<key>SMbiosversion</key>
<string>MP31.88Z.00C1.B00.0802091538</string>
<key>SMexternalclock</key>
<string>333</string>
<key>SMmanufacter</key>
<string>Apple Inc.</string>
<key>SMmaximalclock</key>
<string>2833</string>
<key>SMmemmanufacter_1</key>
<string>OCZ</string>
<key>SMmemmanufacter_2</key>
<string>OCZ</string>
<key>SMmemmanufacter_3</key>
<string>OCZ</string>
<key>SMmemmanufacter_4</key>
<string>OCZ</string>
<key>SMmempart_1</key>
<string>OCZ2G10664GK</string>
<key>SMmempart_2</key>
<string>OCZ2G10664GK</string>
<key>SMmempart_3</key>
<string>OCZ2G10664GK</string>
<key>SMmempart_4</key>
<string>OCZ2G10664GK</string>
<key>SMmemserial_1</key>
<string>0x48092D503537345336304350362D09352020</string>
<key>SMmemserial_2</key>
<string>0x48092D503537345336304350362D09352020</string>
<key>SMmemserial_3</key>
<string>0x48092D503537345336304350362D09352020</string>
<key>SMmemserial_4</key>
<string>0x48092D503537345336304350362D09352020</string>
<key>SMmemspeed</key>
<string>1066</string>
<key>SMmemtype</key>
<string>19</string>
<key>SMproductname</key>
<string>MacPro3,1</string>
<key>SMserial</key>
<string>W88261E7YP4</string>
<key>SMsystemversion</key>
<string>1.0</string>
</dict>
</plist>

FKA · November 18, 2009

I dropped dropSSDT, and used the new dsdt.aml.

Seem that i have p-states. but CPU temperature is at 58 degrees. (Looks like no c-states). cpu status is fixed at

2.83ghz at 1.244 volts. No stepping. I don't have restart and shutdown working anymore since i removed EvOreboot.

here is my code for smbios.plist: maybe you can see what I am missing. looks like an error with MacPro3,1 not being recognized.

Note: My Q9550 only has C1E and EIST. No c2 or c4. I double checked with Intel this morning.

Thanks in advance. Hope we can find a solution.

I don't know what OS you have ? are you running Snow?

And you have changed your SMC kext no? if yes try with original SMC kext.

Try reinstalling your original SMC kext also try Master Chief's legacy SMC with your original SMC kext ( i think it's on page 18 of this thread, attachment called archive.zip.)

Also can you see LCP loaded in ioreg?

Thanks mate! Works for me

Top bananas ...

I still think you have an error in you PSD part of DSDT.

It should read:

        Method (_PSD, 0, NotSerialized)
       {
           Return (Package (0x05)
           {
               [b][color="#ff0000"]0x05[/color][/b], 
               Zero, 
               Zero, 
               0xFC, 
               0x04
           })
       }

Not:

        Method (_PSD, 0, NotSerialized)
       {
           Return (Package (0x05)
           {
               [b][color="#ff0000"]0x04[/color][/b], 
               Zero, 
               Zero, 
               0xFC, 
               0x04
           })
       }

This is down to a collective mistake, I'd say

D.

-----------------------------------------------------------------------------------------------------------------

OK SPOT POLE !!!

Do I amend the first post with a generic Scope (PR) with instructions of what values are variable and how to find them.....

OR do we start a new thread "Generic Scope (PR ) for speedstep"??

Please bare in mind this thread has gotten a tad long!

Cheers

D.

kdawg · November 18, 2009

This is down to a collective mistake, I'd say

D.

-----------------------------------------------------------------------------------------------------------------

OK SPOT POLE !!!

Do I amend the first post with a generic Scope (PR) with instructions of what values are variable and how to find them.....

OR do we start a new thread "Generic Scope (PR ) for speedstep"??

Please bare in mind this thread has gotten a tad long!

Cheers

D.

New Thread

Liquid Ice · November 18, 2009

I don't know what OS you have ? are you running Snow?
And you have changed your SMC kext no? if yes try with original SMC kext.

Try reinstalling your original SMC kext also try Master Chief's legacy SMC with your original SMC kext ( i think it's on page 18 of this thread, attachment called archive.zip.)

Also can you see LCP loaded in ioreg?

Cheers

D.

Thanks, I did a fresh install of snow 10.6, after moving archive.zip kext to E/E and now have speedstep working. I can see it stepping from x 6.0 to x 8.0.

I have to use Evoreboot.kext in E/E to get shut down and restart working.

Those are the only two things left i need to work on.

Thanks for all your help.

If anyone can help me with sleep / reboot and shutdown let me know :unsure:

MB: EP45-UD3L F7

OS: 10.6 (updating to 10.6.2 stay tuned for any changes)

UPDATE: Speedstep still working without LegacyACPI and LegacyAGPM. continuing with update.

E/E folder contains:

fakesmc.kext

EvOreboot.kext

LegacyHDA.kext

PlatformUUID.kext

LegacyACPI_SMC_PP.kext

LegacyAGPM.kext

VoodooMonitor.kext

FKA · November 18, 2009

Thanks for all your help.

If anyone can help me with sleep / reboot and shutdown let me know

Good news ...

Please see the gigabyte DSDT thread for sleep/ shutdown help ... I don't believe there is an answer just yet but some great minds are currently working on it

Peace out

D.

UPDATE: Speedstep still working without LegacyACPI and LegacyAGPM. continuing with update.

Note: LegacyAGPM is for GPU power management (I'd say quite important!).. MC's legacyAGPM kext stopped working with 10.6.2 ..

We're hoping has a new one on the way ....

D.

Liquid Ice · November 18, 2009

Good news ...

Please see the gigabyte DSDT thread for sleep/ shutdown help ... I don't believe there is an answer just yet but some great minds are currently working on it

Peace out

D.

Note: LegacyAGPM is for GPU power management (I'd say quite important!).. MC's legacyAGPM kext stopped working with 10.6.2 ..

We're hoping has a new one on the way ....

D.

I must have missed the GPU power management. Okay so my 9800 gtx+ is going to like that .. ill add it in the morning.

Right now 10.6.2 is fully up and running with low temps in the 30s.

Quick question with the dsdt you sent me, can i over clock safely. I didnt notice p-states defined. just wondering. (might be a noob question... boy this makes me feel real stupid)

thanks again

blackosx · November 18, 2009

OK SPOT POLE !!!
Do I amend the first post with a generic Scope (PR) with instructions of what values are variable and how to find them.....

OR do we start a new thread "Generic Scope (PR ) for speedstep"??

Please bare in mind this thread has gotten a tad long!

This thread is great, and a new one dedicated for Scope (_PR) is a good idea, as long as you don't mind running another thread!

FKA · November 18, 2009

I must have missed the GPU power management. Okay so my 9800 gtx+ is going to like that .. ill add it in the morning.
Right now 10.6.2 is fully up and running with low temps in the 30s.

Quick question with the dsdt you sent me, can i over clock safely. I didnt notice p-states defined. just wondering. (might be a noob question... boy this makes me feel real stupid)

thanks again :censored2:

Yes you can overclock - but you will need to run voodoopstate and pstatechanger again once you've OC'd to get new FID /VID

D.

scwhar · November 18, 2009

New thread please this one is too massive, I'm trying to make sense of it but ow.

Cheers

FKA · November 18, 2009

Post #1 updated ....

Sorry no new thread - I think I've got everything we need in post #1 ..

Please let me know if anything is missing or wrong - I'll spellcheck when I get back to a Mac - untill then you'll have to manage with my dyslexic (why is that word so hard to spell?!) text !!

D.

blackosx · November 18, 2009

Sorry no new thread - I think I've got everything we need in post #1 ..

Please let me know if anything is missing or wrong - I'll spellcheck when I get back to a Mac - untill then you'll have to manage with my dyslexic (why is that word so hard to spell?!) text !!

Good overhaul FormerlyKnownAs :wacko: I have given it a quick scan and I think it will help others a great deal. I will point to it from my threads.

mitch_de · November 19, 2009

Post #1 updated ....
Sorry no new thread - I think I've got everything we need in post #1 ..

D.

PERFECT - an ALLINONE Page (even i normally dont like ALLINONEs from Apple )

The DL Link to PstateChanger (Info+Controll App to Voodoo...) is Snow Leo only - any chance for the newest Leo build to ?

More an hint: Would be fine to add also always the unpatched dsdt.dsl on final dsdt_patched.dsl sharings.

So users can better see whats added or patched. Its near impossible to find out without having unpatched dsdt to conpare to that patched and also compare to own unpatched one - some MBs, even near same, have different dsdt (devices +/-, other changes)

mitch_de · November 19, 2009

I got my mVolts = zeros shown in PstateChanger fixed !

Was useACPI=yes (means voodoopower based use ACPI _PSS (dsdt) insted of computing it by cpu type).

One more thing:

superhai did it again : voodoopowermini SL is OUT!!!!

My abolute favorite for speedstepping : less cpu usage than the set of PstateChanger/VoodooPstate.kext.!!

I am 110% sure:

Even Fred Astaire would have used that for stepping !

scwhar · November 19, 2009

Post #1 updated ....

Sorry no new thread - I think I've got everything we need in post #1 ..

Hey that's great thanks, finally rid of nullcpupowermanagement here, the new first post is very clear makes it easy even for a muppet like me

10 p-states too

juanerson · November 19, 2009

Hi FormerlyKnownAs, thank you for your amazing work, and please sorry for my bad english. My situation is that Snow leopard recognize 3-pstates and I have native speedstep without kexts (only MB3,1 smbios), because I can see the frecuency changes from 1016-1200-1400 mhz with mark-i application, but my real speedstep should be 800-1200-1400-1600 mhz. I need add the others p-states right? Please, can you tell me where I can place the code? I dont found Scope (_PR). In my .dsl I have this:

*/

DefinitionBlock ("./dsdt.aml", "DSDT", 1, "HP ", "nc6xxxs", 0x00010000)

{

External (\_SB_.PCI0.C3D3)

External (\_SB_.C2AF._STA)

Name (C000, 0x00)

Name (C001, 0x00)

Processor (\_PR.CPU0, 0x01, 0x00001010, 0x06)

{

Name (C002, 0x00)

Method (CSTH, 0, NotSerialized)

{

If (LEqual (C002, 0x00))

{

Store (0x01, C002)

Store (0x00, \_SB.PCI0.LPCB.C005)

}

Store (\_SB.PCI0.LPCB.EC.C007 (), Local0)

Return (Local0)

}

Method (INI, 0, NotSerialized)

{

If (LAnd (And (\_SB.C008, 0x01000000), LEqual (C009 (), 0x04)))

{

\_SB.ISMI (0x3D, 0x00, 0x00, 0x00)

}

Method (PPC, 0, NotSerialized)

{

Return (0x00)

}

Processor (\_PR.CPU1, 0x02, 0x00001010, 0x06)

{

Method (PPC, 0, NotSerialized)

{

Return (0x00)

}

Method (C00A, 0, Serialized)

{

If (LGreater (\_SB.C00B, 0x00))

{

Subtract (\_SB.C00B, 0x01, Local1)

}

Else

{

Store (0x00, Local1)

}

...........

Thanks in advance.

ape_rez · November 20, 2009

Hey everybody.

I've been working on this pstate thing for awhile now, scanning this thread as much as I can. I've appended my cpu cst ist and pm tables in their corresponding places at the end of my dsdt.aml. I believe my pstates are working: cpu-i shows my multiplier changing, the cpu is running cooler than it was before, but I'm confused on three things:

1. CPUi does not show the FID and VID values I have entered into my DSDT, instead it shows lower values that I have no Idea where they came from. I've tried changing them to multiple values, but cpu-i doesn't reflect these changes, only IOregistry does. Voodoopstate only shows the same values as cpu-i as well. Why would it be doing this? Is this really a problem?

2. This is related to my first problem. The voltages I'm seeing in CPU-i are lower than I expected for my processor for the higher multiplier speedstates. Would limit my system?

3. My CPU idle temperatures are not as low as they were when i was simply running a disabler kext and sleepenabler. They are like 10 degrees hotter (I'm running like 55 degrees at idle versus running 45 degrees on my other setup). How can I achieve those temperatures with speedstepping?

I would really appreciate any help you all can give. I have attached a screenshot of the different FID and VID values, and a copy of my DSDT.aml.

fidvidproblem.tiff

dsdt.aml_2.zip

mitch_de · November 20, 2009

Most voodoopower based .kext didnt use _PSS (dsdt) data for their Pstates. They normally do compute them itself by cpy_type+FSB.

So it can happen, if you use voodoopower.kext (or all based .kext on src from superhai) that you get different Pstates.

To use YOUR _PSS enties , like AppleIntelCPU.kext you must set useACPI to YES , voodoopower.kext has that also that .kext comes with Pstatechanger .

voodoopowermini didnt has that useACPI.

That flag wasnt needed/used because at the beginning of speedstep on OS X near noone has an working BIOS with _PSS or dsdt injection with _PSS. So superhai made that pStates buildin into his kext.

Now, its better to use useACPI flag in such vooodoopwoer based .kext.

One problem was with the pstatechanger .kext that it doesnt showed the mVolts but correct VID (from _PSS).

I got fixed that by adding the VID>mVolts compute also in the useACPI method.

Look here: (scroll a bit down) Post 111

http://www.insanelymac.com/forum/index.php...90&start=90

agrajag · November 20, 2009

Shouldn't the _PSD method's last byte reflect the number of processors?

Method (_PSD, 0, NotSerialized)
	{
		Return (Package (0x05)
		{
			0x05, 
			Zero, 
			Zero, 
			0xFC, 
			0x0R
		})
	}

i.e. R is 4 for a Quad-core and 2 for a dual core CPU.

mitch_de · November 20, 2009

Shouldn't the _PSD method's last byte reflect the number of processors?
Method (_PSD, 0, NotSerialized)
	{
		Return (Package (0x05)
		{
			0x05, 
			Zero, 
			Zero, 
			0xFC, 
			0x0R
		})
	}
i.e. R is 4 for a Quad-core and 2 for a dual core CPU.

maybe. But i am 90% sure that that _PSD entry doesnt do anything realat all.

I cant see any differences if i have it or not - all is working even i dont have it in my dsdt!

So sometimes its better to aviod adding things that are not really needed in dsdt !

I would keep your dsdt as slim (less adding) as possible!

DSDT - Vanilla Speedstep - Generic Scope (_PR)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites