linux-kernel - Re: [2.6.28-rc2]: iwl4965 doesn't connect / cfg80211 failure

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20081028172418.3c8e91f1@mtlp.12.dimension>
Date:	Tue, 28 Oct 2008 17:24:18 +0100
From:	Mirco Tischler <mt-ml@....de>
To:	Zhu Yi <yi.zhu@...el.com>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	"John W.Linville" <linville@...driver.com>,
	"Chatre, Reinette" <reinette.chatre@...el.com>,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: [2.6.28-rc2]: iwl4965 doesn't connect / cfg80211 failure

On Tue, 28 Oct 2008 13:23:34 +0800, Zhu Yi wrote:
> On Mon, 2008-10-27 at 22:32 -0600, Arjan van de Ven wrote:
> > I had this same issue
> > 
> > turning on CONFIG_WIRELESS_OLD_REGULATORY fixed it for me....
> 
> Arjan,
> 
> This is a different bug. He has the wireless worked sometimes.
> 
> I think your problem relates to 5GHz channel usage. We have already a
> patch queued to resolve the problem. We will have regulatory framework
> reworked to better solve the problem. But I guess it will be in .29 time
> frame.
> 
> Thanks,
> -yi
I tested Arjan's solution nevertheless and it seems to do the job. I can't find
the "TX Power requested" line anymore on dmesg output with that config option
enabled anymore and it connects without problems.
This is how it looks now:
[  777.680750] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux,1.3.27kds 
[  777.680753] iwlagn: Copyright(c) 2003-2008 Intel Corporation
[  777.680878] iwlagn 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[  777.680908] iwlagn 0000:06:00.0: setting latency timer to 64
[  777.680977] iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
[  777.731255] iwlagn: Tunable channels: 13 802.11bg, 19 802.11a channels
[  777.732432] phy1: Selected rate control algorithm 'iwl-agn-rs'
[  781.764539] iwlagn 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[  781.764821] iwlagn 0000:06:00.0: irq 41 for MSI/MSI-X
[  781.764919] iwlagn 0000:06:00.0: firmware: requesting iwlwifi-4965-2.ucode
[  781.980719] Registered led device: iwl-phy1:radio
[  781.980764] Registered led device: iwl-phy1:assoc
[  781.980808] Registered led device: iwl-phy1:RX
[  781.980856] Registered led device: iwl-phy1:TX
[  782.014001] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  783.633713] wlan0: authenticate with AP 00:c0:a8:e5:e5:a5
[  783.635637] wlan0: authenticated
[  783.635644] wlan0: associate with AP 00:c0:a8:e5:e5:a5
[  783.642770] wlan0: RX AssocResp from 00:c0:a8:e5:e5:a5 (capab=0x431 status=0
aid=1) 
[  783.642776] wlan0: associated [  783.669684] ADDRCONF(NETDEV_CHANGE): wlan0:
link becomes ready

I tested it quickly and not very thoroughly on the wpa-eap encrypted network at
university and it showed the same behaviour: no connection without
CONFIG_WIRELESS_OLD_REGULATORY and no problems with it enabled.

Thanks
Mirco

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)