New version 1.1 of GenericCPUPowerManagement

[Nick14]

I installed 1.1.2 version on my Aspire One (boot 132, Leo 10.5.5) with Voodoo RC. I recived kernels panic wich I supose wa sconnected with sound generation (KP occurs during start-up sound of Skype, sound of sutter when I grab screen, and when I run Itunes -- sound was chopped when cpu goes down to 796 MHz).

 

1st attempt to grab a screen [apple+shift+3]

 

 

2nd attempt to grab a screen [apple+shift+3]

 

Skype is starting

 

 

 

 

iTUnes

 

 

On Shut Down after removing GenericCPU kext:

 

 

And finally I grab a screen: look at Freq on CPU0... 6368 MHz

 

Why do you run Speedstep on your Atom It only uses like 5w

[mitch_de]

I agree !

ATOM CPU itself is very less in power consumption !

The % of power usage of whole system (TFT+Mainboard+RAM+GPU+HD/SSD) is much less than 20 %.

Even if you would save 50%or more of the CPU power usage (which will be hard to get) , your accu time will be less than 10% longer, which is not really much.

Dont forget that this .kext (and if running COntrol App) takes some cpu cycles to do the work !

I would say: Experimental+Interesting but really not helpful for ATOM based Netbooks.

Maybe the future 2 core ATOMS, take more watts , will have an advantage using speedstep.

[Wiwi]

This is output of my mother AMD 64 :

 

Problems : Mouse hung and lower PState is 1800MHz (in ubuntu 1000MHz), App crash on startup (show 9999MHz !!)

 

bash-3.2# sudo dmesg | grep GenericCPUPowerManagement
GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Release) Dec  5 2008 04:07:15 [1050]
GenericCPUPowerManagement: (C) 2008 Superhai, All Rights Reserved
GenericCPUPowerManagement: [Warning] Unloading
GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Release) Dec  5 2008 04:07:15 [1050]
GenericCPUPowerManagement: (C) 2008 Superhai, All Rights Reserved
GenericCPUPowerManagement: [Warning] Unloading
GenericCPUPowerManagement: [Debug] Initialization : Probe
GenericCPUPowerManagement: [Debug] Found 1 I/O Kit CPU's and 2 ACPI CPU's
GenericCPUPowerManagement: [Debug] AMD PN 06101010 12060808
GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete
GenericCPUPowerManagement: [Debug] Initialization : Start
GenericCPUPowerManagement: [Debug] Attempting BIOS control handover
GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Debug) Dec  5 2008 04:20:41 [1050]
GenericCPUPowerManagement: (C) 2008 Superhai, All Rights Reserved
GenericCPUPowerManagement: [Debug] P-State 0: 2400 MHz [10-00] - 1350 mV [08]
GenericCPUPowerManagement: [Debug] P-State 1: 2200 MHz [0E-00] - 1350 mV [08]
GenericCPUPowerManagement: [Debug] P-State 2: 2000 MHz [0C-00] - 1350 mV [08]
GenericCPUPowerManagement: [Debug] P-State 3: 1800 MHz [0A-00] - 1350 mV [08]
GenericCPUPowerManagement: [Debug] CPU 0: CTL 1008 TR 000
GenericCPUPowerManagement: [Debug] Last loop used 0 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0315 P-State 0 (exact) and frequency 2400
GenericCPUPowerManagement: [Debug] Last loop used 46 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0093 P-State 0 (exact) and frequency 2400
GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 3 - Requesting 0A08
GenericCPUPowerManagement: (AMD PowerNow!) Result code 2GenericCPUPowerManagement: [Debug] Last loop used 1020306 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0449 P-State 0 (exact) and frequency 2400
GenericCPUPowerManagement: [Debug] Last loop used 64 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0170 P-State 3 (exact) and frequency 1800
GenericCPUPowerManagement: [Debug] Last loop used 68 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0205 P-State 3 (exact) and frequency 1800
GenericCPUPowerManagement: [Debug] Last loop used 62 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0173 P-State 3 (exact) and frequency 1800
GenericCPUPowerManagement: [Debug] Last loop used 60 us
GenericCPUPowerManagement: [Debug] CPU 0 load 0193 P-State 3 (exact) and frequency 1800

