Help - Search - Members - Calendar
Full Version: Version 1.4.5 beta out now
InsanelyMac Forum > InsanelyMac Lounge > The X Labs > Intel SpeedStep
mercurysquad
Version 1.4.5 is out as a beta. Please test and report.
http://code.google.com/p/xnu-speedstep
  • "Error getting PState array from ACPI" - if you get this error with older versions, this new version will try to create a pstate table for you based on some heuristics. It is not optimal, but will give you a headstart. Later you can fine-tune the pstate table yourself.
  • Info.plist has a new key "TargetCPULoad" currently set to 30%. Change it to whatever you want to be the default.
  • Should also fix the incorrect (high or -ve) cpu frequency problem.
konistehrad
The module failed to load on my machine. Confirmed the same behavior in both xnu-dev's most recent beta (2c) and Vanilla 9.5. Attached is the dump generated by the Vanilla kernel. Vitals in the sig. Thanks again for your great work on this project! smile.gif
QUOTE
machdep.cpu.address_bits.virtual: 48
machdep.cpu.address_bits.physical: 36
machdep.cpu.cache.size: 512
machdep.cpu.cache.L2_associativity: 2
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: 544
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® Celeron® CPU E1400 @ 2.00GHz
machdep.cpu.vendor: GenuineIntel

Edit: add sysctl dump
Gugiwuz
same problem here.

QUOTE
$ sysctl machdep.cpu && uname -a
machdep.cpu.address_bits.virtual: 48
machdep.cpu.address_bits.physical: 36
machdep.cpu.cache.size: 6144
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 SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1
machdep.cpu.brand: 0
machdep.cpu.signature: 67190
machdep.cpu.extfeature_bits: 537919488 1
machdep.cpu.feature_bits: -1075053569 582653
machdep.cpu.stepping: 6
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 1
machdep.cpu.model: 23
machdep.cpu.family: 6
machdep.cpu.brand_string: Intel® Core™2 Duo CPU E8400 @ 3.00GHz
machdep.cpu.vendor: GenuineIntel
Darwin manis-macpro31 9.5.0 Darwin Kernel Version 9.5.0: Tue Oct 14 07:39:11 IST 2008; Voodoo; Beta 2c :xnu-1228.7.58/BUILD/obj/RELEASE_I386 i386


System:
OSX 10.5.5
Gigabyte GA-P35-DS3
Intel Core 2 Duo E8400
nVidia GeForce 9600 GT
4 GB Ram
SAMSUNG HD501LJ (SATA, 500GB)
aliasa_anderson
Hi Mercurysquad,

Has the memory Leak issue been fixed ?

Does this kext use ACPI_SMC_PlatformPlugin.kext to get the pstates ?

Regards
aliasa

d!g!t@lTr@sh
My system hangs during the installation wallbash.gif I install using terminal. After seemingly successful sudo copy of the file, the system just hangs ... and there's nothing I can do except hard reboot. Booting in single user mode then shows the file is not there huh.gif

Will update as it goes when I can install it!

Thanks for the release though. Great work.
d!g!t@lTr@sh
Finally installed (although still unsucessfully, using kext helper, machine still hangs after copying the kext). After repairing permissions in single mode, get a kernel panic.

CODE
machdep.cpu.brand_string: Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
Darwin Hackintosh.local 9.4.0 Darwin Kernel Version 9.4.0




mercurysquad
aaaaaaaaaaaaa .....

trying to fix the panic. hold on guys.
r0987
Works fine for me here.
yuanshijie
i just installed it and got kernel panic ! sad.gif


Model: HP Compaq V3706
CPU: T5450 1.66Ghz
Chipset:Intel PM965
OSX86 : iDeneb 1.3 10.5.5
Kernel : vanilla 9.5
Gugiwuz
update:
with Vanilla 9.5 the kext works!
aliasa_anderson
QUOTE(Gugiwuz @ Nov 25 2008, 07:04 PM) *
update:
with Vanilla 9.5 the kext works!



