Monitor Not Detected

[lkatz]

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.

[lkatz]

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]

[Carlo]

The device is malfunctioning, PID 0x8060 means that the device can't boot properly. I'd ask for a replacement.

[MikeKulls]

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.

This looks like a common problem as this is the third post I've found in the first 2 pages of this forum.

[Pawel]

This looks like a common problem as this is the third post I've found in the first 2 pages of this forum.

The problem with Product ID = 0x8060 is not a very common problem however our customers report it from time to time. DisplayLink cannot however be blamed for this problem as the chip in the device is not booting up properly and it means that the device is faulty. PID = 0x8060 shows that it has booted from the bootrom (rather than the EEPROM). This means it will not enable any video outputs.

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.

[MikeKulls]

The problem with Product ID = 0x8060 is not a very common problem however our customers report it from time to time. DisplayLink cannot however be blamed for this problem as the chip in the device is not booting up properly and it means that the device is faulty. PID = 0x8060 shows that it has booted from the bootrom (rather than the EEPROM). This means it will not enable any video outputs.

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.

That is incorrect. The device most definitely is working as it works under windows on the same machine. It even works on windows inside virtual box under Mac OSX.

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).

[CodeMonkey]

I have this line in my logs:


Jan 5 10:14:42 daves-mbp pcscd[65564]: Non-smartcard device launched pcscd [Vendor: 0X17E9, Product: 0X36]


Does it mean anything good / bad?

[dcoulson]

I have this line in my logs:


Jan 5 10:14:42 daves-mbp pcscd[65564]: Non-smartcard device launched pcscd [Vendor: 0X17E9, Product: 0X36]


Does it mean anything good / bad?

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.

[CodeMonkey]

I have a feeling that the problem is my wide screen monitors . . . But, I haven't had a chance to take it home and try it with a smaller one.

[fmlogue]

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."

[CodeMonkey]

Nope, that didn't work either:


USBF: 510773.546 [0xc3eeb00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x26000000)
USBF: 510774.287 [0xc3eeb00] The IOUSBFamily has successfully enumerated the device.

[dcoulson]

Nope, that didn't work either:


USBF: 510773.546 [0xc3eeb00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x26000000)
USBF: 510774.287 [0xc3eeb00] The IOUSBFamily has successfully enumerated the device.

Do you have a different system to plug it into to see if it is the adapter or the USB port/hub? If you are going through a hub, try connecting it to a direct port on the Mac.

If it still doesn't work, I'd try to arrange a replacement adapter with whoever you purchased it from.

[JohnTHarrison]

The problem with Product ID = 0x8060 is not a very common problem however our customers report it from time to time. DisplayLink cannot however be blamed for this problem as the chip in the device is not booting up properly and it means that the device is faulty. PID = 0x8060 shows that it has booted from the bootrom (rather than the EEPROM). This means it will not enable any video outputs.

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.

I tend to close the lid on my Macbook Pro and then use a Apple mini DVI adapter and the USB device to give me two screens. Just recently I've had problems getting the USB device to boot. Using OSX 10.6.6 The above solution worked for me. cheers

[CodeMonkey]

Just bought and tried my third display link device. A Sewell Minideck. I actually bought it because I thought it was NOT a display link device.

Again does not work. This can not be hardware . . . must be a driver issue. Oh well, time to return a third device.