At the bottom....
> On Wed, May 03, 2000, Mike Davison <[EMAIL PROTECTED]> wrote:
> >
> > I recently patched the 2.3.99 (http://www.suse.cz/development/usb-backport/)
> > backport into a 2.2.14 kernel. After some effort, I was able to use my
> > Kodak 265 digital camera. Great! However, when I tried to use it again
> > a few days latter I ran into a problem that I am not sure how to debug.
> >
> > I may have bungled the backport. Most everything seemed to go well, but
> > I had to create an fstab entry and a device file. The /dev/dcxx* files
> > have the wrong device numbers, which seems odd.
> >
> > The fstab entry looks like:
> >
> > none /proc/bus/usb usbdevfs defaults 0 0
> >
> >
> > The device file looks like:
> >
> > crwxrwxrwx 1 root root 180, 80 Apr 28 18:25 /dev/kodak
> >
> > Yes, I know the permissions are silly, but I didn't want a simple permission
> > problem causing problems while I was debugging this.
> >
> >
> > The contents of /proc/bus/usb/drivers:
> >
> > 80- 95: dc2xx
> > hub
> > usbdevfs
> >
> >
> > The contents of /proc/bus/usb/devices:
> >
> > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> > D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> > P: Vendor=0000 ProdID=0000 Rev= 0.00
> > S: Product=USB UHCI Root Hub
> > S: SerialNumber=f500
> > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
> > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= -1 Spd=12 MxCh= 0
> > D: Ver= 0.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 0 #Cfgs= 0
> > P: Vendor=0000 ProdID=0000 Rev= 0.00
> >
> > The last 3 lines show up when the camera is connected, but seem incomplete.
> > When I used this successfully a few days ago it seems like there was more
> > data there.
> >
> > So, does anyone have any suggested debugging techniques? I'm not sure how
> > to proceed.
>
> Those last three lines tell us that something went wrong during the
> enumeration process. There should be something in your logs. Can you
> give us the output from dmesg pertaining to USB?
Sure, I should have thought to add that information. Here it is:
hub.c: port 2 connection change
hub.c: portstatus 101, change 1, High Speed
hub.c: portstatus 103, change 0, High Speed
usb.c: USB new device connect, assigned device number 2
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb.c: USB device not responding, giving up (error=-110)
hub.c: hub: disabling port 2
hub.c: port 2 connection change
hub.c: portstatus 100, change 3, High Speed
usb.c: USB disconnect on device -1
> Although it probably won't make too much of a difference, which UHCI
> driver are you using?
Hmmm... The header for drivers/usb/usb-uhci.c says:
/*
* Universal Host Controller Interface driver for USB (take II).
*
* (c) 1999 Georg Acher, [EMAIL PROTECTED] (executive slave) (base guitar)
* Deti Fliegl, [EMAIL PROTECTED] (executive slave) (lead voice)
* Thomas Sailer, [EMAIL PROTECTED] (chief consultant) (cheer
leade
r)
* Roman Weissgaerber, [EMAIL PROTECTED] (virt root hub) (studio
porter)
*
* HW-initalization based on material of
*
* (C) Copyright 1999 Linus Torvalds
* (C) Copyright 1999 Johannes Erdfelt
* (C) Copyright 1999 Randy Dunlap
*
* $Id: usb-uhci.c,v 1.228 2000/04/02 19:55:51 acher Exp $
*/
Useful?
Thanks,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
