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

aliasa_anderson
aliasa_anderson
Posted
Posted
I answer what i know:

1. AppleIntelCPUPowermanagement kext didngt use speedstep function (Intel CPU, buildin), does throttle other way

2. This .kext also supports AMDs Cool&Quit -_- , which is not supported by Mercurysquad

3. On Intel (with speedstep CPU + Speedstep in BIOS enabled) both, this + Mercurysquad work near same, this has also an

Tool for showing MHZ+VID+TEMP (also in Menue).

 

 

Thank you very much for the info. ;)

 

Mitch_de do you know how AppleIntelCPUPowermanagement throttles ?

I mean why is it that this helped in getting CPUs cooler in tiger,but makes them hot in Leopard.

 

 

Thanks again for the help.

Superhai
Superhai
Posted
  • Author
Posted
superhai, thank you -_- , the last version is not there

Kp anymore, work smoothly with the MSi wind.

but whether the feature t-state controll still remain on the atom?

thanks

 

Yes T-States is still there. It was overwriting some of the reserved space due to a small bug. Now should be fixed.

 

superhai i post also in your forum why u don't reply me?

Your question has been answered elsewhere. Take the time to read!!!!!!!!!!!!!!!!!

Goron
Goron
Posted
Posted

Now i´m confused:

 

as u said i tried new .kext 1.1.1 and it KPéd EVERY restart AND shutdown. I did a fresh retail install, updated via SU, transfered info through MigrationAss. and now it works flawlessly ?????

 

 

Seems, that something in my installation was broken, nevermind ;)

 

 

Cheers

 

Goron

Superhai
Superhai
Posted
  • Author
Posted
Hi, i also tried newest 1.1.1 (i am that with the VID not trothhled problem, all info some post before).

 

Problems stay:

1. kextload, some throttleing then: stays at PSTATE slowest +1 even near no Load (see shoot)

2. VIDs didnt change (sometimes for short time 1187 mV - not in PSTATE VID-array, maybe from gigabyte EP35 board made itself)

 

I got you the first time. No need to repost this every day... It is a bit... annoying...

 

Just wanted to know,how is this kext different from AppleIntelCPUPowermanagement kext in principle.

I know that the AppleIntelCPUPowermanagement.kext causes a kp without fixed HPET,so did you modify its sources to remove HPET dependency ?

what about its differences with the speedstep kext by Mercurysquad ?

 

It is closer to the speedstep.kext than aicpupm.kext. There is no HPET dependency.

 

 

Mitch_de do you know how AppleIntelCPUPowermanagement throttles ?

 

It depends on Apple_SMC... to get the P-States.

U.C.
U.C.
Posted
Posted

Well first off happy to report, your latest kext works awesome on my Wind.

 

Just one issue, I just tried your ACPIBattery.kext and it kernel panics with GenericCPUPowerManagement.kext, if used with battery.

 

The machine will work and boot fine with the AC Adapter. If booted without AC it will KP and if AC is removed AFTER Boot, then it will just hang, dunno if it KP's or not.

 

Till now I had been using AppleACPIBatteryManager.kext

post-14713-1228428683_thumb.jpg

Superhai
Superhai
Posted
  • Author
Posted
Just one issue, I just tried your ACPIBattery.kext and it kernel panics with GenericCPUPowerManagement.kext, if used with battery.

The machine will work and boot fine with the AC Adapter. If booted without AC it will KP and if AC is removed AFTER Boot, then it will just hang, dunno if it KP's or not.

 

Hm, so it still same issue... I have to take a look.

 

Try the newest upload. Should have this fixed...

mitch_de
mitch_de
Posted
Posted

For Information (throttling BUG on C2D).

 

GenericCPUPowerManagement: [Debug] Initialization : Probe

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

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

GenericCPUPowerManagement: [Debug] Minimum VID Probe

GenericCPUPowerManagement: [Debug] Minimum VID Probe Complete : 28

GenericCPUPowerManagement: [Debug] Intel 06000A28 0A280A28

GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete

GenericCPUPowerManagement: [Debug] Initialization : Start

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.2 (Debug) Dec 4 2008 23:33:37 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Debug] P-State 0: 2660 MHz [0A-00] - 1325 mV [28]

GenericCPUPowerManagement: [Debug] P-State 1: 2394 MHz [09-00] - 1225 mV [20]

GenericCPUPowerManagement: [Debug] P-State 2: 2128 MHz [08-00] - 1125 mV [18]

GenericCPUPowerManagement: [Debug] P-State 3: 1862 MHz [07-00] - 1025 mV [10]

GenericCPUPowerManagement: [Debug] P-State 4: 1596 MHz [06-00] - 0925 mV [08]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 0A28 TR 063

