shilohhh Posted March 12, 2014 Share Posted March 12, 2014 I'm using a 4930k with a P9X79-E WS mobo. I have working CPUPM with just an SSDT for PM created with the latest version of ssdtPRGen script. The only thing i needed to do was use the flag for the script that adds both ivy bridge fixes. No patched kext is needed.Thanks! Glad to hear it. I heard mention of problems with the CPU being properly detected to enable CPUPM. Doing a build for a friend this weekend. Link to comment Share on other sites More sharing options...
Rampage Dev Posted March 12, 2014 Share Posted March 12, 2014 I'm using a 4930k with a P9X79-E WS mobo. I have working CPUPM with just an SSDT for PM created with the latest version of ssdtPRGen script. The only thing i needed to do was use the flag for the script that adds both ivy bridge fixes. No patched kext is needed. Can you post a stock SSDT and a 4.5 GHz Turbo generated one. Thanks. Link to comment Share on other sites More sharing options...
rockitlikeithot Posted March 12, 2014 Share Posted March 12, 2014 Can you post a stock SSDT and a 4.5 GHz Turbo generated one. Thanks. Yeah no problem. I won't be back at my rig until tomorrow but once I get back I will post it. Link to comment Share on other sites More sharing options...
rockitlikeithot Posted March 13, 2014 Share Posted March 13, 2014 Can you post a stock SSDT and a 4.5 GHz Turbo generated one. Thanks. As promised... Stock SSDT: https://www.dropbox.com/s/9ewl7z7r95yijmx/SSDT.aml 4.5 SSDT: https://www.dropbox.com/s/kd1qx4fau6at5z4/SSDT.aml Link to comment Share on other sites More sharing options...
xelanaiznac Posted March 13, 2014 Share Posted March 13, 2014 As promised... Stock SSDT: https://www.dropbox.com/s/9ewl7z7r95yijmx/SSDT.aml 4.5 SSDT: https://www.dropbox.com/s/kd1qx4fau6at5z4/SSDT.aml so are you using the vanilla appleintelcpupowermanagement.kext or are you using a modified one? which version of fakesmc.kext? Link to comment Share on other sites More sharing options...
rockitlikeithot Posted March 13, 2014 Share Posted March 13, 2014 so are you using the vanilla appleintelcpupowermanagement.kext or are you using a modified one? which version of fakesmc.kext? I am using the vanilla appleintelcpupowermanagement.kext and i'm using the fakesmc.kext from Rampage Dev's .dmg. Link to comment Share on other sites More sharing options...
xelanaiznac Posted March 13, 2014 Share Posted March 13, 2014 I am using the vanilla appleintelcpupowermanagement.kext and i'm using the fakesmc.kext from Rampage Dev's .dmg. fantastic. working like a charm for me! i'm using 4960x and finally i'm using too vanilla appleintelcpupowermaagement.kext and latest version of fakesmc (but with some plugins from rampagedev's fakesmc, like test.kext and fakesmckeystore.kext). how can i send the ssdt to rampage? i have not his mail Link to comment Share on other sites More sharing options...
shilohhh Posted March 13, 2014 Share Posted March 13, 2014 He'll get it from here or you can find his email on his site Link to comment Share on other sites More sharing options...
xelanaiznac Posted March 13, 2014 Share Posted March 13, 2014 Can you post a stock SSDT and a 4.5 GHz Turbo generated one. Thanks. hi rampage. here a ssdt for the 4960x (made with -w 3) at stock freq, turbo 4000 https://dl.dropboxusercontent.com/u/58538839/ssdt-1.aml.dmg done using vanilla appleintelcpupowermanagement Link to comment Share on other sites More sharing options...
xelanaiznac Posted March 14, 2014 Share Posted March 14, 2014 hi rampage. here a ssdt for the 4960x (made with -w 3) at stock freq, turbo 4000 https://dl.dropboxusercontent.com/u/58538839/ssdt-1.aml.dmg done using vanilla appleintelcpupowermanagement hi rampage, here the 4960x with turbo 4500 https://dl.dropboxusercontent.com/u/58538839/ssdt-1%204.5%204690x.aml.zip Link to comment Share on other sites More sharing options...
stinga11 Posted March 15, 2014 Share Posted March 15, 2014 In the second beta of 10.9.3 the appleintelcpupowermanagement changed a little bit but the omni patch for sandy bridge-E still working. 842f01 to 852f01 3e753a to 3e9090 845f01 to 855f01 7410b9 to eb10b9 7507b9 to eb07b9 fc0274 to fc02eb 017458 to 01eb58 1 Link to comment Share on other sites More sharing options...
Rampage Dev Posted March 16, 2014 Share Posted March 16, 2014 updated to OS X 10.9.3 (13D17) New AICPUPM.kext (v.216.100.1 previous was v216.0.0) Pros Now IPG and HW monitors see OOTB low steps (cpu 2690 V2) Cons AICPUPMI now freezes my system Greater wattage and temperature shown with kextstat seems that AICPUPM is not loaded I have to do others tests but probably I will revert to first 10.9.3 beta or better to 10.9.2 added to check if mach_kernel is the same of previous versions Try roll back as well. Link to comment Share on other sites More sharing options...
omni Posted March 16, 2014 Author Share Posted March 16, 2014 It's nice that you guys are beta testing Apple's unfinished code, but perhaps we should wait till they come out officially with a final build before trying to get it working? 1 Link to comment Share on other sites More sharing options...
magnifico Posted March 16, 2014 Share Posted March 16, 2014 To clarify better: rampage, without this thread, maybe your fakesmc test.kext solution should have had a different time release.. or not? In fact, he says to do not use mac mini StepContextDict, and then with this kext it emulates, and chickens bite Link to comment Share on other sites More sharing options...
Rampage Dev Posted March 16, 2014 Share Posted March 16, 2014 Hi omni, I don't understand your statement here because forum like IM here helps to try different things before other people fixes bugs or similar stuff For me, hackintosh is a funny hobby, so I try all I can..and then if things go wrong I revert it to the previous step without complain, but only trying to understand better accordly to my knowledge. And then, people trying things in this post or in other are not beta tester? Also.. I don't understand rampagedev like :-) or maybe yes? :-P To clarify better: rampage, without this thread, maybe your fakesmc test.kext solution should have had a different time release.. or not? Apple blowup 10.9.3 to bring out issues. Let it get to a higher build number before we begin to really dig in. Also the Test.kext injects code that corrects the issue with the lower speed step not being achieved. Using the Mac Mini SMBIOS loaded other items which in turn caused issues. This is the safe way to implement the required changes. Link to comment Share on other sites More sharing options...
magnifico Posted March 16, 2014 Share Posted March 16, 2014 Apple blowup 10.9.3 to bring out issues. Let it get to a higher build number before we begin to really dig in. Also the Test.kext injects code that corrects the issue with the lower speed step not being achieved. Using the Mac Mini SMBIOS loaded other items which in turn caused issues. This is the safe way to implement the required changes. what kind of problem they had users who have used SMBIOS Mac mini, you make me understand? Link to comment Share on other sites More sharing options...
Rampage Dev Posted March 17, 2014 Share Posted March 17, 2014 It is the right way. I did not patch fakesmc at all for pm. I just put the file in there so people would not worry about it. Link to comment Share on other sites More sharing options...
magnifico Posted March 17, 2014 Share Posted March 17, 2014 It is the right way. I did not patch fakesmc at all for pm. I just put the file in there so people would not worry about it. Sure ? You are convinced that is the right way? I do not think .... try to ask someone who has the overclocked cpu ... and tell him to launch an prime 95 mac .... and see if they are stable overclock .... andrew listen with my 3930 k overclocked to 4700 emulation with the Mac mini restarts .... I had the time ... when I was working with fotoshop ... ahahahahah .... please do not say nonsense .... for me is' just aesthetics. I tell you ... and also the reason ... on asus R4 I measured the voltage tester .... and it 'all ok ... so for me it is' a mental masturbation .... Link to comment Share on other sites More sharing options...
Rampage Dev Posted March 17, 2014 Share Posted March 17, 2014 Sure ? You are convinced that is the right way? I do not think .... try to ask someone who has the overclocked cpu ... and tell him to launch an prime 95 mac .... and see if they are stable overclock .... andrew listen with my 3930 k overclocked to 4700 emulation with the Mac mini restarts .... I had the time ... when I was working with fotoshop ... ahahahahah .... please do not say nonsense .... for me is' just aesthetics. I tell you ... and also the reason ... on asus R4 I measured the voltage tester .... and it 'all ok ... so for me it is' a mental masturbation .... 4.75 GHz here and stable. OCing issues can be due to a lot of factors. Link to comment Share on other sites More sharing options...
magnifico Posted March 18, 2014 Share Posted March 18, 2014 4.75 GHz here and stable. OCing issues can be due to a lot of factors. I solved my problem ... eliminating emulation stepcontentdict Mac mini from x86 platform...lol Link to comment Share on other sites More sharing options...
shilohhh Posted March 18, 2014 Share Posted March 18, 2014 MM6,2 StepContextDict works beautifully for me. 1 Link to comment Share on other sites More sharing options...
mr. west Posted March 18, 2014 Share Posted March 18, 2014 Sabertooth X79/4930k user here. I'm on 10.9.2 using Clover, although everything I describe has happened under Chameleon as well. PM works fine for me using Vanilla AICPUPM and latest FakeSMC. However I'm having stability issues. Every once in a while it just randomly restarts. The console log isn't much help. A whole lot of mdworker errors. It follows a pattern though. Typically programs will start crashing, especially Chrome and finder. And eventually the whole ship goes down. This is the typical way. Some times it is more sudden. I've chased some red herrings when looking through the console logs, thinking it may be certain programs. But in time all the crashes persist. I've run MEMTEST86 and everything is good there. My current working theory is that with turbo and XMP and otherwise stock settings, perhaps the newly available speeds (3.9 ghz) are causing issues. So I've upped the voltage, tweaked load line calibration, etc. We'll see. I've run overclocked and the issues seem to appear faster, so perhaps that is it. My solutoin was always to go back to stock (or near) settings and run with no OC. So maybe I just need more voltage etc. on stock settings. I don't know. It is frustrating. Anyone else experiencing similar problems? Besides the random restarts it all works great. Link to comment Share on other sites More sharing options...
joe75 Posted March 18, 2014 Share Posted March 18, 2014 Open a new topic, mr. west. Restarting without a panic is usually a hardware problem. I would suspect ram, oc, psu, can also happen from not having full graphics support. Link to comment Share on other sites More sharing options...
mr. west Posted March 18, 2014 Share Posted March 18, 2014 Open a new topic, mr. west. Restarting without a panic is usually a hardware problem. I would suspect ram, oc, psu, can also happen from not having full graphics support. I'll start another thread but this seemed like an appropriate place as everything is *rock solid* when not loading a SSDT for PM. And has been for years (3820) and months (4930k pre-PM). So I'm all ears as to what could be causing the issue, but it seems like it has to be PM related. If I remove the SSDT for PM, everything is stable as can be. Link to comment Share on other sites More sharing options...
magnifico Posted March 18, 2014 Share Posted March 18, 2014 @rampage dev I know rampage that many factors help to achieve a good and stable OC, but before I was explain you that with same firmware settings I have random freeze if I use your test.kext (with inside MacMin6.2 stepcontentdict) instead, with vanilla fakesmc and MacPro6.1 SMBios.plist all is perfect. Do you understand me now? Link to comment Share on other sites More sharing options...
Recommended Posts