You are not logged in.

#1 2011-09-26 06:01:09

jubei
Member
Registered: 2009-10-09
Posts: 8

Wireless switch

Hello,
Some years ago, I installed Arch to my laptop (BenQ P41 - Turion X2 TL60 - Radeon Xpress 1100 - Atheros AR5006EG).
In windows I have to press Fn+F12
once: activate wireless switch (blue led on)
twice: activate bluetooth, switch wireless off (orange led on)
three times: both bluetooth and wireless are on (pink led on)
4 times: both switched off (no led)
At that time Arch can connect to my wireless network without me pressing Fn+F12 (I had to install madwifi driver). However pressing Fn+F21 did not turn blue led on. However bluetooth switch workwith no problem

Anyway, my old harddisk just died and I replaced it with a new one. I installed Arch again and is now having small annoying problem with the wireless switch. Apparently my card is now automatically recoqnized as wlan0.
If I pressed Fn+F12 during boot up process then everything worked like a charm even the LED showed correct colors. Only problem is that it stays connected eventhough I switched off the button.
However, if I pressed Fn+F12 once I arrived in my desktop environment (KDE) than the wireless switch did not work at all it can only show orange LED (bluetooth on) other than that no LED at all. In other word I can not connect through wlan0.
dmesg gave me the following:
[  141.333171] atkbd serio0: Unknown key pressed (translated set 2, code 0xc0 on isa0060/serio0).
[  141.333176] atkbd serio0: Use 'setkeycodes e040 <keycode>' to make it known.
Searching google I found a suggestion to set it in /etc/rc.local
running dumbkeys, I got following empty key code
keycode 120 =
keycode 121 =
keycode 122 =
keycode 123 =
......
So I set the following in rc.local:
setkeycodes e040 <248>

But it did not solve my problem....
Any help??????

Last edited by jubei (2011-09-26 06:09:25)

Offline

Board footer

Powered by FluxBB