From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
Matthew Garrett <mjg@redhat.com>, Frans Pop <elendil@planet.nl>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux acpi <linux-acpi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFT] hp-wmi: improved rfkill support for wifi
Date: Sun, 19 Jul 2009 10:15:32 +0200 [thread overview]
Message-ID: <8db1092f0907190115l6c55df77o47ae40c20b04c2a6@mail.gmail.com> (raw)
In-Reply-To: <71cd59b00907181437l6ef362ejc345818a5197a6c4@mail.gmail.com>
2009/7/18 Corentin Chary <corentin.chary@gmail.com>:
>> Linux can also do enabling "by software". At the moment, you need to
>> download and compile a utility to poke /dev/rfkill. I wouldn't bother
>> testing it, because I didn't change that bit :-).
>
> Utility is here
> http://git.sipsolutions.net/?p=rfkill.git
> And a patch to restore write access to /sys/class/rfkill/*/state file is here
> http://lkml.org/lkml/2009/7/10/339
Great tool.
Block bluetooth:
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill block 3
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill unblock 3
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Block wireless:
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill block 0
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill list
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill unblock 0
root@gumis:/home/maciek/zrodelka/rfkill/rfkill# ./rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Works very nice on my laptop
Thanks!
--
Maciej Rutecki
http://www.maciek.unixy.pl
next prev parent reply other threads:[~2009-07-19 8:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 16:55 Alan Jenkins
2009-07-18 17:03 ` Matthew Garrett
2009-07-18 18:55 ` Maciej Rutecki
2009-07-18 20:46 ` Alan Jenkins
2009-07-18 21:37 ` Corentin Chary
2009-07-19 8:15 ` Maciej Rutecki [this message]
2009-07-19 7:28 ` Maciej Rutecki
2009-07-19 17:21 ` Alan Jenkins
2009-07-19 18:10 ` Maciej Rutecki
2009-07-19 18:24 ` Alan Jenkins
2009-07-19 19:08 ` Maciej Rutecki
2009-07-20 17:10 ` Alan Jenkins
2009-07-20 19:54 ` Maciej Rutecki
2009-07-20 20:08 ` Alan Jenkins
2009-07-19 18:25 ` Matthew Garrett
2009-07-19 19:08 ` Maciej Rutecki
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=8db1092f0907190115l6c55df77o47ae40c20b04c2a6@mail.gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=corentin.chary@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
/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
all inboxes | Powered by JetHome®