Monitor not waking up after 10.9.3 update

1. What log? There is no crash, so I don't see crash report showing up. Or am I missing something?

2. No

3. No, but I am using the HDMI port, so I can't move it elsewhere. It could be a HDMI only issue, but I see other people using TB port having similar issue.

thanks.

- By using /Utilities/Console.app -> All Messages and use a search term "wake" , we are looking at system wide messages, and how apps, and the SMC detect sleep and wake events.

- Also try in /Utilities/Terminal.app, the commands: pmset -g

and pmset -g log

- a good look at man pmset also helps.

- Also confirm pmset with Energy Saver settings in System Preferences.

- Generally when there are sleep / wake issues, disable all Energy Saver settings and get to a point that all hardware is detected and works.

- Then gradually apply back Energy Saver settings via System Preferences and verify with the pmset command.

Hope this helps

As usual there are plenty of invalid display entries in the log, same as with any version of 10.0. When FCP or Aperture has a window, nothing happens. Other apps report window error. There is a timing issue or race condition.

I should note that after FCP or the Aperture app is closed, the external monitor is immediately recognized, no invalid display entries, just successful. Perhaps the rMBP is corrupting the packets.

I should note that after FCP or the Aperture app is closed, the external monitor is immediately recognized, no invalid display entries,

- Are these apps set to open in the "Login Items" of your account at Logon?

or

- Do you auto-save the apps so they reopen at next logon?

7/2/14 6:11:10.063 PM WindowServer[122]: CGXDisplayDidWakeNotification [92976397008341]: posting kCGSDisplayDidWake

Active Profiles:

AC Power -1*

Currently in use:

standby 1

Sleep On Power Button 1

womp 1

autorestart 0

hibernatefile /var/vm/sleepimage

darkwakes 1

gpuswitch 2

networkoversleep 0

disksleep 0

sleep 0 (sleep prevented by coreaudiod, uTorrent)

autopoweroffdelay 14400

hibernatemode 0

autopoweroff 1

ttyskeepawake 1

displaysleep 20

standbydelay 10800

pmset -g log is too long to post.

BTW, the system works perfectly if I disable display power saving, turning on/off the display manually.

Also, I have to reboot the system if the display wake fails. I wonder if that reset the "log."

No the apps were simply open when the machine went to sleep. When the machine wakes, it tries to open the previously active windows.... Or I should say perhaps the apps make the attempt.

I've been following this post for a few days now because I was having the same issue.

I have a Dell U2414H, when I wake my MacPro from sleep my monitor remained in sleep mode, I've been tinkering my monitors settings and found that if I leave the USB hub on the monitor to remain On in stand by mode the issue disappears.

I'm still not sure In my case if it was a hardware issue or an OS issue. but for two days running now I have had no problems with my monitor waking when the MacPro does.

I have read on other posts that for some monitors, the usb is a channel for these sleep/wake signals. So it maybe that the USB cable also needs to be connected.

Cheers

Should I try to use the USB hub internal to my LG, the rMBP has insomnia or dark wake issues, similar to the Belkin crap. The USB hub in this monitor is independent of the display port.

- If you have the dark wake issues, you should update to 10.9.4 first. ( it does address wake / sleep issues for portables )

- disconnect all external devices while you perform the update.

- then perform an SMC and NVRAM reset to ensure the SMC's proper operation.

- after, reboot the machine using the Safe Boot option and afterwards, reboot normal.

- Now reconnect the LG thru the display port and connect a USB cable to the LG.

- Gradually after the machine is stable, reconnect other external devices.

; Intel-based Macs: Resetting the System Management Controller (SMC)

: About NVRAM and PRAM

: OS X: What is Safe Boot, Safe Mode?

Cheers

Thanks for taking the time and trying but, unfortunately is not any help. I have not had dark wake issues since I replaced the Belkin USB hub with a Plugable hub and put a LaCie Big5 in the thunderbolt/display port chain. I don't use the built in LG USB hub as it is just a basic keyboard/device hub that is not suitable for hard drives.

I have done the SMC and NVRAM resets. I am reluctant to upgrade to 10.9.4 because the reports here is that this wake timing issue is not resolved and it seems to have introduced other sleep and device recognition issues. As long as I'm careful about the wake sequence and recognize the timing/race issues I seem to be getting by. I'm going to wait at least another month to try 10.9.4 until most of the other issues are resolved or identified as they seem to be more annoying than this monitor wake thing.

Well I updated to 10.9.4 and the display wake behavior seems to have returned to normal and apps are not holding the display hostage. I have not tried all the sleep scenarios, but the ones I've tried are OK.

10.9.4 solved 90% of my waking issues with my monitor. I still have issues (sometimes) when my macpro has not been sleeping very long. I don't recall a monitor issue after waking from a sleep of ~ 10 hours (overnight).

It is much better but not completely solved for me.

I am also still having this issue with 10.9.4. It was okay for quite some time (a few weeks). But the problem came back last night...

I unplugged the connector on the Mac Pro and re-inserted it. I tried it for 3 times. None of them woke up the 2nd monitor.

Then I had to hard reset the Mac Pro. However, another old problem came back as well: Mac Pro freezes while booting up. There are several threads on the forum about this common problem as well. I tried to reboot the Mac Pro three times. All failed.

Then I did a SMC reset and the Mac Pro booted up fine. What a mess!

I got this Mac Pro in May as a replacement computer for my first Mac Pro which had the exact problems. I have been working with Apple Care but they cannot help much at all. They sent me to a Sr. Advisor who claimed he would work with Apple Engineering team to get my problems resolved. But after a few weeks, he stopped responding to me. Apparently, he found something that he did not want to share with me.

Very disappointed about Apple...