Yosemite sleep/wake problems.

[maxhk]

Hi guys !

I'm having same wake problems on my build (asus p5wh deluxe, c2duo e8400, HD4870 512mb,), under mavericks i've used my custom dsdt patched for my build, and there was no sleep/wake problems.

But when i installed yosemite (uni beast, clean install),
tweaked it with multibeast (user dsdt), it'd works:

lan ootb
ram and cpu speed recognized ok (it also uses different speeds, depending on load)
graphic card recognized ok
sound via patched kext
no problems with other things just wake up is getting on my nerves




Well system needs 20-30 seconds to sleep properly, and if i try to wake it up (keyboard, mouse, power button) system fans come up, but display stays in sleep, nor mouse or keyboard lights are on. I must restart computer

I've tried installing exotic patch for 4870, no difference, but if i change bios option from "repost video on s3 resume" no to yes, this time display turns on but there is black image.

i've also tried changing graphic enabler settings, ati frame buffer config, dark wake parameters, hibernation modes, and still no luck waking

I know its very old build but its still fighting

Any tip would be great.

I have the same graphics card and similar spec, and accidentally fixed the sleep/wake problems by reinstalling clover with ticking CsmVideoDxe-64 and BiosBlockIO.
I hope it'll help

 

[brotherofjared5]

My iMac defined machine was working great in Mavericks. Then I went to Yosemite and it still looked great. Sleep worked but then I started noticing what is described in this thread. For me, after a long sleep, like all day, when I return, the power light is on and the screen is blacked out but still on (on displaying all black). The USB laser mouse light is off. At that point I cant do anything with the machine but restart it.

Now If I am just sitting there and let the machine go to sleep or sleep it manually, for the most part I can wake it back up only with the power button provided that not too much time has passed.

Interestingly last night I left my GoPro style camera on and after 15-20 minutes it was set for display to sleep, that passed and the screen went off, then a few seconds later the power button went off and it was asleep. Well something like 7 hours passed according to my GoPro files which are 30 minutes each. Then the machine powered back on, and I briefly saw the Gigabyte logo and then a grey screen then that familiar screen displaying all black.

So my theory now (without helping any) is that it can sleep, but at some point it powers down more fully and thats when it breaks the sleep cycle. Im at work so I cant really test it now but thats sort of what I can gather from all the times since the Yosemite was added. But I will say one thing. Its still a perfect build AFAIC. I got a macbook pro and my build is doing stuff that the macbook isnt doing so far. A call comes in and my computer rings. Although I cant talk on the computer, no mic. But still cool.

For what its worth.

I am experiencing this exact same behavior. Sleeping for short/medium amounts of time works great, but often while I am asleep at night, the system wakes up to a black screen that is unresponsive and requires a reboot. I'm wondering if this has anything to do with some sort of deep sleep or hibernate that only kicks in after longer periods of time. Any ideas?

 

[Ozgur]

I have the same cooler h80i i might give that a try...

and I bet it'll do the trick.

 

[duntouchablepnk]

Removing Clock ID and INJECT under USB in Devices in the Clover Configurator did it for me had already downloaded another RehabMan genericUSB kext a day or 2 prior b/c i was getting a hang on the boot on USBMSC that kext fixed it for me. Sleep is now working and waking from keyboard instead of having to press the power button. Fixed autosleep by using darkwake=8 in clover configurator.

 

[duntouchablepnk]

repost

 

[jginsbu]

I am experiencing this exact same behavior. Sleeping for short/medium amounts of time works great, but often while I am asleep at night, the system wakes up to a black screen that is unresponsive and requires a reboot. I'm wondering if this has anything to do with some sort of deep sleep or hibernate that only kicks in after longer periods of time. Any ideas?

Similar problem here. Sleep/wake works for shorter periods (wakes from USB keyboard just fine), but let it sleep too long and waking results in application crashes followed by a spontaneous reboot. (The display usually awakens for me though.) There's another thread discussing this type of problem here:
http://www.tonymacx86.com/general-help/148289-memory-corrupted-after-longer-sleep.html

It could also be your system is hibernating and Clover (if that's what you're using) doesn't yet properly support waking from hibernation. You can try the following:

sudo pmset -a hibernatemode 0
sudo pmset -a standby 0
sudo pmset -a autopoweroff 0

