Jump to content

New version 1.1 of GenericCPUPowerManagement

Superhai

By Superhai,
in New Releases and Updates

 Share
625 posts in this topic

Recommended Posts

Superhai
Superhai
Posted
  • Author
Posted
System working slower with 1.1 than with 1.0.20. Benching low in Geekbench and OpenGL Viewer (Test 2.1, which is cpu intensive).

If you notice the "Frequency Highest" is being reported as 0x1f9 which is 505 MHz, when it actually should be 2500 MHz..... thanks

 

The frequency issue should be fixed with latest download. That may also cause problems with speed as well.

 

Also, limit function does'nt work, maybe i don't understand what i have to do with, but when i write 1167 or 1200 to limit at 1167 Mhz my proc on battery, it just stop throttling on new version (before not but it stucked at 1000 (minimal freq)), and it can stuck at 1500 if roc was at 1500 before unpluging...

 

You limit per p-state not frequency.

 

I will make a instruction manual for the kext that will explain all the options.

 

so i will post it later if u need it.

 

yes please

 

Yes, the new app should be able to access via system preferences. That would be fantastic!

 

It is in the plans, but the app (or prefpane) is lowest priority now. And it would be nice to hear what you want in it if i create a prefpane. I want to know what controls you want and need.

 

After download and loading newest kext again, common hang occure,

 

I think I have removed the dividezero error.

talisman
talisman
Posted
Posted
The frequency issue should be fixed with latest download. That may also cause problems with speed as well.

 

Im not sure what you mean by latest download as I downloaded the new kext and the commandline app this morning (~ 6 AM EST USA 24th Nov 08). Did you release something after that?? Thanks a heap.

Superhai
Superhai
Posted
  • Author
Posted
Im not sure what you mean by latest download as I downloaded the new kext and the commandline app this morning (~ 6 AM EST USA 24th Nov 08). Did you release something after that?? Thanks a heap.

I am not sure about your time, but i uploaded it around 7-8 hours ago. :D

mitch_de
mitch_de
Posted
Posted
The help document is here

GenericCPUPowerManagement Help

THANKS, will help + clear most things in ONE !

Q:

If i do overwrite Voltages i get different status (from contol command tool)

bash-3.2# /Users/ami/Desktop/SPEEDSTEP/gcpupmcontrol status (overwrite voltage )

**** CPU: 1 - (CPU0) ****

P-State 4 (false) [06/00/21]

**** CPU: 2 - (CPU1) ****

P-State 4 (false) [06/00/21]

bash-3.2# /Users/ami/Desktop/SPEEDSTEP/gcpupmcontrol status (not overwrite voltage)

**** CPU: 1 - (CPU0) ****

P-State 4 (true) [06/00/27]

**** CPU: 2 - (CPU1) ****

P-State 4 (true) [06/00/27]

What does this true/false means ?

 

Also if i do an kextunload CPU stays at last P-state (for example 3, for me its 1800 MHZ of 2660 max).

So its not running at highest MHZ anymore. I tried it to get max CPU load (with benches, load >> 50% ) but it stays at state 3 (of 4).

Would it be possible to do an "set Pstate to 0=fastest MHZ" if kext is unlaoded/deaktivated within the kext code ?

talisman
talisman
Posted
Posted
I am not sure about your time, but i uploaded it around 7-8 hours ago. ;)

 

Thanks Superhaı.... great job!!!

 

Just that now ıts reportıng a max frequency of 2800 MHz when ıt should be 2500 MHz..... don't know ıf I should worry about that.....

 

./gcpupmcontrol frequency
 **** CPU: 1 - (CPU0) ****
 2800 MHz
 **** CPU: 2 - (CPU1) ****
 2800 MHz

 

And I don't think it should have a 2400 MHz freq:

 

./gcpupmcontrol frequency
 **** CPU: 1 - (CPU0) ****
 2400 MHz
 **** CPU: 2 - (CPU1) ****
 2400 MHz

 

This is what I have:

 

./gcpupmcontrol all
GenericCPUPowerManagement.kext 1.1.0 (Release) Nov 24 2008 15:59:32 
 CPU: 2 x Mobile Intel(R) Core(TM)2 Duo CPU	 T9300  @ 2.50GHz (10676)
P-States: 12 - Frequency 600 MHz -> 2800 MHz - Voltage 1137 mV -> 1137 mV 
	  [86-00-22] -> [4c-00-22] 
Auto throttle on at startup: true, Voltage Override: false, Timer: 250 ms

 

 

sysctl says:

 