The earlier one did,so this one should also work.
rimmi2002
I installed the IntelEnhancedSpeedStep.kext and it installed fine. How do I check to see if it is working and doing what it is suppose to do. I was thinking the speedstep.app would have some gui function when I try to run it...nothing pops up or nothing happens. Am I suppose to only install the kext or not run the app or do I install the kext and run the app. Any help will be appreciated. Thanks.


PS- I installed version 1.4.0 since many ppl here are reporting problems with 1.4.5.
mercurysquad
QUOTE(rimmi2002 @ Nov 29 2008, 11:21 PM) *
I installed the IntelEnhancedSpeedStep.kext and it installed fine. How do I check to see if it is working and doing what it is suppose to do. I was thinking the speedstep.app would have some gui function when I try to run it...nothing pops up or nothing happens. Am I suppose to only install the kext or not run the app or do I install the kext and run the app. Any help will be appreciated. Thanks.
PS- I installed version 1.4.0 since many ppl here are reporting problems with 1.4.5.


If the kext is installed it is probably doing its job quietly in the background. You don't need to start any app.

To confirm, open Terminal and type:

sysctl -a | grep throttle

You should be able to see the current frequency and voltage, the list of available frequencies and voltages, the target cpu load, and whether auto throttle is active (kern.cputhrottle_auto: 1).
rimmi2002
QUOTE(mercurysquad @ Nov 30 2008, 07:13 AM) *
If the kext is installed it is probably doing its job quietly in the background. You don't need to start any app.

To confirm, open Terminal and type:

sysctl -a | grep throttle

You should be able to see the current frequency and voltage, the list of available frequencies and voltages, the target cpu load, and whether auto throttle is active (kern.cputhrottle_auto: 1).



When I type in the sysctl -a | grep throttle in the terminal, I get the following error: "kern.exec: unknown type returned" Does this mean the kext did not install properly or do I have a non compatible kernel runnning? Thank for your help.
aliasa_anderson
QUOTE(mercurysquad @ Nov 24 2008, 06:23 AM) *
aaaaaaaaaaaaa .....

trying to fix the panic. hold on guys.



Hi,

Has the KP been fixed ?or was this issue with old kernel only(kernels older than 9.5) ?
mercurysquad
QUOTE(rimmi2002 @ Nov 30 2008, 10:46 PM) *
When I type in the sysctl -a | grep throttle in the terminal, I get the following error: "kern.exec: unknown type returned" Does this mean the kext did not install properly or do I have a non compatible kernel runnning? Thank for your help.

The kext is compatible with all kernels. If you only get that line and don't get anything else then that means the kext is not working properly. In that case you should edit the kext's Info.plist file and set DebugMessages to true, then type sudo touch /System/Library/Extensions and reboot. After rebooting type sudo dmesg | grep Intel to see a list of debug messages. Paste those here.

QUOTE(aliasa_anderson @ Dec 1 2008, 03:01 PM) *
Hi,

Has the KP been fixed ?or was this issue with old kernel only(kernels older than 9.5) ?

Not yet, I got busy with the Voodoo kernel and other things .. once Voodoo is released I'll work on this.
aliasa_anderson
QUOTE(mercurysquad @ Dec 1 2008, 10:24 AM) *
The kext is compatible with all kernels. If you only get that line and don't get anything else then that means the kext is not working properly. In that case you should edit the kext's Info.plist file and set DebugMessages to true, then type sudo touch /System/Library/Extensions and reboot. After rebooting type sudo dmesg | grep Intel to see a list of debug messages. Paste those here.
Not yet, I got busy with the Voodoo kernel and other things .. once Voodoo is released I'll work on this.




Thanks man,no problems.

You've really inspired me to read "Mac OS X Internals By Amit Singh".I'll just grap a copy and start reading it.Chapter 10 would be of more interest to me coz of IOKit.
Anyways thanks for everything.

