07-29-2011, 07:32 PM | #11 |
Junior Member
Join Date: Feb 2010
Location: NJ
Posts: 9
|
|
07-29-2011, 10:36 PM | #12 |
Junior Member
Join Date: Jul 2011
Posts: 17
|
Tried beta 3
I loaded beta 3 today and got much the same results. I loaded the driver, rebooted, plugged into USB port 2, and waited. In about 20 seconds the UV+ monitor came on and stayed on. Then I moved my cursor over to it and down it went. Then it came back on. Then I moved a window halfway into the UV+ monitor and the display went out again. Then the display came back on but every time I either moved the window into the display or my cursor, it went out. If finally just stopped all together. Weird.
I emailed my logs. |
08-01-2011, 08:03 PM | #13 |
Junior Member
Join Date: Jul 2011
Posts: 2
|
Still getting AppleUSBDC: start initDevice failed on beta 3
|
08-02-2011, 05:20 PM | #14 |
Junior Member
Join Date: Jul 2011
Posts: 17
|
Other devices
I see other devices have problems to with Lion. Geez, was Lion a surprise to everyone? If I had hardware out there for Mac, I think I would be ready for a major upgrade like this. Amazing.
|
08-04-2011, 10:32 PM | #15 |
Junior Member
Join Date: Jul 2011
Posts: 17
|
Open it up
Hey, if y'all can't get this thing figured out, open source it and let us fix it.
Tim |
08-08-2011, 01:35 PM | #16 |
Senior Member
Join Date: Apr 2011
Posts: 280
|
Sorry for the very late answer. From your logs, it seems a problem related to the USB Apple family driver. The driver logs a lot of errors on the raw USB communication. We are trying to replicate your setup and we are still investigating the issue. Not sure, but it could be a VMWare or VirtualBox related issue.
|
08-09-2011, 12:57 AM | #17 |
Junior Member
Join Date: Jul 2011
Posts: 17
|
vmware and virt-box removed, no workie.......
8/8/11 7:32:05.483 PM com.apple.launchd.peruser.501: ([0x0-0xc00c].com.apple.Safari[178]) Exited: Killed: 9
8/8/11 7:32:05.609 PM com.apple.launchd.peruser.501: ([0x0-0x23023].com.apple.systemevents[255]) Exited: Killed: 9 8/8/11 7:32:05.615 PM com.hp.devicemonitor: on write, error=-1 8/8/11 7:32:05.615 PM com.hp.devicemonitor: on write, error=-1 8/8/11 7:32:05.618 PM MagicMenuHotKeyDaemon: Quit 8/8/11 7:32:05.621 PM [0x0-0x19019].com.stuffit.MagicMenu: 2011-08-08 19:32:05.615 MagicMenuHotKeyDaemon[250:707] Quit 8/8/11 7:32:05.630 PM com.apple.launchd.peruser.501: (com.apple.talagent[180]) Exited: Killed: 9 8/8/11 7:32:05.633 PM com.apple.launchd.peruser.501: ([0x0-0x16016].com.apple.AppleSpell[215]) Exited: Killed: 9 8/8/11 7:32:05.633 PM com.apple.launchd.peruser.501: (com.apple.quicklook[205]) Exited: Killed: 9 8/8/11 7:32:05.637 PM com.apple.launchd.peruser.501: ([0x0-0x1a01a].com.apple.iTunesHelper[247]) Exited: Killed: 9 8/8/11 7:32:05.639 PM com.apple.launchd.peruser.501: (com.displaylink.useragent[235]) Exited: Terminated: 15 8/8/11 7:32:06.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed 8/8/11 7:32:06.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed 8/8/11 7:32:07.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed 8/8/11 7:32:08.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed 8/8/11 7:32:09.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed 8/8/11 7:32:09.837 PM com.apple.launchd.peruser.501: (com.Logitech.Control Center.Daemon[232]) Job appears to have crashed: Bus error: 10 |
08-09-2011, 12:39 PM | #18 | |
Senior Member
Join Date: Apr 2011
Posts: 280
|
Quote:
We released yesterday a new debug tool at this page http://www.displaylink.com/support/ticket.php?id=269 that enable to switch the driver log verbosity. Could you please download it, run it first and change the Log verbosity in the advanced menu to Debug (unplug and replug the adapter after the change) and then collect the log info as usual? Thanks |
|
08-09-2011, 10:06 PM | #19 |
Junior Member
Join Date: Jul 2011
Posts: 17
|
verbose log files
Here ya go.
|
08-11-2011, 09:52 AM | #20 |
Senior Member
Join Date: Apr 2011
Posts: 280
|
Thanks for the detailed logs.
From the behaviour listed in the logs, it could be an hardware issue. A similar behaviour have been reported when the usb device is somehow locked by another process, typically a virtualization software. Have you tried the adapter on another system? it would be nice, if you could check the adapter against a windows machine. I know you already tried to remove vmware and virtual box, but I'm wondering if there is any other virtualization software installed or any component that can interact with the usb device. It would help if you could test the adapter for example with an external disk partition, just with plain Lion installed. Thanks for your help. |
|
|