GenericCPUPowerManagement: [Debug] CPU 1: CTL 0A28 TR 063

GenericCPUPowerManagement: [Debug] Last loop used 0 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0041 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 1 load 0041 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 4 - Requesting 0608

GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 4 - Requesting 0608

GenericCPUPowerManagement: [Debug] Last loop used 292 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0043 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 1 load 0058 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 4 - Requesting 0608

GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 4 - Requesting 0608

 

I found out some ???(Bug) about throttling. Also Control App shows that.

... after startup of kext, running low CPU LOAD, all OK PSTATE 4 = 1596 = lowest MHZ

GenericCPUPowerManagement: [Debug] CPU 0 load 0035 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0025 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] Last loop used 115 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0038 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0028 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] Last loop used 116 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0045 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0045 P-State 4 (approximate) and frequency 1596

Generic

 

... after some CPU load, and back to low load, PSSATE number and MHZ in debug log dont fit together anymore

GenericCPUPowerManagement: [Debug] CPU 0 load 0030 P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] CPU 1 load 0023 P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Last loop used 102 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0028 P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] CPU 1 load 0028 P-State 4 (approximate) and frequency 1862

Gener

Near same CPU load, PSTATE shows 4 but that doenst fit with shown 1862 MHZ (thats PSTATE 3!!!)

So after some throttling maybe the "real" PSTATE is lost / PSTATE shift bug

Also it never goes to PSTATE 4 anymore (like short after kextload) , stays PSATE 3 which is 1862, but in debug log

computed as PSTATE 4 (which is 3).

I checked MHZ with MSR tool if MHZ shown in debug and control app is real.

Yes, debug 1862 MHZ is real. But 1862 MHZ should be PSTATE 3 , not in debug shown PSTATE 4 - this is 1596 MHZ.

 

This (PSTATE / MHZ shift) maybe the reason why i wrote some days ago that the new kext wont get to my lowest MHZ - only short after kextload.

 

 

Thanks

crencom
crencom
Posted
Posted

Still getting the below warning on yesterday and todays releases. The kext does appear to load. No KP system loads / runs fine. The 1.1 version did not give this error. Any recommendations for changes.

 

System - GA EP43 DS3L C2Q 6600 ocd to 2.65gz - 10.5.5 retail install w/ vanilla kernel w/ DSDT

 

sudo dmesg | grep GenericCPUPowerManagement

Password:

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

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Release) Dec 3 2008 07:35:16 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

 

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Status"

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0x2790730e,"Profile"=0x0,"CPU"=({"Load"={"User"=0x2a,"Accumulated"=0x2a,"System"=0x0,"Idle"=0x3d5,"Nice"=0x0},"Clock Modulation"=0x400,"Frequency"=0x6ea,"Current P-State"=0x3,"DID"=0x0,"VID"=0x1b,"Thermal Readout"=0x40,"FID"=0x6,"Voltage"=0x48a,"Exact"=Yes,"Name"="CPU0"},{"Load"={"User"=0x0,"Accumulated"=0x0,"System"=0x0,"Idle"=0x400,"Nice"=0x0},"Clock Modulation"=0x400,"Frequency"=0x6ea,"Current P-State"=0x3,"DID"=0x0,"VID"=0x1b,"Thermal Readout"=0x41,"FID"=0x6,"Voltage"=0x48a,"Exact"=Yes,"Name"="CPU1"},{"Load"={"User"=0x0,"Accumulated"=0x0,"System"=0x0,"Idle"=0x400,"Nice"=0x0},"Clock Modulation"=0x400,"Frequency"=0x6ea,"Current P-State"=0x3,"DID"=0x0,"VID"=0x1b,"Thermal Readout"=0x41,"FID"=0x6,"Voltage"=0x48a,"Exact"=Yes,"Name"="CPU2"},{"Load"={"User"=0x0,"Accumulated"=0x0,"System"=0x0,"Idle"=0x400,"Nice"=0x0},"Clock Modulation"=0x400,"Frequency"=0x6ea,"Current P-State"=0x3,"DID"=0x0,"VID"=0x1b,"Thermal Readout"=0x3f,"FID"=0x6,"Voltage"=0x48a,"Exact"=Yes,"Name"="CPU3"}),"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"=0x47253}

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Characteristics"