smile.gif
Nick14
Will this work with a P-M ? i tried superhai but i gave me problems
rimmi2002
QUOTE(mercurysquad @ Dec 1 2008, 10:24 AM) *
The kext is compatible with all kernels. If you only get that line and don't get anything else then that means the kext is not working properly. In that case you should edit the kext's Info.plist file and set DebugMessages to true, then type sudo touch /System/Library/Extensions and reboot. After rebooting type sudo dmesg | grep Intel to see a list of debug messages. Paste those here.


Thanks for your help. I made the changes you asked and below is the output. Most of the errors point to "Please create your P-State table manually"

IntelEnhancedSpeedStep: DBG Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG Starting
IntelEnhancedSpeedStep: DBG On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI. Please create your P-State table manually.
IntelEnhancedSpeedStep: DBG Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG FSB = 333 MHz
IntelEnhancedSpeedStep: DBG Probing for Intel processor...
IntelEnhancedSpeedStep: DBG Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG Starting
IntelEnhancedSpeedStep: DBG On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI. Please create your P-State table manually.
IntelEnhancedSpeedStep: DBG Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG FSB = 333 MHz
IntelEnhancedSpeedStep: DBG Probing for Intel processor...
IntelEnhancedSpeedStep: DBG Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG Starting
IntelEnhancedSpeedStep: DBG On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI. Please create your P-State table manually.
IntelEnhancedSpeedStep: DBG Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG FSB = 333 MHz
IntelEnhancedSpeedStep: DBG Probing for Intel processor...
IntelEnhancedSpeedStep: DBG Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG Starting
IntelEnhancedSpeedStep: DBG On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI. Please create your P-State table manually.
IntelEnhancedSpeedStep: DBG Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG FSB = 333 MHz
IntelEnhancedSpeedStep: DBG Probing for Intel processor...
IntelEnhancedSpeedStep: DBG Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG Starting
IntelEnhancedSpeedStep: DBG On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI. Please create your P-State table manually.
IntelEnhancedSpeedStep: DBG Freeing driver resources
IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG FSB = 333 MHz
IntelEnhancedSpeedStep: DBG Probing for Intel processor...
IntelEnhancedSpeedStep: DBG Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG Starting
IntelEnhancedSpeedStep: DBG On your processor, voltages can be changed in 16 mV steps
IntelEnhancedSpeedStep: DBG Using data from CPU0
IntelEnhancedSpeedStep: WARN There was an error while getting PState array from ACPI. Please create your P-State table manually.
IntelEnhancedSpeedStep: DBG Freeing driver resources
aliasa_anderson
QUOTE(mercurysquad @ Nov 22 2008, 01:35 PM) *
Version 1.4.5 is out as a beta. Please test and report.
http://code.google.com/p/xnu-speedstep
  • "Error getting PState array from ACPI" - if you get this error with older versions, this new version will try to create a pstate table for you based on some heuristics. It is not optimal, but will give you a headstart. Later you can fine-tune the pstate table yourself.
  • Info.plist has a new key "TargetCPULoad" currently set to 30%. Change it to whatever you want to be the default.
  • Should also fix the incorrect (high or -ve) cpu frequency problem.


Mercurysquad,
I was wondering that if I have a correct DSDT will I still get "Error getting Pstate array from ACPI" ?(Assuming i use version 1.4.4 of this kext)

Regards
Aliasa
mercurysquad
QUOTE(Nick14 @ Dec 1 2008, 11:15 PM) *
Will this work with a P-M ? i tried superhai but i gave me problems

Yes mine is heavily tested for pentium M. Superhai's kext has problems.

QUOTE(rimmi2002 @ Dec 2 2008, 11:21 AM) *
Thanks for your help. I made the changes you asked and below is the output. Most of the errors point to "Please create your P-State table manually"

OK. This was fixed in 1.4.5 but gives a kernel panic on most machine. So please wait until I fix and upload a newer version in a few days.
radioheadkid
It works GREAT for me! Fantastic!

iDeneb 10.5.5, Voodoo-RC1 kernel, and Pentium-M750 SSE2, works with all 8 PStates(800~1866 MHz)

GMA900 problem also solved, and now I have a real MacBook biggrin.gif

