** Summary changed: - iwlagn 5300: Wireless can't be activated after disabling kill switch + iwlagn 5300 + acer wmi rf-kill bug
** Description changed: - UPDATE: Seems similar to bug 193970 except the workaround does not work, and chipset, driver, and distribution are all different. - ------------------------- - I'm running 2.6.28-4-generic with an intel 5300 AGN wireless card that works perfectly out of the box with intrepid. The iwlagn module is loaded and iwconfig sees an interface that supports wireless, but the device is unenableable in network manager. + Issue: - $ lspci |grep Wireless - 03:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection + I have an acer laptop with an intel 5300 wifi link card. The rf-kill + toggle switch works flawlessly with 2.6.27. - $ iwconfig - lo no wireless extensions. + In 2.6.28 with acer-wmi loaded The LED starts on, the + /sys/bus/.../rfkill*/state is 1 but the kernel believes the card is + disabled. Toggling the switch once turns the LED off, and the state to + 2, and the kernel still thinks the rf-kill switch is on. Finally further + toggling the switch does not change it ; it remains stuck at state 2. - eth0 no wireless extensions. + The only work around for 2.6.28 is to modprobe -r acer_wmi, which causes + the bad behavior to go away. - wmaster0 no wireless extensions. - - wlan0 IEEE 802.11abgn ESSID:"Asoka" - Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated - Tx-Power=14 dBm - Retry min limit:7 RTS thr:off Fragment thr=2352 B - Power Management:off - Link Quality:0 Signal level:0 Noise level:0 - Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 - Tx excessive retries:0 Invalid misc:0 Missed beacon:0 - - pan0 no wireless extensions. + $ uname -r + 2.6.28-8-generic $ lsmod |grep iw iwlagn 100228 0 iwlcore 93568 1 iwlagn led_class 12036 2 acer_wmi,iwlcore mac80211 217208 2 iwlagn,iwlcore cfg80211 38800 3 iwlagn,iwlcore,mac80211 -- iwlagn 5300 + acer wmi rf-kill bug https://bugs.launchpad.net/bugs/318078 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