"Characteristics" = {"Voltage Highest"=0x520,"Signature"=0x6fb,"CPU Count"=0x4,"Build Date"="Dec 3 2008","Constant TSC"=Yes,"Voltage Lowest"=0x48a,"VID Lowest"=0x1b,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.1","Individual Core Control"=No,"Frequency Lowest"=0x6ea,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x0,"Mobile CPU"=No,"Build Time"="07:35:16","Auto Throttle On Startup"=Yes,"Build Config"="Release","Frequency Highest"=0xa5f,"String"="Intel® Core2 Quad CPU Q6600 @ 2.40GHz","DID Highest"=0x0,"FID Lowest"=0x6,"VID Highest"=0x27,"FID Highest"=0x9,"P-State Count"=0x3}

mitch_de
mitch_de
Posted
Posted
Updated the gui app with some options... requires download of new kext.

Thanks - GUI getting really cool !

 

My report (throttling ??? C2D) of newest .kext

 

start of kext: didnt gp to PState 4 (my slowest MHZ), stays at Psate 3 (same as before)

.... CPU load very less

enericCPUPowerManagement: [Debug] Last loop used 103 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0015 P-State 4 (approximate) and frequency 1862 should be 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0023 P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] Got userland request

....

starting geekbench

GenericCPUPowerManagement: [Debug] CPU 1 load 0918 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] Last loop used 88 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0933 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 1 load 0628 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 0 load 0368 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 1 load 0200 P-State 0 (exact) and frequency 2660

geekbench finished

GenericCPUPowerManagement: [Debug] Last loop used 119 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0013 P-State 4 (approximate) and frequency 1596 YEAH, my 1596 :)

GenericCPUPowerManagement: [Debug] CPU 1 load 0013 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] CPU 0 load 0015 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0008 P-State 4 (approximate) and frequency 1596

... but only for short time - an short midrange cpu load gives 1862 again - and stays there forever even cpu load isgain low

GenericCPUPowerManagement: [Debug] CPU 0 load 0015 P-State 4 (approximate) and frequency 1862 should be 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0023 P-State 4 (approximate) and frequency 1862

I get only 1596 (PSate 4 ) again :

A) if i force manual trottle 1596

:D or i full load cpus (geekbench again) - after full load it went to 1592 (PState 4)YEAH! until some short midrange load gives 1862 and stays here also with no load (should be PStaze 4 then)

 

MSR TOOL verify:

I also seen with that newest .kext an maybe undifined target Multiplier in my CPU1 : MSR target Multiplyer (= PSate) went to 0 Zero

Actual Multipyiers shown in MSR Tool are OK and same as Control App (also newest) shows.

Also the VIDs seem target (only) now changing but shown little different between CPU0 and CPU 1

Actual VIDs while trottling are 1325 (max) and 1164 - both correct, but never got my 925.

Also only MSR Tool (screen shoot) shows my 1164 mVolts (in .plist for Pstate 3) - your app shows 1187 therefore

Added screenshoot ,

also V 1.0.20 MSR target multipliers CPU0/1 are same, target VIDs CPU0/1 are same here, also 1596 MHZ without forcing trothle or short full load)

Thanks

Bild_115.jpg

Bild_116.jpg

Alex HQuest
Alex HQuest
Posted
Posted

bash-3.2# dmesg | grep GenericCPUPowerManagement

 

GenericCPUPowerManagement: [Debug] Initialization : Probe

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

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

GenericCPUPowerManagement: [Debug] Intel 00000F2D 00000F2D

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: 3375 MHz [0F-00] - 1387 mV [2D]

GenericCPUPowerManagement: [Debug] P-State 1: 3150 MHz [0E-00] - 1350 mV [2A]

GenericCPUPowerManagement: [Debug] P-State 2: 2925 MHz [0D-00] - 1312 mV [27]

GenericCPUPowerManagement: [Debug] P-State 3: 2700 MHz [0C-00] - 1275 mV [24]

GenericCPUPowerManagement: [Debug] P-State 4: 2475 MHz [0B-00] - 1237 mV [21]

GenericCPUPowerManagement: [Debug] P-State 5: 2250 MHz [0A-00] - 1200 mV [1E]

GenericCPUPowerManagement: [Debug] P-State 6: 2025 MHz [09-00] - 1162 mV [1B]

GenericCPUPowerManagement: [Debug] P-State 7: 1800 MHz [08-00] - 1125 mV [18]

GenericCPUPowerManagement: [Debug] P-State 8: 1575 MHz [07-00] - 1087 mV [15]

GenericCPUPowerManagement: [Debug] P-State 9: 1350 MHz [06-00] - 1050 mV [12]

GenericCPUPowerManagement: [Debug] P-State 10: 1125 MHz [05-00] - 1012 mV [0F]

GenericCPUPowerManagement: [Debug] P-State 11: 0900 MHz [04-00] - 0975 mV [0C]

GenericCPUPowerManagement: [Debug] P-State 12: 0675 MHz [03-00] - 0937 mV [09]

GenericCPUPowerManagement: [Debug] P-State 13: 0450 MHz [02-00] - 0900 mV [06]

