lordaskan Posted February 26, 2015 Share Posted February 26, 2015 Hi. using EDP installing Yosemite on my Lenovo x201 (meaning arrandale cpu) worked out great, almost everything works. There's just one thing that's slightly annoying. Comparing to a Linux setup, the cpu die temperature is about 10°C higher. Looking at HWMonitor reveals that the frequency is almost always at 2.53 GHz (that is one step below maximum) with occasional spikes to the lower frequency states. Interestingly, when I run SMC Monitor, I get a much higher population of the lower states (see attached screenshot, during the "wild sections" SMC Monitor was running, the values do match those of SMC Monitor). Am I having some weird measurement problem? If the values are right, when SMC Monitor is running are right, shouldn't the frequencies be ramped up more gently and generally spend more time in the lower states (considering this is idle mode, nothing really running)? Greetings, J Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 26, 2015 Administrators Share Posted February 26, 2015 Look here for pointers. There's also a very good article on CPU power management at InsanelyMac. Sorry I can't provide a link but look it up. Link to comment Share on other sites More sharing options...
lordaskan Posted February 28, 2015 Author Share Posted February 28, 2015 Hi, thanks for your hints. I finally found out, what the problem of the high temperatures was, AppleLPC.kext was not loaded. Adding the device string of the ISA bridge solved that. My feeling is, speedstep was working from the beginning, just HWMonitor can give very misleading results, SMCMonitor and DPCIManager consistently gave much more sensible data. However I tried to follow your guide and edited FakeSMC.kext according to http://www.osxlatitude.com/tuning-performance-with-fakesmc-smbios-plistand https://osxlatitude.com/index.php?/topic/7283-apple-mac-smc-keys (I think the x201 most resembles a MacBookPro 6,2). That went fine, but changing from 6,1 to 6,2 in smbios.plist caused a boot failure (errors seemed a bit unrelated, like utun0 error=6). Since everything seems to work like a charm now, I don't see any benefits from fixing that or should I? Do you recommend also reverting the fakeSMC.kext to the original version? Since that might be of interest to other x201-owners, can I somehow contribute this "patch" for AppleLPC.kext into EDP? Greetings, J Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 28, 2015 Administrators Share Posted February 28, 2015 As I wrote in the article, I invite people to make their own experiment and opt for what works best according to factual results. What worked well for the Core2Duo based Latitude D Series does not systematically apply to other and more recent system. In particular, power management is very different with Core "i" CPUs and is not configured the same way: no selection of P + C States and systematic tuned FakeSMC for Sandy/Ivy/Haswell CPUs for instance but generated SSDT, that seems to suffice... For EDP, sorry, I pass! Contact a crew member. EDP has been too problematic to my liking for several months now; I stopped using and recommending it. Publish your own guide and full pack, that's my suggestion for what it's worth... Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted February 28, 2015 Administrators Share Posted February 28, 2015 for EDP you can contact EMlyDinEsH Link to comment Share on other sites More sharing options...
Recommended Posts