lkml.org 
[lkml]   [2009]   [Dec]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRfkill buttons : bi-stable, mono-stable, tactile
Date
Hello Developers,

I'm sorry for not cc:ing to relevant people and other lists, I just encountered
a situation I wanted to share.

On Acer Aspire One, A150 Aw, sold to me with Linpus but then rooted up and
installed Ubuntu Karmic (yes, 9.10) and updated the BIOS to 3309 (latest). This
however isn't Ubuntu-specific (actually if I googled correctly, only one
distribution got it right, the original Linpus Lite...)

The issue I am talking about is : the killswitch for the wireless adaptor.

The Internet is almost 'flooded' with reports of this not working on various
distributions, that's why decided to go a level higher.

I have actually found that pushing this button repeatedly, produces 2 scancodes
: showkey reports keycode 238 pressed and keycode 238 released; in -s mode
reports 0xe0 0xf3 and 0xe0 0x73.

Also I think the firmware (BIOS) reports these only when the operation on the
WIFI card has been done, i.e. when it successfully toggled it, because when
pushing the button too often (too small gap between pushes)

As this netbook gives a completely unusable WMI interface (found out by Carlos
Corbacho, the acer-wmi developer) there is no other way the rfkill
infrastructure can be aware of the hard-lock status;

The killswitch itself is a mono-stable sliding button, not a bi-stable slider;
so I think this might also be related to some people's problems with
(de)activating wifi hardware on laptops that have just a Fn+wifi toggle;
This is why I think this might be a more generic issue, and why I decided to
post here.

Apologies, if it really really doesn't belong here.

Lukasz



\
 
 \ /
  Last update: 2009-12-17 12:49    [W:0.063 / U:8.996 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site