beta 2.2

[Walter0132]

I was running Mavericks 10.9.2 with display driver 2.1... all 3 of my displays would come up in mirrored mode and I could unselect mirror and rearrange the displays no problem. of course it would not retain the positions or settings the next time i connected them i could go thru and make the changes and everything would work again. today i installed 2.2 and now I can only get 1 monitor of the 3 i have connected working. the mac display panel shows all 3 but only 1 is working. i tried to uninstall driver 2.2 and reinstall driver 2.1 and now i only have 1 display working with that driver also. WTF. come on, now i can't use 2 of my 3 monitors!!!!! this is getting old. how can i completely removed display drivers 2.2 to roll back completely to 2.1? atleast i could use 2.1... 2.2 had rendered my external monitors completely unuseable.. and worse not i can't get 2.1 working like it did before i updated!!!!!!!
this is becoming almost not worth the effort and I'm thinking I might have to look for another solution. Any help at all here??????

[earle]

Walter maybe try connecting only 1 display via usb displaylink?

They clearly mentioned in the release notes for 2.2beta that only one display is supported for 10.9.

I understand its frustrating and am not trying to suggest that it is ok.

[ChristianP]

Walter, could you please grab the logs with 2.2b driver installed and all 3 monitors connected. You can download the debug tool from here: http://www.displaylink.com/support/ticket.php?id=269

The 2.2b uninstaller completely uninstalls the driver. The OS could cache some info about the displays previously connected and this could slightly alter the initial state making 2.1 not working too. The logs should help us identify the cause of the issue. Thanks

[Walter0132]

i installed 2.2beta and set the log utility per instructions. let me know if you need anything else.. here is the file it created.

[ChristianP]

Thanks Walter for the logs. We have found something in the logs that could explain the issue with your setup. We'll be back to you shortly with additional info.

[Walter0132]

any help would be appreciated.. thank you...

[Carlo]

Hi Walter,

We are now testing a fix for this issue. You'll be able to try it, Christian is going to be in touch next week.

Cheers,
Carlo

[loganbest]

I'm also having an issue on 10.9.2. With the device in I can't get the monitor to get a signal even though the display prefs show that the monitor is recognized.

Attached is my verbose debug.

[Walter0132]

this was also one of the side effects I was seeing. It appears that I had 3 monitors in the display pref but only one would show anything on the screen. Sounds like you are experiencing the same problems I am having.

[Walter0132]

any update on this issue???

[ChristianP]

any update on this issue???

Hi Walter, please check your private messages, there are further instructions. Thanks

[ChristianP]

I'm also having an issue on 10.9.2. With the device in I can't get the monitor to get a signal even though the display prefs show that the monitor is recognized.

Attached is my verbose debug.

Hi Logan, please check your private messages, there are further instructions that could help in fixing your issue. Thanks

[MickM]

Christian, would it be possible to post a quick fix update to the 2.2 beta to prevent the gigantic amount of console logging of messages - it's the only thing holding me back from using it:

WindowServer(152): _CGXGLDisplayContextForDisplayDevice: No matching context for device )0x7fa6c0608d70) - disabling OpenGL

[Carlo]

Christian, would it be possible to post a quick fix update to the 2.2 beta to prevent the gigantic amount of console logging of messages - it's the only thing holding me back from using it:

WindowServer(152): _CGXGLDisplayContextForDisplayDevice: No matching context for device )0x7fa6c0608d70) - disabling OpenGL

Hi Mick,

We're looking at this now. These are WindowServer logs and not directly in our control but we're trying to see if we can do anything else than raising a bug with Apple.

The Window Server should not continuously try to use an unsupported OpenGL function and be surprised about the outcome every 250 milliseconds.
The system logger is clever though and does not log streams of identical log lines when they're too frequent.

Cheers,
Carlo

[Carlo]

Hi Mick,

We have not found a way to work around the excessive Window Server logging while using the API recommended by Apple for Mavericks.

Googling around it looks like other solutions are affected as well. We opened a bug with Apple.

Cheers,
Carlo

[zappcatt]

Hi Walter,

We are now testing a fix for this issue. You'll be able to try it, Christian is going to be in touch next week.

Cheers,
Carlo

Any update? It has been over a month....and many of us have more than one monitor connected to our Mac's...thus the need for this product.