[Bug 15346] Wireless device requires wlanctl-ng commands in order to work properly

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15346
Ubuntu | linux





------- Additional Comments From arzajac at yahoo.ca  2005-09-15 15:09 UTC -------
Perhaps there are hardware revisions of this device that work better than others?  This 
problem has existed since 2002 and there seem to be a number of variations on a theme to work 
around it. There is a recent thread on the linux-wlan-ng list about this too (see below, c)

a)
http://www.berndporr.me.uk/wireless/
"The original script has to be called two times. The first time the driver gives an error 
message. The second time it succeeds"

b)
http://lists.linux-wlan.com/pipermail/linux-wlan-user/2002-May/005834.html
"Solution:
---------

Disable the wlan0 interface first. This command sequence worked:

wlanctl-ng wlan0 lnxreq_ifstate ifstate=disable
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable"


And more recently:
c)
http://lists.linux-wlan.com/pipermail/linux-wlan-user/2005-August/013407.html
" # ADD THE FOLLOWING LINE
        $WLANCTL $1 lnxreq_ifstate ifstate=disable
        result=`$WLANCTL $1 lnxreq_ifstate ifstate=enable`"

This is equivalent to modifying the linux-wlan-ng script in /etc/networking/if-pre-up.d to do 
the ifstate=enable command twice, or at least try again in the even of an implementation 
failure.

I tried this morning to add the "wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable" command in 
that script just before it does the actual evalutation.  It did not work, but I really suck at 
bash scripting so I may have done it wrong.

I can compile the most recent linux-wlan-ng from source.  Would that save some time?  Or have 
Debian/Ubuntu-specific changes been made to the linux-wlan-ng package that I would not get 
from the linux-wlan-ng source?

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.