On Mon, 2002-04-15 at 12:52, Rodrigo Moya wrote: > On Mon, 2002-04-15 at 21:43, Dmitri wrote: > > > Attached is my /proc/bus/usb/devices and the output of lsusb when the > > > camera is connected. If you need more info, please tell me. > > > > The camera is NOT connected - either the cable is bad, or you are > > connecting the cable to an unused connector. > > > ugh! Thought something was detected, since a new file appears in > /proc/bus/usb/00x/ any time I connect the camera (don't know what this > means though :-)
You can talk to the device through these "files".
> and the output of lsusb seems to show something
> different (AIPTEK...) when the camera is 'connected'.
Obviously. /proc/bus/usb/devices did not reflect that...
But the camera eventually got connected:
> Apr 15 21:48:44 zubiri kernel: usb.c: USB device not accepting new
> address=6 (error=-110)
> Apr 15 21:48:45 zubiri kernel: hub.c: USB new device connect on bus1/1,
> assigned device number 7
> Apr 15 21:48:45 zubiri kernel: usb.c: USB device 7 (vend/prod
> 0x8ca/0x101) is not claimed by any active driver.
The nearest matches are:
08ca AIPTEK International Inc.
0020 APT-6000U Tablet
0103 Pocket DV Digital Camera <======== THIS ONE ===
The 0x101 product ID is not even listed there
(http://www.linux-usb.org/usb.ids), but at least this does not look like
one of IBM/Xirlink remakes. Hopefully, someone will recognize this
chipset.
But you should look into /proc/bus/usb/devices problem - what you posted
in your previous message did not show the camera connected. Maybe it was
still "connecting", since it took unusually long for the hardware to
come alive.
Thanks,
Dmitri
signature.asc
Description: This is a digitally signed message part
