Experimental Intel SpeedStep kext

DrDeelay · August 6, 2008

Hi there!

CPU Typ Mobile DualCore Intel Core 2 Duo T5500, 1666 MHz (10 x 167)

Motherboard Name BenQ Joybook R55v

Motherboard Chipsatz Mobile Intel Calistoga-PM i945PM

Arbeitsspeicher 2048 MB (DDR2 SDRAM)

DIMM1: Hynix HYMP512S64CP8-C4 1 GB DDR2-533 DDR2 SDRAM (5-4-4-12 @ 266 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)

DIMM3: Aeneon AET760SD00-30DB97X 1 GB DDR2-667 DDR2 SDRAM (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)

BIOS Typ Phoenix (02/06/07)

Works great with Vanilla-Kernel 9.4. Can change Frequency manually and dynamic.

keep up the great work, please... :-)

DrDeelay!

THe KiNG · August 6, 2008

OMG so this is "The light at the end of the tunnel..."

Really great work guys!

Now my results:

INFO  P-State 0: 2401 MHz at 1212 mV, consuming 35 W
INFO  P-State 1: 2400 MHz at 1137 mV, consuming 35 W
INFO  P-State 2: 2000 MHz at 1100 mV, consuming 28 W
INFO  P-State 3: 1600 MHz at 1050 mV, consuming 22 W
INFO  P-State 4: 1200 MHz at 1000 mV, consuming 16 W
INFO  P-State 5: 800 MHz at 925 mV, consuming 14 W

bash-3.2# sysctl kern.cputhrottle_freqs
kern.cputhrottle_freqs: 800 1200 1600 2000 2400 2401 
bash-3.2# sysctl -w kern.cputhrottle_curfreq=800
kern.cputhrottle_curfreq: 2400 -> 1200
bash-3.2# sysctl -w kern.cputhrottle_curfreq=1200
kern.cputhrottle_curfreq: 1200 -> 1200
bash-3.2# sysctl -w kern.cputhrottle_curfreq=1600
kern.cputhrottle_curfreq: 1200 -> 1600
bash-3.2# sysctl -w kern.cputhrottle_curfreq=2000
kern.cputhrottle_curfreq: 1600 -> 2000
bash-3.2# sysctl -w kern.cputhrottle_curfreq=2400
kern.cputhrottle_curfreq: 2000 -> 2400
bash-3.2# sysctl -w kern.cputhrottle_curfreq=2401
kern.cputhrottle_curfreq: 2400 -> 2400

For some reason SpeedStep.app dosent like me beta app works but with bugs same sound problems but sound is ok when i switch freq manual in terminal so is not kext fault, only bug i found in kext is 800 & 2401 freq, both dosen't work. Also i notice a temp increase on stock freq 2400 ~51 C was never before more then 44 C

BTW that "cat /dev/urandom > /dev/null" keeps 1 core of cpu in 100%

"sudo dmesg | grep IntelEnhancedSpeedStep" returns nothing on me.

Pastebin results

mercurysquad · August 6, 2008

Hey people, please keep issues separate, ie. if it's an issue with one of the speedsteps apps, it is not in my control So if you are having problems, please close the speedstep apps and try throttling manually using the terminal (sysctl command).

Primarily I am testing the .kext because that's what's new. tuxx is working on improving SpeedStep.app (which will also support voltage changes). Will keep you all posted.

New kext will come tomorrow with a lot of the issues fixed. Please keep the test reports coming! Thanks.

lovedahackintosh · August 7, 2008

eagerly waiting the next version of this. i tried it on my inspiron 6000 (against your recommendation) and wasnt too successful. i am now using your beta 9.2 kernel from the other thread as my default as it is the only thing that FINALLY fixed my sound... even if i can only throttle down to 1ghz.

any chance this (as opposed to the custom 9.2 kernel) will eventually work for sse2 cpus?

THe KiNG · August 7, 2008

Until new beta is out here is my PC results:

bash-3.2# sysctl kern.cputhrottle_freqs
kern.cputhrottle_freqs: 1596 2394 
bash-3.2# dmesg | grep IntelEnhancedSpeedStep
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x827
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x827
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x827
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x827
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x827
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 1
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x51b
IntelEnhancedSpeedStep: DBG   Throttle done.
bash-3.2# sysctl machdep.cpu && uname -a
machdep.cpu.address_bits.virtual: 48
machdep.cpu.address_bits.physical: 36
machdep.cpu.cache.size: 4096
machdep.cpu.cache.L2_associativity: 8
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: 32
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.cores_per_package: 4
machdep.cpu.logical_per_package: 4
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 VMX EST TM2 SSSE3 CX16 TPR PDCM
machdep.cpu.brand: 0
machdep.cpu.signature: 1787
machdep.cpu.extfeature_bits: 537919488 1
machdep.cpu.feature_bits: -1075053569 58301
machdep.cpu.stepping: 11
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 0
machdep.cpu.model: 15
machdep.cpu.family: 6
machdep.cpu.brand_string: Intel® Core(tm)2 Quad CPU    Q6600  @ 2.40GHz
machdep.cpu.vendor: GenuineIntel
Darwin THeKiNG-PC.local 9.5.0 Darwin Kernel Version 9.5.0: Fri Jul 25 16:58:20 PDT 2008; root:xnu-1228.7.52~1/RELEASE_I386 i386

