Yosemite sleep/wake problems.

[Walril]

Well my system Clover + Yosemite sleeps/wake fine.

Just one issue, it wakes up every approx. 2 hours, then back to sleep. And sometimes, it failed to back to sleep, so the system just keeps running ON.

You would think it's Ethernet Wake Up issue, NOPE.
Bluetooth wake up issue, NOPE.

It's in Yosemite, Apples changes the way how the DNS daemons works, Apple switches to discoveryd.

And it broadcast the multicast to look for any legitimate Apple devices in your home network for communication - such as AirPlay, AppleTV, AirDrop, or so other devices.

I have to cite that this is the same issues applied to all Apple products - on MBP, it won't go to sleep probably - same thing happened to my MBP.

I have to disable the multicast, and I lost the autodiscovery of Apple devices services ability, but I don't care, because I don't use them on my network.

Refer to this post for how to disable multicast.

http://ispire.me/fix-yosemite-rtc-alarm-wakeup-issue/




with --no-multicast, my system sleeps like a beauty, untill I wake her up

Thats normal behavior though.

 

[george86]

I have read that it might be usb on the liquid cooling system and i have that too, goes to sleep and it wake up right away.. Some people said it could be usb ports or bluetooth and wifi...
George

 

[jk2309]

Thats normal behavior though.

Well, maybe it's normal. But personally I find it very annoying. I asked the system to sleep, it should sleep tight. Do Not wake up and attempt to do some stuff and back to sleep, and sometimes it failed to sleep itself.



anyway, that's just my personal choices.

 

[todesto]

After trying this and that for last three days, I came down to conclusion that some of the system that is having a sleep/wake problem has to do with USB3.0. My system worked flawlessly including sleep and wake until 10.10 and it got sleeps but won't wake up problem.
I notice GenericXHCI won't load no matter what I do and my 3.0 port doesn't get recognized as well as patched AppleHDA. (<- this I don't care as I use USB sound thru Apple Cinema).

So I disabled USB 3.0 in my bios, delete genericXHCI kext and boot and tested sleep then click the mouse to wake the system.

Voila! system wakes up.

Tested few more and it's working fine and I notice it wakes up regardless GenericXHCI is in S/L/E or not.

Definitely USB3.0 problem.

 

[nobodynose]

After trying this and that for last three days, I came down to conclusion that some of the system that is having a sleep/wake problem has to do with USB3.0. My system worked flawlessly including sleep and wake until 10.10 and it got sleeps but won't wake up problem.
I notice GenericXHCI won't load no matter what I do and my 3.0 port doesn't get recognized as well as patched AppleHDA. (<- this I don't care as I use USB sound thru Apple Cinema).

So I disabled USB 3.0 in my bios, delete genericXHCI kext and boot and tested sleep then click the mouse to wake the system.

Voila! system wakes up.

Tested few more and it's working fine and I notice it wakes up regardless GenericXHCI is in S/L/E or not.

Definitely USB3.0 problem.

I think there are multiple problems, and whichever one is plaguing you depends on your system configuration. I seem to have more or less fixed mine, or at least made it tolerable; I can wake it reliably now by first hitting a key on the keyboard or double clicking the mouse, and then pressing the power button on the system once. It starts to wake just from the keyboard or mouse action, but the display doesn't come back on until I hit the power button. Here's what I did:

I have an older Gigabyte Z68 motherboard (GA-Z68MA-D2H-B3) that has been updated to the most recent UEFI BIOS available, U1d. I'm not using processor graphics, I have an nVidia GT 640. So I thought, why have the BIOS options for processor graphics sleep and deep sleep enabled when I'm not even using processor graphics? I disabled those two options, then the improvement happened of being able to wake it from sleep with the two-step process described above (vs. the previous behavior, which was that I had to hit the reset button and reboot once the system had gone to sleep). I hope this helps someone else.

 

[beelzebozo]

Open terminal and run 'sudo pmset -g'

For a desktop, make sure that hibernate mode is set to 0 if it's set to 3.

 

[nobodynose]

Open terminal and run 'sudo pmset -g'

For a desktop, make sure that hibernate mode is set to 0 if it's set to 3.

Mine is already set to 0.

 

[jblparisi]

I am going to re post this again, as it may help some of you having hibernate/sleep problems on Yosemite.


Ok, I was able to solve my issue setting both standbydelay and standby to = 0

sudo pmset -g standbydelay 0

sudo pmset -g standby 0

If I remember the syntax correctly as I am writing this from top of my head.

This prevented (I think) the hibernate function from writing to disk (SSD) after a certain period of time, even tho technically setting hibernatemode = 0 should have taken care of that.

Hibernatemode 0 = Active RAM only.

Hibernatemode 3 = Active RAM + Physical disk

Either a bug or this was intended with Yosemite?

 

[Tenczys]

I am going to re post this again, as it may help some of you having hibernate/sleep problems on Yosemite.


Ok, I was able to solve my issue setting both standbydelay and standby to = 0

sudo pmset -g standbydelay 0

sudo pmset -g standby 0

If I remember the syntax correctly as I am writing this from top of my head.

This prevented (I think) the hibernate function from writing to disk (SSD) after a certain period of time, even tho technically setting hibernatemode = 0 should have taken care of that.

Hibernatemode 0 = Active RAM only.

Hibernatemode 3 = Active RAM + Physical disk

Either a bug or this was intended with Yosemite?

Am I going to be able to put my Hackintosh to auto sleep after this as well and

Active Profiles:AC Power -1*
Currently in use:
hibernatemode 0
womp 0
networkoversleep 0
sleep 10
Sleep On Power Button 1
ttyskeepawake 1
hibernatefile /var/vm/sleepimage
autorestart 0
disksleep 0
displaysleep 10

Those are my active profiles. I've noticed that there is ttyskeepawake set to 1. should i change it to 0 by pmset -a ttyskeepawake 0 ?

I've tried http://ispire.me/fix-yosemite-rtc-alarm-wakeup-issue/ but I need to use adobe cc and with this fix creative cloud doesn't open...

 

[Asus-Freak]

I've been testing for Yosemite sleep/wake problem with the following boards:

Asus Gryphon Z87: Works fine
Asus Z97M-Plus: Works fine
Asus Z97I-Plus: Works fine
MSI Z97M Gaming: Works fine (providing you don't OC)
ASRock Z97M Killer: Does not work (someone screwed the pooch with this bios)

All tested @bios defaults. All tested using onboard 4600. All tested with GFX650 and GFX760.
All tested tested with fresh install. All tested with Clone of my personal drive.
All tested using CloverUEFI

Conclusion: Can't really draw one as I don't have any older boards to test. It appears that sleep/wake generally works with newer hardware.

If in fact it's a Yosemite problem, isn't doesn't affect my rMBP (late2013)