"Characteristics" = {"Voltage Highest"=0x546,"Signature"=0x20ff2,"Front Side Bus Indicated"=0x2fec110,"CPU Count"=0x1,"Build Date"="Dec  5 2008","Constant TSC"=No,"Voltage Lowest"=0x546,"Front Side Bus"=0x2fec110,"VID Lowest"=0x8,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.2","Individual Core Control"=No,"Frequency Lowest"=0x3e8,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x1,"Mobile CPU"=No,"Build Time"="04:20:41","Auto Throttle On Startup"=Yes,"Build Config"="Debug","Frequency Highest"=0x960,"String"="AMD Athlon(tm) 64 Processor 3800+","DID Highest"=0x0,"FID Lowest"=0x2,"VID Highest"=0x8,"FID Highest"=0x10,"P-State Count"=0x3}

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0x267aadcc,"Profile"=0x0,"CPU"=({"Load"={"User"=0x77,"Accumulated"=0xb7,"System"=0x40,"Idle"=0x347,"Nice"=0x0},"Clock Modulation"=0x0,"Frequency"=0x708,"Current P-State"=0x3,"DID"=0x0,"VID"=0x8,"Thermal Readout"=0x0,"FID"=0xa,"Voltage"=0x546,"Exact"=Yes,"Name"="CPU0"}),"Timer Timeout (ms)"=0xfa,"P-State Limit"=0x0,"P-State Capability"=0x0,"Current Latency"=0x64,"Kernel Extension Ready"=Yes,"Hysteresis"=0x32,"Auto Throttle Running"=Yes,"Routine Payload TSC"=0x23724}

[coccolino_dbro]

Same hangups here (not only mouse, but overall system periodic hangups) on Turion64, only 2 p-states detected and application crashes at startup. With previous version p-states were corectly detected, although throtling wasn't featured.

 

bash-3.2# sudo dmesg | grep Generic

 

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Release) Dec 5 2008 04:07:15 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Warning] Unloading

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Release) Dec 5 2008 04:07:15 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Warning] Unloading

GenericCPUPowerManagement: [Debug] Initialization : Probe

GenericCPUPowerManagement: [Debug] A/C Power Connected

GenericCPUPowerManagement: [Debug] Found 1 I/O Kit CPU's and 1 ACPI CPU's

GenericCPUPowerManagement: [Debug] AMD PN 080A0008 1E08160A

GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete

GenericCPUPowerManagement: [Debug] Initialization : Start

GenericCPUPowerManagement: [Debug] Attempting BIOS control handover

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Debug) Dec 5 2008 04:20:41 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Debug] P-State 0: 1800 MHz [0A-00] - 1300 mV [0A]

GenericCPUPowerManagement: [Debug] P-State 1: 1600 MHz [08-00] - 1250 mV [0C]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 080A TR 000

GenericCPUPowerManagement: [Debug] Last loop used 0 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0137 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] Last loop used 54 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0105 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] Last loop used 78 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0053 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] Last loop used 67 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0363 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462746 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0458 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462634 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0455 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462753 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0446 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462718 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0722 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462687 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0710 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462706 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0526 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462748 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0482 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462705 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0425 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462603 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0444 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462735 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0426 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462714 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0538 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462633 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0495 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462768 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0532 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code 1GenericCPUPowerManagement: [Debug] Last loop used 1462793 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0434 P-State 1 (approximate) and frequency 1600

GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0A0A

GenericCPUPowerManagement: (AMD PowerNow!) Result code

 

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

 

bash-3.2# ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Characteristics"

 

