Jump to content

Can't read out Frequences in Commandline


yan.kun
 Share

7 posts in this topic

Recommended Posts

Hi, if I try to read out frequences, i will get following mesage:

 

imac:~ Jan$ sysctl kern.cputhrottle_freqs

second level name cputhrottle_freqs in kern.cputhrottle_freqs is invalid

 

What does this mean? Using 10.5.5 with Vanilla Kernel.

Link to comment
Share on other sites

Hi, if I try to read out frequences, i will get following mesage:

 

imac:~ Jan$ sysctl kern.cputhrottle_freqs

second level name cputhrottle_freqs in kern.cputhrottle_freqs is invalid

 

What does this mean? Using 10.5.5 with Vanilla Kernel.

 

It means the kext was not able to load.

 

Try to load the kext manually: sudo kextload /System/Library/Extensions/IntelEnhancedSpeedStep.kext

And then check the messages: sudo dmesg | grep Speed

 

If you get any WARN messages or similar, turn on DebugMessages flag in the kext's info.plist and try loading it again so it gives more detailed output.

 

Also check whether your CPU actually supports speedstep: sysctl hw | grep EST

If it doesn't print anything, your cpu doesn't support speedstep.

Link to comment
Share on other sites

  • 1 month later...

I have the same problem as yan kun, but my CPU is a Q6600, which does support SpeedStep.

After loading it by hand and doing "sudo dmesg | grep Speed"; I get "There was an error while getting PState array from ACPI. Please create your P-State table manually." many times the same Warning (It's version 1.4.0)

 

There is no overclocking going on, Ci1 and other Bios things are enables, as should for speedstep.

When doing "sysctl hw | grep EST" it prints nothing.

 

Will try activating the DebugMessages flag and post back.

 

And mercurysquad, don't bother about me, you certainly have better things to do, just if you or someone have an idea.

 

Comming back with DebugMessages.

Link to comment
Share on other sites

So after turning debugmessages on and reinstalling, it seems to load at startup.

sysctl hw | grep EST still don't give anything..

 

Here is the full output from sudo dmesg | grep Speed

 

Thank you for your attention, and don't worry about it, I can also try again in some months.

It's just that it would be nice to save a few watts.

 

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 = 266 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 = 266 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 = 266 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 = 266 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 = 266 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

Link to comment
Share on other sites

It means the kext was not able to load.

 

Try to load the kext manually: sudo kextload /System/Library/Extensions/IntelEnhancedSpeedStep.kext

And then check the messages: sudo dmesg | grep Speed

 

If you get any WARN messages or similar, turn on DebugMessages flag in the kext's info.plist and try loading it again so it gives more detailed output.

 

Also check whether your CPU actually supports speedstep: sysctl hw | grep EST

If it doesn't print anything, your cpu doesn't support speedstep.

 

 

Cannot be...

 

After "sudo dmesg | grep Speed" i only get:

 

IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>

IntelEnhancedSpeedStep: INFO Using 4 PStates.

 

 

And after "sysctl hw | grep EST":

 

Nothing!

 

 

But i have an Speedstep CPU and your kext seems to work because the fan is slower/more quiet when not loaded high......

 

Any other way to read out the current speed of the cpu?

Link to comment
Share on other sites

Cannot be...

 

After "sudo dmesg | grep Speed" i only get:

 

IntelEnhancedSpeedStep: INFO Initializing version 1.4.0 © Prashant Vaibhav <mercurysquad@yahoo.com>

IntelEnhancedSpeedStep: INFO Using 4 PStates.

And after "sysctl hw | grep EST":

 

Nothing!

But i have an Speedstep CPU and your kext seems to work because the fan is slower/more quiet when not loaded high......

 

Any other way to read out the current speed of the cpu?

 

1) Edit the Info.plist inside the kext and set DebugMessages to true so that you get more output than just those 2 lines. Don't forget to sudo touch /System/Library/Extensions after editing the plist.

 

2) It is sysctl machdep | grep EST -- NOT hw

Link to comment
Share on other sites

1) Edit the Info.plist inside the kext and set DebugMessages to true so that you get more output than just those 2 lines. Don't forget to sudo touch /System/Library/Extensions after editing the plist.

 

2) It is sysctl machdep | grep EST -- NOT hw

 

 

bash-3.2# sysctl machdep | grep EST
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

 

Any other idea?? :-D

 

 

PS: Yes, i forgot the DebugMessages...:angel:

Link to comment
Share on other sites

 Share

×
×
  • Create New...