CODE
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 800
kern.cputhrottle_curvolt: 732
kern.cputhrottle_freqs: 1866 1733 1600 1466 1333 1200 1066 800
kern.cputhrottle_factoryvolts: 1020 988 956 908 876 844 812 732
kern.cputhrottle_ctl: 1538
kern.cputhrottle_auto: 1
kern.cputhrottle_targetload: 50

aliasa_anderson
Mercurysquad,

from where does this kext get the P-states from ?


Thanks.
Nick14
Why dont you and SuperHai work together on a Singel app
aliasa_anderson
QUOTE(Nick14 @ Dec 7 2008, 01:27 PM) *
Why dont you and SuperHai work together on a Singel app



Yeah it would be great !!! rolleyes.gif
mercurysquad
QUOTE(Nick14 @ Dec 7 2008, 06:57 PM) *
Why dont you and SuperHai work together on a Singel app


I have tried, but let me explain:

Superhai is free to fork the code and make his additions, and he did. But his version is too different now and strays from my philosophy as well as practicality. My idea is to build a kext which just works and the user doesn't need to configure much. Superhai's kext has a LOT of features and a GUI, BUT he removed many features of my kext (which in my opinion is a step backward - for example you can no longer change settings from the Terminal). Also, my main priority is Pentium M processors, but Superhai's kext doesn't work well on Pentium M (and other CPUs which need clock re-calibration) because the kext makes too many assumptions.

You can apply the same logic and say Superhai could work on my kext, but in an open-source community it doesn't really matter. Everyone has their own agenda, for me Pentium M is top priority, for Superhai, support for newer CPUs is higher priority. He seems to consistently ignore Pentium M and the most important reason I made my kext: clock re-calibration. I have suggested bugfixes and changes to Superhai but last I checked, the kext didn't contain those fixes. I don't know about the current version as the kext always crashes on my system.

Since my kext is 'good enough' and does the job for me and most people, I only have to fix bugs and add some workarounds instead of adding more and more features. So I decided to keep my project active.

In short: mine is a coservative, 'just-does-the-job' version of the original kext, and I prefer to keep control of it.
Nick14
QUOTE(mercurysquad @ Dec 7 2008, 06:29 PM) *
I have tried, but let me explain:

Superhai is free to fork the code and make his additions, and he did. But his version is too different now and strays from my philosophy as well as practicality. My idea is to build a kext which just works and the user doesn't need to configure much. Superhai's kext has a LOT of features and a GUI, BUT he removed many features of my kext (which in my opinion is a step backward - for example you can no longer change settings from the Terminal). Also, my main priority is Pentium M processors, but Superhai's kext doesn't work well on Pentium M (and other CPUs which need clock re-calibration) because the kext makes too many assumptions.

You can apply the same logic and say Superhai could work on my kext, but in an open-source community it doesn't really matter. Everyone has their own agenda, for me Pentium M is top priority, for Superhai, support for newer CPUs is higher priority. He seems to consistently ignore Pentium M and the most important reason I made my kext: clock re-calibration. I have suggested bugfixes and changes to Superhai but last I checked, the kext didn't contain those fixes. I don't know about the current version as the kext always crashes on my system.

Since my kext is 'good enough' and does the job for me and most people, I only have to fix bugs and add some workarounds instead of adding more and more features. So I decided to keep my project active.

In short: mine is a coservative, 'just-does-the-job' version of the original kext, and I prefer to keep control of it.

Thanks for the explanation well your speedstep workes prefectly on My P-m So i'm happy
aliasa_anderson
QUOTE(aliasa_anderson @ Dec 5 2008, 04:53 PM) *
Mercurysquad,

from where does this kext get the P-states from ?


Thanks.


Sorry for this question,got the answer myself,its ACPI.Please correct me if I am wrong.
If this kext(1.4.5) does not get it from there,it uses a lookup table right ?

