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

[jidanni at jidanni.org]

Here's one of the files from the Windows driver set that my buddy gave
me with the computer back in town that is actually used when the antenna
works (perfectly) under windows.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: NetGtks.inf
URL: <http://lists.alioth.debian.org/pipermail/linux-wlan-ng-devel/attachments/20100602/8a61137a/attachment.txt>
-------------- next part --------------

As you can see both company's IDs are in there so your ID theory is
probably correct but it would still be nice to know what to put into
/etc/udev/rules.d/70-persistent-net.rules in case one wants try with a
corrected ID -- or should I file a udev bug for them not providing a way
or documenting it.

P.S., these just get over and over...
modprobe prism2_usb
ifconfig wlan0 up
SIOCSIFFLAGS: Cannot assign requested address

wlanctl-ng wlan0 lnxreq_ifstate ifstate=disable
message=lnxreq_ifstate
  ifstate=disable
  resultcode=success

wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
CTLX[1] error: state(Request failed)
cmd_initialize() failed on two attempts, results -5 and -5
hfa384x_drvr_start() failed,result=-5

One last thing I could try is the ndiswrapper thing... more complexity.

Anyway, when I get back to my windows house with just wireless, I cannot
use linux to get on the network, so I had better test out these items
here on my mountain.

TV> There must be something the Windows driver does right that we don't.
TV> Would have liked to find out what.

I can confirm that this
http://www.sparklan.com/download.php?prod_id=119 -->
HEAD http://www.sparklan.com/downloadSupport.php?support_id=89
Content-Length: 3550323
DriverWindows_WL-382F_v1[1].2.2.66.zip
is the exact file that my windows buddy set me up with and that works
back in town.  And I wish to thank you in advance for having a look at
it to see what it does right that you don't... Maybe it even does a ID switch.