|
11-05-2010, 07:28 PM | #1 |
Junior Member
Join Date: Nov 2010
Posts: 2
|
Monitor Not Detected
I am having trouble getting the DisplayLink working. The monitor is just not being detected. I have uninstalled the drivers, ran Disk Utility->Repair Disk Permissions , and reinstalled the drivers. Unfortunately that did not help.
The System Profiler reports that the DisplayLink device is connected. However, it states that it has not been configured: USB Display Adapter: Product ID: 0x8060 Vendor ID: 0x17e9 (DisplayLink (UK) Ltd.) Version: 0.17 Speed: Up to 480 Mb/sec Manufacturer: DisplayLink Location ID: 0x26200000 Current Available (mA): 500 Current Required (mA): Unknown (Device has not been configured) Any help would be greatly appreciated. |
11-08-2010, 09:45 PM | #2 |
Junior Member
Join Date: Nov 2010
Posts: 2
|
I'm not sure if this is relevant, but in the system.log I am seeing:
Nov 8 17:36:47 MacBook pcscd[3330]: Non-smartcard device launched pcscd [Vendor: 0X17E9, Product: 0X8060] |
11-11-2010, 12:04 PM | #3 |
Mac Team
Join Date: Feb 2009
Posts: 606
|
The device is malfunctioning, PID 0x8060 means that the device can't boot properly. I'd ask for a replacement.
|
11-29-2010, 09:23 PM | #4 | |
Junior Member
Join Date: Jun 2010
Posts: 18
|
Quote:
|
|
11-30-2010, 10:22 AM | #5 | |
Moderator
Join Date: Aug 2010
Posts: 214
|
Quote:
We recommend unplugging all cables from the adapter, then connecting USB and then connecting the DVI/HDMI cable. This might resolve the problem Ikatz is experiencing. If it won't, then the manufacturer should be contacted for the replacement. |
|
12-06-2010, 08:31 PM | #6 | |
Junior Member
Join Date: Jun 2010
Posts: 18
|
Quote:
As for the problem not being common all I can say is that it has happened twice within days of me reinstalling the OS (the only solution I could find). |
|
01-05-2011, 04:16 PM | #7 |
Junior Member
Join Date: Oct 2010
Posts: 15
|
I have this line in my logs:
Code:
Jan 5 10:14:42 daves-mbp pcscd[65564]: Non-smartcard device launched pcscd [Vendor: 0X17E9, Product: 0X36] Does it mean anything good / bad? |
01-07-2011, 08:55 PM | #8 |
Member
Join Date: Mar 2010
Posts: 55
|
I have a DL195 based adapter which is working fine - I get the same syslog message at boot time also (Product 0x2A7 in my case). I would disregard it, or at least not infer a failure from the message.
|
02-02-2011, 08:51 AM | #9 | |
Junior Member
Join Date: Feb 2011
Posts: 1
|
This worked for me
Quote:
|
|
01-29-2011, 09:14 PM | #10 |
Junior Member
Join Date: Jan 2011
Posts: 3
|
My problem was somewhat different than the gentleman above. I couldn't get the device to work (light wouldn't go on) when plugged directly into a DVI monitor cable but it would work fine when using the DVI to VGA adapter and a VGA cable. However I discovered that in order to use the DVI cable, the sequence of first plugging in the USB cable, waiting until the light came on, then plugging in the DVI cable worked. The sequence was immaterial with the VGA adapter. The answer was hidden in this forum: "We recommend unplugging all cables from the adapter, then connecting USB and then connecting the DVI/HDMI cable. This might resolve the problem Ikatz is experiencing. If it won't, then the manufacturer should be contacted for the replacement."
|
|
|