Johannes Berg skrev:
On Fri, 2009-07-17 at 01:09 +0300, Thomas Backlund wrote:
Nope.
Nothing gets logged when I press the rfkill...
I'd say that the rfkill rewrite killed my wireless :-(
Bluetooth works at it whould, but not the wireless
But now I have atleast found one way to get it working...
I've built the rfkill utility, and with it I can get the wireless working...
Thanks for the analysis!
Here is the output when wireless works:
[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: no
Hard blocked: no
Makes sense that it works at this point :)
Pressing the rfkill button gets me this:
[root@tmb-laptop rfkill]# ./rfkill list
0: acer-wireless: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: acer-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
So far so good. Your platform's soft-switch is wired to the card's hard
kill line. Mind trying
./rfkill unblock 0
(or whatever ID the acer-wireless has) at this point to see what
happens? I would hope it goes back to the working state.
Nothing happends...
It does not change anything on either acer-wireless or phy0
--
Thomas
--
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
