sk7
11-16-2014, 11:37 PM
When I move my mouse on the external screen it lags.
I'm using:
* i-tec USB 3.0 DVI Display Adapter
* DisplayLink OS X Software 2.3 Beta (10 Oct 2014)
* OS X 10.9.5
* Macbook Air Mid 2012
I can set it 60 Hz or 75 Hz, both work but the mouse lags.
The screen works fine when I attach it via a mini displayport to dvi adapter.
My logs are also spammed, see the thread
Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device (http://www.displaylink.org/forum/showthread.php?t=62987)
There seems to be a lot of discussions here regarding a bug in OS X that prevents DisplayLink from writing a proper driver. see the thread
Reply from Apple regarding Displaylink bug report (http://www.displaylink.org/forum/showthread.php?t=63338).
Is there any progress here? I would really like to use this i-Tec adapter but apparently a software problem prevents me (and everybody else?) from using it. for months.
Can DisplayLink maybe put their drive code publicly on GitHub or somewhere else, so we can fix this on our own? The license doesn't have to be open (MIT, GPL, ...) but it would be great to just have the code and see if we can fix it on our own
I'm using:
* i-tec USB 3.0 DVI Display Adapter
* DisplayLink OS X Software 2.3 Beta (10 Oct 2014)
* OS X 10.9.5
* Macbook Air Mid 2012
I can set it 60 Hz or 75 Hz, both work but the mouse lags.
The screen works fine when I attach it via a mini displayport to dvi adapter.
My logs are also spammed, see the thread
Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device (http://www.displaylink.org/forum/showthread.php?t=62987)
There seems to be a lot of discussions here regarding a bug in OS X that prevents DisplayLink from writing a proper driver. see the thread
Reply from Apple regarding Displaylink bug report (http://www.displaylink.org/forum/showthread.php?t=63338).
Is there any progress here? I would really like to use this i-Tec adapter but apparently a software problem prevents me (and everybody else?) from using it. for months.
Can DisplayLink maybe put their drive code publicly on GitHub or somewhere else, so we can fix this on our own? The license doesn't have to be open (MIT, GPL, ...) but it would be great to just have the code and see if we can fix it on our own