From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi (4965) regression since 2.6.30
Date: Wed, 5 Aug 2009 00:56:26 +0200 [thread overview]
Message-ID: <20090804225626.GZ3382@ics.muni.cz> (raw)
In-Reply-To: <1249426183.30019.4581.camel@rc-desk>
On Tue, Aug 04, 2009 at 03:49:43PM -0700, reinette chatre wrote:
> This is strange. My previous test results were based on recent
> wireless-testing. I now retested with a fresh pull from Linus's repo
> (2.6.31-rc5) and I see the same behavior with Fn+F5 not changing the
> wifi radio status at all. I do not know why we would see different
> behavior considering we have the same platform and running the same
> kernel. I found one related option in the BIOS, but with that I was only
> able to have wireless HW rfkill permanently enabled.
>
> I am not sure about the original problem though. In your original report
> you mention that you are unable to use wireless due to rfkill. From your
> email it seems that you are able to toggle wifi rfkill state using the
> Fn+F5 keys, so with that disabling rfkill you should be able to use your
> wireless. Can you still not use wireless even when rfkill reports
> "RFKILL event: idx 6 type 1 op X soft 0 hard 0" ?
No.
I can use wifi if rfkill reports "RFKILL event: idx 6 type 1 op X soft 0 hard
0".
My problem is, that since 2.6.31-rcX Fn+F5 toggles soft rfkill state. It did
not happen in 2.6.30 and earlier. In that case, Fn+F5 triggered an acpi event
(key press). Now, it triggers acpi eveny *and* touches soft rfkill of WIFI.
I like the previous behavior, i.e., don't touch anything, just report acpi
event.
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2009-08-04 22:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 7:57 Lukas Hejtmanek
2009-07-27 16:03 ` reinette chatre
2009-07-27 16:06 ` Johannes Berg
2009-07-28 11:21 ` Lukas Hejtmanek
2009-07-28 12:54 ` Johannes Berg
2009-08-02 22:12 ` Lukas Hejtmanek
2009-08-03 21:47 ` reinette chatre
2009-08-04 8:49 ` Lukas Hejtmanek
2009-08-04 22:49 ` reinette chatre
2009-08-04 22:56 ` Lukas Hejtmanek [this message]
2009-08-04 23:38 ` reinette chatre
2009-08-06 13:22 ` Henrique de Moraes Holschuh
2009-08-06 22:41 ` Lukas Hejtmanek
2009-08-06 23:07 ` Henrique de Moraes Holschuh
2009-08-07 20:32 ` Johannes Stezenbach
2009-08-07 21:16 ` Lukas Hejtmanek
2009-08-07 21:35 ` Lukas Hejtmanek
2009-08-13 22:59 ` reinette chatre
2009-08-14 2:10 ` Henrique de Moraes Holschuh
2009-08-14 16:07 ` reinette chatre
2009-07-27 16:07 ` Marcel Holtmann
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=20090804225626.GZ3382@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.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®