"Characteristics" = {"Voltage Highest"=0x514,"Signature"=0x20f42,"Front Side Bus Indicated"=0x2faf080,"CPU Count"=0x1,"Build Date"="Dec 5 2008","Constant TSC"=No,"Voltage Lowest"=0x3e8,"Front Side Bus"=0x2faf080,"VID Lowest"=0x16,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.2","Individual Core Control"=No,"Frequency Lowest"=0x320,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x1,"Mobile CPU"=No,"Build Time"="04:20:41","Auto Throttle On Startup"=Yes,"Build Config"="Debug","Frequency Highest"=0x708,"String"="AMD Turion 64 Mobile Technology MT-34","DID Highest"=0x0,"FID Lowest"=0x0,"VID Highest"=0xa,"FID Highest"=0xa,"P-State Count"=0x1}

 

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

 

bash-3.2# ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Status"

 

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0xffffffffda9a778b,"Profile"=0x0,"CPU"=({"Load"={"User"=0x5,"Accumulated"=0x1ac,"System"=0x1a7,"Idle"=0x252,"Nice"=0x0},"Clock Modulation"=0x0,"Frequency"=0x640,"Current P-State"=0x1,"DID"=0x0,"VID"=0xa,"Thermal Readout"=0x0,"FID"=0x8,"Voltage"=0x514,"Exact"=No,"Name"="CPU0"}),"Timer Timeout (ms)"=0xfa,"P-State Limit"=0x0,"P-State Capability"=0x0,"Current Latency"=0x64,"Kernel Extension Ready"=Yes,"Hysteresis"=0x32,"Auto Throttle Running"=Yes,"Routine Payload TSC"=0xffffffff9878cb91}

[macNApiecu]

I agree !

ATOM CPU itself is very less in power consumption !

The % of power usage of whole system (TFT+Mainboard+RAM+GPU+HD/SSD) is much less than 20 %.

Even if you would save 50%or more of the CPU power usage (which will be hard to get) , your accu time will be less than 10% longer, which is not really much.

Dont forget that this .kext (and if running COntrol App) takes some cpu cycles to do the work !

I would say: Experimental+Interesting but really not helpful for ATOM based Netbooks.

Maybe the future 2 core ATOMS, take more watts , will have an advantage using speedstep.

 

I use speedstep because it's possible But seriously would be great that all kext would be universal. With voodoo RC and 1.0.20 all is ok, with 1.1 only KP during Shut Down, with 1.1.2 is as you seen above...

10% from 2h is 12min, from 6 cell is... etc so its nothing stupid.

[Goron]

Hmm, new version of .kext still autothrottles with wrong Frequencies ...

 

sh-3.2# dmesg | grep GenericCPUPowerManagement

GenericCPUPowerManagement: [Warning] Your FSB is out of bounds, attempting to fix

GenericCPUPowerManagement: [Warning] Your CPU supports constant TSC but only in C0 and C1, you should disable C2+ states

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Release) Dec 3 2008 18:46:11 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Warning] Unloading

GenericCPUPowerManagement: [Warning] Your FSB is out of bounds, attempting to fix

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Release) Dec 5 2008 04:07:15 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

sh-3.2#

 

sh-3.2# ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Characteristics"

"Characteristics" = {"Voltage Highest"=0x52d,"Signature"=0x6fd,"Front Side Bus Indicated"=0xbebc200,"CPU Count"=0x2,"Build Date"="Dec 5 2008","Constant TSC"=Yes,"Voltage Lowest"=0x4a3,"Front Side Bus"=0x81b3200,"VID Lowest"=0x1d,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.2","Individual Core Control"=No,"Frequency Lowest"=0x330,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x0,"Mobile CPU"=No,"Build Time"="04:07:15","Auto Throttle On Startup"=Yes,"Build Config"="Release","Frequency Highest"=0x550,"String"="Intel® Pentium® Dual CPU E2180 @ 2.00GHz","DID Highest"=0x0,"FID Lowest"=0x6,"VID Highest"=0x28,"FID Highest"=0xa,"P-State Count"=0x4}

sh-3.2#

 

sh-3.2# ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Status"

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0x306da5b2,"Profile"=0x0,"CPU"=({"Load"={"User"=0x28,"Accumulated"=0x28,"System"=0x0,"Idle"=0x3d7,"Nice"=0x0},"Clock Modulation"=0x8,"Frequency"=0x330,"Current P-State"=0x4,"DID"=0x0,"VID"=0x1d,"Thermal Readout"=0x31,"FID"=0x6,"Voltage"=0x4a3,"Exact"=Yes,"Name"="CPU1"},{"Load"={"User"=0x25,"Accumulated"=0x4a,"System"=0x25,"Idle"=0x3b4,"Nice"=0x0},"Clock Modulation"=0x8,"Frequency"=0x330,"Current P-State"=0x4,"DID"=0x0,"VID"=0x1d,"Thermal Readout"=0x32,"FID"=0x6,"Voltage"=0x4a3,"Exact"=Yes,"Name"="CPU2"}),"Timer Timeout (ms)"=0xfa,"P-State Limit"=0x0,"P-State Capability"=0x0,"Current Latency"=0x6,"Kernel Extension Ready"=Yes,"Hysteresis"=0x32,"Auto Throttle Running"=Yes,"Routine Payload TSC"=0x37c3a}

