I have been having a **** of a time with OSX10.11 and a Macbook Pro (circa 2014) waking from sleep. About 90% of the time, if it goes to sleep when the lid is closed, when it wakes one of two things will happen. 1) most often, the login screen will appear, cursor blinking, sounds, etc, but the mouse and keyboard, either internal or external, are frozen. Only the power button will work to force a shutdown. 2) occasionally, the screen will appear as though I'm looking at a second monitor at the login screen (I see only frosted background, no login prompt). If I blindly type the password, it will log in, but I can't swipe to switch screens or bring the mouse "over" to the screen. I can use command key combinations to force a restart. I've scoured the logs. It looks like a lot of crap is happening on wake, but nothing obvious. I've also had to reset the NVRAM a couple of times because I only get a black screen on boot, no sound. Is any one else having similar issues?
Problems waking from sleep
You are not alone,
I've a Macpro (end 2013) with Promise THB2 dicks and a USB 3 swith. when the MAc is entering on standby (sleep) after few seconds everything goes to sleep.
After 1-2 seconds USBsw and HDD wake up ... then the procees is entering in a random situation and the devices goes to standby and wake without control, often the MAc is showing the disc as unpluged incorrectly.
This is happening since the El Capitan installation, No complains with Yosemite........
I tried with out succes to change values in system preferences including BT setup.
I hope it will be solved by new releases of the beta!!!
I've been having similar issues on 15A215h:
- Unable to wake my late 2013 27" iMac with Apple's USB keyboard. Can only wake with a mouse click on my Razer Taipan.
- Frustratingly long length of time stuck at the "frosted glass" stage without the ability to enter input
- Occasionally, the password box doesn't even appear
I've also noticed random wakes during the day/night, but not due to network activity as far as I know. This was also happening occasionally in 10.10, so this issue isn't necessarily 10.11-specific