![]() |
|
|
|
|
#1 |
|
Junior Member
Join Date: Sep 2011
Posts: 12
|
|
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Mar 2011
Posts: 2
|
Right now, I have one monitor connected via DisplayPort, another connected with DisplayLink, and my MacBook Air is closed. I can see that the MBA's screen is active because the Apple logo is glowing, and I have taken a screen capture of the System Preferences as well which shows three active screens.
Pressing "Detect Displays" doesn't help. This is clearly an issue with the DisplayLink software, because this behavior does not occur if the drivers are uninstalled. I'd be happy to help experiment on ways to fix the issue. I am fairly comfortable with the terminal. I've been wondering if there is a way to force the system to reevaluate which displays are active more thoroughly than the "Detect Displays" method does, but haven't found any success. |
|
|
|
|
|
#3 |
|
Mac Team
Join Date: Feb 2009
Posts: 606
|
I'm afraid I don't have any good news for this clamshell mode issue. We're not really sure this is our issue since we can't directly modify the behaviour of the internal screens, but it may be a side effect of something we can avoid doing.
We have one possible lead and most importantly looking into this area as a whole so the hope is to come up at least with a convenient workaround for you. As usual I prefer not to give time scales: you never know when the OS vendor decides to throw a spanner in our schedules. Cheers Carlo |
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Dec 2011
Posts: 14
|
I would hope the OS vendor we're talking about would be interested in helping you solve this problem.
![]() I wish we could dynamically load and unload the drivers in the meantime. Then at least I could script it. Thanks for your efforts guys. It's much appreciated. Please keep us updated more frequently? |
|
|
|
|
|
#5 |
|
Member
Join Date: Aug 2009
Posts: 30
|
Our impression is that it's DisplayLink's issue since the problem does not occur when the DisplayLink drivers are not installed. Can you confirm that the driver team has at least been able to reproduce this problem?
|
|
|
|
|
|
#6 | |
|
Mac Team
Join Date: Feb 2009
Posts: 606
|
Quote:
We've been able to reproduce this issue some time ago on 10.7.2, but when we retried last week on the same system we could not see the issue. We'll be trying different power saving options and login options to see if it has any effect. You are welcome to help finding the exact use case! Cheers, Carlo |
|
|
|
|
|
|
#7 | |
|
Junior Member
Join Date: Sep 2011
Posts: 12
|
Quote:
This happens constantly without a doubt. The ONLY rememdy is to completely reboot my macbook while docked. Once it is put to sleep again, the problem reoccurs again. ![]() I've been patiently waiting on a fix for this. Other than that, the adapter works perfectly fine for what I use it for. |
|
|
|
|
|
|
#8 |
|
Junior Member
Join Date: Jan 2012
Posts: 16
|
I've also found this issue to be regular on multiple configurations of hardware, driver version, and OS version.
Since I can't restart my computer every time I return with my laptop to my desk, I haven't been able to use multiple monitors for ~8 months. Aren't people at DisplayLink needing to restart their Mac laptops every couple of hours? |
|
|
|
|
|
#9 | |
|
Member
Join Date: Aug 2009
Posts: 30
|
Quote:
AC Power: System Sleep Timer (Minutes): 0 Disk Sleep Timer (Minutes): 10 Display Sleep Timer (Minutes): 0 Wake on AC Change: No Wake on Clamshell Open: Yes Wake on LAN: Yes Current Power Source: Yes Display Sleep Uses Dim: No PrioritizeNetworkReachabilityOverSleep: 0 RestartAfterKernelPanic: 15 Standby Delay: 4200 Standby Enabled: 1 Battery Power: System Sleep Timer (Minutes): 15 Disk Sleep Timer (Minutes): 10 Display Sleep Timer (Minutes): 15 Wake on AC Change: No Wake on Clamshell Open: Yes Display Sleep Uses Dim: No Reduce Brightness: Yes RestartAfterKernelPanic: 15 Standby Delay: 4200 Standby Enabled: 1 Using a BVU195 DisplayLink adapter; I see this problem whether I'm connecting two 19-inch LCDs in one location or one 20-inch LCD in another. And as others have said, steps to reproduce:
Let me know if you're able to reproduce it following these steps. I'll even make a video of the process if that will be helpful. Please try and help us out with this. |
|
|
|
|
|
|
#10 |
|
Member
Join Date: Aug 2009
Posts: 30
|
This problem is going on over six months now, and it’s been given peripheral attention, at best, when given any attention at all. If it’s being actively worked on — which would be great — we haven't heard about it.
DisplayLink team: What else can we do by way of logging, driver testing, or any other troubleshooting to help track this problem down? We’re willing to help solve this problem alongside you, but we can’t help if we aren’t hearing any communication that this is being worked on or even acknowledged. |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|