From: Ben Hutchings <ben@decadent.org.uk>
To: platform-driver-x86@vger.kernel.org
Cc: Tomasz Nitecki <tnnn@tnnn.pl>,
756947@bugs.debian.org, Alan Wilson <al_wilson@ns.sympatico.ca>
Subject: hp-wmi: wifi rfkill can't be reversed
Date: Tue, 26 Aug 2014 00:50:42 -0700 [thread overview]
Message-ID: <1409039442.3033.65.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1409018140.5921.3.camel@debian1>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
Alan Wilson (in cc) reported that rfkill doesn't work correctly on the
HP Compaq nc6230.
- Without the hp-wmi driver loaded, the hard rfkill switch controls both
wifi and BT while soft rfkill only works for wifi.
- With the hp-wmi driver loaded, soft and hard rfkill switches can be
used to turn wifi and BT off and to turn BT back on, but wifi cannot be
turned back on without using the BIOS setup program.
(The full bug report is logged at <https://bugs.debian.org/756947>.)
This was reported against Linux 3.2, but I don't think there have been
relevant fixes since then.
Perhaps the hp-wmi driver should blacklist this model for wifi rfkill
(while leaving all the others features enabled). Does that seem like a
reasonable approach to fix this?
Ben.
--
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next parent reply other threads:[~2014-08-26 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53ED47BA.60904@tnnn.pl>
[not found] ` <1408389040.2618.31.camel@deadeye.wl.decadent.org.uk>
[not found] ` <53F27EFC.3030409@tnnn.pl>
[not found] ` <1408916663.12973.88.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1409018140.5921.3.camel@debian1>
2014-08-26 7:50 ` Ben Hutchings [this message]
2014-08-26 22:40 ` hp-wmi: wifi rfkill can't be reversed Darren Hart
2014-08-27 6:57 ` Ben Hutchings
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=1409039442.3033.65.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=756947@bugs.debian.org \
--cc=al_wilson@ns.sympatico.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tnnn@tnnn.pl \
/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