From: Corentin Chary <corentin.chary@gmail.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
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: Sat, 18 Jul 2009 23:37:49 +0200 [thread overview]
Message-ID: <71cd59b00907181437l6ef362ejc345818a5197a6c4@mail.gmail.com> (raw)
In-Reply-To: <4A623490.50305@tuffmail.co.uk>
On Sat, Jul 18, 2009 at 10:46 PM, Alan
Jenkins<alan-jenkins@tuffmail.co.uk> wrote:
> Maciej Rutecki wrote:
>> 2009/7/18 Alan Jenkins <alan-jenkins@tuffmail.co.uk>:
>>
>>> I borrowed a HP G7000 last week. The hp-wmi driver seemed a bit
>>> confused about hard v.s. soft blocks on the wifi, so I fixed it based on
>>> acpidump output [1]. I hope this will work on other HP model numbers,
>>> but it would benefit from testing. Any volunteers?
>>>
>>
>> HP/Compaq nx6310
>> 2.6.31-rc3+patch
>>
>> When is enabled by button:
>> root@gumis:/sys/class/rfkill# ls
>> rfkill0 rfkill1 rfkill2 rfkill3
>> root@gumis:/sys/class/rfkill# cat rfkill*/name
>> phy0
>> hci0
>> hp-wifi
>> hp-bluetooth
>> root@gumis:/sys/class/rfkill# cat rfkill*/state
>> 1
>> 1
>> 1
>> 1
>>
>> When disabled by button:
>> root@gumis:/sys/class/rfkill# ls
>> rfkill0 rfkill2 rfkill3
>> root@gumis:/sys/class/rfkill# cat rfkill*/name
>> phy0
>> hp-wifi
>> hp-bluetooth
>> root@gumis:/sys/class/rfkill# cat rfkill*/state
>> 2
>> 1
>> 0
>>
>> I enable again by button:
>> root@gumis:/sys/class/rfkill# ls
>> rfkill0 rfkill2 rfkill3 rfkill4
>> root@gumis:/sys/class/rfkill# cat rfkill*/name
>> phy0
>> hp-wifi
>> hp-bluetooth
>> hci0
>> root@gumis:/sys/class/rfkill# cat rfkill*/state
>> 1
>> 1
>> 1
>> 1
>>
>> I disable "by software" in Windows XP (bluetooth and wireless):
>> root@gumis:/sys/class/rfkill# ls
>> rfkill0 rfkill1 rfkill2 rfkill3
>> root@gumis:/sys/class/rfkill# cat rfkill*/name
>> phy0
>> hp-wifi
>> hp-bluetooth
>> hci0
>> root@gumis:/sys/class/rfkill# cat rfkill*/state
>> 2
>> 0
>> 1
>> 1
>>
>> Bluetooth works fine when I back to Linux, it seems be enabled during
>> boot. Wireless is disabled. I cannot connect to network. So I
>> re-enable it in Windows:
>> root@gumis:/sys/class/rfkill# ls
>> rfkill0 rfkill1 rfkill2 rfkill3
>> root@gumis:/sys/class/rfkill# cat rfkill*/name
>> phy0
>> hci0
>> hp-wifi
>> hp-bluetooth
>> root@gumis:/sys/class/rfkill# cat rfkill*/state
>> 1
>> 1
>> 1
>> 1
>>
>> Regards
>>
>
> Great detail! That all fits with what I was expecting.
>
> 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
> I'll try extending this to bluetooth and wwan as Matthew suggested. If
> you have time to run "acpidump" and send me the output, that would help
> me check the details.
I have an HP 8710p, so if you want acpidump and test on another
hardware, just ask :).
--
Corentin Chary
http://xf.iksaif.net - http://uffs.org
next prev parent reply other threads:[~2009-07-18 21:37 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 [this message]
2009-07-19 8:15 ` Maciej Rutecki
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=71cd59b00907181437l6ef362ejc345818a5197a6c4@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=elendil@planet.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--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®