On Fri, 23 Sep 2005, Greg Lee wrote: > Alan and David, thanks for the responses. The original output that I sent > was generated by the show_usb_* functions in usb_debug.c. Here is the lsusb > (ver 0.71) output for the non-working firmware. The lsusb output seems to > be less thorough than the show_usb_* output. > > Is it conceivable that the new firmware might be sending a Remote Wakeup > request which the 2.4 stack is discarding or responding to in a way that > causes the modem to shut down?
No, that's not possible. > bash-2.05# lsusb -v -d 0681:0034 > > Bus 002 Device 005: ID 0681:0034 Siemens Information and Communication > Products Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 2 Communications > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0681 Siemens Information and Communication Products > idProduct 0x0034 > bcdDevice 0.00 > iManufacturer 1 Siemens AG Wireless Modules > iProduct 2 MC75 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 0 > bDescriptorType 0 > wTotalLength 0 > bNumInterfaces 0 > bConfigurationValue 0 > iConfiguration 0 > bmAttributes 0x00 > MaxPower 0mA This configuration descriptor is meaningless. It looks like the device didn't send the data at all. What do you see in /proc/bus/usb/devices? Alan Stern ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
