Alan,
  Yes it did attempt it 4 times,  This error occurs on multiple PC's
and using different devices (a customer first reported it to us), so I
would say that it's not a problem with the cable.  I'm just confused
why it will work in windows and on a 2.4 kernel.  Have the timeout
values greatly changed from 2.4 to 2.6?  If so, maybe I'll try
tweaking with that and see if I can get it to work.

Thanks!

-Jeff


On 1/4/06, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 4 Jan 2006, Jeff Lange wrote:
>
> > Hi all,
> >
> >   I'm attempting to port my 2.4 USB driver for a Samsung SDI USB 2x20
> > VFD (vacuum florescent display) (USB ID= 0f70:0201).  Unfortunately,
> > the 2.6 kernels that I've tried (SuSE 10's 2.6.13, and vanilla 2.6.15)
> > will not detect the device when I plug it into the system.
> >
> > I compiled the kernel with USB Debugging support and this is the
> > output that I get when I plug in the device.
>
> > Jan  4 15:36:31 linux kernel: usb 3-2: new full speed USB device using
> > uhci_hcd and address 2
> > Jan  4 15:36:32 linux kernel: uhci_hcd 0000:00:1d.2:
> > uhci_result_control: failed with status 440000
> > Jan  4 15:36:32 linux kernel: [dd22b180] link (1d22b142) element (1d22a030)
> > Jan  4 15:36:32 linux kernel:   0: [dd22a030] link (1d22a060) e0
> > Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=2, PID=2d(SETUP)
> > (buf=1dbb7560)
> > Jan  4 15:36:32 linux kernel:   1: [dd22a060] link (1d22a090) e3 SPD
> > Active Length=0 MaxLen=1f DT1 EndPt=0 Dev=2, PID=69(IN) (buf=1f5ffe40)
> > Jan  4 15:36:32 linux kernel:   2: [dd22a090] link (00000001) e3 IOC
> > Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=2, PID=e1(OUT)
> > (buf=00000000)
> > Jan  4 15:36:32 linux kernel:
> > Jan  4 15:36:32 linux kernel: usb 3-2: unable to read config index 0
> > descriptor/all
> > Jan  4 15:36:32 linux kernel: usb 3-2: can't read configurations, error -71
> >
> >
> > And obviously, after this fails, the device does not show up in lsusb.
>
> These error messages indicate that the device is failing to respond to a
> request after having correctly responded to an earlier request.  It's
> possible that the time interval between the requests is too short for the
> device to cope, although that seems pretty unlikely.
>
> It's also possible that you have a bad cable connection somewhere.
>
> > An interesting thing to note that is on a 2.4.20 box, when I do a
> > lsusb -v, it throws up the following warnings:
> >
> > Language IDs: none (cannot get min. string descriptor; got len=-1,
> > error=110 connection timed out)
> > cannot get string descriptor 1, error = Invalid or incomplete
> > multibyte or wide character(84)
> > cannot get string descriptor 2, error = Invalid or incomplete
> > multibyte or wide character(84)
> > cannot get string descriptor 3, error = Invalid or incomplete
> > multibyte or wide character(84)
> >
> >
> > So this leads me to believe that there is something not quote right
> > with the device descriptor.
>
> Not the device descriptor, the string descriptors.
>
> >  However if I plug it into a windows box
> > and use usbview, it grabs all the string descriptions correctly.  So
> > something needs to be a little more fault tolerant in the 2.6 kernel
> > somewhere.
>
> It's hard to tolerate a failure to respond.  Although you didn't show it
> in your log, the device initialization sequence should have occurred four
> times because of various retries.  Did they all end up with the same error
> occurring at the same place?
>
> > If anyone has any suggestions as to how I might be able to get around
> > this issue, please let me know.
>
> Is it possible for you to try running a 2.6 kernel on your 2.4.20 box?
>
> Alan Stern
>
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to