Is it possible to use SMC plugin to get the P-states ? Like what Surehai's kext does ?
Also does this kext gather Tjmax for getting the max allowed core CPU temperature ?If this can be done,the
runaway issue can be resolved.I mean with high CPU load, Voltage will be incread up,
freq will also be stepped up but after sometime the temp will rise,if the long pending
task is not completed,the CPU temp will remain high.
So if Temp is monitored,we can use this value to reduce/step down the freq and/or voltage
after sometime
(even though it might slow the processing a bit),but this will prevent CPU from overheating[Tj nearly equal to Tjmax]
Better/safe option would be to have the condition:
Tj < (Tjmax - x),
where x is say tolerance coz at Tjmax the cpu will be automatically shutdown by thermstrip to prevent damage to the die.


Please let me your concerns.


Regards
aliasa.
kramer2k
KP upon installation and with subsequent reboot with 1.4.5 sad.gif
Specs below
moly82
hi mercurysquad, I have just installed the Speedstep.kext version 1.4.5 with kexthelper and immediately get a kernel panic (10.5.5 iDeneb voodoo kernel running on a pentium m + gma900 based notebook) and the only way to boot the system is to boot in single user mode and delete the kext.

in single user mode I can load the kext without any problem, what I can see and think it is wrong are the factoryvolts which are all the same:
CODE
bash-3.2# sysctl kern | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 800
kern.cputhrottle_curvolt: 716
kern.cputhrottle_freqs: 800 1067 1333 1733
kern.cputhrottle_factoryvolts: 2796 2796 2796 2796 2796
kern.cputhrottle_ctl: 1537
kern.cputhrottle_auto: 1
kern.cputhrottle_targetload: 30


what do you suggest? please help!! sad.gif

bye and thanks for your great work!!


EDIT: last thing, is it normal that in the Info.plist file I can see <key>PStateTableDisabled</key> ?? Why it says it is disabled?
moly82
EHILA'!!!!! I just modified the Info.plist file changing this:
CODE
<key>PStateTableDisabled</key>


into this:
CODE
<key>PStateTable</key>


then re-installed the kext with KextHelper and now I don't get the kernel panic anymore!!!! Why is it set to "disable" by default??

now it says:
CODE
Moly$ sudo dmesg | grep IntelEnh
IntelEnhancedSpeedStep: INFO  Initializing version 1.4.5 (C) Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: INFO  Loaded 4 PStates from Info.plist



...and if I run: sysctl kern | grep throttle

CODE
bash-3.2# sysctl kern | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 800
kern.cputhrottle_curvolt: 716
kern.cputhrottle_freqs: 800 1067 1333 1733
kern.cputhrottle_factoryvolts: 716 780 860 1084
kern.cputhrottle_ctl: 1537
kern.cputhrottle_auto: 1
kern.cputhrottle_targetload: 30



....and the cpu scaling seems to work automatically, as if I run some apps and try the sysctl kern | grep throttle again, I can see the "curfreq" value increasing...... so it seems that everything is working now just after changing the PStateTable key!!!!!

the only problem is that if I boot the laptop on battery, when I get to the desktop it doesn't work, it is freezed, and touchpad/keyboards don't work.. don't know why, what you think? While if I boot the system connected to the power, then I disconnect it after I get to the desktop, then it works on battery... strange... What changes if I boot with the power cord connected or not? Is the system using different kexts??

finally, can you confirm this entry is correct in my Info.plist and must be set to -1?
CODE
<key>KernelFeatures</key>
<integer>-1</integer>


and can you tell me what does this entry mean/do?
CODE
<key>TargetCPULoad</key>
<integer>30</integer>



thanks!!
marionez
CODE
sudo dmesg | grep Intel
Password:
IntelEnhancedSpeedStep: INFO  Initializing version 1.4.5 (C) Prashant Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: INFO  Loaded 4 PStates from Info.plist


CODE
sysctl kern | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 1733
kern.cputhrottle_curvolt: 987
kern.cputhrottle_freqs: 800 1067 1333 1733
kern.cputhrottle_factoryvolts: 725 775 837 1012
kern.cputhrottle_ctl: 1558
kern.cputhrottle_auto: 1
kern.cputhrottle_targetload: 35