That should disable hibernation. If you're awake to see it happen, waking up the hibernated system brings up the Clover boot loader, which indicates that the boot volume as hibernated; trying to boot the volume doesn't work, necessitating a hard reset. If you've got Clover set to automatically boot a volume, you'll just see the blank screen when you get there. Setting hibernatemode and standby to 0 has eliminated this problem for me, but I'm still experiencing the crash/reboot on wake problem discussed in the other thread.

In addition, Yosemite seems to be ignoring the darkwake=0 setting and waking every two hours or so anyway. This is a general Yosemite issues, not confined to hacks. Sometimes the system will crash and reboot during one of these darkwakes, so you may wake up to a system that is frozen/crashed/rebooted during one of these events.

I've tried a few things to fix the sleep/wake problem I'm experiencing without luck: tested for bad RAM, generated an SSDT for my system to enable native power management, tested various settings with pmset, and adjusted a few BIOS settings. With sleep disabled my system seems very stable.

 

[Asus-Freak]

It appears that some of the sleep/wake problems are Yosemite related. Apples's support forum is loaded with post on the topic but the majority of them relate to the Mac Mini Mid 2012, other models don't seem to have the problem. My rMBP (late2013) also has no issue at all.

MacRumors has many post on the topic, again mostly Mac Mini Mid 2012 with no clear solution defined. I've been testing a wide range of Z97 boards recently and confident the issues are, as far as Hack's go, bios related...

The boards in my sig (+ a few other Asus Z97 boards) have no sleep/wake issues at all with Yosemite. The Z87 counterparts also have no problem. Yet Z97 MSI and Z97 ASRock suck with the issue, you can forget 'bout making them work. Not to say a bios upgrade or a proper DSDT won't fix the problem, but at this point in time they don't offer any reason to work very hard at fixing it.

Nothing in this post helps anyone here at the moment because most people in this thread are using Gigabyte boards (no problem by the way - lol). For testing, and out of curiosity, I've got a few Gigabyte Z97 boards ordered to do my own testing. I'll post back with the results. Additionally, all system and board testing are done with CloverUEFI; it's just a bootloader, it's reliable, and properly configured has no impact on OS X functionality.

Luck with your builds...

 

[roadzy]

It appears that some of the sleep/wake problems are Yosemite related. Apples's support forum is loaded with post on the topic but the majority of them relate to the Mac Mini Mid 2012, other models don't seem to have the problem. My rMBP (late2013) also has no issue at all.

MacRumors has many post on the topic, again mostly Mac Mini Mid 2012 with no clear solution defined. I've been testing a wide range of Z97 boards recently and confident the issues are, as far as Hack's go, bios related...

The boards in my sig (+ a few other Asus Z97 boards) have no sleep/wake issues at all with Yosemite. The Z87 counterparts also have no problem. Yet Z97 MSI and Z97 ASRock suck with the issue, you can forget 'bout making them work. Not to say a bios upgrade or a proper DSDT won't fix the problem, but at this point in time they don't offer any reason to work very hard at fixing it.

Nothing in this post helps anyone here at the moment because most people in this thread are using Gigabyte boards (no problem by the way - lol). For testing, and out of curiosity, I've got a few Gigabyte Z97 boards ordered to do my own testing. I'll post back with the results. Additionally, all system and board testing are done with CloverUEFI; it's just a bootloader, it's reliable, and properly configured has no impact on OS X functionality.

Luck with your builds...

Any word if the new 10.10.1 patch fixed any of this?

 

[ImacTony]

Any word if the new 10.10.1 patch fixed any of this?

It DID NOT for me, at least not with Bluetooth. Sleep and wake are fine with a Microsoft USB mouse/keyboard, but give me fits with the Apple bluetooth keyboard/mouse. Are you using Bluetooth or wired?

A "fix" I saw on another thread is to put only the display to sleep in the Energy Saver preferences, and set the slider for computer sleep to "Never." When I think about it, both sleeps (display and computer) seemed to work on my Mountain Lion installation, but when I woke it in the morning, I would see hourly Time Machine Backups and that mail was downloaded during the night (no doubt due to the options I unknowingly chose). So how much sleep did the computer really get? My "display only" sleep/wake works fine with Bluetooth.

 

[dickybow]

You have to change configuration in Clover/config.plist
These are the correct setting to let the computer wake from keyboard/mouse/trackpad (also bluetooth apple keyboard and apple magic trackpad if you have a bluetooth dongle that support resume from sleep):

View attachment 108924

Thankyou !

My i5 3570k + GA-B75M-D3H now resumes from Sleep via keyboard/mouse and not the power button