128 replies to this topic

[cparm]

hi,

i wondered how to set my vmin and vmax

as you can see here vmin=987 and vmax=1100





but accordding to the intel website those value should be vmax=1362.5mv and vmin=850mv

[mitch_de]

Maybe the calulation from the right VID to mV is other than expected.
For my knowledge there are 2 ways to calculate them , depends on cpu type.
Also an reason why for example MSR tool shows other mV than voodoopower , even both use same VID (hex)!

[hnak]

mitch_de, on Oct 1 2009, 07:47 PM, said:

THANKS!

But how can i set that PstateLimit High (fastest) to 1 ?
I started the Pstatechanger, PREFS and changed the P-Min (is that same as PstateLimitHigh in screenshoot i have in voodoopower?) but i only hear "DONG", error beep. If i leave the Pstatechanger and run again the vefore added new values are not saved. I clicked APPLY + SAVE but onl heared the DONG sound.
Also no .plist was created in the preferences (home).

I must have that Pstate Limit before i can load the .kext, because without that KP if short Pstate 0.

Can i put that key (which name ?) in the .kext itself as an workaround ?

Here the screenshoot of my voodoopower .plist, which works perfect chaning that Limit from 0 > 1

You hear "DONG" if you set pstate-min (highest) > p-state max (lowest). Did you change only pstate-min from default ?

[mitch_de]

I only want to change PstateLimitHigh (so named in voodoopower .plist, Screenshoot 2 post above) from 0 > 1.
What the key name in the pref i must change ? One was 0 one was -1 by default.

[hnak]

mitch_de, on Oct 1 2009, 11:23 PM, said:

I only want to change PstateLimitHigh (so named in voodoopower .plist, Screenshoot 2 post above) from 0 > 1.
What the key name in the pref i must change ? One was 0 one was -1 by default.

Set p-state max to 1 ( default = 0 ) and leave p-state max as is ( default = 4 ? ).

[hnak]

cparm, on Oct 1 2009, 09:02 PM, said:

as you can see here vmin=987 and vmax=1100
...
but according to the intel website those value should be vmax=1362.5mv and vmin=850mv

As far as I know, Intel Core CPU's voltage is calculated as ( maybe ) :
voltage = 850.0 + VID * 0.0125 ( desktop CPU )
  voltage = 712.5 + VID * 0.0125 ( mobile CPU )
and VoodooPower follows those equations.
Though VID-Voltage relationship is defined for VID = 0..0x3F, available max/min VIDs defined by BIOS may differ among CPU/MB, so the range is different from the widest range in spec.

[userx]

This works great. Thanks!

Any way of making a Sys Pref Pane for this instead of

using the App, or minimizing it to the menubar?

[hnak]

userx, on Oct 2 2009, 04:17 AM, said:

This works great. Thanks!

Any way of making a Sys Pref Pane for this instead of

using the App, or minimizing it to the menubar?

As the app needs to be resident, it is hard to do p-state switching solely by PrefPane.
It is possible in theory by splitting  app into daemon / PrefPane ( or converting it into toolbar app ), though it is not an easy programing exercise.

For now, just hide it from Apple Menu.

[mitch_de]

hnak, on Oct 2 2009, 01:52 AM, said:

Set p-state max to 1 ( default = 0 ) and leave p-state max as is ( default = 4 ? ).

Thanks will try that later and report.

[tdh]

Working well on the hp mini 2140 thanks!!

[rals2007]

hnak

Is it possible to make this kext a standalone (will work even without launching the app)?

Thanks,

[hnak]

rals2007, on Oct 7 2009, 08:06 AM, said:

hnak

Is it possible to make this kext a standalone (will work even without launching the app)?

Thanks,

Please read my first post --- at least, I could not make it.
If you are comfortable with 32bit, VoodooPower is all that you need.

[Brewers]

Works quite well with my E6600 and Snow Leopard, thanks!

I found out that CPU-X doesn't show the correct CPU frequency when this tool does set the CPU to a lower P-state, e.g. PStateChanger shows 1600Mhz (lowest PState), but CPU-X always shows 2400Mhz (stock freq). This was not the case with VoodooPower and CPU-X under Leopard. Did someone else observe this behaviour?

And, might it somehow be possible to add more PStates with this tool?
And of course... a toolbar app would be _very_ nice!

[hnak]

Brewers, on Oct 10 2009, 11:35 AM, said:

Works quite well with my E6600 and Snow Leopard, thanks!

I found out that CPU-X doesn't show the correct CPU frequency when this tool does set the CPU to a lower P-state, e.g. PStateChanger shows 1600Mhz (lowest PState), but CPU-X always shows 2400Mhz (stock freq). This was not the case with VoodooPower and CPU-X under Leopard. Did someone else observe this behaviour?

And, might it somehow be possible to add more PStates with this tool?
And of course... a toolbar app would be _very_ nice!

It's because VoodooPState.kext does not update CPU frequency variables of kernel. I thought it is not necessary as PStateChanger.app shows the values.

The number of p-state is the same as VoodooPower. You need to tweak the code if you want more.

I looked at a menubar app sample code, but Apple discourages ordinary applications to use the menubar.
1.0.2 shows workloads/pstates in doc icon when it's hidden. Just launch and hide it (command-H).

By the way, I use the same MB (P5B-E Plus) patching AppleYukon2 Info.plist.

[mitch_de]

Would be really nice if you adding that "changing freq for variables of kernel" so that an sysctl -a or any other tool reads out that can see the pstate changes =MHz changes also !
Only MSR read Tools like MSR would be able to readout the real MHz, but for my knowledge no MSR SL is available. And also if i use MSR after some time (minutes) it stalls may whole system.
Thanks for already done great work !!!

[hnak]

mitch_de, on Oct 10 2009, 05:47 PM, said:

Would be really nice if you adding that "changing freq for variables of kernel" so that an sysctl -a or any other tool reads out that can see the pstate changes =MHz changes also !
Only MSR read Tools like MSR would be able to readout the real MHz, but for my knowledge no MSR SL is available. And also if i use MSR after some time (minutes) it stalls may whole system.
Thanks for already done great work !!!

I  made a build to reflect frequency change and updated 1.0.2 links in the first post.

[pug999]

when wake form sleep,  


sleep will kill "Auto pstate"  ,

have to cancel  &  select "Auto" once

Intel T3200 2.0GHZ (Pentium Dual-Core)
voodoopower 1.2.3 fine
but only 32bit in snowleopoard

[hnak]

pug999, on Oct 12 2009, 01:50 AM, said:

when wake form sleep,  


sleep will kill "Auto pstate"  ,

have to cancel  &  select "Auto" once

Intel T3200 2.0GHZ (Pentium Dual-Core)
voodoopower 1.2.3 fine
but only 32bit in snowleopoard

It seems to be an application side problem. Quit and relaunch works ?
Unfortunately, however, sleep never works on my system, so the the symptom cannot be reproducible here and I cannot fix it.
I wish someone who has sleep-enabled system solve this problem.

[pug999]

Quit and relaunch works ?


Yes,Quit and relaunch is ok..

But, no need.
Just do once   ----- cancel & select "Auto"

[hnak]

pug999, on Oct 12 2009, 07:00 AM, said:

Quit and relaunch works ?


Yes,Quit and relaunch is ok..

So the problem is not in kext but application. It should be easy if my system could sleep...