Jump to content

Experimental Intel SpeedStep kext


  • This topic is locked This topic is locked
290 replies to this topic

#41
eclau

eclau

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
Still no go :)

#42
wingrunr21

wingrunr21

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 496 posts
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.


#43
mercurysquad

mercurysquad

    InsanelyMac Legend

  • Retired Developers
  • 521 posts
  • Gender:Male
  • Location:India
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.

#44
mitch_de

mitch_de

    InsanelyMacaholic

  • Local Moderators
  • 2,879 posts
  • Gender:Male
  • Location:Stuttgart / Germany
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

#45
wingrunr21

wingrunr21

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 496 posts

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!

#46
mercurysquad

mercurysquad

    InsanelyMac Legend

  • Retired Developers
  • 521 posts
  • Gender:Male
  • Location:India
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.

#47
mitch_de

mitch_de

    InsanelyMacaholic

  • Local Moderators
  • 2,879 posts
  • Gender:Male
  • Location:Stuttgart / Germany
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.

#48
mercurysquad

mercurysquad

    InsanelyMac Legend

  • Retired Developers
  • 521 posts
  • Gender:Male
  • Location:India

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.

#49
wingrunr21

wingrunr21

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 496 posts
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.

#50
mitch_de

mitch_de

    InsanelyMacaholic

  • Local Moderators
  • 2,879 posts
  • Gender:Male
  • Location:Stuttgart / Germany

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 cant 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

#51
mercurysquad

mercurysquad

    InsanelyMac Legend

  • Retired Developers
  • 521 posts
  • Gender:Male
  • Location:India

OK, Sudo i clear.
But why kern.cputhrottle_curvolt value changes if the command cant 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


1) Voltage can change if the cpu speed changes. Voltage depends on cpu speed.
2) Value is not saved or cached in the kext - it is read directly from the CPU. So what you see is what the cpu is running at in real.
3) Factory setting is as reported by ACPI -- and it is often wrong. Better to use other methods like manual pstate table.

#52
mitch_de

mitch_de

    InsanelyMacaholic

  • Local Moderators
  • 2,879 posts
  • Gender:Male
  • Location:Stuttgart / Germany

1) Voltage can change if the cpu speed changes. Voltage depends on cpu speed.
2) Value is not saved or cached in the kext - it is read directly from the CPU. So what you see is what the cpu is running at in real.
3) Factory setting is as reported by ACPI -- and it is often wrong. Better to use other methods like manual pstate table.



Thanks, now all clear !