sh-3.2#

 

 

 

Any conclusion 4 that???

 

Thanks

 

Goron

[Superhai]

Hmm, new version of .kext still autothrottles with wrong Frequencies ...

 

You have a fsb issue. Correct that.

[Superhai]

Same hangups here (not only mouse, but overall system periodic hangups) on Turion64, only 2 p-states detected and application crashes at startup. With previous version p-states were corectly detected, although throtling wasn't featured.

 

Ok, first I want to try to make the throttling work, then we look at the additional P-States. Try the newest download (Dec 6 version), some fixups made. I added more debug output from the throttling for the debug version, try that - will show where and maybe a bit more why i fails.

 

sorry for my post but i have also post on superhai forum and he never reply my question...is work is alredy great but he drive me crazy when he don't reply.

For your issue there is already an answer, so no need to answer again - better for you to read instead. I don't do personal support.

 

This is output of my mother AMD 64 :

Problems : Mouse hung and lower PState is 1800MHz (in ubuntu 1000MHz), App crash on startup (show 9999MHz !!)

 

You also can try the newest download (dec 6) might give better results, at least more debug info from debug kext.

 

What does TStateThrottle? I have to change YES to NO in Infp.plist for Battery/LowBattery, or it freezes when I unplug the power adapter and it does not boot then.

But it works fine, it throttles 600 to 2000 Mhz with 900mV to 1087mV.

 

There was a bug with the T-State throttler, should be fixed now. Have you tried the latest download?

T-State is same as stopclock throttling, it dont save as much power as P-States, but some. Gives me around 30 mins longer battery time. I use it only when the cpu is close to idle and on lowest P-State. It is not the same as C-States.

 

I installed 1.1.2 version on my Aspire One (boot 132, Leo 10.5.5) with Voodoo RC. I recived kernels panic wich I supose wa sconnected with sound generation (KP occurs during start-up sound of Skype, sound of sutter when I grab screen, and when I run Itunes -- sound was chopped when cpu goes down to 796 MHz).

1st attempt to grab a screen [apple+shift+3]

2nd attempt to grab a screen [apple+shift+3]

Skype is starting

iTUnes 

On Shut Down after removing GenericCPU kext:

 

You have the newest kext? You can try to disable the TStateThrottle option.

 

And finally I grab a screen: look at  Freq on CPU0... 6368 MHz

 

Just a calc bug in the app. No worries, download the latest version. It show the effective stopclock throttle frequency.

[Goron]

You have a fsb issue. Correct that.

 

 

The system is overclocked by FSB, instead of 200 (standard) its running with 325MHz FSB ... what do you mean with "Correct that." I do not understand, what issues occur ???

 

Goron

[mitch_de]

The system is overclocked by FSB, instead of 200 (standard) its running with 325MHz FSB ... what do you mean with "Correct that." I do not understand, what issues occur ???

 

Goron

Maybe using an newer bootloader (boot in / folder) like chameleon V11 or PCEFI V9 .

Or if you have that already, using an SMSBIOS which handle that (like superhai smsresolver).

[Wiwi]

New kext instantly freeze AMD system, even in -s, can't post debug....

[Ztardust]

Hei Superhai!

 

I tried the latest version of the kext... no kernel panic this time!

 

But, unfortunately as soon as I have installed the kext with the kext helper, then my machine begins stuttering... the mouse moves for 1 second, and then stops for 3 seconds, moves for another 1 second, and stops again for 3 seconds, and so on and so forth...

