This is a consistent solutionfor me. Weird. If only the display is asleep it wakes fine. But if the computer and display are both asleep, the display does not awaken. If the display is on (not asleep) and the computer is woken from sleep all works well.
Very interesting information, especially the first and the second finding.
The third point is clear.
In this case no "wake up" burst have to be interpreted by the displays interface.
Thanks for that!
Well, I've found a workaround for my Mac Mini (which didn't wake the 30" ACD connected with the Mini DisplayPort to Dual-Link DVI Adapter from Apple):
If I wake the Mac Mini via the Bluetooth Keyboard or the Bluetooth Mouse, the display stays in stand-by mode.
But if I use the power button at the back of the Mac Mini, the display leaves the stand-by mode just fine. I prefer this workaround much more over my previous workaround—which was unplugging either the USB connector or the MDP connector of the MDP2DLDVI adapter from the Mac Mini after each wake from sleep.
So for those whose Mac Mini's display has issues which the wake from sleep—I suggest you might want to try to wake the Mac Mini with a short push of the rear power button. Hope this helps.
Thomas Voßen wrote:
Well, I've found a workaround for my Mac Mini (which didn't wake the 30" ACD connected with the Mini DisplayPort to Dual-Link DVI Adapter from Apple):[...]
But if I use the power button at the back of the Mac Mini, the display leaves the stand-by mode just fine.
Found that the same "work around" works on portables too as the issue is not limited to MacMini.
If you look around you will find the same description for iMac, MacBook and MacBook Pro but never read about on Mac Pro systems.
It seems that the wake up via mouse or keyboard did not push the system to send a sufficient wake up burst to connected displays.
I was able to reproduce that issue with my new MacBook Pro even on a old CRT, a projector and a new flatpanel.
Interestingly the wake up via mouse or keyboard works on most projectors I had to work with in the last 5 month.
By the way, I had the same issue with my older MacBook since 2008 but rarely and if on flatpanels only.