On Friday 26 June 2009, Johannes Berg wrote: > On Fri, 2009-06-26 at 14:10 +0200, Frans Pop wrote: > > Well, with 2.6.30 hp-wmi worked together with rfkill without > > problems. Looking at the commit logs, it looks like the rfkill > > rewrite by Johannes and Alan is the cause here. CCs added. > > Hmm, looks like there might be another polarity error, try this: > - int query = BIT(b + 8) | ((!!blocked) << b); > + int query = BIT(b + 8) | ((!blocked) << b); Thanks Johannes, that makes wireless work again. However, I just saw another possible issue. When I disable wireless using the hardware switch and the enable it again almost immediately after on 2.6.30, I get: [disable] iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On: Kill switch must be turned off for wireless networking to work. usb 3-1: USB disconnect, address 2 [enable] Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX usb 3-1: new full speed USB device using uhci_hcd and address 3 usb 3-1: configuration #1 chosen from 1 choice wlan0: no probe response from AP 00:14:c1:38:e5:15 - disassociating iwlagn 0000:10:00.0: index 0 not used in uCode key table. wlan0: authenticate with AP 00:14:c1:38:e5:15 wlan0: authenticate with AP 00:14:c1:38:e5:15 wlan0: authenticated wlan0: associate with AP 00:14:c1:38:e5:15 wlan0: RX ReassocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=1) wlan0: associated And without any other action networking is up again. With 2.6.31 I get this: [disable] wlan0: deauthenticating by local choice (reason=3) iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 mac80211-phy0: failed to remove key (0, 00:14:c1:38:e5:15) from hardware (-5) iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5) usb 3-1: USB disconnect, address 2 [enable] usb 3-1: new full speed USB device using uhci_hcd and address 3 usb 3-1: configuration #1 chosen from 1 choice A lot uglier with those errors. And after that I have to run ifdown/ifup before networking is up again (ifup only does not work as it will complain "interface already configured"): [ifdown wlan0] Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX ADDRCONF(NETDEV_UP): wlan0: link is not ready [ifup wlan 0] Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: authenticate with AP 00:14:c1:38:e5:15 wlan0: authenticated wlan0: associate with AP 00:14:c1:38:e5:15 wlan0: RX AssocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=1) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready BTW, would it make sense to bring back the first two lines shown with .30 (or at least the first one): iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On: Kill switch must be turned off for wireless networking to work. IMHO it's good to register the reason for the disconnect. Cheers, FJP -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
