Inaky Perez-Gonzalez <inaky.perez-gonzalez <at> intel.com> writes: > > Sounds like a case of a missing id; please try: > > $ echo 8086 0187 > /sys/bus/usb/drivers/i2400m/new_id > > [I forgot the exact format, if 8086 0187 fails to trigger it, try > "8086:0187", or adding also a '-n ' in front of the 8086]. > > That will tell the driver about a new hw ID it should recognize and > trigger a driver bind. > actualy seems this doesnt help at least with 2.6.35-rc5 after binding usb device to driver i get this in dmesg i2400m_usb 2-1.3:1.0: boot-mode cmd -1: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: boot-mode cmd 15: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: boot-mode cmd 1: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: boot-mode cmd 1: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: device boot: tried all the echo/acks, could not get device to respond; giving up i2400m_usb 2-1.3:1.0: read mac addr: bootrom init failed: -108 i2400m_usb 2-1.3:1.0: cannot setup device: -108 i2400m_usb: probe of 2-1.3:1.0 failed with error -108 iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio. ADDRCONF(NETDEV_UP): wlan0: link is not ready usb 1-1.4: new full speed USB device using ehci_hcd and address 7 i2400m_usb 2-1.3:1.0: boot-mode cmd -1: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: boot-mode cmd 15: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: boot-mode cmd 1: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: boot-mode cmd 1: error waiting for an ack: -110 i2400m_usb 2-1.3:1.0: device boot: tried all the echo/acks, could not get device to respond; giving up i2400m_usb 2-1.3:1.0: read mac addr: bootrom init failed: -108 i2400m_usb 2-1.3:1.0: cannot setup device: -108 i2400m_usb: probe of 2-1.3:1.0 failed with error -108
