piyokos
05-07-2014, 01:53 AM
I purchased this product to use a third display - a 1440p Apple LED Cinema display - with my early 2013 MBPr. I bought a StarTech USB32DPPRO and wired it to the LED Cinema Display with a Monoprice DisplayPort to mini DisplayPort adapter cable + mini DisplayPort coupler.
Connecting the DL-3500 causes it to 'recognize' the display - as in, it sees a third display called 'LED Cinema Display' with the correct resolutions listed, but the display is just blank, not turned on. I have tried the 2.1 and 2.2 versions of your drivers to no avail.
The console is endlessly spammed with the following two kinds messages when the DisplayLink is active:
5/6/14 9:46:05.757 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:05.825 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:05.889 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:05.942 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.025 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.063 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.126 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.190 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.259 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.308 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.375 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.426 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.492 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.555 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.609 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.676 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.730 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.792 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.855 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.920 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.976 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.042 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.110 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.157 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.220 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.284 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.342 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.409 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.460 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:08.750 PM Console[201]: CGSCopyDisplayUUID: Invalid display 0x042803c2
5/6/14 9:46:08.751 PM Console[201]: CGSCopyDisplayUUID: Invalid display 0x7bd7fc3d
I have verified the LED Cinema Display is working when directly connected through one of the Thunderbolt/mini DisplayPort plugs on the MBPr. That's just to test though - I bought this product because those ports can only hold two displays, which are already taken by two Thunderbolt displays (and by the way - I tried removing them and running it just vanilla laptop + DisplayLink, same problem).
I doubt StarTech will be much help so if you can't help me here I'll probably just end up returning the product.
Connecting the DL-3500 causes it to 'recognize' the display - as in, it sees a third display called 'LED Cinema Display' with the correct resolutions listed, but the display is just blank, not turned on. I have tried the 2.1 and 2.2 versions of your drivers to no avail.
The console is endlessly spammed with the following two kinds messages when the DisplayLink is active:
5/6/14 9:46:05.757 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:05.825 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:05.889 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:05.942 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.025 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.063 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.126 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.190 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.259 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.308 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.375 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.426 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.492 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.555 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.609 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.676 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.730 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.792 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.855 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.920 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:06.976 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.042 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.110 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.157 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.220 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.284 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.342 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.409 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:07.460 PM WindowServer[129]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbfc0422a30) - disabling OpenGL
5/6/14 9:46:08.750 PM Console[201]: CGSCopyDisplayUUID: Invalid display 0x042803c2
5/6/14 9:46:08.751 PM Console[201]: CGSCopyDisplayUUID: Invalid display 0x7bd7fc3d
I have verified the LED Cinema Display is working when directly connected through one of the Thunderbolt/mini DisplayPort plugs on the MBPr. That's just to test though - I bought this product because those ports can only hold two displays, which are already taken by two Thunderbolt displays (and by the way - I tried removing them and running it just vanilla laptop + DisplayLink, same problem).
I doubt StarTech will be much help so if you can't help me here I'll probably just end up returning the product.