PDA

View Full Version : Issue with identification of the primary screen

gennadyd
06-28-2011, 10:25 PM
I am experiencing a strange problem after switching to a newer and faster Mac. DisplayLink was working fine on the old computer but on the new one the display connected to DisplayLink wakes up consistently first and OSX assigns to this display to be a primary. Then DVI-connected monitor wakes up and it becomes a primary. Needless to say that it changes dramatically the window layout on both monitors. Not sure if it is a driver problem (maybe just being too fast) but does anyone know how to prevent this really annoying effect.

Thanks.
Carlo
06-29-2011, 06:07 AM
What model is the new computer? Have you installed any faster HD/memory on it?
gennadyd
06-29-2011, 06:35 PM
Yes, this is the latest 2011 Mac with iCore7 with 8GB of memory and installed SSD - very fast system. Any suggestions to fix screen swapping?
xiao2012
06-30-2011, 06:40 AM
The same anguish
Carlo
06-30-2011, 09:02 AM
The description makes sense, it's possible that the OS considers the internal screen detached if a timeout occurs. It's unlikely we can reproduce this issue in our lab, otherwise we would have seen it already...

Our only hope is to find something in the system logs: can you please send us the output from this tool? http://www.displaylink.com/support/ticket.php?id=269
gennadyd
07-01-2011, 01:45 AM
Collected info attached. Any ideas?
Carlo
07-03-2011, 03:14 PM
The system log in the profile is filled with _CGSFindSharedWindow errors, so I could not see much more.
There might be an application that has many windows, maybe invisible, or is trying to create windows. This might also slow down the graphics driver. The first candidate as usual is Parallels but others might have similar effects.
Just a theory.
I would not try to experiment by slowing down our responsiveness if we can't reproduce the issue, but we will check again the power management behaviour to see if there is anything obvious in this area that we are not considering.
I would run two experiments on your system:
1) Make sure Parallels is disabled and try to reproduce
2) Delete \System\Library\Extensions\DisplayLinkGA.plugin (admin password required) and reboot
You can restore the GA acceleration by reinstalling our driver.