Waiting for the new kext for testing!

Thanks!

rhyguy · August 7, 2008

This doesnt work, as well as every other sppedstep solution out there

IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI

Dell inspiron 530, intel q6600

zillac · August 7, 2008

Works great here on Thinkpad T60p, C2D T7200, "1000 1333 1666 2000" all works.

Thanks for the great work.

uuid · August 7, 2008

Q6600 on GA-P35-DS3L:

Kext loads and works fine when NOT overclocked. Available Frequencies are 1600 and 2400.

Load: http://pastie.org/249044

DMESG: http://pastie.org/249045 (and so on)

When OC'd, I get the often reported "IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI"

Thanks for the hard work! This is turning out to be a great kext! :tomato:

edit:

Sleep/resume works (did before)

Playback is smooth (3 HD videos simultaneously)

Changing frequencies between the two values seems to work (what is a reliable way to determine actual freq?)

tuxx · August 7, 2008

Changing frequencies between the two values seems to work (what is a reliable way to determine actual freq?)

the most reliable way is to read the "kern.cputhrottle_curfreq" value using sysctl. just do:

sudo sysctl -a kern.cputhrottle_curfreq

mitch_de · August 8, 2008

the most reliable way is to read the "kern.cputhrottle_curfreq" value using sysctl. just do:
sudo sysctl -a kern.cputhrottle_curfreq

Thanks.

Question:

Does the new speedstep.kext trottle allone (after setup as dynamic) or does it need an running App like CPUThrottler / SpeedStep too and stops throttling when no CPUThrottler/SpeedStep is running?

I dont need (always) an feedback how fast the cpu is running (App Window/Menue).

Would be great if , if it is possible to include the throttling in the speedstep.kext itself and use CPUThrottler only for setup/changing setup.

mercurysquad · August 8, 2008

New kext out, check 1st page.

Kext does no throttling on its own. Either do it via terminal, or via one of the apps. In the future we may add autothrottle support.

SSE2 users: This will work but clock will be messed up. Even on my modified 9.2 kernel. Next beta 1.2.1 probably this evening will support sse2 with 9.2 rtc fixed kernel also, but no sleep with that unfortunately. A new universal 9.4 kernel with fixed clock+sleep is in the works as well.

Cheers.

uuid · August 8, 2008

New kext out, check 1st page.

It works! Amazing, thanks so much! I'm running my Q6600 at 1.2 volts / 1600 MHz at the moment, and seems to be stable. Anything specific that I should test?

mercurysquad · August 8, 2008

SSE2 Users - version 1.2.1 now supports SpeedStep kernels with rtcfix! Set KernelFeatures to 1 in Info.plist to enable it!

THe KiNG · August 8, 2008

Well the new kext dosen't work on my lappie stuck on 2401 MHz and is the only freq reported!

On Pc same 2 value, only thing that is changed to me is the debug info on boot.

Waiting for new beta to test.

Keep up the good work, I can see the light XD

r_o_o_s · August 8, 2008

I have a Dell D830 and I have now done som more testing. (system/kernel info below)

The bios setting dynamic accelleration seems to affect the kext.

with the old one (1.0 or 1.1 or whatever it was)

DA off: gives me 5 modes 800,1200,1600,2000,2001 (neither 800 nor 2001 works)

DA on: gives me 4 modes 800, 1200,1600,2000 (800 doesnt work, guess i need fixed kernel)

with 1.2.1b

DA off: gives me 3 modes (1200,1600,2000)

DA on: gives me 1 mode (2001)

Messing with kernelfeatures causes kernel panic

Sleep works with both kexts

Sound is affected the moment one changes mode, not else

Have a look at the end of this post for interesting voltage behaviour

/roos

_____________________________

INFO

roos-D830:~ roos$ sysctl machdep.cpu && uname -a

machdep.cpu.address_bits.virtual: 48

machdep.cpu.address_bits.physical: 36

machdep.cpu.cache.size: 4096

machdep.cpu.cache.L2_associativity: 8

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 VMX EST TM2 SSSE3 CX16 TPR PDCM

machdep.cpu.brand: 0

machdep.cpu.signature: 1786

