Go Back   DisplayLink Forum > Alpha, Beta Software Testing Programs > Closed Alpha and Beta Programs > CLOSED: 5.3 Software Release

 
 
Thread Tools Search this Thread Display Modes
Old 04-19-2010, 03:55 PM   #1
rodrigo
Junior Member
 
Join Date: Apr 2010
Posts: 1
Default USB Graphics Adapters doesn't show up in the Display Properties screen.

I have two monitors running from my nvidia quadro NVS 160M graphics, and after connecting the USB display adapater into a USB, when going to Display properties, I don't see a USB graphics adapter on the Display drop-down menu.

DisplayLinkUI won't start, can't configure the card adapter.

It seems as if the system doesn't recognize the external USB adapter, although when I connect it, it install drivers.

See below from log files and attached from support tool.

00:00:00.001 DisplayLinkManager 0012F9FC ALWAYS Logger.cpp:886 Version 5.3.24179.0. Built by BLACKWOOD\buildmaster, at 08:58:33 Mar 30 2010. Started at Mon Apr 19 11:13:18 2010
00:00:00.002 DisplayLinkManager 0012FE9C ALWAYS DisplayLinkManager.cpp:29 Operating system: Windows 7: time since machine start up 283188ms.
00:00:00.002 DisplayLinkManager 0012FE9C INFO DisplayLinkManager.cpp:44 Command Line: C:\Program Files\DisplayLink Core Software\DisplayLinkManager.exe
00:00:00.010 DisplayLinkManager DisplayLinkApp 0012FE50 INFO DisplayLinkManager.cpp:96 run as service true

++++++++++++++

00:00:00.001 DisplayLinkUI 0012FCA0 ALWAYS Logger.cpp:886 Version 5.3.24179.0. Built by BLACKWOOD\buildmaster, at 08:58:33 Mar 30 2010. Started at Mon Apr 19 11:40:48 2010
00:00:00.001 DisplayLinkUI:01381184 DisplayLinkUI 01381184 DEBUG DisplayLinkUIApp.cpp:30 Starting
00:00:00.003 DisplayLinkUI:01381184 MonitorableAppThread 0136BC34 DEBUG MonitorableApp.cpp:44 Monitorable pipe DLMonitorableApp:C:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1
00:00:00.064 DisplayLinkUI:01381184 DLUI::Root 0196FE20 INFO Root.cpp:261 dl::app::trayui::Root::main entry
00:00:00.065 DisplayLinkUI:01381184 WindowsUpdateSearcher 0136D66C DEBUG WindowsUpdate.cpp:124 UpdateSearchHandler built
00:00:00.083 DisplayLinkUI:01381184 WindowsUpdateSearcher 0136D66C DEBUG WindowsUpdate.cpp:183 Search for updates has started.
00:00:01.125 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:02.217 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:03.341 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:04.595 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:05.268 WindowsUpdateSearcherCallback 0136DEC8 DEBUG WindowsUpdate.cpp:327 Update search done
00:00:05.841 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:07.073 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:08.212 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:09.304 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:00.001 DisplayLinkUI 0012FCA0 ALWAYS Logger.cpp:886 Version 5.3.24179.0. Built by BLACKWOOD\buildmaster, at 08:58:33 Mar 30 2010. Started at Mon Apr 19 11:40:57 2010
00:00:10.396 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:11.488 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:00.000 DisplayLinkUI 0012FCA0 ALWAYS Logger.cpp:886 Version 5.3.24179.0. Built by BLACKWOOD\buildmaster, at 08:58:33 Mar 30 2010. Started at Mon Apr 19 11:41:00 2010
00:00:12.580 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:13.672 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:14.765 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:15.856 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:16.948 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.
00:00:18.040 MonitorableAppThread:0136BC34 IpcPipeClientImpl DLMonitorableAppC__Program_Files_DisplayLink_Core_ Software_DisplayLinkUI_exe_1 ERROR Pipe.cpp:523 Failed to find pipe client with pipe name \\.\pipe\DLMonitorableAppC:\Program Files\DisplayLink Core Software\DisplayLinkUI.exe:1: 0x00000002: The system cannot find the file specified.



Any help would be appreciated.

Thanks
Attached Files
File Type: zip 20100419_114105.zip (1.33 MB, 1204 views)

Last edited by rodrigo; 04-19-2010 at 04:50 PM. Reason: add file
rodrigo is offline  
Old 04-21-2010, 03:10 AM   #2
whitemoo
Junior Member
 
Join Date: Feb 2010
Posts: 8
Default

what cable are you using to connect the displaylink to the screen? DVI?

I had the same problem connecting my displaylink adapter to my screen through DVI cable, but as soon as i used VGA cable my adapter worked.

also i notice you have a NVS 160m and using displaylink, keep us posted when you do get it working. i am encountering issues using a older revision of the NVS graphics and windows 7 32 bit.
whitemoo is offline  
Old 05-21-2010, 05:44 PM   #3
fredv
Junior Member
 
Join Date: May 2010
Posts: 1
Default

Exactly the same error for me .. on 3 computers ..
drivers ok but the led never shines and nothing happens with DisplayLinkUI

Windows Seven, nvidia
XP Intel on Asus
XP Intel

with DVI or VGA monitor

Always the same problem ..

Can someone help us ? what to test ?
Thanks
fredv is offline  
Old 05-22-2010, 04:54 AM   #4
Wim
Senior Member
 
Join Date: Feb 2009
Posts: 1,561
Default

Hi

I've had a look at the log files, and it appears that the chip in the device is not booting up properly. Its coming up as PID 0x8060 in device manager, which shows its booted from its internal ROM, not the external boot device. This means it will not enable any video outputs.

Could you try unplugging all cables from the adapter, then connect USB, then connect the video cable? If it still comes up as 0x8060, then I suspect the device is faulty I'm afraid.

Thanks

Wim
Wim is offline  
Old 05-23-2010, 09:48 AM   #5
whitemoo
Junior Member
 
Join Date: Feb 2010
Posts: 8
Default

Quote:
Originally Posted by Wim View Post
Hi

I've had a look at the log files, and it appears that the chip in the device is not booting up properly. Its coming up as PID 0x8060 in device manager, which shows its booted from its internal ROM, not the external boot device. This means it will not enable any video outputs.

Could you try unplugging all cables from the adapter, then connect USB, then connect the video cable? If it still comes up as 0x8060, then I suspect the device is faulty I'm afraid.

Thanks

Wim
I get the 8060 message sometimes, but when turn off the monitor, disconnect the cord and reconnect all the cables, the monitor works. I get the 8060 message 1 times out of 10, so i didnt think it was a issue.

Would you recommend me contacting the vendor where i got my displaylink graphics module from and ask for a replacement? Will this issue get worse with time?

Hope you guys get your problems sorted. Mine is very buggy. On top of the 8060 error, I have to disconnect one monitors on my video card connect the displaylink adapter, then re-enable the disconnected video card monitor for mine to work correctly. Quite annoying when you just want to turn on the computer and get work done.
whitemoo is offline  
 

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 10:25 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.