sysctl -a | grep hw.cpufreq
 kern.exec: unknown type returned
 hw.cpufrequency = 600000000
 hw.cpufrequency_max: 2800000000
 hw.cpufrequency_min: 600000000
 hw.cpufrequency: 600000000

 

Don't know whats up!!!

Wiwi
Wiwi
Posted
Posted
It is in the plans, but the app (or prefpane) is lowest priority now. And it would be nice to hear what you want in it if i create a prefpane. I want to know what controls you want and need.

 

- For me, i just want to check temps, voltage and frequencies and battery status (so even a dashboard widget could be good !)

- Also i think for some guys who want to set thereholds or voltage for undervolting it could be cool to mod plist options (thanks for documentation !!!) via a prefpane/widget instead of use the terminal or reinstall the kext... (even if they always have to restart !? perhaps not with a kextload / kextunload script ?)

- If this prefpane/widget could control behaviour of clamshelldisplay too it would be very good ! (just in bonus !)

 

That's all...?

ferywu
ferywu
Posted
Posted
Update on 23th November 2008

 

New today is the release of the Command Line Control Tool. Found under download. The new gui app will be available during next week hopefully.

 

Thank and thank again, now loading without any error.

 

Some info

1. option cpu, status report false output

2. option voltage report 1500mV , on xp, vista, other bsd, linux, and bios report max 1400mV

3. option all and kernel log when loading kext report max freq 2000MHz and the voltage at 1350mV, differ from point 2

4. sysctl freq min and max point the same value ( 2000MHz)

5. Your app report lost the kext, and the value of frequency and voltage are weird, i think old app still don't matching the new design of yout code

6. Great it can be goes under 1000MHz (it displayed as 800MHz)

 

bash-3.2# ./gcpupmcontrol about
GenericCPUPowerManagement.kext 1.1.0 (Debug) Nov 24 2008 15:59:20

 

bash-3.2# ./gcpupmcontrol all
GenericCPUPowerManagement.kext 1.1.0 (Debug) Nov 24 2008 15:59:20 
 CPU: 2 x Desktop AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (20fb1)
P-States: 1 - Frequency 2000 MHz -> 2000 MHz - Voltage 1350 mV -> 1350 mV 
	  [0c-00-08] -> [0c-00-08] 
Auto throttle on at startup: true, Voltage Override: false, Timer: 250 ms

 

bash-3.2# ./gcpupmcontrol cpu
**** CPU: 1 - (CPU1) ****
P-State 0 (false) [00/00/00] 
**** CPU: 2 - (CPU2) ****
P-State 0 (false) [00/00/00]

 

bash-3.2# ./gcpupmcontrol frequency
**** CPU: 1 - (CPU1) ****
800 MHz
**** CPU: 2 - (CPU2) ****
800 MHz

 

bash-3.2# ./gcpupmcontrol load
**** CPU: 1 - (CPU1) ****
Total 4% System 1% User 3% Idle 95% Nice 0%
**** CPU: 2 - (CPU2) ****
Total 5% System 1% User 4% Idle 94% Nice 0%

 

bash-3.2# ./gcpupmcontrol profile
0 Threshold 25% Hysteresis 5 Valid P-States 0 to 0

 

bash-3.2# ./gcpupmcontrol status
**** CPU: 1 - (CPU1) ****
P-State 0 (false) [00/00/00] 
**** CPU: 2 - (CPU2) ****
P-State 0 (false) [00/00/00]

 

bash-3.2# ./gcpupmcontrol thermal
**** CPU: 1 - (CPU1) ****
0° to tjMax
**** CPU: 2 - (CPU2) ****
0° to tjMax

 

bash-3.2# ./gcpupmcontrol voltage
**** CPU: 1 - (CPU1) ****
1550 mV
**** CPU: 2 - (CPU2) ****
1550 mV

 

bash-3.2# sysctl -a | grep hw.cpufreq
kern.exec: unknown type returned
hw.cpufrequency = 800000000
hw.cpufrequency_max: 2000000000
hw.cpufrequency_min: 2000000000
hw.cpufrequency: 800000000

 

bash-3.2# kextstat | grep superhai
  92	0 0x1abcf000 0xb000	 0xa000	 com.superhai.driver.GenericCPUPowerManagement (1.1.0) <18 12 7 5 4 2>

 