Anyhow, I managed to go into the terminal, inspite of this stuttering, and do the ioreg for generic, and I´ve attached the output with this message.

 

Thanks!

 

-Ztardust-

ioeg_gen.txt

[moderndrummer]

hello there. I just discovered this AWESOME GUI you made.. Excellent work my friend. Thanks a million times. works just fine

 

I need to ask sth I don't quite understand. What is the TjMAX option? When set to 100% it "reads" the same temperature as Temperature monitor. When changed it reads sth else.

On Which percentage is the reading more accurate?

 

A suggestion would be to enable a Fan control preference pane working with the GUI. Just for us humans who are passionate with controlling fans to their own will on their laptops and smcfancontrol just refuses to work.. do you think that can be made possible???

 

Thanks again, keep up the good work

[Goron]

Maybe using an newer bootloader (boot in / folder) like chameleon V11 or PCEFI V9 .

Or if you have that already, using an SMSBIOS which handle that (like superhai smsresolver).

 

 

I already use PCEFI v9, SMBiosresoler did .... hmmmmm ... some part of the job, i´d say. Now it throttles between 1200 and 2000 MHz, which should be normal for that CPU.

 

How about overclocking? Is it possible to modify it, so it detects the actual frequencies? I believe 1.0.20 did the job, but i lost the kext

 

 

 

New kext instantly freeze AMD system, even in -s, can't post debug....

 

+1

 

On Athlon x2 4000+ on GA-M68sm-s2 freezes ad hoc in any run level.

 

 

 

Goron

[macNApiecu]

You have the newest kext? You can try to disable the TStateThrottle option.

 

Just a calc bug in the app. No worries, download the latest version. It show the effective stopclock throttle frequency.

 

I set false in TStateThrottle option info.plist file. But after that I can run only in safe mode. I use kext and apps from 6 dec ca. 1.30 pm GMT.

 

App working OK.

[lordbath]

ok, Superhaia i did just like u toldme to do, i booted in the -s mode and loaded the kext but again as soon as i loaded the kext the system froze instantly, from the above posts i see that some other people are facing the same issue. i realize that in order to help us u need some debug info. pls tell me what i can do to help u resolve this issue?

 

thx

[Superhai]

This thread is becoming a bit unmanageble for me to follow, because there are so many different issues, and some of you are very poor at posting specs or outputs and following directions.

 

I suggest all of you with some kind of issue. Read the documentation. If you don't find an answer, make a new thread on my forum at http://www.superhai.com/ , describe it as detailed as possible. Ensure this has to do with CPU power management, or are caused by it. (I.e. no fan control, backlight, smbios, or whatever)

 

If it freezes, run the debug version of the kext in "single user mode" (only -s option at boot). Include in the post a picture of the screen when it freezes.

 

If it is not freezing you need to post me a bug report as it is stated in the documentation. You find a link to the documentation at the first post or on my website.

 

Failure to do the above, will either result in ignore and the issue considered solved or that your post is deleted.

 

And no PM's whatsoever.

[BIM167]

Much to my regret neither the second, nor the third variant has not gone. The second variant caused a panic, and in the third pressure on the processor is not regulated. During the same time the first variant works quite regularly. Screen pictures I apply.

[lordbath]

this is just the follow-up regarding the issues i'm facing. well, booting in the -s mode doesn't do much as my laptop freezes instantly once the kext is loaded. i've tried loading the kext manually as well as automatically. neither one of the options seem to make any difference.

 

what's really weird is that the previous kexts beginning from version 1.0 up to 1.19 are working just fine, though 1.20 and onward versions freeze my laptop momentarily.

 

just to let u know my specs. it's a vaio laptop with Core 2 duo @1.8

 

is there is anything to help u resolve this problem pls let me know.

 

thx

 

this what i managed to get from the console once the kext loaded and then froze:

 

 

12/7/08 8:43:23 AM loginwindow[25] Login Window Started Security Agent

12/7/08 8:43:23 AM SecurityAgent[99] User info context values set for

12/7/08 8:43:24 AM SecurityAgent[99] Login Window done

12/7/08 8:43:24 AM loginwindow[25] Login Window - Returned from Security Agent

