My Mac Pro (early 2009 2.66 GHz Quad-Core Intel Xeon) won't wake from deep sleep after installing OS X 10.8.2 . I have the default setting set for sleep. The only way to "wake" the machine is to hold the power button down to shut down and then restart. I've reset NVRAM (pram) and tried removing power cable. Nothing helps.
Mac Pro, OS X Mountain Lion (10.8.2)
Ok, I've got great news for some of you. I've got a macpro (early 2009). After upgrading to 10.8.2 and changing the energy saver preferences to use the wake on ethernet option, I've had the un-wakeable sleep problem and its driven me nuts the past week!
I suggest you all carefully look at your /var/log/system/system.log file, as well as the /var/log/DiagnosticMessages/{date}.asl file. (you can read those with syslog -f {filename}). That is how I traced down the source of my problem.
So here's my situation. My monitors would sleep at exactly the time interval specified in energy saver preferences, note that the status light next to the powerbutton would stay solid. Then computer would then sleep roughly the time I expected it to, but rarely at the exact time. Anyways, after going to sleep, I'd hear a click and the status light would go from solid to the heartbeat thing. After reviewing the system.log, I noticed that precisely 2 hours after sleeping, the computer would go into a maintenance mode. You'll see this in the system.log:
Oct 26 14:51:25 MacPro kernel[0]: Wake reason: RTC (Alarm)
Oct 26 14:51:25 MacPro kernel[0]: RTC: Maintenance 2012/10/26 21:51:24, sleep 2012/10/26 19:51:27
Oct 26 14:51:25 MacPro kernel[0]: No interval found for . Using 8000000
Oct 26 14:51:25 MacPro kernel[0]: Graphics suppressed 0 ms
Oct 26 14:51:25 MacPro kernel[0]: Previous Sleep Cause: 5
Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0
Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face001, 0
Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0
Oct 26 14:51:25 MacPro.local configd[17]: network changed: v4(en1-:192.168.1.239) DNS- Proxy- SMB
Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face001, 0
Oct 26 14:51:28 MacPro kernel[0]: Ethernet [Intel82574L]: Link up on en1, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,af48,0de1,0200,c5e1,3800]
Oct 26 14:51:28 MacPro kernel[0]: Intel82574L::setLinkStatus - active 1face001, b
Oct 26 14:51:32 MacPro.local configd[17]: network changed: v4(en1+:192.168.1.239) DNS+ Proxy+ SMB
Oct 26 14:51:34 MacPro kernel[0]: Intel82574L::timeoutHandler - no link - reset the chipset once 1face000, 0
Oct 26 14:51:34 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0
Oct 26 14:52:05 --- last message repeated 2 times ---
Oct 26 14:52:10 MacPro kernel[0]: NVDA::setPowerState(0xffffff801df17000, 0 -> 1) timed out after 45476 ms
Note the 4th line, where it says graphics suppressed, then the last line where it says NVDA:: .... timed out.... That was the clue I needed. It seems that this maintenance mode wakes up to turn on the network interfaces, but tries to suppress the graphics card from waking up... However, the graphics card just times out. Apparently it doesn't support this action very well. I carefully watched my system and precisely 2 hours after it goes to sleep, I hear the system click, and the status light would go from heartbeat to solid.... Thats when the system freezes and you can no longer revive it. Actually, to be clear, the system was still accessible by ssh, so more accurately I'd say that probably it was just the graphics card was frozen... Nothing but a reboot would fix it. Note that I even tried issuing a reboot via SSH (thinking that was slightly safer than just holding the powerbutton), and although it did shut down some services (like SSH) it wouldn't complete the reboot and I'd still have to hit the Power button....
So anyway, now that I was pretty sure it was graphics card related (and triggered by the maintenance mode apparently related to the wake-on-lan), I googled 10.8.2 and nvidia... and what do you know? Nvidia released new drivers specifically for 10.8.2 this month!
This is the driver I needed for my stock GeForce GT 120:
http://www.nvidia.com/object/macosx-304.00.05f02-driver.html
PLEASE read the notes, it says its that this particular driver is for MacPro's only and 10.8.2 only.
Possibly check for drivers for other nvidia cards if this isn't you!
http://www.nvidia.com/Download/index.aspx?lang=en-us
So I installed the driver, rebooted, and voila, all works fine. I let it sleep, it went into maintenance mode after sleeping for two hours, and this time the monitor came on for 30 seconds, then went back to sleep (again with the heartbeat). I could issue a wakeonlan signal and then ssh in, or I could wake the computer by pressing the power button briefly. From my perspective, all is working fine. I can wake it properly from the power button, and I can wake-on-lan it properly too.
And just for reference, I use this wake-on-lan perl script. It works great, even through a router and wifi.
http://gsd.**.uminho.pt/jpo/software/wakeonlan/
I didn't realize this at first, but when sending the wakeonlan through a router you don't specify the IP address of the computer you're trying to contact. Just use the default ip (255.255.255.255 or your local network broadcast ip, like 192.168.1.255). The problem with routers is that once you're computer sleeps the router forgets your computer, so you need to broadcast the message to ALL ips and wait for the right one to match the macaddress and wake up... So just run it like "wakeonlan <macaddress>" and it works perfect. It even wakes my macbookpros connected only by wifi.
Also note that I tried the "darkwake=0" thing as well. I'm not really sure if that made any difference, but it is still set that way on my machine. You may or may not need that, I'm just not sure.
And one last note, I called applecare thinking my macpro still had coverage, but it turns out it expired a few months ago. They had me explain the problem anyways and said this is a "known issue" and that they could fix it for $59 or whatever. I told them no and figured it out on my own, but, it kinda ****** me off considering this was NOT really a hardware problem. It was an issue introduced by OS X 10.8 and I just recently PAID for this O/S upgrade. Personally I think they should be supporting this since I bought the O/S. My hardware was fine, it was the stock graphic card drivers bundled in 10.8.2 that was the problem! I fully assume that a future upgrade (maybe 10.8.3 if you're lucky) will include the updated drivers... Until then they're happy to NOT publish this simple fix anywhere and charge you for it instead. VERY LAME APPLE!
Best of luck to the rest of you. If this doesn't solve your problem, check those log files I pointed out, try to pinpoint the time your machine freezes and look for related events in the log files!
Cheers,
Rob
The reset of NVRAM did not fix the issue for me.
I'm loathed the burn and rebuild my system, so I will turn off sleep until Apple fix this stupidness. Come on down 10.8.3!
Oh yes, I will also use the Apple feedback form and let them know how I feel.
I had wondered aloud whether Apple monitors these discussion lists. Well, I just missed a phone call that turned out to be someone from Apple tech support. The voicemail said they'd try to call me again (I called back, and got the "office is closed" message).
Just thought I'd mention it since it's a promising sign.
Also, for those who might be discouraged from calling Apple (as I was) because they have an out-of-warranty machine, I just noticed that Apple gives 90 day tech support on the OS, and since Mountain Lion came out less than 90 days ago, that means everyone!
Did all the recommended steps. If my MP sleeps for more than 1 hour its toast. I know the machine is awake because it performed a TM backup. The power light was not pulsing, on solid. No display wake.
Only solution was to had shutdown and restart. I wish I never installed this. Stop using us as guinea pigs.
I installed the supplemtal update and restored my Energy Saver settings to the default last night but I'm not sure if I have left my Mac long enough to get to the deep sleep that causes the problem. I have let it sleep for a couple hours and so far the problem has not surfaced but will need to test the deep sleep state before getting too excited. I was pleased to return to my Mac after a coudple of hours this morning and wake it up without a problem. fingers crossed and I will report back either way.
Supplemental update to 10.8.2 has no positive effect on this problem.
Also unchecking "Wake for Network Access" doesn't solve it for me.
So this morning after about 8 hours of 'sleep' I had to switch my MacBook Pro off with the power button again because the screen stayed black.
When I switched it on, I ended up with the root console! The Macbook Pro had booted in single user mode for a reason unknown to me and I had to type 'exit' to perform another reboot.
This is getting weirder and weirder.
I'll stop to perform tests on this problem now and just shutdown the computer everytime I otherwise would just have closed the lid and put it into sleep mode.
I wanted to point out two things, first Rob's Nvidia driver fix worked on my Mac Pro4,1 with dual GeForce GT 120s.
Second I just realised that it seemed to also fix my 2/3 monitor wake up issue were when the monitors did wake from sleep one often was not recognized and I'd have to reboot to get all three up. Of course Mountain Lion doesn't allow Display to "detect displays" any more... progress?
I finally got the Show Display and resolution picking back by grabbing HD/Library/CoreServices/Menu Extras/Displays.menu from my backup of LIon.
Well - Ever since ML upgrade I have had ntermittent 'comatose' mac problems (mac pro 2010), two GT120 cards.
I followed this thread's tip to update the nvidia drivers and the problem was no longer intermittent -- it was permanent!
Now ever time I put mac to sleep it is unwakeable.
Definitely driver related it seems.
Wake on LAN on/off: no difference. comatose.
Help. At least the irregularly regular problem is now regularly regular. IE -- broken!
apple please help.
Eric
Early Macbook Pro 2009 same issue. Have reinstalled Mountain Lion, set wake up to 25, downloaded new Graphics update, SMC Pram done it all, was running fine for about a week, and now it's doing it all again sigh..and not only doesn't it wake up the entire system is running slow and fans are running high. I'm going to delete the Cache and Cookies again to see if that helps and to a SMC reset.
Althouth it seems like a very simple solution, I too with a late 2010 MBP have the same 'wake from sleep' issue that has seemingly plagued 1000's of people with no 10.8.3 release to address this issue.
I have found that when I am running the MBP on the battery, I do not seem to have this issue at all.
When I am running the MBP with the MagSafe Power Adapter, on many occaisoins, the lighted keyboard would be indicating that my power was fine but I too would experience the Black Screen of Nothing
I closed the cover, disconnected the MagSafe Power Adapter from the side of the MBP putting it back on ""Battery Power"" opened the MBP cover and it displays as normal.
I have done this several times and although it could be conincidence, it is working every time.
I do realize 10.8.2 was an upgrade to allow Time Machine to ''backup'' even when the Machine was in sleep mode, and perhaps this has something to do with this "wake from sleep" issue.
In the IMAC world and another thread i'm sure, the Wi-FI issue of not working after sleep seems to be connected as well. The only thing I do to remedy that is to shut WI-FI off for about 2 minutes and then turn it back on again, and that solves that problem.
These are issues that MAC users SHOULD NOT have to deal with for sure and the size of this thread regarding the "Wake From Sleep" issue should be large enough to raise the eyebrows of Apple's best technicians.
We can only hope for another ''bug'' fix release in the near future.
No fixes as of now. Interesting that you're having the problem on 10.7.5 since it's most common in 10.8.2.
Send your feedback to Apple in hopes that they'll fix it very soon.
http://www.apple.com/feedback/macosx.html
Hi Billy,
I ment the PRAM battery on the print, not the normal (power supply) battery.
Since your MacbookPro (MBP) is from 2009, the PRAM battery probably will be fine.
It's possible that the (normal) battery in your MBP was almost empty (1-3%) so needed loading.
It than sometimes happens that the MBP won't wake up.
As soon as you connect the power supply and than try to wake it after 5 minutes,
it will problably work.
Best regards,
Danny
10.8.3 was JUST RELEASED today, March 14.
Let's hope this fixes the issue!
Danny,
How can i undo these two deltes if already trashed. Meaning that when I open my lid from sleep i don't have a login screen anymore. I'd prefer one for security. Is there a command to undo this?
com.apple.screensaver.plist
com.apple.screensaver.plist.lockfile
Thanks.
I think it is safe to assume not everyone is having the same issue, on different systems, with different configurations. That said, most of the people are reporting the same symptoms as you reported: black screen, no backlight, nothing after wake. No beach ball, no kernel panics (although I experienced those periodically).
The only solution was to hold the power button to shut down, then restart.
Many work-arounds have been suggested: like disabling hibernation/sleep, and installing 3rd party apps (like SmartSleep), but that is a lousy band-aid solution that fixes nothing.
Some swear that it is a graphics driver/hardware issue, some are convinced that it is software that crashes upon sleep/during the wake procedure.
People report often that the issue is "fixed" after changing system setting, deleting pref files and temp files, or after an OS X update, but they more often than not return here to report that the issue has come back.
I have done the bandaid of turning off sleep. It has help much but I have still had the freez happen once in about 2 weeks (VS once a day). In this case, the mosue worked fully, iTunes continued to play songs and the UI was simply dead. No beach ball. It was almost as the WindowServer simply died and the only thing that would react was the mouse pointer.
BTW: This was with 10.8.3. I have since updated to 10.8.4 but have not turned sleep back on.
Back to report that EVEN after reformatting and reinstalling OSX Snow Leopard from ML the sleep-wake problem has returned!!!!
Leaves me to only assume it's a hardware related issue. In which case I give up hope. (Have a mid-2010 MBP)
Problem with waking from sleep with 10.8.2
