I have a Ralink RT2573 WiFi USB module that is connected to the USB OTG port of a TI OMAP 3503 based platform device, running linux-omap3-2.6.29 kernel. I get the following kernel boot error messages
usb 1-1: New USB device found, idVendor=148f, idProduct=2573
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: 802.11 bg WLAN
usb 1-1: Manufacturer: Ralink
usb 1-1: rejected 1 configuration due to insufficient available bus power
usb 1-1: no configuration chosen from 1 choice
The TI OMAP 3503 motherboard's USB OTG port can only supply 100mA of power. The Ralink WiFi device requires 300mA.
However, the motherboard circuitry has been modified to directly apply power to the WiFi module's USB connectors from the motherboard's 3.3v power source, so power is right now being externally applied.
I can activate it temporarily by typing the following command
$ echo -n 1 >/sys/bus/usb/devices/1-1/bConfigurationValue
usb 1-1: new config #1 exceeds power limit by 200mA
# phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt2500usb
wmaster0 (rt73usb): not using net_device_ops yet
wlan0 (rt73usb): not using net_device_ops yet
Registered led device: rt73usb-phy1:radio
Registered led device: rt73usb-phy1:assoc
Registered led device: rt73usb-phy1:quality
usbcore: registered new interface driver rt73usb
rt73usb 1-1:1.0: firmware: requesting rt73.bin
ADDRCONF(NETDEV_UP): wlan0: link is not ready
What should I do to fix this error message?
The error message means that the device has a USB ID which both matches rt2500usb as well as rt73usb drivers. So it first tries to load rt2500usb and when that fails it tries the rt73usb driver. The only thing to prevent the problem is blacklisting the rt2500usb module.
That tells what the problem is. I am getting Kernel boot error messages and now I figure out the reason behind this message. There is an old rt73usb is installed which I am not using. I guess I will un-install that driver software to fix this issue.