First of all, please use the Enter/Return key around line 70 on each
line so that your mail is readable by everyone. Thanks.
On Wed, 5 May 2004 23:11:10 -0500 Zariel Skotlex <[EMAIL PROTECTED]> wrote:
| Hi...
| I asked this a long time ago when I just got subscribed, but got no answer... I
guess I'll have to ask again and try to be specific/simpler this time.
|
| When my kernel 2.6.5 tries to detect the modem, it goes on like this:
| //---------------------------------------------------------------------------
| usb 2-2: new full speed USB device using address 3
| usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=3
| ohci_hcd 0000:00:02.0: urb df530240 path 2 ep0in 82d60000 cc 8 --> status -75
| drivers/usb/core/message.c: error getting string descriptor 0 (error=-75)
| drivers/usb/core/message.c: USB device number 3 default language ID 0x409
| ohci_hcd 0000:00:02.0: urb df530240 path 2 ep0in 82d60000 cc 8 --> status -75
| drivers/usb/core/usb.c: usb_hotplug
| usb 2-2: registering 2-2:1.0 (config #1, interface 0)
| drivers/usb/core/usb.c: usb_hotplug
| usb 2-2: registering 2-2:1.1 (config #1, interface 1)
| drivers/usb/core/usb.c: usb_hotplug
| usbnet 2-2:1.0: usb_probe_interface
| usbnet 2-2:1.0: usb_probe_interface - got id
| ohci_hcd 0000:00:02.0: urb df530240 path 2 ep0in 82d60000 cc 8 --> status -75
| usbnet: probe of 2-2:1.0 failed with error -75
| drivers/usb/core/usb.c: registered new driver usbnet
| ohci_hcd 0000:00:02.0: urb df5a2c40 path 2 ep0in 82d60000 cc 8 --> status -75
| ohci_hcd 0000:00:02.0: urb df5a2c40 path 2 ep0in 82d60000 cc 8 --> status -75
| ohci_hcd 0000:00:02.0: urb df5a2c40 path 2 ep0in 82d60000 cc 8 --> status -75
| ohci_hcd 0000:00:02.0: urb df5a2c40 path 2 ep0in 82d60000 cc 8 --> status -75
| ohci_hcd 0000:00:02.0: urb df5a2c40 path 2 ep0in 82d60000 cc 8 --> status -75
| ohci_hcd 0000:00:02.0: urb df5a2c40 path 2 ep0in 82d60000 cc 8 --> status -75
| //---------------------------------------------------------------------------
|
| Pretty much says that my ohci_hcd driver couldn't probe the hardware.. and the error
code is -75 (what does -75 means anyway?). I've been having this problem since 2.6.1,
I think (it was working before... but strangely enough, my cable modem stopped working
the day I accidentally unplugged it... ever since then it won't work. I tried
connecting to other usb ports, I even got a new usb cable to no avail).
To look up USB error codes, first look at linux/include/asm-generic/errno*.h
to find the value. 75 is EOVERFLOW in Linux.
Now read linux/Documentation usb/error-codes.txt to see how linux-usb
uses error codes. EOVERFLOW means:
-EOVERFLOW (*) The amount of data returned by the endpoint was
greater than either the max packet size of the
endpoint or the remaining buffer size. "Babble".
and the (*) footnote says:
(*) Error codes like -EPROTO, -EILSEQ and -EOVERFLOW normally indicate
hardware problems such as bad devices (including firmware) or cables.
This has been our experience most of the time, so first guess is a
suspect device. It doesn't reply as expected, and possibly it's
sending more data than was requested by linux-usb.
This happens sometimes when linux-usb is trying to read descriptors
from the device. linux-usb often tries to read partial
descriptors and some devices don't like that, even though it's
allowed by the USB spec.
| Strange thing is that the kernel 2.4.25 has no problems loading my cable modem,
EXCEPT after rebooting from a 2.6 kernel, when I do a 2.6-> 2.4 change, my cable modem
also fails to be detected!
Oh. So this represents some kind of regression in linux-usb, eh?
Could you try Linux-2.6.6-rc3? (hopefully 2.6.6 will be out soon
and you can test it)
Alan, any thoughts about this one?
It seems that Zariel thinks it is OHCI-related, so you wouldn't be
the right person for that, but it seems more related to
descriptor parsing to me. Of course, that is just a guess.
| //---------------------------------------------------------------------------
| hub.c: new USB device 00:02.0-2, assigned address 3
| CDCEther.c: Ethernet information found at device configuration. Trying to use
| it anyway.
| CDCEther.c: Found Header descriptor, CDC version 110.
| CDCEther.c: Imperfect filtering support - need sw hashing
| CDCEther.c: Can't use SetEthernetMulticastFilters request
| CDCEther.c: detected BULK OUT packets of size 64
| CDCEther.c: interrupt address: 5
| CDCEther.c: interrupt interval: 64
| usb.c: string descriptor 0 too short
| CDCEther.c: Attempting to get MAC address failed: 22
| CDCEther.c: eth1: ? Broadcom Corporation USB Cable Modem
| CDCEther.c: eth1: 00:00:00:00:00:00
| usb.c: registered new driver acm
| acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN
| adapters
| //---------------------------------------------------------------------------
|
| If I rmmod CDCEther and then modprobe CDCEther the modem gets correctly identified.
So my guess is that ohci_hcd is doing "something" to my cable modem and is screwing it
up... and it doesn't gets fixed until I unload/reload the 2.4's CDCEther driver =/
| Any ideas on what I should try/do? I've been trying with every 2.6 kernel
release until now... and my cable modem fails the same way everytime. Is there some
sort of configuration perhaps stored somewhere on my disk which I can just delete and
then retry? (I wonder this because of HOW my cable-modem stopped working so
mysteriously after unplugging it so long ago).
|
| The motherboard is a NForce2 based one (XFX Mach4 NF2S-ALH)
| //---------------------------------------------------------------------------
| 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if
10 [OHCI])
| Subsystem: Asustek Computer, Inc. A7N8X Mainboard
| Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11
| Memory at e6003000 (32-bit, non-prefetchable) [size=4K]
| Capabilities: [44] Power Management version 2
|
| 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if
10 [OHCI])
| Subsystem: Asustek Computer, Inc. A7N8X Mainboard
| Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
| Memory at e6004000 (32-bit, non-prefetchable) [size=4K]
| Capabilities: [44] Power Management version 2
|
| 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if
20 [EHCI])
| Subsystem: Asustek Computer, Inc. A7N8X Mainboard
| Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12
| Memory at e6000000 (32-bit, non-prefetchable) [size=256]
| Capabilities: [44] #0a [2080]
| Capabilities: [80] Power Management version 2
| //---------------------------------------------------------------------------
|
| Help anyone?
--
~Randy
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
