linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: Rfkill always soft/hard blocked upon boot
Date: Sun, 30 Jan 2011 21:09:42 +0200	[thread overview]
Message-ID: <4D45B776.4000403@pardus.org.tr> (raw)
In-Reply-To: <4D45B338.8010802@lwfinger.net>

On 30.01.2011 20:51, Larry Finger wrote:

> The nature of that Fn-F2 key depends on how the motherboard manufacturer coded
> their BIOS. Most do it as a toggle and use some WMI (Windows Management
> Interface) code to initialize it on boot up. As this no-name laptop is unlikely
> to have a WMI driver the way that name brands do, it probably generates a
> keystroke. That is easy to check - Use CTRL-ALT-F1 to switch to a console, log
> in, and issue the command "showkey". Is a keycode returned when Fn-F2 is pressed?

Hmm I've got it. So maybe taking look at the ACPI tables/WMI block can 
reveal a way to initialize the toggle? I'm not really experienced in 
these things but I'll take a look out of curiosity.

Thanks!


-- 
Pardus Linux
http://www.pardus.org.tr/eng

  reply	other threads:[~2011-01-30 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 12:46 Rfkill always soft/hard blocked upon boot Ozan Çağlayan
2011-01-30 18:51 ` Larry Finger
2011-01-30 19:09   ` Ozan Çağlayan [this message]
2011-01-31  2:08     ` Joey Lee
2011-01-31  9:03       ` Ozan Çağlayan
2011-01-31 10:21         ` Joey Lee
2011-01-31 11:04           ` Ozan Çağlayan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D45B776.4000403@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).