On Fri, 7 May 2004, Zariel Skotlex wrote:

> Well, my kernel is still 2.6.5, so I had to manually apply the patch's
> chunks #2 and #3 (after 2.6.6 goes out, I'll try it on that). And this
> is what now happens when I plugin the modem:

Maybe you should try moving to 2.6.6-current.  It's faintly possible this 
will make a difference.  (Not likely, though.)

> usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=3
> usb_control_msg2: result = 4
> drivers/usb/core/message.c: USB device number 2 default language ID
> 0x409
> usb_control_msg2: result = 2
> usb 2-2: Product: USB Cable Modem
> usb_control_msg2: result = 0
> usb_control_msg2: result = 2

That's just what I would expect to see.  Those results mean that even
without the patch applied it should have worked okay.

> I find it odd that it didn't even try to load the usbnet driver... so
> I loaded it manually:

Yes, it's odd.  You should see what /proc/bus/usb/devices says at this 
point.

> usbnet 2-2:1.0: usb_probe_interface
> usbnet 2-2:1.0: usb_probe_interface - got id
> usb_control_msg2: result = 26
> usbnet: probe of 2-2:1.0 failed with error -22
> drivers/usb/core/usb.c: registered new driver usbnet
> //-------------------------------------------------------
> 
> Which is an invalid argument... so.. basicly, the data my modem is
> sending is just plain garbage.

Not necessarily; it could be a problem in usbnet.  Admittedly, it's much
more likely to be a problem with the modem.

>  What was mentioned on a buggy firmware
> upgrade made me think about it... does the cable-modem performs
> firmware upgrades automatically? (or my isp forces them on my modem?)
> That would explain why it just suddenly stopped working next time I
> tried to start it up. I'll look around to see if I can upgrade the
> firmware myself (altough I don't have much hope in that). For the sake
> of completeness here goes what happens on my brother's uhci-based host
> controller:
> 
> //-------------------------------------------------------
> uhci_hcd 0000:00:11.2: wakeup_hc
> uhci_hcd 0000:00:11.2: port 1 portsc 0093
> hub 1-0:1.0: port 1, status 101, change 1, 12 Mb/s
> hub 1-0:1.0: debounce: port 1: delay 100ms stable 4 status 0x101
> usb 1-1: new full speed USB device using address 2
> usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=3
> usb_control_msg2: result = 26
> drivers/usb/core/message.c: USB device number 2 default language ID 0x30
> usb_control_msg2: result = 4
> usb_control_msg2: result = 4
> usb_control_msg2: result = 32

Those last five lines are total garbage.  Did you cycle the power on the 
modem between your two tests?

> The logs don't look at ALL between both computers... but I just "know"
> they are the ones that belong to the modem (since my brother's pc
> didn't have any other usb's items attached, and neither did mine).
> Well.. I dunno if this is the end of the road for now, I'll go look
> into firmware upgrading for my cable modem.

That's probably your best bet.

Alan Stern



-------------------------------------------------------
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-devel

Reply via email to