machdep.cpu.extfeature_bits: 537919488 1

machdep.cpu.feature_bits: -1075053569 58301

machdep.cpu.stepping: 10

machdep.cpu.extfamily: 0

machdep.cpu.extmodel: 0

machdep.cpu.model: 15

machdep.cpu.family: 6

machdep.cpu.brand_string: Intel® Core2 Duo CPU T7300 @ 2.00GHz

machdep.cpu.vendor: GenuineIntel

Darwin roos-D830.local 9.2.2 Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386 i386

kern.cputhrottle_curfreq: 1200

kern.cputhrottle_curvolt: 1068

kern.cputhrottle_freqs: 1200 1600 2000

kern.cputhrottle_factoryvolts: 1068 1228 1388

kern.cputhrottle_ctl: 1559

roos-D830:~ roos$

roos-D830:~ roos$ sudo sysctl -w kern.cputhrottle_curvolt=1

Password:

kern.cputhrottle_curvolt: 1068 -> 1036

eclau · August 8, 2008

Still no go

wingrunr21 · August 8, 2008

The beta no longer works for me. dmesg output seems to show it finding the correct number of Pstates but it only finds one available scaling frequency. It also is only finding one of the "phantom" Pstates. Here is my dmesg output:

sudo dmesg | grep Intel
IntelEnhancedSpeedStep: INFO  Initializing version 1.2.1b (C) Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG   Probing for Intel processor...
IntelEnhancedSpeedStep: INFO  Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG   Processor Family 6, Model 39
IntelEnhancedSpeedStep: INFO  Starting
IntelEnhancedSpeedStep: DBG   FSB = 199 MHz
IntelEnhancedSpeedStep: INFO  On your processor, voltages can be changed in 12.5 mV steps
IntelEnhancedSpeedStep: DBG   Using data from CPU0
IntelEnhancedSpeedStep: DBG   Found 6 P-States
IntelEnhancedSpeedStep: INFO  P-State 0: 2601 MHz at 1250 mV, consuming 32 W, latency 10 usec
IntelEnhancedSpeedStep: DBG   Using 1 PStates.

mercurysquad · August 8, 2008

Sorry stupid bug in culling code showed the phantom and culled the real ones instead of the other way round :-)

Fix is being tested, original post will be updated when it seems to work.

mitch_de · August 8, 2008

Hi,

the news about the kernel flags (in your .plist) are a bit ???

"New features/fixes :

- Kernel feature autodetection, override via Info.plist key "KernelFeatures" in IOKitPersonalities. Set to -1 for autodetect (only works with new kernels which are NOT out yet), 0 = no speedstep,1ghz+, 1=speedstep kernel,1ghz+, 2=speedstep kernel,less than 1ghz support."

In the downloaded new kext, there is kernelFeatures = -1, which means only for kernels which did not exist now?

To what number have i switch(edit .plist) if i have normal vanilla , 0 = no speedstep,1ghz+ ?

i use 0. Perhaps better to change the DL version with 0 as default.

Get:

kern.cputhrottle_curfreq: 1864

kern.cputhrottle_curvolt: 1340

kern.cputhrottle_freqs: 1398 1864 2330

kern.cputhrottle_factoryvolts: 1564 1564 1564 (cool!)

kern.cputhrottle_ctl: 2088

E4400 2330 max, trotteling is working well (as last version).

If i want to change volts, which steps are to set ?

(only steps of 2 mV, even Voltages), would 1500 an value which could word (1,500 V insted of 1,564 V)

Thanks

wingrunr21 · August 8, 2008

Sorry stupid bug in culling code showed the phantom and culled the real ones instead of the other way round :-)
Fix is being tested, original post will be updated when it seems to work.

Ok, sounds good!

mercurysquad · August 8, 2008

