![]() |
|
|
#1 |
|
Junior Member
Join Date: Sep 2012
Posts: 5
|
The Displaylink driver version 2.0 worked fine for a while. I guess since upgrading to OS X 10.8.4 a few weeks ago, the screen controlled by a DL-3xxx device will turn pink completely after a few minutes of use. Replugging the device will fix it for a few minutes, then the screen turns pink again.
Any ideas? |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Feb 2012
Posts: 13
|
I get something similar, except my screen turns completely black.
This happens much less often than what you're describing. It only started happening with the latest 2.0 driver. jpap |
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Sep 2012
Posts: 5
|
I have now seen all kinds of colors including green.
Tried repairing permissions, as suggested in another thread in this forum, without success. The Displaylink-screen will still switch to a single color after a few minutes. Rebooting will help for a while. The console log shows: 28.07.13 21:39:28,513 DisplayLinkUserAgent[4340]: CGSServiceForDisplayNumber: Invalid display 0x2b285990 28.07.13 21:39:28,513 DisplayLinkUserAgent[4340]: CGSGetDisplayBounds: Invalid display 0x2b285990 28.07.13 21:39:28,514 DisplayLinkUserAgent[4340]: CGSServiceForDisplayNumber: Invalid display 0x2b285990 28.07.13 21:39:28,514 DisplayLinkUserAgent[4340]: CGSGetNumberOfDisplayModes: Invalid display 0x2b285990 Any ideas from the Displaylink support team? |
|
|
|
|
|
#4 |
|
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
We have heard of the screen turning strange colours before, and this can be due to faulty DDR memory in the device.
If you are seeing this often, I would suggest returning the dock for a replacement. Wim |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Sep 2012
Posts: 5
|
Thanks Wim. The affected product is a Lindy USB to Displayport adapter. It was returned to Lindy, however, they say they can't find a problem.
I just received it back and again the screen will turn to a strange color after about 3 minutes. I tried reinstalling the display link driver, repairing permissions and all that voodoo. Could it be related to OS X 10.8.4? Any further idea? Best regards Max |
|
|
|
![]() |
|
|