On Sun, 9 May 2004, Zariel Skotlex wrote: > On Sat, 08 May 2004 19:51:42 -0700 > David Brownell <[EMAIL PROTECTED]> wrote: > > Ok... applied that patch and rewent through the boot-up sequence and checked the > output of dmesg. > //------------------------------------------------------- > ehci_hcd 0000:00:02.2: GetStatus port 1 status 003402 POWER OWNER sig=k CSC > hub 1-0:1.0: port 1, status 0, change 1, 12 Mb/s > ehci_hcd 0000:00:02.2: GetStatus port 5 status 001803 POWER sig=j CSC CONNECT > hub 1-0:1.0: port 5, status 501, change 1, 480 Mb/s > hub 1-0:1.0: debounce: port 5: delay 100ms stable 4 status 0x501 > ehci_hcd 0000:00:02.2: port 5 full speed --> companion > ehci_hcd 0000:00:02.2: GetStatus port 5 status 003001 POWER OWNER sig=se0 > CONNECT > ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [3] = 0x00010101 CSC PPS CCS > hub 2-0:1.0: port 3, status 101, change 1, 12 Mb/s > hub 2-0:1.0: debounce: port 3: delay 100ms stable 4 status 0x101 > ohci_hcd 0000:00:02.0: GetStatus roothub.portstatus [3] = 0x00100103 PRSC PPS > PES CCS > usb 2-3: new full speed USB device using address 3 > usb 2-3: new device strings: Mfr=1, Product=2, SerialNumber=3 > usb_control_msg2: result = 4 > drivers/usb/core/message.c: USB device number 3 default language ID 0x409 > usb_control_msg2: result = 2 > usb 2-3: Product: USB Cable Modem > usb_control_msg2: result = 0 > usb_control_msg2: result = 2 > drivers/usb/core/usb.c: usb_hotplug > usb 2-3: registering 2-3:1.0 (config #1, interface 0) > drivers/usb/core/usb.c: usb_hotplug > usb 2-3: registering 2-3:1.1 (config #1, interface 1) > drivers/usb/core/usb.c: usb_hotplug > usbnet 2-3:1.0: usb_probe_interface > usbnet 2-3:1.0: usb_probe_interface - got id > usbnet 2-3:1.0: CDC descriptors on config > usb_control_msg2: result = 26 > usbnet: probe of 2-3:1.0 failed with error -22
There's only one place that error can be coming from; it's where the CDC driver tries to retrieve the Ethernet (MAC) address from the device. That's the get_ethernet_addr() routine in usbnet.c. The ethernet address stored as a string descriptor, and the call to read it isn't working. The result from usb_control_msg2 should always be either 0 or 2 (except the first time when it should be 4) -- the 26 indicates that the modem doesn't like what it has been asked to do. It could be this is because some of the other descriptors are messed up. The output from 'lsusb -v' would be useful here. Make sure you run it while the modem is in a "working" state, before it gets messed up by any drivers. 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