Ok, fixed version 1.2.1c is out. Please download that one instead. Sorry that the bug slipped in (hey it's beta!). Thanks to The_King for beta testing.

As for the KernelFeatures flag, here is the explanation:

Using -1 is safest, and recommended for anyone with SSE3/core or better processor.

Using 0 is also generally safe. It explicitly turns off extra things not needed for SSE3 processors.

Using 1 is ONLY for those who are using a speedstep kernel on SSE2 (specially my rtcfix kernel).

Do NOT use 1 for any other kernel, it will panic.

Do NOT use 2 for any kernel at all. This will only be used in the future to force clock recalibration and speed<1ghz. Currently it will panic on ALL kernels.

Even when our universal speedstep+sleep kernel is out, use -1. This will make the kext autodetect which features to use.

Hope that clears up the confusion.

About the voltage steps: it will either be 16 mV or 12.5 mV depending on your processor. If you do sudo dmesg just after loading the kext, the log messages will tell you what voltage step your processor supports. If you set a voltage in any other step, it's not a problem, kext will choose the nearest voltage that your processor supports. It will also not allow setting to too high voltage.

Minimum voltage is 700mV or 712.5 mV depending on CPU. If you set a voltage too low, processor will automatically use the lowest voltage it will support.

mitch_de · August 8, 2008

Thanks!

I tried VID setting now.

kern.cputhrottle_curfreq: 1398

kern.cputhrottle_curvolt: 1564

kern.cputhrottle_freqs: 1398 1864 2330

kern.cputhrottle_factoryvolts: 1564 1564 1564

my kern.cputhrottle_curvolt without chaning (factory) was 1564

e180058210:~ ami$ sysctl -w kern.cputhrottle_curvolt=1464

kern.cputhrottle_curvolt: 1340 (??)

sysctl: kern.cputhrottle_curvolt: Operation not permitted sudo needed ?( but -a shows that 1340)

kern.cputhrottle_curfreq: 1398

kern.cputhrottle_curvolt: 1340

kern.cputhrottle_freqs: 1398 1864 2330

kern.cputhrottle_factoryvolts: 1564 1564 1564

kern.cputhrottle_ctl: 1576

Are there fixed steps (i read at Intel that there are 12,5 mV Steps,)

12,5 mV = 12,5 in our numbers.

AT least NO crash since 2 hours (using the first version of VID +/-) using kernel flag 0

Now setting it (fixed) to 1864 MHZ

kern.cputhrottle_curfreq: 1864

kern.cputhrottle_curvolt: 1340

kern.cputhrottle_freqs: 1398 1864 2330

kern.cputhrottle_factoryvolts: 1564 1564 1564

kern.cputhrottle_ctl: 2088

But kern.cputhrottle_curvolt didnt use the setting before, it stays at 1340 mV.

mercurysquad · August 8, 2008

Thanks!

I tried VID setting now.

my kern.cputhrottle_curvolt without chaning (factory) was 1564

e180058210:~ ami$ sysctl -w kern.cputhrottle_curvolt=1464

kern.cputhrottle_curvolt: 1340 (??)

sysctl: kern.cputhrottle_curvolt: Operation not permitted sudo needed ?( but -a shows that 1340)

sysctl ern.cputhrottle_curvolt also gives 1340

Are there fixed steps (i read at Intel that there are 12,5 mV Steps,)

12,5 mV = 12,5 in our numbers.

AT least NO crash since 2 hours (using the first version of VID +/-) using kernel flag 0

Please read the explanation above about voltage steps.

Your voltage depends on frequency, so if the voltage doesn't make sense (ie. too low or otherwise), check the frequency. For lower frequency, voltage is lower. Best to always check using sysctl -a | grep throttle. So you see the possible frequencies and their corresponding voltages along with current freq and voltage the cpu is running at. Most probably your processor was running at a frequency whose voltage was 1340 mV.

Also, you need to add sudo before sysctl to be able to change any values.

UPDATE: According to the additional info you posted, it seems (once again) ACPI is to blame -- it is not giving proper data. The _curvolt is read directly from the CPU, and the CPU is properly reporting 1340 mV, but ACPI is reporting 1564 mV for all frequencies (which is clearly VERY high). For the next version we are going to add pstate tables for a lot of processors to avoid relying on ACPI.

For now you can make your own pstate table in the info.plist. You can get the voltages for each frequency by switching the curfreq and then checking the curvolt. Switch to each fequency and make a not of its voltage. Then ediit Info.plist and set the proper freq/voltage, and change the name of the array from PStateTableDisabled to PStateTable.

wingrunr21 · August 8, 2008

Very nice! It works properly for me now. dmesg output looks good and the phantoms are gone.

You do have to restart SpeedStep.app to get it to see the new pstates.

Still getting very slight delays when the cpu throttles but it seems a bit better than last time. Audio is not choppy and video playback is smooth.

mitch_de · August 8, 2008

Please read the explanation above about voltage steps.

... Best to always check using sysctl -a | grep throttle. So you see the possible frequencies and their corresponding voltages along with current freq and voltage the cpu is running at. Most probably your processor was running at a frequency whose voltage was 1340 mV.

Also, you need to add sudo before sysctl to be able to change any values.

OK, Sudo i clear.

But why kern.cputhrottle_curvolt value changes if the command can´t work because no permission.

Before sysctl .... kern.cputhrottle_curvolt was 1564, after (without sudo) 1340.

Or is it only changed in value but NOT in real.

But my factory settings are all the same for the VID

kern.cputhrottle_curfreq: 1864

kern.cputhrottle_curvolt: 1340

kern.cputhrottle_freqs: 1398 1864 2330

kern.cputhrottle_factoryvolts: 1564 1564 1564

Experimental Intel SpeedStep kext

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites