Comment 13 for bug 395358

On Wed, Sep 09, 2009 at 02:17:29PM -0000, Stefan Bader wrote:
> No that has a ipw2200. I was mislead by the assumption that the wireless hotkey
> only is connected to the ec which then has to relay that through acpi drivers.
> But I learned that it also might be routed to the wireless device directly.

> Could you gather the output of "rfkill list" during the sequence of 4 presses
> of the wireless button (with acpid enabled)? This might show the various hard
> and soft states better.

Well, there are going to be fewer than 4 states being cycled through because
of bug #397698 (which I'm not trying to fix so long as the one system I have
to test with has broken rfkill handling in the kernel). Initial state, with
bluetooth manually disabled using 'rfkill block bluetooth':

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: yes
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
$

press it once:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
7: hci0: Bluetooth
 Soft blocked: yes
 Hard blocked: no
$

twice:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: yes
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
$

Similarly, if I manually unblock bluetooth first, it cycles between these
two states:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: yes
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
9: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
$

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>