Jump to content

New version 1.1 of GenericCPUPowerManagement


Superhai
 Share

625 posts in this topic

Recommended Posts

using 1.0.6 on T7200:

 

ioreg -lw0 | grep PerformanceStateArray:

(<

d0070000187900000a0000000a0000002b0c00002b0c0000>,<83060000a86100000a0000000a000000230a0000230a0000>,
<35050000384a00000a0000000a0000001b0800001b080000>,<e8030000c83200000a0000000a0000001306000013060000>)

 

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

 "CPU Status" = {"Frequency ID"=0x6,"Low jump"=0x190,"Temperature"=0xffffffffffffffc9,"Auto Throttle"=Yes,"Timer"=0xfa,"High jump"=0x258,"Voltage ID"=0x13,"Load"=0x13}
  "CPU Init" = {"CPU Signature"=0x6f6,"CTL max"=0xc2c,"FSB frequency min"=0x27bc86ac,"FSB frequency max"=0x27bc86ac,"CPU frequency min"=0x3b9aca02,"CTL min"=0x610,"CPU frequency max"=0x77359404}

 

 

sysctl -a | grep freq:

kern.exec: unknown type returned
hw.busfrequency = 666666668
hw.cpufrequency = 2000000004
hw.tbfrequency = 1000000000
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 2000000004
hw.cpufrequency_min: 1000000002
hw.cpufrequency: 2000000004
hw.busfrequency_max: 666666668
hw.busfrequency_min: 666666668
hw.busfrequency: 666666668

Link to comment
Share on other sites

1.0.6 on M1530 with T8300:

 

ioreg -lw0 | grep PerformanceStateArray

	| |		 "PerformanceStateArray" = (<61090000007d00000a0000000a000000280d0000280d0000>,<60090000187900000a0000000a000000220c0000220c0000>,
<d0070000a86100000a0000000a0000001f0a00001f0a0000>,<40060000384a00000a0000000a0000001b0800001b080000>,
<b0040000c83200000a0000000a0000001706000017060000>,<20030000102700000a0000000a0000001388000013880000>)

 

sysctl -a | grep freq

kern.exec: unknown type returned
hw.busfrequency = 800000000
hw.cpufrequency = 2400000000
hw.tbfrequency = 1000000000
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 2400000000
hw.cpufrequency_min: 600000000
hw.cpufrequency: 2400000000
hw.busfrequency_max: 800000000
hw.busfrequency_min: 400000000
hw.busfrequency: 800000000

 

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

	  "CPU Status" = {"Frequency ID"=0x86,"Low jump"=0x190,"Temperature"=0xffffffffffffffcb,"Auto Throttle"=Yes,"Timer"=0xfa,"High jump"=0x258,"Voltage ID"=0x13,"Load"=0x10e}
  "CPU Init" = {"CPU Signature"=0x10676,"CTL max"=0xd2c,"FSB frequency min"=0x17d78400,"FSB frequency max"=0x2faf0800,"CPU frequency min"=0x23c34600,"CTL min"=0x8810,"CPU frequency max"=0xffffffff8f0d1800}

Link to comment
Share on other sites

I posted my spec before, but now i checked the hex values., maybe some problems ?

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

"CPU Status" = {"Frequency ID"=0xa,"Low jump"=0x190,"Temperature"=0xffffffffffffffc8,"Auto Throttle"=Yes,"Timer"=0xfa,"High jump"=0x258,"Voltage ID"=0x28,"Load"=0x2d2}

"CPU Init" = {"CPU Signature"=0x6f2,"CTL max"=0xa2c,"FSB frequency min"=0x2faf0800,"FSB frequency max"=0x2faf0800,"CPU frequency min"=0x47868c00,"CTL min"=0x610,"CPU frequency max"=0x77359400}

CPU frequency min"=0x47868c00," = 1,2 GHZ

CPU frequency max"=0x77359400 = 2,0 GHZ (C2D 2000 GHZ, BUT! its overclocked (FSB=200>240 ) to 2,4 GHZ - problem ?

FSB frequency min"=0x2faf0800,"FSB frequency max"=0x2faf0800, = 800 MHZ (200*4) , but its 960 MHZ (4*240)

Systemprofiler shows correct 960 MHZ

Thanks

Link to comment
Share on other sites

i cant find 1.06 .. neither the app that is supposed to work on it .

i have 1.05 without the app .

