From: Howard Chu <hyc@highlandsun.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k rfkill behavior
Date: Tue, 21 Jul 2009 14:01:00 -0700 [thread overview]
Message-ID: <4A662C8C.9030702@highlandsun.com> (raw)
In-Reply-To: <200907211327.03954.chunkeey@web.de>
Christian Lamparter wrote:
> On Tuesday 21 July 2009 02:56:11 Howard Chu wrote:
>> I'm currently running 2.6.31-rc2 and noticed an annoying change in rfkill
>> behavior now; I can no longer toggle the state by echoing 0/1 into
>> sys/class/rfkill/rfkillX/state, it says write operation not permitted. I
>> haven't found any posts online related to this change in behavior, can anyone
>> point me to an explanation/rationale? The only way to change the state now
>> appears to be by using the wifi toggle switch on the laptop.
>
> http://lkml.org/lkml/2009/7/10/339
>
> but no need to patch the kernel (again):
> the legacy iwconfig tool can let you do the same:
>
> iwconfig wlanX txpower off
> and if you want it back:
> iwconfig wlanX txpower auto
Ah, not quite. I want the bluetooth off and the wifi on; if I hit the toggle
switch which turns them both off, iwconfig is unable to turn the wifi back on,
and there is no other command which turns off only the bluetooth.
The above patch works fine, thanks again.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
prev parent reply other threads:[~2009-07-21 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 0:56 ath9k rfkill behavior Howard Chu
2009-07-21 11:27 ` Christian Lamparter
2009-07-21 17:21 ` Howard Chu
2009-07-21 21:01 ` Howard Chu [this message]
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=4A662C8C.9030702@highlandsun.com \
--to=hyc@highlandsun.com \
--cc=chunkeey@web.de \
--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).