I've never seen at 1733, I think there's something wrong, my E8400 frequency are not so low: 800 - 1067 - 1333 - 1733 as the maximum frequency.

Is that the CPU frequency?

Maybe is because I did the same edit of moly82 on Info.plist
CODE
                        <key>[b]PStateTable[/b]</key>
                        <array>
                                <array>
                                        <integer>1733</integer>
                                        <integer>1084</integer>
                                </array>
                                <array>
                                        <integer>1333</integer>
                                        <integer>860</integer>
                                </array>
                                <array>
                                        <integer>1067</integer>
                                        <integer>780</integer>
                                </array>
                                <array>
                                        <integer>800</integer>
                                        <integer>716</integer>
                                </array>
                        </array>


I removed the disabled on Table!
Should I set the CPU frequency manually?
moly82
QUOTE(marionez @ Dec 11 2008, 09:48 PM) *
I've never seen at 1733, I think there's something wrong, my E8400 frequency are not so low: 800 - 1067 - 1333 - 1733 as the maximum frequency.

Is that the CPU frequency?

Maybe is because I did the same edit of moly82 on Info.plist

I removed the disabled on Table!
Should I set the CPU frequency manually?


that table is perfect for me as I have a pentium m 1.73 GHz but probably you need different values.... why you did modify the files as I did? were you getting kernel panics? by the way yes the first value in the table is the frequency, and the second value is the relevant voltage for the that frequency value..

bye!
marionez
My lower speedstep frequency I think it's 2 GHz and it gets higher with the multiplyer 333x6=2 Ghz 333x7=2,3 GHZ 333x8=2,6 GHz 333x9=3 GHz

So is that konsole info false? I think, yes...

If I leave the TableDisabled osx won't boot.
moly82
QUOTE(marionez @ Dec 11 2008, 10:51 PM) *
My lower speedstep frequency I think it's 2 GHz and it gets higher with the multiplyer 333x6=2 Ghz 333x7=2,3 GHZ 333x8=2,6 GHz 333x9=3 GHz

So is that konsole info false? I think, yes...

If I leave the TableDisabled osx won't boot.


yes in your case I think they are not real, but in mine I think (hope biggrin.gif ) they are true..
I hope mercurysquad will come back soon so he can clarify..... angel.png
marionez
Any news?
lordbath
hello,

this is what i get from terminal:

sysctl kern | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 1067
kern.cputhrottle_curvolt: 1068
kern.cputhrottle_freqs: 800 1067 1333 1733
kern.cputhrottle_factoryvolts: 716 780 860 1084
kern.cputhrottle_ctl: 1559
kern.cputhrottle_auto: 1
kern.cputhrottle_targetload: 30

even though it says that my cpu can be set to 800, it never gets there. is there any way to force the cpu to be set to 800?? would this require setting custom values in the PStateTable??

thx
Boombeng
Hi MercurySquad, thanks very much for all the great work
I just come to delete the intelenhancedspeedstep.kext and i'm surpised to see the autothrottle still working as if the kext was still loaded (i've repaired permissions and rebooted, and verified the kext is trully not loaded). Idon't have neither genericpuetc... from Superhai. Note that the speedstep app is still working.
I also noticed that when the kext was loaded, the CPUthrottle i could see in sysctl -a | grep throttle
was not the same as in plist from kext...

Here is the sysctl -a | grep throttle when the kext is not loaded (it is the same when the kext is loaded) :

CODE
HAL:~ boombeng$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 1000
kern.cputhrottle_curvolt: 1004
kern.cputhrottle_freqs: 1000 1333 1667 2000
kern.cputhrottle_factoryvolts: 1004 1132 1260 1388
kern.cputhrottle_ctl: 1555
HAL:~ boombeng$


Is it because i patched the dsdt ? Does this mean i don't need any kext like intelenhancedetc... or GenericCPUetc... ? wacko.gif

