Problem with waking from sleep with 10.8.2

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)

Posted on Sep 21, 2012 1:53 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 26, 2012 11:47 PM

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

267 replies
Question marked as Top-ranking reply

Oct 26, 2012 11:47 PM in response to SusanLake

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

Sep 26, 2012 5:33 AM in response to CalChloe

THANK YOU. This seems to be the solution. My computer woke up this morning for the first time since I installed 10.8.2. Let's hope it stays "fixed."


I'm reposting the solution provided by CalChloe


1. Boot up holding down the CMD and R keys to get to Disk Utilities.

2. Run Repair Permissions. (I had lots of permission fixes needed)

3. Run Repair Disk. (My disk had no problems.)


4. Close out of the Disk Utilities and boot the machine.


5. Open the Finder. Hold down the Option key, choose GO from the menu and select LIBRARY.


6. From the Library drag the CACHE fold and the COOKIES folder to the trash.


7. Delete the trash. (I missed this step the first time I tried. In order to get my trash completely empty, I had to restart and delete a final cache.db file that wouldn't go away.)


I also reset my SMC just for good measure.

Oct 19, 2012 10:55 AM in response to SusanLake

Hi,


I had the same problem after installing a new SSD and reinstalling Mountain Lion fresh from the AppStore: after going to sleep I got problems when waking up. Either the whole system froze instantly, sometimes I could use it but within seconds one application by another started to freeze. It seems, the system could not access the disk (no entries were written into the system.log upon wakeup !)


I finally solved the issue by first starting the original 10.8.0 Installer which gave me - after reboot into the main installer - the option to "repair" (or "restore") my system.


After that everything worked perfectly. All my settings still existed.

I only got some problems which were resolved after clearing all cashes etc. (using Onyx).

As the latest iPhoto won't work with 10.8.0 (needed 10.8.2) I finally decided to give it a try using the downloaded Combo-Installer (10.8.2) from apple.com.


Now I am using 10.8.2 incl. Suppl.Update for over a week with no problems concerning wake up from sleep !


Hope, it will help you !

Oct 28, 2012 1:24 PM in response to Chet Rindfuss

bummer, sorry to hear this didn't help.


clearly, there are various video driver / sleep issues going on, I even read on the NVidia site about known osx/sleep issues.


If you look closely at your /var/log/system.log - if you find something like this line:


NVDA::setPowerState(0xffffff801df17000, 0 -> 1) timed out after 45476 ms


then you know this is likely a video driver problem. If so, then I'd keep my eye on the nvidia website, maybe even try emailing their support so you can get notified when an update does come out for you.


it was that message that popped up at precisly the time my machine would freeze up - and after my driver upgrade, that message no longer shows up, and I no longer have the problem. if you're lucky, they'll be releasing more updates soon.


Best of luck.

Rob

Jan 13, 2013 5:49 AM in response to laurent demaret

I'm going to add my 2 cents here since I just bought another monitor for my Mac Pro as well as upgrading to ML all in the same week before facing the sleep/wake issue.


Bonfire posted earlier in this thread somewhere a link to an update from Nviida that worked instantly for me and I didn't have to remove/add/terminal anything.


I'm going to repost this link and hopefully it can help others: http://www.nvidia.com/object/macosx-304.00.05f02-driver.html

Feb 4, 2013 1:35 PM in response to SusanLake

Hello everybody, I have the solution.

This program change the default configuration, open your terminal and type


pmset -g | grep hibernatemode


This option display your configuration of sleep mode, the default is 3. The program make 5


For back to 3, just type in your terminal


sudo pmset -a hibernatemode 3


And congratulations!!!


Problema com deepsleep.com no Mac 10.8


Olá a todos, eu tive problema após instalar esse componente em meu Mac, pois toda vez precisava ser reiniciado, quando eu fechava a tela era para hibernar e simplesmente ao voltar travava, perdia tudo.


Desistalei o widget e nada, então fui ver o que ele fez no terminal. Ele muda a configuração padrão de sleep.


O padrão é 3, ele altera para o 5 e trava na hora de "hibernar", para ver como está sua configuração digite


pmset -g | grep hibernatemode


Caso não apareça o número 3, então volte a configuração original, para isso digite


sudo pmset -a hibernatemode 3


Agora é só baixar a tela e parabéns !!!! Tudo deve voltar ao normal.


www.site7dias.com.br

Feb 22, 2013 3:40 AM in response to SusanLake

Hello,


Just found out that on an iMac Intel model early 2008

OS-X 10.8.2 (fresh install) also gives a sleep mode buck.

I tested the same iMac with 10.7.5 and 10.6.8 and no wake up problems.

So this is definately a bug in 10.8.2


When the computer is in sleep mode and I wake up the iMac,

I see a double (stereo) distorted screen.

Changing the hibernate mode unfortunately won't help.

Change the resolution to a lower level and than back to normal won't help.

I cannot stop the 'stereo' distorted screen, untill I restart the iMac.



TEMPORARY SOLUTION

To temporary solve sleep mode problems in 10.8.2 with every Mac,

is to change the sleep mode of the iMac into 'never'.


Best regards,

Danny

Feb 22, 2013 8:02 AM in response to T3GT

Hi Billy,


Try a wired keyboard in stead of a wireless keyboard and see if this solves the wake-up problem.


If not,

go to your 'User library' and than to 'preferences'.

Delete these two files:


com.apple.screensaver.plist


com.apple.screensaver.plist.lockfile


Restart computer.

Repair disk permissions.

Try again.


If the problem is still there,

make a (temporary) new user.

Try the wake up issue in this new user and see if the problem is gone.

If the problem is gone, maybe more preferences and/ or caches in your user library became corrupted.


If problem is still there, disconnect all third party usb and firewire devices that are (wired) connected to your mac.

Try again.



Best regards,

Danny

Mar 5, 2013 1:28 AM in response to trypt

I believe that this is an in ability to wake up from "safe sleep" which turned into hibernate after a certain amount of time


there are several sleep modes:


regular sleep just cut off power to disk and monitor, but keeps the RAM powered.


safe sleep keeps RAM powered but also writes the contents of RAM to disk, just in case power is cut off (usually for laptops where battery can be drained/removed, but normally would wake up from RAM


deep sleep is full on hibernation, RAM is written to disk and the machine is shut down.


check your hibernatemode:


pmset -g | grep hibernatemode


0 = no hibernation i.e. regular sleep


1 = immediate hibernation i.e. deep sleep


3 = safe sleep


25 = agresive pageout with deep sleep.


therefore it could be that you mac can wakup from short sleeps before hibernation, i.e. before writing RAM to disk, but once memory is written to disk and power is cut off, it will not wak up.


check your hibernatemode



my first iMac (27" late 2012) was exhibited the fan going on full blast upon connecting to power, off when the machine was booted, and on again when the machine was off.


I am now on my third replacement iMac, the last two are exhibiting identical issue with sleep: the machines will go to sleep and will not wake up, and in addition the power button is disabled, i.e. pressing the power button will not restart the machine.


I am guessing that the SMC crashed, as the only course of recovery is to reset the SMC by removing power, pressing the power button for a while, and attempting to restart (does not work all the time, so I sometimes have to repeat the SMC reset procedure).


after doing some research on the net, I found how to view the hibernate mode, and saw that my machine was set to hibernate mode 5, which is NOT an approved setting, see below.


I used the system pref -> energy saver and clicked restore defaults which restored the hibernatemode to 0.


HOWVER, upon plugging in a powered USB hub, the hibernate mode was automagically reset to 5.

once at hibernate mode 5, putting the machine to sleep manually exhibited the same symptoms, i.e. not wake from sleep and disabled power button.


this was done with an apple care tech on the phone, and he recommended replacing the iMac once again, and sending me a fourth replacement!


overnight I played some more with this


I reset the hibernate mode but this time to 3 and I tried a different USB hub.


hibernate mode stayed at 3 after plugging in the USB hub.


I then created a small shell script to monitor and display the hibernate mode:


function showhibernate() {

while true

do echo -n `date` " ";pmset -g|grep hibernatemode;sleep 10

done

}


and executed it overnight


this evening after I came home from work, I noticed that the hibernate mode somehow was switched from 3 to 7!?


unfortunately, I did not have the echo `date` on the first version, so I do not know when it was switched from 3 to 7.


however, the machine did wake up from sleep... (so it seems that 7 is not as bad as 5?)


I am guessing that some powered USB hubs cause unexpected changes to the hibernatemode, which in turn cause the SMC to crash, disabling the power button.


why plugging in some powered USB hubs but not others will cause the hibernatemode to switch to 5?


why hibernate mode would automagically switch from 3 to 7?


neither 5 nor 7 are documented in the man page, and the only recommended modes are 0 3 and 25:


We do not recommend modifying hibernation settings. Any changes you make are not supported. If you choose to do so anyway, we recommend using one of these three settings. For your sake and mine, please don't use anything other 0, 3, or 25.


For now I cancled the shipment of the fourth replacement, as this seems to be an issue affecting all iMacs (and a specific USB powered hub), so that a new machine will not resolve the issue...


bottom line, remove the USB hub, and/or try another one.


hope this helps.

Mar 15, 2013 2:47 AM in response to Pharmacoapple

Pharmacoapple,


Changing sleep preferences to never solves temporary the sleeping problem on

almost every mac w've tested. Did you restart your mac after doing this?


My solution is a TEMPORARY workaround untill Apple comes with a working update.

If you shut down your computer every night,

changing the sleep modus in 'never' won't damage your mac.


If you wan't your mac to be on all day (it damages your electricity bill),

- for instance if you use your mac as a (mail)server or when it is rendering 3D etc. in the night -

downgrade to 10.7.5 since this OS has NO sleep related issues.

Mar 15, 2013 6:14 AM in response to Berend de Meyer

I'm happy to say that yesterday's 10.8.3 update solved all my problems: Mac Pro not waking properly up from sleep (I had to reboot every time) and second display not detected (connected via a standard Apple Mini-DisplayPort to VGA adapter). 🙂 Entering sleep mode also succeeds almost instantly now. Both problems seemed related to bad graphics drivers.


My config:

Mac Pro 5.1 (mid-2010)

24 GB RAM (from OWC)

Startup disk: 240 GB SSD (Intel 520 series, trim support was disabled by the update)

Graphics card: ATI Radeon HD 5770

Mar 25, 2013 1:13 PM in response to SusanLake

Mine is solved! Updated the driver for my video card, and that took care of it. I found the solution here.... although I don't know where. (Sorry) But I can tell you that someone checked the log and discovered his machine was erring out on on a video card driver issue, and discovered that was the issue, then found out that NVIDIA had recognized the problem and issued a new driver. is card - and mine: NVIDIA GeForce GT 120. But there may be similar issues with others.


I'll go see if I can find the thread. brb.


...


Found it!


https://discussions.apple.com/thread/4326602?answerId=20248681022#20248681022


Hope this helps! (It definitely did for me.)

Jul 8, 2013 6:50 AM in response to SusanLake

I don't know if anyone who has a Mac Pro has posted in this thread (the standalone desktop machine, not the laptop). I do have one, and my symptoms began long ago with the original ATI 5870 graphics card, which has since been replaced since the fan on it died. I now have the Mac edition ATI Radeon 7950, which has more or less worked flawlessly since install back in April. Until now.


My symptoms are very similar to others - usually happens during wake from sleep, machine clicks and comes alive, and sometimes the displays turn on (2 x Dell 2407WFP monitors) but remain black, and sometimes they just stay in power saver mode. Also, this will more often than not also happen when power cycling my machine immediately after this happens during wake from sleep.


I do however have happy news (at least for MP users) - there is a workaround that does not involve a power cycle! Simply unplug the display adapter plug and replug it in to the back of the machine. This has caused OS X to re-detect the displays and either I see the login prompt (I have my screensaver set to require login), or a mouse. If I see just the mouse, I just type my password and then the display comes back to life as if nothing ever happened.


This to me indicates that there is some fault in the monitor detection logic inside OS X. Somehow it is failing on waking from sleep, and then that state does not resolve itself when power cycling the machine, but unplugging / replugging in the display cable seems to reset things. Also doesn't hurt to power cycle the monitors too.


At any rate, this all started happening about 2 weeks ago, had zero issues up til then with the 7950 card.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Problem with waking from sleep with 10.8.2

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.