The newest Dl is 1.0.6, always same DL Link on the SUPERHAI ( Megalodon would be better name for that hero :) )

Downloadsite.

YOu get there the .kext, which is autotrottled , but you cant change the settings, the left Controlapp will follow next days, i think.

 

sudo mv SUPERHAI MEGALODON

http://en.wikipedia.org/wiki/Megalodon

Link to comment
Share on other sites

One Question :

 

When i run lots of cpu-demanding apps ( Like VMware and Photoshop together ) does the CPU return to original non-throttled state ?

Sure, if the CPU gets over an CPU 60% (both kernels added) it trottles one step up until run as full speed and stays there util CPU is lees tahn 40% , throttling one step down. The only thing is, that it can take up to 250 mS to change from lowered to max speed (250 mS Timer clock). All that - timer speed, Min Low, Max High values can configed with the Controll App, which we get in some time.

Now, you can only ajust those initial values (timer, CPU min/max kevels) by changing it in the source & compile it.

Link to comment
Share on other sites

I have uploaded the new app, and also a new version of the kext. Undervolting is possible by altering vid values in Info.plist. Use at own risk!

Any comments would be welcome. Pentium M should not crash, but might have timing issues. A fix is coming. Also I will change the fsb routine (i.e. remove it) as it is not useful if you have overclocked fsb. Temperature is not updated yet.

More to come.

Link to comment
Share on other sites

I still have a max value of 2000MHz instead of 2100MHz. Look at the screenshot.

 

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

