Monitor not waking up after 10.9.3 update

Only happens with 2 monitors attached with my nMP.

I have two monitors connected to the mac pro, U2713H and U2713HM. The second (U2713HM) is also connected to another PC (DP to mac and DVI to PC).

Normally on waking there are no issues. Over the night they both wake up.

But if I switch the second monitor U2713HM to DVI to the PC, and after a few hours switch it back to DP, the mac pro recognise the monitor but will not show anything, and the monitor enters to power saving mode, shows black, and thats it. Nothing I do wakes it up.

When I disconnect only the U2713HM from the mac pro and reconnect, the main monitor actually turns off and I can only see the second monitor.

If I don't disconnect the main monitor as well, I will not get anything from it.

I swear, today when I disconnected those monitors, iTunes started to play music out of the blue....

I hope apple address this issue on the next build.

ma.eyal-

The Mac uses one highly-parameterized Driver for every display you can attach. To set the Driver settings properly, your Mac sends a query to the display at certain times. The display must answer with its name and its capabilities, or it will remain dark. The times are:

• At Startup

• When the Mac-end of the cable is inserted

• When you use Option-(Detect displays) button in the preference pane

• At wake from sleep

If you have a display that is paying attention to a different computer, it may not respond when the Mac sends it query.In that case, it will remain dark.

If you think this is Apple's problem, you need to communicate with Apple support. Without your allowing them the opportunity to see the problem, there may not be enough complaints for them to know a fix is needed.

Thank you for the response.

I have to say its strange, as when the switch on the monitor from DVI to DP, the monitor sends a signal with "hello, I'm here", and while windows see this and acknowledge the monitor, the osx does not.

I have tried this using the bootcamp and windows 8.1, and under bootcamp, the mac pro acknowledge the U2713HM when I switch it form the PC to the mac.

What you are saying is that if the monitor is not waking up, I can enter the preferences, hold options and click on the detect displays? Will this wake the monitor? (I will have to check this later when I get home).

It looks like the mac pro still saves the monitor's desk as you can flip to it, but you can't show it on the monitor for some reason.

Try unplug the thunderbolt connector at the Mac Pro side. Power cycle your monitor. Then reinsert the thunderbolt connector and see if your Mac Pro can display to the monitor. If it can't, as is the case in my Mac Pro, the chance is that the Mac Pro is in a strange state that it cannot use that monitor.

This is a very well known problem in Apple. In fact, one of the bug fixes in 10.9.4 was supposed to address this issue. From my experience, it was an improvement but it did not completely fix the problem. See Apple's 10.9.4 note in:

About the OS X Mavericks v10.9.4 Update

Apple is also aware that 10.9.4 has not addressed the issues completely. I am working with a senior advisor on my issue. According to him, there are others who have the same issues and Apple Engineering is working on it. However, I would suggest that anyone who has the problem, please contact Apple ASAP.

Apple is working on 10.9.5 and it is probably the last release for 10.9. So we need to get them to resolve this issue.

I actually tried to do what you propose, to unplug the monitor, power off, power on, reconnect.

What happens is that the mac pro is actually losing the signal from the working monitor.

For example if the U2713H is working fine and woke up, and the U2713HM did not, disconnect and recycle the power on the U2713HM makes it work, but the U2713H suddenly goes black and enters power saving mode (you get the feeling the mac pro is trolling you).

Reconnect cables on the computer side is never a good sign in any case.

I will try to contact apple support as suggested hopefully they will find some way around it.

The behavior of your nMP's problem is different from mine. It is important to let them know. In my case, after reinserting the connector, Mac Pro detected something had happened and moved some items away from the working monitor. But It did not wake up the sleeping monitor.

...telling indeed.

Somehow Apple managed to build a new Mac Pro workstation that crashes with more than one Apple Cinema Display! What is going on with Apple??

the same here,

although it started with my old mac pro some time ago and continued with the new mac pro late 2013.

it happens only with my second EIZO FlexScan S2243WFS.

i can only wake it up by turning the monitor off and than back on, of course after that all my windows and panels are messed up.

i still need to try if the "detect displays" trick is working.

I haven't had this issue in 3 days now. The only thing that differs is I removed a USB cable that was attached to the monitor to power the 4 USB ports on the side. The offending monitor is a BenQ EW2730 and is currently contacted to the Mac Pro via an Apple Thunderbolt to DVI convertor. No other devices have been removed.

Is the monitor with 4 USB ports the BenQ W2730? It is not clear from your statement.

Are these 4 USB ports powered by the monitor?

Yes the 4 USB ports are on the BenQ W2730. I don't know if the ports are powered by the monitor or not sorry. It was plugged in to a powered USB hub but I hadn't used them in months and had forgotten about them tbh.

Are these 4 USB ports on monitor connected to the powered USB hub first and then connected to Mac Pro? In other words, is it "Mac Pro->Powerd USB Hub->Monitor Hub" or "Mac Pro->Monitor Hub->Powered USB Hub"?

What other devices are connected to the USB hubs?

In my case, I have 2 external USB-bus powered HDs connected to Mac. Then I have a passive USB Hub connected to the Mac Pro as well. On this passive USB Hub, it connects to a webcam, a UPS, and then to a monitor's HUB hub. (This monitor seems to work fine.) All these USB devices operate normally. In theory, the power used by USB ports shouldn't impact thunderbolt port power, right? This shouldn't impact thunderbolt port's power capability to wake up monitors.

Yes the order is Mac Pro->Powerd USB Hub->Monitor Hub. As I said I removed the USB connection to the Monitor Hub as I wasn't using it.

Connected to the Powered USB 2 hub is a powered 2TB Western Digital External HDD (for TimeMachine), a bus-powered HP Webcam HD 2300 and a powered Winstars SATA Hard drive USB 2 docking station.

Connected directly to the Mac Pro USB 3 ports is a unbranded bus-powered 500gb USB 3 external HDD (which frequently disconnects itself from the new Mac Pro - it rarely did this when connected to my 2010 Mac Pro), a bus-powered Kingston USB 3 multi-card reader, a wired Apple Keyboard and of course the powered USB 2 hub.

Connected to the Thunderbolt ports is a Caldigit T3 Raid and my 2 monitors via Apple TB to DVI convertors. The second monitor is a Iiyama PL2710HD but unlike the BenQ has always switched on after sleep - the only difference is it never had a USB cable connected for its built-in USB hub.

My wake from sleep procedure is as follows - I press a key on the keyboard and wait about 5 seconds, then type my password and hit enter and wait around 5 seconds, then power on both monitors. Both monitors have came on without any problems in over a week now. My Mac Pro is sleeping from around 6pm each evening until 9am the next morning. At weekends it sleeps a lot longer.

I also have boot up crash issues that I thought were caused by my Caldigit T3 thunderbolt raid, but on testing again last weekend the Mac Pro crash was caused by the bus-powered 500gb USB 3 external HDD! So now I'm totally confused... its not a major issue as I rarely power the Mac Pro down.

A couple of ideas I had suggested to me by various Apple experts was to make sure the monitors are plugged in to different Thunderbolt buses on the Mac Pro. Secondly when performing an OSx update to 10.9.4, download and install the 10.9.4 Combo update instead of using the software update method. The Combo update will re-install, verify and fix all drivers on the Mac Pro. My Mac Pro came with 10.9.1 installed so it automatically installed the 10.9.4 Combo update as I suppose going from 10.9.1 to 10.9.4 required it.

I installed yosemite preview... all working again.

...with only one slight hick-up.

So I guess, ressources to fix the problem on mavericks are quite tight up right now, with all the releases just now.

I think Yosemit will appear soon.

greez

- raf