cannot follow ifdown with ifup with prism2_usb
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-wlan-ng (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
I have a 802.11b device which is (at the present time) working okay with
Dapper's prism2_usb module and the linux-wlan-ng. This is a bit of a nitpick
now that this setup is generally working okay, but . . .
If you have the interface up, and you bring it down with "sudo ifdown
wlan0", then you can't bring it back up with "sudo ifup wlan0". If you try,
it looks like this:
toojays@
wlanctl-ng: No such device
Failed to enable the device, exitcode= 1 .
run-parts: /etc/network/
code 1
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; No such device.
Error for wireless request "Set Encode" (8B2B) :
GET failed on device wlan0 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
wlan0: ERROR while getting interface flags: No such device
Failed to bring up wlan0.
The reason is that the ifdown script removes the prism2_usb module. So if I
want to bring the interface up, I have to unplug/replug the device. This is
a pain.
Doesn't the kernel automatically remove unused modules?
| Tormod Volden (tormodvolden) wrote | #1 |
| Changed in linux-wlan-ng: | |
| status: | Unconfirmed → Confirmed |
| Tormod Volden (tormodvolden) wrote | #2 |
| Tormod Volden (tormodvolden) wrote | #3 |
| Changed in linux-wlan-ng: | |
| status: | Confirmed → Fix Released |
You can also, instead of unplugging/
This is at least a smaller pain :)
See also bug #21569 about the prism2_usb issues.