El Capitan - Problems with sleep

[cubswinfllclssic]

Good morning!  I'd like to add my two cents here, since I'm also trying to get sleep working in El Capitan 10.11.1 with Clover.  

 

I have an older LGA775 board (GA-P35-DS3L) and NVIDIA GTX 650 graphics.  I'm seeing very similar behavior: I can put the machine to sleep and wake it up with my bluetooth mouse/keyboard, but the screen is completely black (no cursor or anything, though).

 

I get the same experience with one of several DSDT.aml files, two of them built from my F9 BIOS, or even if I don't use a DSDT and rely on Clover to patch it at runtime.

 

However, I noticed one strange thing that I'm hoping is a clue:  if the machine falls asleep on its own, I am occasionally able to wake it up without issue (after a short amount of time, like 20 minutes to an hour-- waiting more than a couple hours causes the same black screen issue).  If I manually sleep it (Apple menu --> Sleep), I consistently am able to wake it but to a black screen.  I did some digging and tried disabling hibernate using pmset in terminal, assuming that after a couple of hours it hibernates (same when I manually sleep it), but so far no luck.

 

I have played with many configurations in Clover and thus far am unable to get the machine to wake up.  I'm hoping that the fact that I'm able to get the machine to sleep and wake up when it falls asleep on its own is a good sign.  Any ideas?

[xenophon]

Well, the problem manifests in many incarnations.

 

As far as I can tell, it mostly affects Z97 systems after longer periods of sleep, when the machine goes into "standby" (not "hibernation" as defined by OS X and Clover). Apparently, memory becomes unstable after waking up (from this particular state), culminating into a freeze/reboot/kernel panic/crash.

 

I can't claim expertise on the subject, but your problem does not appear to be related. It could be anything, from, say the NVidia "Fermi freeze", to some rogue kext.

 

Sorry for not being able to help.

[Adventuro-3]

Changed to SMBIOS 14,2 and now sleep is working [for now only? I will continue to monitor].

Well, that didn't last long. Sleep is now back to not working, with the same symptoms as before. Console messages again show the problem (shortened to remove many duplicates of "Attempt to set push wake topics without dark wake enabled"):

 

11/4/15 11:26:41.519 AM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
11/4/15 11:26:41.785 AM apsd[76]: Peer [pid=422] requested push wake but lacks APSPushWakeEntitlement

I really think this has something to do with the way dark wake is used and/or provisioned in the software. Also, as stated in other threads on this forum, I think the implementation of USB and putting USB items to rest during sleep is part of the problem.

[phuanh004]

I hope somebody can solve this   

[randomusername00]

After updating to ElCap, and getting USB all sorted out, is when I actually first got sleep working

 

Part of that process for me was disabling the ASMedia USB controller via the BIOS configuration

 

Somewhere in 10.11.1, the ASMedia started working again, so I turned it back on

 

While I didn't collect proof of it, I would swear that - at that point - is when I started occasionally getting these hangs-on-wake. Only happened a few times, one with Power Napping turned on, and then a few more times after I turned that off, and manually woke the machine up after a longer sleep.

 

I have since bought an FL1100-based USB controller, and my motherboard also came with an Intel controller, so I just gave up the ASMedia and turned it off again.

I have yet to see the wake-to-dark happen since, but admittedly it wasn't that common to begin with for me