I think also manual (typing command on the fly / "real time" ) changes of VID is risky (tipping wrong numbers :( ) so pstate (in .plist) is the best way - if something to change safe.

So, installed latest kext, all running OK !!

IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c 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 15
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: DBG FSB = 233 MHz (OK)
IntelEnhancedSpeedStep: INFO On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: DBG Found 3 P-States

IntelEnhancedSpeedStep: INFO P-State 0: 2330 MHz at 1564 mV, consuming 88 W, latency 160 usec
IntelEnhancedSpeedStep: INFO P-State 1: 1864 MHz at 1564 mV, consuming 71 W, latency 160 usec
IntelEnhancedSpeedStep: INFO P-State 2: 1398 MHz at 1564 mV, consuming 56 W, latency 160 usec
IntelEnhancedSpeedStep: DBG Using 3 PStates.
e180050208:~ ami$

I will , first, not change VID, only use stepping.
The factory settings for VID are all the same - maybe like you said buggy ACPI report from bios.
kern.cputhrottle_curvolt: 1340 (REAL VIS frtom your .kext, unchanged since boot).

Now:
e180050208:~ ami$ sysctl kern.cputhrottle_curvolt
kern.cputhrottle_curvolt: 1340
e180050208:~ ami$ sudo sysctl -w kern.cputhrottle_curvolt=1292 (i have 16mV steps, so 3*16 lower)
Password:
kern.cputhrottle_curvolt: 1340 -> 1292
e180050208:~ ami$
Working , i think


Thanks

#53
lovedahackintosh

lovedahackintosh

    InsanelyMac Protégé

  • Members
  • Pip
  • 33 posts
ok, i am trying to run this on a dell inspiron 6000 which uses a pentium M 1.86. speedstep.app will not startup at all and cputhrottler only shows 0 and wont allow me to set anything

Robert-Martins-Hackbook:~ robert_martin$ sysctl kern.cputhrottle_freqssecond level name cputhrottle_freqs in kern.cputhrottle_freqs is invalid

Robert-Martins-Hackbook:~ robert_martin$ sudo dmesg | grep IntelEnhancedSpeedStep
Password:
IntelEnhancedSpeedStep: INFO P-State 2: 1067 MHz at 780 mV
IntelEnhancedSpeedStep: DBG Loaded 3 PStates from Info.plist
IntelEnhancedSpeedStep: DBG Probing for Intel processor...
IntelEnhancedSpeedStep: INFO Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG Processor Family 6, Model 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c © 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 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c © 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 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c © 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 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c © 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 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c © 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 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.2.1c © 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 13
IntelEnhancedSpeedStep: INFO Your processor doesn't support constant_tsc, but you have a kernel which can compensate for it.
IntelEnhancedSpeedStep: INFO Starting
IntelEnhancedSpeedStep: WARN EFI registry entry not found!
IntelEnhancedSpeedStep: INFO Freeing driver resources

Robert-Martins-Hackbook:~ robert_martin$ sysctl machdep.cpu && uname -a
machdep.cpu.address_bits.virtual: 32
machdep.cpu.address_bits.physical: 32
machdep.cpu.cache.size: 2048
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.linesize: 64
machdep.cpu.arch_perf.fixed_width: 0
machdep.cpu.arch_perf.fixed_number: 0
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.events_number: 0
machdep.cpu.arch_perf.width: 0
machdep.cpu.arch_perf.number: 0
machdep.cpu.arch_perf.version: 0
machdep.cpu.thermal.ACNT_MCNT: 0
machdep.cpu.thermal.thresholds: 0
machdep.cpu.thermal.dynamic_acceleration: 0
machdep.cpu.thermal.sensor: 0
machdep.cpu.mwait.sub_Cstates: 0
machdep.cpu.mwait.extensions: 0
machdep.cpu.mwait.linesize_max: 0
machdep.cpu.mwait.linesize_min: 0
machdep.cpu.cores_per_package: 1
machdep.cpu.extfeatures: XD
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS TM EST TM2
machdep.cpu.brand: 22
machdep.cpu.signature: 1752
machdep.cpu.extfeature_bits: 1048576 0
machdep.cpu.feature_bits: -1343620097 384
machdep.cpu.stepping: 8
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 0
machdep.cpu.model: 13
machdep.cpu.family: 6
machdep.cpu.brand_string: Intel® Pentium® M processor 1.86GHz
machdep.cpu.vendor: GenuineIntel
Darwin Robert-Martins-Hackbook.local 9.2.0 Darwin Kernel Version 9.2.0: Wed Jul 30 03:20:06 IST 2008; mercurysquad; based on ToH kernel:xnu-1228.3.13/BUILD/obj/RELEASE_I386 i386

Robert-Martins-Hackbook:~ robert_martin$ sysctl -a | grep throttle
kern.exec: unknown type returned

any ideas?

#54
mercurysquad

mercurysquad

    InsanelyMac Legend

  • Retired Developers
  • 521 posts
  • Gender:Male
  • Location:India
You must use an EFI bootloader for this kext to function properly. Next version will add an Info.plist option if you are using nonEFI, but for now just switch to Chameleon or another EFI bootloader.

#55
lovedahackintosh

lovedahackintosh

    InsanelyMac Protégé

  • Members
  • Pip
  • 33 posts
lol. you replied just as i fixed it.

btw, its working now with chameleon efi and i still have no stuttering. i am going to switch to a sleep kernel to see if that still holds true.

#56
lovedahackintosh

lovedahackintosh

    InsanelyMac Protégé

  • Members
  • Pip
  • 33 posts
ok, worked great on the first bootup after i unloaded acpicputhrottle.kext and moved the folder to the trash, then loaded intelenhancedspeedstep and started cputhrottler (speedstep wont load). but after i rebooted it crashes everytime i load the kext and try and set cpu speed (either with a gui or manually)

here is my output:
Robert-Martins-Hackbook:~ robert_martin$ sudo dmesg | grep IntelEnhancedSpeedStep
Password:
IntelEnhancedSpeedStep: INFO P-State 1: 1600 MHz at 1276 mV, consuming 23 W, latency 10 usec
IntelEnhancedSpeedStep: INFO P-State 2: 1333 MHz at 1180 mV, consuming 20 W, latency 10 usec
IntelEnhancedSpeedStep: INFO P-State 3: 1067 MHz at 1084 mV, consuming 17 W, latency 10 usec
IntelEnhancedSpeedStep: WARN Skipping PState frequency 800 MHz because your kernel/CPU doesn't appear to support it.
IntelEnhancedSpeedStep: DBG Using 4 PStates.
Robert-Martins-Hackbook:~ robert_martin$
Robert-Martins-Hackbook:~ robert_martin$ sysctl machdep.cpu && uname -a
machdep.cpu.address_bits.virtual: 32
machdep.cpu.address_bits.physical: 32
machdep.cpu.cache.size: 2048
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.linesize: 64
machdep.cpu.arch_perf.fixed_width: 0
machdep.cpu.arch_perf.fixed_number: 0
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.events_number: 0
machdep.cpu.arch_perf.width: 0
machdep.cpu.arch_perf.number: 0
machdep.cpu.arch_perf.version: 0
machdep.cpu.thermal.ACNT_MCNT: 0
machdep.cpu.thermal.thresholds: 0
machdep.cpu.thermal.dynamic_acceleration: 0
machdep.cpu.thermal.sensor: 0
machdep.cpu.mwait.sub_Cstates: 0
machdep.cpu.mwait.extensions: 0
machdep.cpu.mwait.linesize_max: 0
machdep.cpu.mwait.linesize_min: 0
machdep.cpu.cores_per_package: 1
machdep.cpu.extfeatures: XD
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS TM EST TM2
machdep.cpu.brand: 22
machdep.cpu.signature: 1752
machdep.cpu.extfeature_bits: 1048576 0
machdep.cpu.feature_bits: -1343620097 384
machdep.cpu.stepping: 8
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 0
machdep.cpu.model: 13
machdep.cpu.family: 6
machdep.cpu.brand_string: Intel® Pentium® M processor 1.86GHz
machdep.cpu.vendor: GenuineIntel
Darwin Robert-Martins-Hackbook.local 9.2.0 Darwin Kernel Version 9.2.0: Wed Jul 30 03:20:06 IST 2008; mercurysquad; based on ToH kernel:xnu-1228.3.13/BUILD/obj/RELEASE_I386 i386
Robert-Martins-Hackbook:~ robert_martin$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 1867
kern.cputhrottle_curvolt: 1356
kern.cputhrottle_freqs: 1067 1333 1600 1867
kern.cputhrottle_factoryvolts: 1084 1180 1276 1356
kern.cputhrottle_ctl: 3625
Robert-Martins-Hackbook:~ robert_martin$



so i reinstalled ACPICPUThrottle.kext, loaded it, unloaded it....and now everything works again

#57
mitch_de

mitch_de

    InsanelyMacaholic

  • Local Moderators
  • 2,879 posts
  • Gender:Male
  • Location:Stuttgart / Germany
If speedstep didnt start: you must set rights (look at post on the first site of this thread, someone explains how).
Or perhaps you can find some information in the console.

VID trottleling up/down works !
I was a bit unsure what happens if i lower VID at low speed time and afterwords the cpu runs at full speed.
CPU changes VIS up to factory settung and back if MHZ changes. perfect.
So we can set safe settings in the .plist.
I am running last version now > 2 hours with no problem.

#58
wingrunr21

wingrunr21

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 496 posts
I'll post the SpeedStep instructions here. You must first copy SpeedStep.app to /Applications/Utilites for these commands to work or else modify the commands accordingly:

cd /Applications/Utilities/SpeedStep.app/Contents/MacOS
chmod +x SpeedStep
sudo -s
chown root:wheel SpeedStep
chmod +s SpeedStep

This was first posted by timmyj and eclau and modified slightly by me. MercurySquad, you may just want to add these commands to the first post.

Also, for those that can't get the kext to load, make sure you do this to the kext:

sudo chmod -R 755 IntelEnhancedSpeedStep.kext
sudo chown -R root:wheel IntelEnhancedSpeedStep.kext


#59
lovedahackintosh

lovedahackintosh

    InsanelyMac Protégé

  • Members
  • Pip
  • 33 posts
ok, speedstep.app is now running. thanks for that.

however, throttling still causes a system crash unless ACPICPUThrottle.kext is loaded or has previously been loaded. obviously, this limits me to only using a speedstep capable kernel (tried the 9.2 sleep kerenl but system froze going to sleep anyway...will have to figure that out later)

i have tested with ACPICPUThrottle loaded (both kexts loaded simultaneously) and with it loaded and then unloaded and both situations result in stable throttling.

ok so i now have my system running your modified kernel (which gives great rresults on audio), ACPICPUThrottle still loads at startup, Intelenhacedspeedstep.kext is installed in extensions and running and speedstep works flawlessly...

*EDIT* ok, not quite flawlessly, i went ahead and listened to a few tunes with a pair of bluetooth headphones and there was crackling and stuttering. i went back to the terminal and unloaded ACPICPUThrottle.kext and the stuttering went away. it wasnt bad which is why i only noticed it on headphones. this means that the kext must be loaded AND unloaded for proper operation

#60
Wiwi

Wiwi

    InsanelyMac Guy

  • Members
  • PipPipPipPip
  • 212 posts
  • Gender:Male
WOrks good here, now i can use vanilla kernel on my Asus Z99Sc...

Just some little sound shuttering !

Thanks a lot, waiting for a better Speedstep GUI





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy