- Joined
- Aug 31, 2010
- Messages
- 3,888
- Motherboard
- Asrock Z87E-ITX
- CPU
- i7-4770S
- Graphics
- GTX 760
- Mac
- Mobile Phone
Seems weird quoting myself
Dove into the interwebs and came back up this;
- Late iMac 2013 Does Not Have "Computer Sleep" setting in Energy Preferences.
- No Computer Sleep Setting WTF?
In a nutshell it seems the Haswell chip is handling all of the power management, and users of OEM macs are experiencing the disappearing option as well after upgrading to Mavericks. However, at the time the thread was created Apple hadn't publicly documented the change
So I was partially correct, the change came about after editing the SMC, however, I was incorrect assuming something broke. My assumption was; fans aren't spinning = system isn't going to sleep (especially in light of the change to Energy Saver), when that does not seem to be the case. I ran pmset -g in Terminal and compared my results with those of the OEM machines in the threads. They match up, which leaves me wondering if power management is working properly or am I still missing something? I'll run some more test tomorrow and report my findings.
There seems to be a modification possible to get the slider back (solution posted in the first link above). You can find the models numbers for iMac 14,n here PikerAlpha. The process seems straight forward (for hackintoshers).
I'm going to let it be for now and continue refining the build. I guess I'll have to work out another way to get the fans to match their output with the cpu.
Last but not least, follow this link if you want to know what the heck pmset is.
What you are seeing in that image is correct. I have it on several hacks here as well as with a real mac I own. The options are identical.
Having said that I didnt make any huge effort towards testing sleep on this board since I dont actually use sleep at all really. On its baby brother (Z87E-ITX) sleep works perfectly 100% and has exactly the same view as the one you show above.
Something to consider if sleep is really important is the darkwake flag. You can set this by using 'darkwake=x' where x is a value between 0 and 15 (If memory serves me right). That will mean a few reboots to test them all out but may be worth a shot.