[Linux-wlan-ng-devel] Bug#583522: CTLX[1] error: state(Request failed)

[Tormod Volden]

On Thu, Jun 3, 2010 at 3:14 AM,  <jidanni at jidanni.org> wrote:
> OK, I suppose the ID is right, but odd, when I plug it in I get
> "invalid interface number" messages, no matter what port I plug it into.
>
> new full speed USB device using ehci_hcd and address 5
> config 1 has an invalid interface number: 1 but max is 0
> config 1 has no interface number 0

This is a bug in older firmware. The USB standard says interface
indexes should be zero based, but the firmware reports only number 1.
Linux works around this, so it is not a problem.

> New USB device found, idVendor=09aa, idProduct=3642
> New USB device strings: Mfr=0, Product=0, SerialNumber=1
> SerialNumber: 01190006
> configuration #1 chosen from 1 choice
>
> And then I have to modprobe by hand

I wonder why udev does not load the module itself? You can find
prism2_usb with your USB ID in your current modules.alias, right?

> # modprobe prism2_usb
> prism2_usb: module is from the staging directory, the quality is unknown, you have been warned.
> prism2_usb: Checking for firmware prism2_ru.fw
> usb 1-3.1: firmware: requesting prism2_ru.fw
> prism2_usb: prism2_ru.fw will be processed, size 90662
> CTLX[1] error: state(Request failed)
> CTLX[1] error: state(Request failed)
> cmd_initialize() failed on two attempts, results -5 and -5
> hfa384x_drvr_start() failed,result=-5
> PDA may only be read in the fwload state.
> load_cardpda failed, exiting.

For now, I suggest you remove the firmware, because the problem now is
not loading the firmware but getting contact with the card at all. If
we succeed with that, we can come back to it.

> TV> Make sure that you do "modprobe -r prism2_usb" first to remove it
> TV> before loading it again, and that you try disable/enable just after
> TV> the modprobe (do not run ifconfig). Please attach the full dmesg
> TV> output afterwards.
>
> # wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
> CTLX[1] error: state(Request failed)
> message=lnxreq_ifstate
>  ifstate=enable
>  resultcode=implementation_failure
> CTLX[1] error: state(Request failed)
> cmd_initialize() failed on two attempts, results -5 and -5
> hfa384x_drvr_start() failed,result=-5

I suggest trying several enables in a row, for instance:
modprobe -r prism2_usb
modprobe prism2_usb
wlanctl-ng wlan0 lnxreq_ifstate ifstate=disable
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable

Can you afterwards please run "dmesg > dmesg.txt" then attach
dmesg.txt as a file? You may edit it and remove irrelevant stuff from
before plugging it in, if you like. dmesg output also has timestamps
which could be useful for debugging.