sudo dmesg | grep GenericCPUPowerManagement
GenericCPUPowerManagement: [Debug] Initialization : Probe
GenericCPUPowerManagement: [Debug] Found 2 I/O Kit CPU's and 2 ACPI CPU's
GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete
GenericCPUPowerManagement: [Debug] Initialization : Start
GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.0 (Debug) Nov 24 2008 15:59:20 [1050]
GenericCPUPowerManagement: (C) 2008 Superhai, All Rights Reserved
GenericCPUPowerManagement: [Debug] P-State 0: 2000 MHz [0C-00] - 1350 mV [08]
GenericCPUPowerManagement: [Debug] CPU 0: CTL 0000 TR 000
GenericCPUPowerManagement: [Debug] CPU 1: CTL 0000 TR 000
GenericCPUPowerManagement: [Debug] Last loop used 0 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0218 highest P-State 0 (approximate) and frequency 800
GenericCPUPowerManagement: [Debug] CPU 1 load 0198 P-State 0 (approximate) and frequency 800
GenericCPUPowerManagement: [Debug] Last loop used 76 us
GenericCPUPowerManagement: [Debug] CPU 0 load 1023 highest P-State 0 (approximate) and frequency 800
GenericCPUPowerManagement: [Debug] CPU 1 load 0085 P-State 0 (approximate) and frequency 800
GenericCPUPowerManagement: [Debug] Last loop used 94 us

 

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Characteristics"
"Characteristics" = {"Voltage Highest"=0x546,"Signature"=0x20fb1,"CPU Count"=0x2,"Build Date"="Nov 24 2008","Constant TSC"=No,"Voltage Lowest"=0x546,"VID Lowest"=0x8,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.0","Individual Core Control"=No,"Frequency Lowest"=0x7d0,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x1,"Mobile CPU"=No,"Build Time"="15:59:20","Auto Throttle On Startup"=Yes,"Build Config"="Debug","Frequency Highest"=0x7d0,"String"="AMD Athlon(tm) 64 X2 Dual Core Processor 3800+","DID Highest"=0x0,"FID Lowest"=0xc,"VID Highest"=0x8,"FID Highest"=0xc,"P-State Count"=0x0}

 

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Status"
"Status" = {"Threshold"=0xfa,"Profile"=0x0,"CPU"=({"Load"={"User"=0xae,"Accumulated"=0x13e,"System"=0x90,"Idle"=0x2c0,"Nice"=0x0},"Thermal Readout"=0x0,"Frequency"=0x320,"Current P-State"=0x0,"DID"=0x0,"VID"=0x0,"FID"=0x0,"Voltage"=0x60e,"Exact"=No,"Name"="CPU1"},{"Load"={"User"=0x14e,"Accumulated"=0x369,"System"=0x21b,"Idle"=0x95,"Nice"=0x0},"Thermal Readout"=0x0,"Frequency"=0x320,"Current P-State"=0x0,"DID"=0x0,"VID"=0x0,"FID"=0x0,"Voltage"=0x60e,"Exact"=No,"Name"="CPU2"}),"Timer Timeout (ms)"=0xfa,"P-State Limit"=0x0,"P-State Capability"=0x0,"Kernel Extension Ready"=Yes,"Hysteresis"=0x32,"Auto Throttle Running"=Yes}

post-39951-1227608529_thumb.png

talisman
talisman
Posted
Posted
Thank and thank again, now loading without any error.

 

Some info

1. option cpu, status report false output

2. option voltage report 1500mV , on xp, vista, other bsd, linux, and bios report max 1400mV

3. option all and kernel log when loading kext report max freq 2000MHz and the voltage at 1350mV, differ from point 2

4. sysctl freq min and max point the same value ( 2000MHz)

5. Your app report lost the kext, and the value of frequency and voltage are weird, i think old app still don't matching the new design of yout code

6. Great it can be goes under 1000MHz (it displayed as 800MHz)

 

The app does not work with this 1.1. It worked with 1.0.20. This is mentioned in the first post. It also said that the app will be ready in a few days....

mitch_de
mitch_de
Posted
Posted
First, thank you Superhai! :hysterical:

I had random freezes with the last release version, perhaps it's because i haven't removed the OpenHaltRestart kext?

I also use OH.kext , no freezes with C2D (and V 1.1 superhai).

OpenHalt could only freeze your "Mac" on the time of shutdown - if somethings going wrong.

I dont think OH.kext will have any effekt (at least for Dual Core CPUs) under normal condition.

But i heared also that some people with 4 cores CPU have some problems using OH.kext.

So, if superhais works i would really remove OH with 4 Cores CPUs !

VirtualGuitarist
VirtualGuitarist
Posted
Posted
I also use OH.kext , no freezes with C2D (and V 1.1 superhai).

OpenHalt could only freeze your "Mac" on the time of shutdown - if somethings going wrong.

I dont think OH.kext will have any effekt (at least for Dual Core CPUs) under normal condition.

But i heared also that some people with 4 cores CPU have some problems using OH.kext.

So, if superhais works i would really remove OH with 4 Cores CPUs !

 

Removed, thanks for your answer! :hysterical:

In fact with my brand new quad i have experimented freezes around an hour after booting. Now i will let my system on during 24h to see if there's more freezes and report eventually, thanks!

sonotone
sonotone
Posted
Posted
It is in the plans, but the app (or prefpane) is lowest priority now. And it would be nice to hear what you want in it if i create a prefpane. I want to know what controls you want and need

I was thinking about something like coolbook features: possibility to define stepping and voltages profiles on both battery and AC.

Superhai
Superhai
Posted
  • Author
Posted
THANKS, will help + clear most things in ONE !

Q:

If i do overwrite Voltages i get different status (from contol command tool)

 

What does this true/false means ?

 

If it is a true P-State from the table or if it is only close to it. 

Also if i do an kextunload CPU stays at last P-state (for example 3, for me its 1800 MHZ of 2660 max).

 

 

So its not running at highest MHZ anymore. I tried it to get max CPU load (with benches, load >> 50% ) but it stays at state 3 (of 4).

Would it be possible to do an "set Pstate to 0=fastest MHZ" if kext is unlaoded/deaktivated within the kext code ?

 

Yes that functionality is coming. Or rather it will throttle back to original state, as it did with the former kext. 

 

Just that now ıts reportıng a max frequency of 2800 MHz when ıt should be 2500 MHz..... don't know ıf I should worry about that.....

 

Just a small calculation formula mistake. It is fixed now. I have had to much to do, so I have made a few really stupid mistakes.

 

- For me, i just want to check temps, voltage and frequencies and battery status (so even a dashboard widget could be good !)

- Also i think for some guys who want to set thereholds or voltage for undervolting it could be cool to mod plist options (thanks for documentation !!!) via a prefpane/widget instead of use the terminal or reinstall the kext... (even if they always have to restart !? perhaps not with a kextload / kextunload script ?)

- If this prefpane/widget could control behaviour of clamshelldisplay too it would be very good ! (just in bonus !)

 

The first I will make is an app similar to the previous, except it will show the status for each core as well. 

 

 

For editing the Info.plist I will keep it this way. I will not make an app to modify those files. The values are not supposed to be easily changed so that will stay the way it is now.

 

Clamshelldisplay will eventually retire, as the dsdt mods available will do the same job now. I will instead make a acpibacklight.kext to control the acpi method of backlight control, which could be controlled from the same prefpane.

 

 

 

Thank and thank again, now loading without any error.

 

Some info

1. option cpu, status report false output

2. option voltage report 1500mV , on xp, vista, other bsd, linux, and bios report max 1400mV

3. option all and kernel log when loading kext report max freq 2000MHz and the voltage at 1350mV, differ from point 2

4. sysctl freq min and max point the same value ( 2000MHz)

5. Your app report lost the kext, and the value of frequency and voltage are weird, i think old app still don't matching the new design of yout code

6. Great it can be goes under 1000MHz (it displayed as 800MHz)

 

Thanks for the report, I need to still make some adjustement for the AMD cpus. 

 

First, thank you Superhai! :wacko:

I had random freezes with the last release version, perhaps it's because i haven't removed the OpenHaltRestart kext?

 

This kext is providing the same functionality so that kext is not needed alongside this.

VirtualGuitarist
VirtualGuitarist
Posted
Posted
A new version uploaded, which should solve some issues.

I just realized that the freezes i had are all related to audio (testing some plugins with Logic). Perhaps timing issues when throttling occured? Or simply bad plugins?

I will test your new one and report (no chance at this time, i had a new freeze few hours ago). Dunno if it's related, but i got this strange error in log :

26/11/08 04:17:53 kernel dos2unixtime(): month value out of range (15)

Perhaps a problem with localtime-toggle...

mitch_de
mitch_de
Posted
Posted
I just realized that the freezes i had are all related to audio (testing some plugins with Logic). Perhaps timing issues when throttling occured? Or simply bad plugins?

I will test your new one and report (no chance at this time, i had a new freeze few hours ago). Dunno if it's related, but i got this strange error in log :

26/11/08 04:17:53 kernel dos2unixtime(): month value out of range (15)

Perhaps a problem with localtime-toggle...

If gooten this 26/11/08 04:17:53 kernel dos2unixtime(): month value out of range (15) also (longer time ago) , but i think it was by running n (Voodoo 9.5 Alpha ?) not the orig. vanilla kernel.

 

SUPERHAI:

Compared to the V 1.0.20 i get near no slowest MHZ anymore running lastest kext. !

I changed AC trottle to 300 (up) and it still didnt go on slowest MHZ.

I run itunes - CPU load much less 20% !!!

With an trottle of 200 (version 1.0.20) i get with same itunes my slowes 1600 MHZ ; with latest , even trottle much higher at 300, it stays at 1900 MHZ (one step up the slowest).

talisman
talisman
Posted
Posted
Just a small calculation formula mistake. It is fixed now. I have had to much to do, so I have made a few really stupid mistakes.

 

Perfecto..... everything shipshape.... thanks a heap....

 

 

By the way.... ever heard of int speakers crackling at sound initiation.....

 

 

or the clock running slow in spite of enabling auto update...???

VirtualGuitarist
VirtualGuitarist
Posted
Posted
If gooten this 26/11/08 04:17:53 kernel dos2unixtime(): month value out of range (15) also (longer time ago) , but i think it was by running n (Voodoo 9.5 Alpha ?) not the orig. vanilla kernel.

Interesting... I use the Modbin kernel (the one in Kalyway 10.5.3 ComboUpdate).

Other strange thing too, in System Profiler i read 6Mo L2 cache for my Q9550 in lieu of 12Mo (other values are correct) same thing with my previous PIV 530 3ghz (512 in lieu of 1024 Ko).

 

EDIT: A "mini-freeze" (mouse and screen non responsive during ~20 sec.) occured with the last version, this time with MPlayer OSX Extended (http://mplayerosx.sttz.ch/), when attempting to switch an xvid to fullscreen during play. This don't happen with Quicktime.

 

UPDATE: No way. A new freeze occured ~3 hours after boot, this time i was converting a video with avidemux. Without the kext, everything worked fine during all night.

Carstiman
Carstiman
Posted
Posted

Hello the GenericIntelCPUPowerManagement.kext works for me if i run my Intel Core Duo E7200 OC to 3 GHz.

If i set it up to 3,18 GHz (333 x 9,5) the Sytem Profiler and CPU-X shows me only 3 GHZ and CPU-X shows me that it run only with (9 x 333) (Without the kext it is shown right)

 

The GenericCPUPMControl App start´s shows something and lose the connection to the GenericIntelCPUPowerManagement.kext

 

The old Kext does it all right works faster (Xbench) and the App got connection too.

 

Still nice work, thanks :unsure:

 

Kalyway Leopard 10.5.5 / Intel Core Duo E7200 / P5K Pro / 4 GB DDR2 1066 / Gforce 8800 GS

B612
B612
Posted
Posted

Dear Superhai,

I am using a retail installation of Leopard, booting my kexts from EFI partition (see my specs in the signature).

 

At the moment, the only CPU related kext I am using is IntelCPUPMDisabler.

 

All the non-vanilla kexts I am using are:

LegacyJMicronATA

LegacyAppleIntelPIIXATA

LegacyIOAHCIBlockStorage

LegacyAppleAHCIPort

LegacyHDAController

LegacyHDAPlatformDriver

HDAEnabler

IntelCPUPMDisabler

OpenHaltRestart

AppleDecrypt

SMBIOSResolver

 

Do you think I would need your GenericCPUPowerManagement? Would I need to delete IntelCPUPMDisabler once I use your kext?

Thank you.

mitch_de
mitch_de
Posted
Posted
Dear Superhai,

I am using a retail installation of Leopard, booting my kexts from EFI partition (see my specs in the signature).

 

At the moment, the only CPU related kext I am using is IntelCPUPMDisabler.

 

All the non-vanilla kexts I am using are:

LegacyJMicronATA

...

IntelCPUPMDisabler

OpenHaltRestart

AppleDecrypt

SMBIOSResolver

 

Do you think I would need your GenericCPUPowerManagement? Would I need to delete IntelCPUPMDisabler once I use your kext?

Thank you.

 

Dont delete IntelCPUPMDisabler , its for disabling to load AppleIntelCPU driver which causes immediatly Kernel Panic - well known by the 10.5 softwareupdates without netkas guide tio avoid loading of that kext !

 

superhais speedstep works without that and didnt need an special kernel (vaniall works!).

the GenericCPUPowerManagement works with without any need of Apple drivers !

B612
B612
Posted
Posted
Dont delete IntelCPUPMDisabler , its for disabling to load AppleIntelCPU driver which causes immediatly Kernel Panic - well known by the 10.5 softwareupdates without netkas guide tio avoid loading of that kext !

 

superhais speedstep works without that and didnt need an special kernel (vaniall works!).

the GenericCPUPowerManagement works with without any need of Apple drivers !

 

So is there a reason why I should use GenericCPUPowerManagement, considering I am using a Vanilla Kernel? Would you do it if you were in my shoes?

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...