From: Larry Finger <Larry.Finger@lwfinger.net>
To: wireless <linux-wireless@vger.kernel.org>
Cc: furlot@free.fr
Subject: Compaq laptop RFKILL problems
Date: Wed, 10 Sep 2008 12:22:09 -0500 [thread overview]
Message-ID: <48C80241.4000409@lwfinger.net> (raw)
I'm trying to help a Ubuntu user get his BCM4303 working on a Compaq
Presario R3215. His radio is hardware disabled, but the RFKILL switch
does not issue a scancode when pushed. Obviously, the Windows software
polls that key in some manner, but we have no idea what it does.
So far, we have updated the RFKILL level to that of wireless-testing,
tried a BIOS reset, and modified the code to issue a KEY_WLAN down/up
sequence when starting. So far, nothing has worked.
Does anyone on this list know of anything else to try, or any software
to handle this button?
Thanks,
Larry
next reply other threads:[~2008-09-10 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 17:22 Larry Finger [this message]
2008-09-11 12:00 ` Compaq laptop RFKILL problems Matthew Garrett
2008-09-11 19:50 ` Larry Finger
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=48C80241.4000409@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=furlot@free.fr \
--cc=linux-wireless@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).