PDA

View Full Version : OSX 10.8.1 Screen never comes on


earle
09-04-2012, 07:40 PM
Hello,

I am using a HIS II which is a DL-195 Adapter.

I was using DisplayLink driver 1.8 with no problems. Then shortly after upgrading to ML 10.8.1 and putting it to sleep for first time since upgrading the display never came back.

I have uninstalled, repaired permissions, and reinstalled multiple times but no luck getting it working again.

It's like it see's my usb adapter just fine it just doesn't start the display.

I really miss having this adapter working, any ideas?
Earle


MacBook Pro 8,2
DL-195 Adapter:
Product ID: 0x028f
Vendor ID: 0x17e9 (DisplayLink (UK) Ltd.)
Version: 1.24
Serial Number: 109480
Speed: Up to 480 Mb/sec
Manufacturer: DisplayLink
Location ID: 0xfd120000 / 4
Current Available (mA): 500
Current Required (mA): 500

earle
09-04-2012, 07:48 PM
Forgot to mention that I have turned off Gatekeeper.

Carlo
09-05-2012, 06:23 AM
The logs show that the device is enumerated and our SW is trying to communicate with it without success. The system log shows several transaction errors on USB by the Apple USB host controller driver.

"AppleUSBEHCI[0xffffff802ccf4000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 4, EP: 0)"

Given that this issue started to happen with 1.8.1 it might be a problem in the updated host controller driver in 1.8.1, but your device is pretty standard and we have not seen the same issue.
We can try to reproduce on more systems with exactly the same device, we have it in our lab, but I'd suggest to contact Apple as well showing them the system profile.

Carlo

earle
09-05-2012, 03:17 PM
So I had a chat with apple support and they suggested that I use a different manufacturer.

They said DisplayLink should be responsible for their drivers, they even went so far to suggest another manufacturer.

Their main goal was not solve this problem but to try and make me happy. Since I already have this device I really would like to get it working again.

Should I try going back to 10.8.0?

Earle