"CPU Status" = {"Auto Throttle"=Yes,"Load"=0x6e,"Temperature"=0xffffffffffffffbc,"High jump"=0x258,"Voltage"=0x3b6,"Timer"=0xfa,"Low jump"=0x190,"Frequency"=0x320,"Kext Timer"=0x2cf,"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0x13,"Frequency ID"=0x88}

"CPU Init" = {"CTL max"=0x4b2c,"FSB frequency min"=0x190,"Signature"=0x10676,"FSB frequency max"=0x320,"CTL min"=0x8810,"Kext unlock"=Yes,"Kext version"=0x10007,"Brand string"="Intel® Core2 Duo CPU T8100 @ 2.10GHz","Voltage max"=0x4ee,"Frequency min"=0x258,"Frequency max"=0x7d0,"Voltage min"=0x390}

 

 

ioreg -lw0 | grep PerformanceStateArray

| | "PerformanceStateArray" = (<35080000b88800000a0000000a000000284b0000284b0000>,<34080000b88800000a0000000a000000224a0000224a0000>,<40060000c05d00000a0000000a0000001c0800001c080000>,<b0040000803e00000a0000000a0000001706000017060000>,<20030000b03600000a0000000a0000001388000013880000>)

 

also the new app doesn't show anything on the tray bar.

post-219791-1223850714_thumb.png

Link to comment
Share on other sites

I have uploaded the new app, and also a new version of the kext. Undervolting is possible by altering vid values in Info.plist. Use at own risk!

Any comments would be welcome. Pentium M should not crash, but might have timing issues. A fix is coming. Also I will change the fsb routine (i.e. remove it) as it is not useful if you have overclocked fsb. Temperature is not updated yet.

More to come.

 

Thanks Superhai... i use undervolting since version 1.0.6, because my cpu can be undervolting at minimum voltage even at maximum frequency, i've edit value min to 2 and value max to 8...

 

Does the app save preferences or have we to set it at each boot ?

Link to comment
Share on other sites

The app is just a quick one. It is not ready, but I uploaded so you have something. Missing is the tray bar, save option (all current options are available to edit in Info.plist) etc. I have unfortunately not so much spare time, so you need to wait. There is also a command line tool for you on its way.

 

And about the T8100 cpu I have a fix (also all other CPUs that have x.5 as max FSB if there are others) but I need to have some information confirmed first. But it should throttle to max ratio when using autothrottle even tough it doesnt say so.

 

And I also added the shutdown/reboot fix into this kext. (from dfe)

Link to comment
Share on other sites

I didn't get far with the older speedstep kext that was in development but I installed your 1.0.6 one earlier and it seems to work fine. It loaded at least and seemed to show that it could throttle down to 1600mhz. I didn't have any way to check if it was actually throttling. I'll try the latest kext and app later.

 

And I also added the shutdown/reboot fix into this kext. (from dfe)

Is this a fix for the shutdown/restart issues people in general have had since 10.5.4 or so? I was using the patched appleacpiplatform.kext and shutdown script, then replaced these recently with openhaltrestart.kext. Can I now replace that with your kext as well?

Link to comment
Share on other sites

And about the T8100 cpu I have a fix (also all other CPUs that have x.5 as max FSB if there are others) but I need to have some information confirmed first. But it should throttle to max ratio when using autothrottle even tough it doesnt say so.

 

And I also added the shutdown/reboot fix into this kext. (from dfe)

 

That's nice, thanx superhai for the work.

 

i also noticed that the min value wih the prevoius version was 600MHz but not came back to 800MHz. i don't know wich is right.

Link to comment
Share on other sites

trying this on Dell Inspiron E1505 with T7200 @ 2.00GHz C2D. worked great in last version. I am not sure if it works in this newest version. The temp meter is red most of the time, then drops completely goes to green after about 10sec and right back to full red. what does this mean? where does it show the current frequency? thought the last version would show the current value. the new one doesn't show it? (autothrottle)

 

ioreg -lw0 | grep PerformanceStateArray

 

 | |		 "PerformanceStateArray" = 
(<d0070000187900000a0000000a0000002b0c00002b0c0000>,
<83060000a86100000a0000000a000000230a0000230a0000>,
<35050000384a00000a0000000a0000001b0800001b080000>,
<e8030000c83200000a0000000a0000001306000013060000>)

 

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

 

"CPU Status" = {"Auto Throttle"=Yes,"Load"=0x46,
"Temperature"=0xffffffffffffffc7,"High jump"=0x258,"Voltage"=0x3b6,
"Timer"=0xfa,"Low jump"=0x190,"Frequency"=0x3e8,"Kext Timer"=0x3a9,
"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0x13,"Frequency ID"=0x6}
"CPU Init" = {"CTL max"=0xc2c,"FSB frequency min"=0x29a,"Signature"=0x6f6,
"FSB frequency max"=0x29a,"CTL min"=0x610,"Kext unlock"=Yes,
"Kext version"=0x10007,"Brand string"="Intel(R) Core(TM)2 CPU T7200  @ 2.00GHz",
"Voltage max"=0x4ee,"Frequency min"=0x3e8,"Frequency max"=0x7d0,"Voltage min"=0x390}

 

edit 1: Oops, sorry superhai. I see you wrote in your post above that "Temperature is not updated yet". do you think it's ok to go back to previous app version with new kext? Or will they not work together. There is no quick way to see whether it's working or not with the new one (e.g. the freq it is at, menu meters not working).

 

edit 2: replaced both kext and app with previous version and everything is working OK. throttle works 100%. I seem to have problems with new kext/app as they do not throttle the machine. It always sticks at 2GHz.

Link to comment
Share on other sites

trying this on Dell Inspiron E1505 with T7200 @ 2.00GHz C2D. worked great in last version. I am not sure if it works in this newest version. The temp meter is red most of the time, then drops completely goes to green after about 10sec and right back to full red. what does this mean? where does it show the current frequency? thought the last version would show the current value. the new one doesn't show it? (autothrottle)

 

Yup, same here. Tried it with a dual celeron.

 

ioreg -lw0 | grep PerformanceStateArray

 

"PerformanceStateArray" = (<40060000c05701000a0000000a0000002808000028080000>,<b004000050f100000a0000000a0000001d0600001d060000>)

 

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

 

"CPU Status" = {"Auto Throttle"=Yes,"Load"=0x46,"Temperature"=0xffffffffffffffcc,"High jump"=0x258,"Voltage"=0x433,"Timer"=0xfa,"Low jump"=0x190,"Frequency"=0x4b0,"Kext Timer"=0x131,"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0x1d,"Frequency ID"=0x6}
  "CPU Init" = {"CTL max"=0x82c,"FSB frequency min"=0x320,"Signature"=0x6fd,"FSB frequency max"=0x320,"CTL min"=0x610,"Kext unlock"=Yes,"Kext version"=0x10007,"Brand string"="Intel(R) Celeron(R) CPU		E1200  @ 1.60GHz","Voltage max"=0x4ee,"Frequency min"=0x4b0,"Frequency max"=0x640,"Voltage min"=0x390}

Link to comment
Share on other sites

to SUPERHAI:

Idea about checking of trottling up/down.

I can see that throttling isnts working perfect if the cores have much different CPU% loads.

IF you add all % CPU loads of the cores the "picture" of load maybe give wrong decision for uP7downs.

 

for example:

often rhe cores are NOT filled with threads of same load.

If core1 has longer 60-80%load but core2 only 10-30% load that time, it would be wrong to stay at lower CPU MHZ or switch CPU down, because an simple average (adding all cores% / number cores) gives only 35% - 55% average.

An average of 60*1.3(see below text)+10= 78c1 + 10c2 = 88 , = 44% load insted of 35%, or 57% insted of 45% (C2=10).

 

Can you change the up/down like that:

if diff of %load cores > 30% then multiply the highest core% by 1.3 before adding all cores% to the average load %.

That will avoid stepping down too early or make happen stepping up early - both will be not good if you only add all cores load% without check if one core is near max load and other low load.

That simple average would give to less average load% for up/down decisions.

I would perfer to add an multiplier(1.2- 1.3) to the load% of highest core load , if cores load diff > some % (> 30%).

For the showing of load in the Menue/Control app, sure use the (simple average) load without multiplier.

Link to comment
Share on other sites

b]Idea[/b] about checking of trottling up/down.

I can see that throttling isnts working perfect if the cores have much different CPU% loads.

IF you add all % CPU loads of the cores the "picture" of load maybe give wrong decision for uP7downs.

 

It throttles based on the cpu with the highest load, not the average.

 

Anyway, a new version of app is out, with statusbar items on. Updated the kext with tjmax value of 100, so you get a more sensible temperature value in the app. But correct temperatures are not coming before i finish a table for the cpus.

 

Should also work better with t8100 cpu, if all is well. Hopefully...

 

Is this a fix for the shutdown/restart issues people in general have had since 10.5.4 or so? I was using the patched appleacpiplatform.kext and shutdown script, then replaced these recently with openhaltrestart.kext. Can I now replace that with your kext as well?

 

It is the same as the openhaltrestart.kext.

Link to comment
Share on other sites

It throttles based on the cpu with the highest load, not the average.

 

Anyway, a new version of app is out, with statusbar items on. Updated the kext (no new version number) with tjmax value of 100, so you get a more sensible temperature value in the app. But correct temperatures are not coming before i finish a table for the cpus.

It is the same as the openhaltrestart.kext.

 

working now with menu. thank you. looking forward to update.

Link to comment
Share on other sites

First of all thanks for your great work.

 

I'm using new kext and new app right now (the ones that are in your site right now) on laptop with core 2 duo T5500.

 

I have to mention that:

-Autothrottling works: I can see how the cpu load, temperature, frecuency and voltage change on the bar that the app has placed on top (beside the sound's icon).

-Throttle Now don't work: I can move the bar for frecuency and timer, but not for Voltage. Furthermore when I move the frecuency bar and push on "Throttle Now" I can see on top of the bar (beside sound's icon) that it still continues doing autothrottling . Altough the letter beside the frecuency value changes to the O it still does autothrottling.

-For some reason the voltage bar is always full and red.

 

Tests:

ioreg -lw0 | grep PerformanceStateArray

Give me nothing

 

-lxw0 -r -c GenericCPUPowerManagement | grep "CPU "

	  "CPU Status" = {"Auto Throttle"=No,"Load"=0xa0,"Temperature"=0x30,"High jump"=0x258,"Voltage"=0x3b6,"Timer"=0xfb,"Low jump"=0x190,"Frequency"=0x3ea,"Kext Timer"=0x454,"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0x13,"Frequency ID"=0x6}
  "CPU Init" = {"CTL max"=0xa00,"FSB frequency min"=0x29a,"Signature"=0x6f6,"FSB frequency max"=0x29a,"CTL min"=0x600,"Kext unlock"=No,"Kext version"=0x10008,"Brand string"="Intel(R) Core(TM)2 CPU		 T5500  @ 1.66GHz","Voltage max"=0x2c8,"Frequency min"=0x3e8,"Frequency max"=0x682,"Voltage min"=0x2c8}

 

sysctl -a | grep freq

kern.exec: unknown type returned

hw.busfrequency = 668000000

hw.cpufrequency = 1002000000

hw.tbfrequency = 1000000000

hw.tbfrequency: 1000000000

hw.cpufrequency_max: 1662000000

hw.cpufrequency_min: 1662000000

hw.cpufrequency: 1002000000

hw.busfrequency_max: 668000000

hw.busfrequency_min: 668000000

hw.busfrequency: 668000000

 

 

Hope it helps ^_^

Link to comment
Share on other sites

I have a dell d830 with t7300 and nvidia quadro.

 

I now only get throttling from 1600 to 2000. The only version that has actully given me 800-2000 is when it still was called IntelEnhancedSpeedStep.kext.

 

 

This is what i get from ioreg:

roos:~ roos$ ioreg -lw0 | grep PerformanceStateArray

| | "PerformanceStateArray" = (<d1070000007d00000a0000000a0000002d0b00002d0b0000>,<d0070000187900000a0000000a0000002b0a00002b0a0000>,<40060000f05500000a0000000a0000002108000021080000>,<b0040000c83200000a0000000a0000001706000017060000>,<20030000102700000a0000000a0000000f8800000f880000>)

roos:~ roos$ ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "CPU "

"CPU Status" = {"Auto Throttle"=Yes,"Load"=0x27,"Temperature"=0x2c,"High jump"=0x258,"Voltage"=0x384,"Timer"=0xfa,"Low jump"=0x190,"Frequency"=0x640,"Kext Timer"=0x41a,"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0xf,"Frequency ID"=0x88}

"CPU Init" = {"CTL max"=0xb2d,"FSB frequency min"=0x320,"Signature"=0x6fa,"FSB frequency max"=0x320,"CTL min"=0x880f,"Kext unlock"=No,"Kext version"=0x10008,"Brand string"="Intel® Core2 Duo CPU T7300 @ 2.00GHz","Voltage max"=0x4fb,"Frequency min"=0x4b0,"Frequency max"=0x7d0,"Voltage min"=0x384}

Link to comment
Share on other sites

New kext doesn't detect pstates as before, now it seems to read ACPI table (where i have 2 pstates - 1000 and 1500), but before this version it read / calculate intermed. pstates (1000, 1169, 1339, 1500). here is my cpu info :

 

CPU Type	   [[url="http://ark.intel.com/cpu.aspx?groupID=30786"]Mobile Intel Core 2 Duo T5250[/url]]
CPU Signature  [] Mobile CPU [Yes] Latency [?] us
Max multiplier [9] Half multiplier [_____] TjMAX [85] C
Control Max	[?] Min [?]
Range: Frequency [1000 - 6.0 x 166.3 MHz] MHz to [1500] MHz, Voltage [950] mV (1004 according to mecusquad kext - stable for ALL freqs) to [1,250] V
Voltage stepping [seems to be 12] mV.
CPU Family	   [6] Model [16] Stepping [M0] or [13]

kern.exec: unknown type returned
hw.ncpu = 2
hw.cpufrequency = 1000000002
hw.availcpu = 2
hw.ncpu: 2
hw.activecpu: 2
hw.cpufrequency_max: 1500000003
hw.cpufrequency_min: 1000000002
hw.cpufrequency: 1000000002
hw.cpufamily: 1114597871
hw.cpu64bit_capable: 1
hw.cpusubtype: 4
hw.cputype: 7
hw.logicalcpu_max: 2
hw.logicalcpu: 2
hw.physicalcpu_max: 2
hw.physicalcpu: 2
machdep.cpu.address_bits.virtual: 48
machdep.cpu.address_bits.physical: 36
machdep.cpu.cache.size: 2048
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.linesize: 64
machdep.cpu.arch_perf.fixed_width: 40
machdep.cpu.arch_perf.fixed_number: 3
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.width: 40
machdep.cpu.arch_perf.number: 2
machdep.cpu.arch_perf.version: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.dynamic_acceleration: 0
machdep.cpu.thermal.sensor: 1
machdep.cpu.mwait.sub_Cstates: 139808
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.cores_per_package: 2
machdep.cpu.logical_per_package: 2
machdep.cpu.extfeatures: XD EM64T
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL EST TM2 SSSE3 CX16 TPR PDCM
machdep.cpu.brand: 0
machdep.cpu.signature: 1789
machdep.cpu.extfeature_bits: 537919488 1
machdep.cpu.feature_bits: -1075053569 58269
machdep.cpu.stepping: 13
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 0
machdep.cpu.model: 15
machdep.cpu.family: 6
machdep.cpu.brand_string: Intel® Core™2 Duo CPU	 T5250  @ 1.50GHz
machdep.cpu.vendor: GenuineIntel

 

+Attached CPUZ dump

 

"PerformanceStateArray" = (<dc050000b88800000a0000000a0000002b0900002b090000>,<e8030000803e00000a0000000a0000001306000013060000>)

 

Undervolting works good ! thanks superhai !

cpuz.txt

Link to comment
Share on other sites

Hi Superhai, thank you very much for your work, is a great tool for us.

 

With the last kext receives this error in the System.log:

Oct 14 03:26:14 macoffs-vgn-fw11e kernel[0]: GenericCPUPowerManagement: [Warning] Unable to get ACPI powerstates

The app seems to work fine, Autothrottle, Throttle Now and menu icons...

 

ioreg -lw0 | grep PerformanceStateArray

    | |     |   "PerformanceStateArray" = 
(<db080000b88800000a0000000a0000002509000025090000>,
<da080000b88800000a0000000a0000001c4800001c480000>,
<40060000983a00000a0000000a0000001706000017060000>,
<20030000e02e00000a0000000a0000000d8600000d860000>)

 

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

"CPU Status" = {"Auto Throttle"=No,"Load"=0x3c,
"Temperature"=0x2e,"High jump"=0x258,"Voltage"=0x426,
"Timer"=0xfa,"Low jump"=0x190,"Frequency"=0x855,"Kext Timer"=0x668,
"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0x1c,"Frequency ID"=0x8}
"CPU Init" = {"CTL max"=0x925,"FSB frequency min"=0x215,"Signature"=0x10676,
"FSB frequency max"=0x42a,"CTL min"=0x860d,"Kext unlock"=No,
"Kext version"=0x10008,"Brand string"="Intel® Core(tm)2 Duo CPU P8400  @ 2.26GHz",
"Voltage max"=0x497,"Frequency min"=0x320,"Frequency max"=0x855,"Voltage min"=0x36b}

 

sysctl -a | grep freq

kern.exec: unknown type returned
hw.busfrequency = 1066666668
hw.cpufrequency = 2133333336
hw.tbfrequency = 1000000000
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 2133333340
hw.cpufrequency_min: 800000001
hw.cpufrequency: 2133333336
hw.busfrequency_max: 1066666668
hw.busfrequency_min: 533333334
hw.busfrequency: 1066666668

post-169936-1223942365_thumb.pngpost-169936-1223942874_thumb.png

 

Greetings, MacOff

Link to comment
Share on other sites

mine is also unable to get ACPI powerstates..data is as follows.. ty

	| |		 "PerformanceStateArray" = (<290a0000007d00000a0000000a000000290e0000290e0000>,<280a0000187900000a0000000a000000220d0000220d0000>,<d0070000d85900000a0000000a0000001e0a00001e0a0000>
,<40060000504600000a0000000a0000001b0800001b080000>,<b0040000c83200000a0000000a0000001706000017060000>,<20030000102700000a0000000a0000001388000013880000>)

	  "CPU Status" = {"Auto Throttle"=Yes,"Load"=0xa0,"Temperature"=0x22,"High jump"=0x258,"Voltage"=0x3b6,"Timer"=0xfa,"Low jump"=0x190,
"Frequency"=0x320,"Kext Timer"=0x16c,"Kext Online"=Yes,"Current state"=0x3,"Voltage ID"=0x13,"Frequency ID"=0x88}
  "CPU Init" = {"CTL max"=0xe29,"FSB frequency min"=0x190,"Signature"=0x10676,"FSB frequency max"=0x320,
"CTL min"=0x8813,"Kext unlock"=No,"Kext version"=0x10008,"Brand string"="Intel(R) Core(TM)2 Duo CPU	 T9500  @ 2.60GHz","Voltage max"=0x4c9,"Frequency min"=0x258,
"Frequency max"=0xa28,"Voltage min"=0x3b6}

kern.exec: unknown type returned
hw.busfrequency = 800000000
hw.cpufrequency = 800000000
hw.tbfrequency = 1000000000
hw.tbfrequency: 1000000000
hw.cpufrequency_max: 2600000006
hw.cpufrequency_min: 600000000
hw.cpufrequency: 800000000
hw.busfrequency_max: 800000000
hw.busfrequency_min: 400000000
hw.busfrequency: 400000000

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...