[Bug 193970] Re: iwl3945: Wireless can't be activated if kill switch was on at boot

[Mary Gardiner]

Current version of hal:
0.5.10+git20080301-1ubuntu1

Current behaviour:
 - if starting system with killswitch on, no wireless networks are found until after /etc/init.d/hal restart

 - if I turn the killswitch off and immediately (say 2 to 4 seconds at
most) turn it back on, everything is fine. "iwlist scan" shows no
interfaces during the off period, but sees them again when switched back
on

 - if I turn the killswitch off and wait until Network Manager notices
that there's no network available (about 20 or 30 seconds), Network
Manager stupidly tries to re-associate with the access point, eventually
asks for its WPA key and continues showing wireless networks available
in its drop-down list. This may be a separate bug in NM, I'll recheck
that behaviour when this one is fixed. "iwlist scan" does not show any
interfaces even when the switch is turned back on. "sudo /etc/init.d/hal
restart" does not seem to help after the switch has been off this long
either, I have no alternative but to reboot my machine.

 - if I turn the killswitch off, suspend to RAM, resume, "iwlist scan"
shows no interfaces. Again, "sudo /etc/init.d/hal restart" does not help

-- 
iwl3945: Wireless can't be activated if kill switch was on at boot
https://bugs.launchpad.net/bugs/193970
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.