Well, NM indeed doesn't seem to always come up when dealing with soft blocks, but Fn-F7 works fine here for stopping and restarting wireless (but thats a hard block on dell-wifi). I have multiple killswitches registered: phy0 and dell-wifi for wifi. A soft block for phy0 shows the device disconnected and not able to bring up interfaces. Soft block for dell-wireless puts the device in "not ready" state which turns it unusable until you enable/disable wifi using the applet.
As such, I think it's worth noting this as affecting linux anyway: the Eeepc's drivers don't properly handle the soft killswitch event: they really should be causing a hard block, not a soft one (and without checking, it might be a soft one as a workaround in userland somewhere). This would need a separate bug, Jeff or Seth, care to open one against linux for the eeepc drivers?
Well, NM indeed doesn't seem to always come up when dealing with soft blocks, but Fn-F7 works fine here for stopping and restarting wireless (but thats a hard block on dell-wifi). I have multiple killswitches registered: phy0 and dell-wifi for wifi. A soft block for phy0 shows the device disconnected and not able to bring up interfaces. Soft block for dell-wireless puts the device in "not ready" state which turns it unusable until you enable/disable wifi using the applet.
As such, I think it's worth noting this as affecting linux anyway: the Eeepc's drivers don't properly handle the soft killswitch event: they really should be causing a hard block, not a soft one (and without checking, it might be a soft one as a workaround in userland somewhere). This would need a separate bug, Jeff or Seth, care to open one against linux for the eeepc drivers?