12/7/08 8:43:25 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[95]) Exited: Terminated

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Initialization : Probe

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] A/C Power Disconnected

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Found 2 I/O Kit CPU's and 2 ACPI CPU's

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Your CPU supports constant TSC but only in C0 and C1, you should disable C2+ states

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Intel 06000925 06170925

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Initialization : Start

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Attempting BIOS control handover

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Debug) Dec 6 2008 01:21:25 [1050]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 0: 1800 MHz [09-00] - 1175 mV [25]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 1: 1600 MHz [08-00] - 1137 mV [22]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 2: 1400 MHz [07-00] - 1112 mV [20]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 3: 1200 MHz [06-00] - 1087 mV [1E]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 4: 1000 MHz [8A-00] - 1050 mV [1B]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 5: 0800 MHz [88-00] - 1025 mV [19]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] P-State 6: 0600 MHz [86-00] - 1000 mV [17]

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] CPU 0: CTL 0925 TR 039

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] CPU 1: CTL 0925 TR 037

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 0 us

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0336 P-State 0 (exact) and frequency 1800

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0296 P-State 0 (exact) and frequency 1800

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 1 - Requesting 0822

12/7/08 8:44:39 AM kernel GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 1 - Requesting 0822

12/7/08 8:44:42 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 210 us

12/7/08 8:44:42 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0620 P-State 0 (exact) and frequency 1800

12/7/08 8:44:42 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0548 P-State 0 (exact) and frequency 1800

12/7/08 8:44:44 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 126 us

12/7/08 8:44:44 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0777 P-State 1 (exact) and frequency 1600

12/7/08 8:44:44 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0341 P-State 1 (exact) and frequency 1600

12/7/08 8:44:44 AM kernel GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 0 - Requesting 0925

12/7/08 8:44:44 AM kernel GenericCPUPowerManagement: [Debug] AutoThrottle - from 1 to 2 - Requesting 0720

12/7/08 8:44:46 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 205 us

12/7/08 8:44:46 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0526 P-State 1 (exact) and frequency 1600

12/7/08 8:44:46 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0565 P-State 1 (exact) and frequency 1600

12/7/08 8:44:48 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 117 us

12/7/08 8:44:48 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0617 P-State 0 (exact) and frequency 1800

12/7/08 8:44:48 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0471 P-State 0 (exact) and frequency 1800

12/7/08 8:44:50 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 114 us

12/7/08 8:44:50 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0622 P-State 0 (exact) and frequency 1800

12/7/08 8:44:50 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0408 P-State 0 (exact) and frequency 1800

12/7/08 8:44:52 AM kernel GenericCPUPowerManagement: [Debug] Last loop used 115 us

12/7/08 8:44:52 AM kernel GenericCPUPowerManagement: [Debug] CPU 0 load 0357 P-State 0 (exact) and frequency 1800

12/7/08 8:44:52 AM kernel GenericCPUPowerManagement: [Debug] CPU 1 load 0753 P-State 0 (exact) and frequency 1800

12/7/08 8:48:00 AM loginwindow[23] Login Window Started Security Agent

12/7/08 8:48:03 AM SecurityAgent[88] Showing Login Window

12/7/08 8:48:06 AM SecurityAgent[88] User info context values set for LordBath

12/7/08 8:48:06 AM SecurityAgent[88] Login Window done

12/7/08 8:48:06 AM loginwindow[23] Login Window - Returned from Security Agent

12/7/08 8:48:07 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[84]) Exited: Terminated

12/7/08 8:48:20 AM Finder[108] [QL ERROR] Generator database update takes too long... we will use what we currently have

[ Mysticus C*]

hello superhai,

 

I know this is not related to your cpupowermanagement, but i dont any other way to post it to you since your pm is not allowed... if you would/feel like to give any advice ideas or solutions we ll really appreciate it...

 

here is the story....

 

we (samsung nc10 netbook users) have one small trouble with sleep with vanilla kernel...

 

It may sound normal or absurd at first but listen to the story...

 

system sleeps perfectly fine if the netbook running on battery only!

 