GenericCPUPowerManagement: [Debug] P-State 14: 0225 MHz [01-00] - 0862 mV [03]

GenericCPUPowerManagement: [Debug] P-State 15: 0000 MHz [00-00] - 0825 mV [00]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 0F2D TR 000

GenericCPUPowerManagement: [Debug] CPU 1: CTL 0F2D TR 000

GenericCPUPowerManagement: [Debug] Last loop used 0 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0259 P-State 0 (exact) and frequency 3375

GenericCPUPowerManagement: [Debug] CPU 1 load 0206 P-State 0 (exact) and frequency 3375

GenericCPUPowerManagement: [Debug] Last loop used 508 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0423 P-State 0 (exact) and frequency 3375

GenericCPUPowerManagement: [Debug] CPU 1 load 0428 P-State 0 (exact) and frequency 3375

GenericCPUPowerManagement: [Debug] Last loop used 252 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0433 P-State 0 (exact) and frequency 3375

GenericCPUPowerManagement: [Debug] CPU 1 load 0273 P-State 0 (exact) and frequency 3375

 

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

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0xffffffff9ce5ba9c,"Profile"=0x0,"CPU"=({"Load"={"User"=0x103,"Accumulated"=0x1ac,"System"=0xa9,"Idle"=0x252,"Nice"=0x0},"Clock Modulation"=0x8,"Frequency"=0xd2f,"Current P-State"=0x0,"DID"=0x0,"VID"=0x2d,"Thermal Readout"=0x0,"FID"=0xf,"Voltage"=0x56b,"Exact"=Yes,"Name"="CPU0"},{"Load"={"User"=0x11c,"Accumulated"=0x1b6,"System"=0x9a,"Idle"=0x248,"Nice"=0x0},"Clock Modulation"=0x8,"Frequency"=0xd2f,"Current P-State"=0x0,"DID"=0x0,"VID"=0x2d,"Thermal Readout"=0x0,"FID"=0xf,"Voltage"=0x56b,"Exact"=Yes,"Name"="CPU1"}),"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"=0x117204}

 

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

"Characteristics" = {"Voltage Highest"=0x56b,"Signature"=0xf41,"Front Side Bus Indicated"=0xbebc200,"CPU Count"=0x2,"Build Date"="Dec 5 2008","Constant TSC"=Yes,"Voltage Lowest"=0x339,"Front Side Bus"=0xd693a40,"VID Lowest"=0x0,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.2","Individual Core Control"=No,"Frequency Lowest"=0x0,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x0,"Mobile CPU"=No,"Build Time"="04:20:41","Auto Throttle On Startup"=Yes,"Build Config"="Debug","Frequency Highest"=0xd2f,"String"="Intel® Pentium® 4 CPU 3.00GHz","DID Highest"=0x0,"FID Lowest"=0x0,"VID Highest"=0x2d,"FID Highest"=0xf,"P-State Count"=0xf}
lordbath
lordbath
Posted
Posted

ok even with the newest version of this kext, the system freezes momentarily once the kext is installed. then i have to do a hard restart and then it freezes again either at the boot or 3-4 sec once the system is loaded. there are no panic messages or kps. can u pls tell me what i should do to fix it?

Superhai
Superhai
Posted
  • Author
Posted
ok even with the newest version of this kext, the system freezes momentarily once the kext is installed. then i have to do a hard restart and then it freezes again either at the boot or 3-4 sec once the system is loaded. there are no panic messages or kps. can u pls tell me what i should do to fix it?

 

Last time I asked you to boot -s (single user mode) and load the kext from there and post me the output. It seem like you have ignored this, how can I help you?

macNApiecu
macNApiecu
Posted
Posted

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]

 

post-220002-1228485452_thumb.jpg

 

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

 

post-220002-1228485531_thumb.jpg

Skype is starting

 

 

post-220002-1228485698_thumb.jpg

 

post-220002-1228485770_thumb.jpg

 

iTUnes 

 

post-220002-1228485881_thumb.jpg

 

On Shut Down after removing GenericCPU kext: 

 

post-220002-1228483657_thumb.jpg

 

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

 

post-220002-1228484460_thumb.jpg

coccolino_dbro
coccolino_dbro
Posted
Posted

Hey man, Superhai is doing his best in helping us with his work, so we all should be gratefull for this... If he hasn't replied in your matter, you should chill out and be a little more patient; maybe he has his reasons for not replying (missed your posts, insufficient info you provided, not had the time etc etc).

 

ontopic: will try the new 1.1.2 later today on my Turion, to see if the throttleing works well.

wingrunr21
wingrunr21
Posted
Posted
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.

 

Does the newest version solve the problem you posted on Superhai's forum?

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