Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 

3 posts in this topic

Recommended Posts

I have been trying to get full SpeedStep and Turbo on my Intel Core i5 430M in OS X Lion 10.7.4 I have patched AppleIntelCPUPowerManagement and removed NullCPUPowerManagement. I also dumped my SSDT tables and they are in /Extra. I have Generate CStates and PStates set to True in org.chameleon.Boot.plist. I am also running the lapic patched kernel to enable all four threads. MSRDumper.kext reports that 0 P states have been reached, but the HackInstaller script by digitaldreamer shows the P States 16-38. Another question, what exactly are P and C states? Sorry if this sounds a bit nooby.

Share this post


Link to post
Share on other sites

Do you have it working in Lion and trying to in ML, or just trying in Lion? Simplified explanation= P states are performance states aka. speedstep. Lowers the CPU frequency while idle and increases closer to or all the way to full rated speed when there is a demand on the CPU. C states, rather than just change active cpu frequency, will shut down various parts of the cpu while idle, with the tradeoff being some latency to get things going again when needed, but all fast enough to where you won't notice. C states are noting new and have been around since before pentium 1.

Share this post


Link to post
Share on other sites

I have been trying to get full SpeedStep and Turbo on my Intel Core i5 430M in OS X Lion 10.7.4 I have patched AppleIntelCPUPowerManagement and removed NullCPUPowerManagement. I also dumped my SSDT tables and they are in /Extra. I have Generate CStates and PStates set to True in org.chameleon.Boot.plist. I am also running the lapic patched kernel to enable all four threads. MSRDumper.kext reports that 0 P states have been reached, but the HackInstaller script by digitaldreamer shows the P States 16-38. Another question, what exactly are P and C states? Sorry if this sounds a bit nooby.

When using the

MSRDumper.kext, did you put your system under load?

In order for the kext to report all states, you'll need to stress your CPU so that it will actually run in those performance states.

Hope that helps.

 

kind regards,

MAJ

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×