On Thu, Jul 16, 2009 at 4:35 PM, Thomas Backlund<tmb@xxxxxxxxxxxx> wrote: > Johannes Berg skrev: >> >> On Fri, 2009-07-17 at 00:18 +0200, Johannes Berg wrote: >> >>>> And pressing it again gets this: >>>> [root@tmb-laptop rfkill]# ./rfkill list >>>> 0: acer-wireless: Wireless LAN >>>> Soft blocked: no >>>> Hard blocked: no >>>> 1: acer-bluetooth: Bluetooth >>>> Soft blocked: yes >>>> Hard blocked: no >>>> 2: phy0: Wireless LAN >>>> Soft blocked: yes >>>> Hard blocked: no >>>> >>>> And after that I cant get wireless back until I again do a: >>>> ./rfkill unblock 2 >>>> (works only when acer-wireless is no/no and Wireless LAN is yes/no) >>> >>> Right. This is bad. The button press shouldn't have affected the >>> soft-state of the rfkill #2. >>> >>>> Applying this patch: >>>> [PATCH] rfkill: fix rfkill_set_states() to set the hw state >>>> sent by Alan Jenkins does not help this issue either... >>>> >>>> Any suggestions how to fix the rfkill ? >>> >>> I'll poke at the acer code to see what it's doing wrong... >> >> Can't see anything wrong. I wonder if the button you have sends both the >> ACPI event _and_ an input event. >> >> Can you try this patch and tell us what happens? >> > > pressing rfkill when I have a working wireless gets this: > > Jul 17 02:24:35 tmb-laptop klogd: rfkill_schedule_toggle(1) > Jul 17 02:24:35 tmb-laptop klogd: iwlagn 0000:04:00.0: Error sending > REPLY_RXON_ASSOC: enqueue_hcmd failed: -5 > Jul 17 02:24:35 tmb-laptop klogd: iwlagn 0000:04:00.0: Error setting > RXON_ASSOC (-5) > Jul 17 02:24:35 tmb-laptop klogd: iwlagn 0000:04:00.0: Error sending > REPLY_ADD_STA: enqueue_hcmd failed: -5 > Jul 17 02:24:35 tmb-laptop klogd: mac80211-phy0: failed to remove key (0, > 00:19:5b:51:dc:27) from hardware (-5) > Jul 17 02:24:35 tmb-laptop klogd: iwlagn 0000:04:00.0: Error sending > REPLY_ADD_STA: enqueue_hcmd failed: -5 > Jul 17 02:24:35 tmb-laptop klogd: mac80211-phy0: failed to remove key (1, > ff:ff:ff:ff:ff:ff) from hardware (-5) > Jul 17 02:24:35 tmb-laptop dhclient: receive_packet failed on wlan0: Network > is down > Jul 17 02:24:35 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [1] > Jul 17 02:24:36 tmb-laptop ifplugd(wlan0)[1790]: Link beat lost. > > > After that I only get (when pressing rfkill several times...): > Jul 17 02:30:16 tmb-laptop klogd: rfkill_schedule_toggle(1) > Jul 17 02:30:16 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [0] > > Jul 17 02:30:28 tmb-laptop klogd: rfkill_schedule_toggle(1) > Jul 17 02:30:28 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [1] > > Jul 17 02:30:31 tmb-laptop klogd: rfkill_schedule_toggle(1) > Jul 17 02:30:31 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [0] > > Jul 17 02:30:45 tmb-laptop klogd: rfkill_schedule_toggle(1) > Jul 17 02:30:45 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [1] > > Jul 17 02:32:23 tmb-laptop klogd: rfkill_schedule_toggle(1) > Jul 17 02:32:23 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [0] > > And no wireless network... > > Issuing ./rfkill unblock 2 gets the wireless back > Jul 17 02:32:48 tmb-laptop klogd: Registered led device: iwl-phy0::radio > Jul 17 02:32:48 tmb-laptop klogd: Registered led device: iwl-phy0::assoc > Jul 17 02:32:48 tmb-laptop klogd: Registered led device: iwl-phy0::RX > Jul 17 02:32:48 tmb-laptop klogd: Registered led device: iwl-phy0::TX > Jul 17 02:33:00 tmb-laptop ifplugd(wlan0)[1790]: Link beat detected. I think we're missing two rfkill defines for compat. Give me a second to review. Luis -- 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
