linux-kernel - Re: iwlwifi (4965) regression since 2.6.30

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090804225626.GZ3382@ics.muni.cz>
Date:	Wed, 5 Aug 2009 00:56:26 +0200
From:	Lukas Hejtmanek <xhejtman@....muni.cz>
To:	reinette chatre <reinette.chatre@...el.com>
Cc:	Johannes Berg <johannes@...solutions.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: iwlwifi (4965) regression since 2.6.30

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/