Thx,
Jim
moly82
QUOTE(Boombeng @ Dec 15 2008, 12:52 AM) *
Hi MercurySquad, thanks very much for all the great work
I just come to delete the intelenhancedspeedstep.kext and i'm surpised to see the autothrottle still working as if the kext was still loaded (i've repaired permissions and rebooted, and verified the kext is trully not loaded). Idon't have neither genericpuetc... from Superhai. Note that the speedstep app is still working.
I also noticed that when the kext was loaded, the CPUthrottle i could see in sysctl -a | grep throttle
was not the same as in plist from kext...

Here is the sysctl -a | grep throttle when the kext is not loaded (it is the same when the kext is loaded) :

CODE
HAL:~ boombeng$ sysctl -a | grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 1000
kern.cputhrottle_curvolt: 1004
kern.cputhrottle_freqs: 1000 1333 1667 2000
kern.cputhrottle_factoryvolts: 1004 1132 1260 1388
kern.cputhrottle_ctl: 1555
HAL:~ boombeng$


Is it because i patched the dsdt ? Does this mean i don't need any kext like intelenhancedetc... or GenericCPUetc... ? wacko.gif

Thx,
Jim



did you remove the extensions cache? a part from looking in the extensions folder, did you check if the kext is really not loaded with kexstat? kexstat | grep Intel from the terminal..

bye
Boombeng
Yes i did, but i found also, following your post Moly, that the Pstate were "disabled" in the plist, so when i insert
CODE
<key>PStateTable</key>
,
I now can see the plist value in speedstep monitor and in sysctl kern | grep throttle, no more problems wink.gif
So I have to find the good values to insert in plist now because the lowest one doesn't seem to work
(even in custom clock)... or to keep the default one without the kext loaded...
Is there a data base where we can find good Pstats with CPU ref ?

[Edit] i have a C2duo T5750 2Ghz FSB667

Thx bye
mercurysquad
The PStateTableDisabled is disabled because it contains settings for Pentium M 740 (1.73 GHz) and it is not applicable to other CPUs. So before renaming it, make sure you put YOUR cpu's pstate table.

Also, it is NOT POSSIBLE to get the sysctl output if the kext is not loaded. The kext must be loaded from the Extensions.mkext, from /Extra or from other places (like /Library/Startup/SpeedStep in iATKOS 5i).
Boombeng
Ok thx for reply,
i'm using iATKOS 5i... angel.png
lordbath
hello,

can somebody please tell me or point me in the right direction how to create custom Ptables?

thx
mnfesq
I am using Speedstep on a Dell Inspiron 6000 with a single core Pentium M, running Leo 10.5.2. I physically overclocked the cpu when I first bought it by inserting a jumper in the cpu socket, which upped the FSB from 400 MHz to 533 MHz. This upped the cpu from 1.6 GHz to 2.13 GHz. By doing this, I have always had to be conscious of temperatures.

The Speedstep 1.4.5 kext has worked perfectly, along with the Speedstep app running in the start bar. When I first installed leo, the cpu ran constantly at 2.13 GHz and the fan also ran constantly at its highest speed. Temperatures ran at about 45-48 C when idling. Since installing Speedstep 1.4.5, my cpu is running at 1067 GHz when idle, and the temp is about 35-38C. That is as good as when I run Vista with the native Intel drivers.

Thank you, thank you, thank you.
Nick14
i dont known if it's supported but P4HT Isn't recongized as an Intel CPU by the KEXT
asstastic
1.4.5 crashes reading pstates from ACPI on startup

1.4.0 loads pstates without issue and has been rock solid stable

running C2D T7400 'Merom' 2.16ghz

i will soon test undervolting on 1.4.0 with custom table. i tried earlier but got crashes because i didn't step the voltage in 4mv increments.
moly82
hi mercurysquad, one question.

my specs are in the signature.. I am using your kext 1.4.5 and everything is working after modifing the plist file in order the enable the PState table... when I am using the laptop connected to the power.... the CPU scales and so on, but when I am on battery the laptop does not start... it freezes at boot without errors... what could it be? if I unload the speedstep kext then I can boot the laptop on battery but speedstep does not work..

thanks in advancve.. bye!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.