PDA

View Full Version : Yosemite 10.10 Monitor doesn't wake up

itadmincrbc
10-22-2014, 02:22 PM
On Yosemite, the only monitor attached to the dock did not wake up this morning. I had to unplug and replug the USB connector just like days of old to get it to wake up.
Gatsu35
10-25-2014, 06:03 AM
I have the same issue on my asus screen it doesn't wake up
Carlo
10-27-2014, 09:05 AM
Which connection are you using to the monitor? DP, DVI, HDMI?

In version 2.3 we have much richer logging, would be great to have the logs collected right after wake up when the screen is black.

The log tool is at http://www.displaylink.com/support/ticket.php?id=269
You can attach the logs here or send them through http://www.displaylink.com/support/ask_question.php

Thank you,
Carlo
itadmincrbc
10-27-2014, 03:47 PM
Which connection are you using to the monitor? DP, DVI, HDMI?

In version 2.3 we have much richer logging, would be great to have the logs collected right after wake up when the screen is black.

The log tool is at http://www.displaylink.com/support/ticket.php?id=269
You can attach the logs here or send them through http://www.displaylink.com/support/ask_question.php

Thank you,
Carlo

HDMI. It did it again this morning. I have to unplug and replug the USB3.0 cable to get it to come on.

I Don't use the second connection because it never worked for me, I use Displayport right from the macbook air.
Carlo
10-29-2014, 09:59 AM
HDMI. It did it again this morning. I have to unplug and replug the USB3.0 cable to get it to come on.

I Don't use the second connection because it never worked for me, I use Displayport right from the macbook air.

Hi itadmincrbc,

Unfortunately you have discovered a bug in the 2.3 beta (!).

The new logging is not enabled when upgrading from an older driver. This means that your logs don't contain the critical information about the resume from sleep. The rest of the logs does not contain much of interest.

To enable the new logging you'll have to uninstall the 2.3 beta using the uninstaller and then install it again.
Then collect the logs again.

Apologies about this, we'll fix the issue in the next release.

Best regards,
Carlo