when you connect the power adapter, system sleep works still however wakes up instantly... dmesg reveals "usb caused wake event" (funny because it does not wake up when on battery only)

 

it happens on stock acpi apic powermananagement acpibattery appleusbehci (slice's version) etc all the sort of possible combinations... it wakes up instantly saying usb caused wake event.... stock kernel as well... 10.5.4 and 10.5.5 same results...

 

what kind of powermanagement issue be responsible for this? and how could we fix it?

 

it is obvious that it is acpi/powermanagement related (because it feeds current or stg? to usb ports when on power, but stops it when on battery power), but cant figure out actual cause...

 

if i knew how to look for right values in a powermanagement bundle source/acpi source i would track down the differences in profiles/states of battery and power... but i dont know...

 

is there anyway you would wanna give some supporting hand/ideas?

 

thanx in advance...

[alicizmar]

I tried this kext just now and had it b0rk my video for some reason. Bootup time is also way slower, or so I can tell for no video. Luckily for me though, I could get in -s fine and immediately tossed it. Sorry I didn't get a debug or whatnot on it, but here's my specs.

AMD Athlon X2 5000+

GA-MA78GM-S2H

10.5.5

 

Oh well, guess my computer will have to run "Hot N' Loud" a bit longer.

[wingrunr21]

when you connect the power adapter, system sleep works still however wakes up instantly... dmesg reveals "usb caused wake event" (funny because it does not wake up when on battery only)

 

it happens on stock acpi apic powermananagement acpibattery appleusbehci (slice's version) etc all the sort of possible combinations... it wakes up instantly saying usb caused wake event.... stock kernel as well... 10.5.4 and 10.5.5 same results...

 

it is obvious that it is acpi/powermanagement related (because it feeds current or stg? to usb ports when on power, but stops it when on battery power), but cant figure out actual cause...

 

I know you said many possible combos but have you tried Superhai's own EHCISleepEnabler? http://www.superhai.com/darwin.html

[ Mysticus C*]

I know you said many possible combos but have you tried Superhai's own EHCISleepEnabler? http://www.superhai.com/darwin.html

 

i will test it as well, but the problem is that, system sleeps just fine, on battery, it wakes up instantly if power adapter connected, so i doubt it is ehci issue... it looks as if it is acpi/power management issue... because either profile or power state is triggering/feeding current on usb and causing wake event anyways i ll test it as well...

 

NOTE: Tested it with ehcisleep enabler have the same effect + worsens the situation, causes ps/2 trackpad to loose control, and mouse pointer gets stuck with round rainbow task indicator...

 

So it has nothing to do with the ehci driver, since it works just fine when it is on battery... this is definetely a power state/profile and/or acpi issue... just wondering if there is any way to find out in either powermanagement or in acpi that there is power enable (or maybe listen to usb ports) when on power adapter and power disable (or maybe do not listen usb ports) option or something that makes sense to explain the situation?

 

SUPERHAI, i think you can shade some light on this situation...?

[mrbonkers]

worked for me but it cause AppleAzalia from being loaded during boot. the previous version does not have this issue.

 

using hard disk boot-132

[sw33t]

I have an Acer 4315, 1.73 Ghz Intel Celeron (Single Core)

iAtkos 2.0i Leopard 10.5.4 (no updates), Vanilla Kernel 9.4.0

Just for the records: everything works except LAN, audio-jack and -- speedstep. Replaced wlan mini-pcie with dell truemobile 1490 - works like a charm

 

The kext does not work for me. dmesg output after loading the kext is nil.

 

Debug output:

bash-3.2# kextload -t GenericCPUPowerManagement.kext
extension GenericCPUPowerManagement.kext has potential problems:
Warnings
{
"Kext has immediate dependencies on both com.apple.kernel and com.apple.kpi components; use only one style" = true
}

kextload: extension GenericCPUPowerManagement.kext appears to be loadable
25GenericCPUPowerManagement is not compatible with its superclass, 9IOService superclass changed?
kextload: a link/load error occured for kernel extension GenericCPUPowerManagement.kext
link/load failed for extension GenericCPUPowerManagement.kext
(run kextload with -t for diagnostic output)
bash-3.2# uname -r
9.4.0