On Tue, Oct 27, 2009 at 08:58:14PM +0000, Chris G wrote: > I am trying to get "USB Networking" to work with a 2Wire 2700HGV ADSL > router. (This is actually a BT Home Hub) > No ideas from anyone on this?? > The hardware is recognising the router as a valid USB device but I'm > getting errors, the following is an extract from /var/log/syslog:- > > Oct 27 20:02:57 server kernel: [ 137.932054] usb 2-2: new full speed USB device using ohci_hcd and address 4 > Oct 27 20:02:57 server kernel: [ 138.144588] usb 2-2: configuration #1 chosen from 1 choice > Oct 27 20:02:57 server kernel: [ 138.267304] usbcore: registered new interface driver cdc_ether > Oct 27 20:02:57 server kernel: [ 138.516030] rndis_host 2-2:1.0: RNDIS init failed, -110 > Oct 27 20:02:57 server kernel: [ 138.516137] rndis_host: probe of 2-2:1.0 failed with error -110 > Oct 27 20:02:57 server kernel: [ 138.516189] usbcore: registered new interface driver rndis_host > Oct 27 20:02:58 server kernel: [ 138.808034] rndis_wlan 2-2:1.0: RNDIS init failed, -110 > Oct 27 20:02:58 server kernel: [ 138.808191] rndis_wlan: probe of 2-2:1.0 failed with error -110 > Oct 27 20:02:58 server kernel: [ 138.808246] usbcore: registered new interface driver rndis_wlan > > The error is just about identical on both a xubuntu 9.04 (kernel 2.6.28-16) > and a xubuntu 9.10 system (kernel 2.6.31-14). > > ... and here is the output from 'lsusb -v' for the 2Wire :- > > Bus 002 Device 004: ID 1630:0042 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 2 Communications > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x1630 > idProduct 0x0042 > bcdDevice 1.00 > iManufacturer 1 2Wire Inc > iProduct 2 2Wire USB Remote NDIS Ethernet > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 67 > bNumInterfaces 2 > bConfigurationValue 1 > iConfiguration 4 2WIREHPL > bmAttributes 0xc0 > Self Powered > MaxPower 40mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 2 Communications > bInterfaceSubClass 2 Abstract (modem) > bInterfaceProtocol 255 Vendor Specific (MSFT RNDIS?) > iInterface 5 ndis5 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 1 > CDC Header: > bcdCDC 1.00 > CDC Call Management: > bmCapabilities 0x00 > bDataInterface 1 > CDC ACM: > bmCapabilities 0x00 > CDC Union: > bMasterInterface 0 > bSlaveInterface 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 10 CDC Data > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 > iInterface 6 ethernet > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 EP 3 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Device Status: 0x0001 > Self Powered > > I've hunted pretty hard but can't find exactly this problem or a fix. > Can anyone here help? I'm quite happy to try some diagnosis, the > system I want to connect to the 2Wire is new so not yet configured and > thus I can do what I like to it. I can even build kernels if > necessary though I'd prefer not to! :-) > > -- > Chris Green > > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Chris Green -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
