From: Arjan van de Ven <arjan@infradead.org>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Mirco Tischler <mt-ml@gmx.de>,
lkml <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W.Linville" <linville@tuxdriver.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [2.6.28-rc2]: iwl4965 doesn't connect / cfg80211 failure
Date: Mon, 27 Oct 2008 21:32:17 -0700 [thread overview]
Message-ID: <20081027213217.53558319@infradead.org> (raw)
In-Reply-To: <1225157618.2917.215.camel@debian.sh.intel.com>
On Tue, 28 Oct 2008 09:33:37 +0800
Zhu Yi <yi.zhu@intel.com> wrote:
> On Mon, 2008-10-27 at 18:02 -0700, Mirco Tischler wrote:
> > Hi
> >
> > I have problems connecting to wlan with my iwl4965 chip and
> > 2.6.28-rc2 (didn't test -rc1). Networkmanager just times out every
> > time. Only after playing around with rmmod/modprobe and killswitch
> > I am sometimes able to connect. But I cannot reproduce this
> > reliably yet.
> >
> > This is what I get in dmesg (from modprobe iwlagn to connection
> > failure):
> >
> > [ 1881.884690] iwlagn: Intel(R) Wireless WiFi Link AGN driver for
> > Linux,1.3.27kds
> > [ 1881.884692] iwlagn: Copyright(c) 2003-2008 Intel Corporation
> > [ 1881.884809] iwlagn 0000:06:00.0: PCI INT A -> GSI 18 (level,
> > low) -> IRQ 18 [ 1881.884836] iwlagn 0000:06:00.0: setting latency
> > timer to 64 [ 1881.884952] iwlagn: Detected Intel Wireless WiFi
> > Link 4965AGN REV=0x4 [ 1881.935149] iwlagn: Tunable channels: 13
> > 802.11bg, 19 802.11a channels [ 1881.936327] phy4: Selected rate
> > control algorithm 'iwl-agn-rs' [ 1885.965591] iwlagn 0000:06:00.0:
> > PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1885.965874] iwlagn
> > 0000:06:00.0: irq 41 for MSI/MSI-X [ 1885.965974] iwlagn
> > 0000:06:00.0: firmware: requesting iwlwifi-4965-2.ucode
> > [ 1886.181600] Registered led device: iwl-phy4:radio [ 1886.181618]
> > Registered led device: iwl-phy4:assoc [ 1886.181635] Registered led
> > device: iwl-phy4:RX [ 1886.181654] Registered led device:
> > iwl-phy4:TX [ 1886.213631] ADDRCONF(NETDEV_UP): wlan0: link is not
> > ready [ 1887.572768] iwlagn: TX Power requested while scanning!
>
> Looks good so far. But I failed to see what are you trying to connect?
> Can you try "iwconfig wlan0 channnel <> essid <>"?
>
I had this same issue
turning on CONFIG_WIRELESS_OLD_REGULATORY fixed it for me....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-28 4:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081028020212.0dfcb6c9@mtlp.12.dimension>
2008-10-28 1:33 ` [2.6.28-rc2]: iwl4965 doesn't connect / cfg80211 failure Zhu Yi
2008-10-28 1:59 ` Mirco Tischler
2008-10-28 2:19 ` Zhu Yi
2008-10-28 3:19 ` Mirco Tischler
2008-10-28 4:32 ` Arjan van de Ven [this message]
2008-10-28 5:23 ` Zhu Yi
2008-10-28 16:24 ` Mirco Tischler
2008-10-28 18:36 ` Johannes Berg
2008-10-28 22:58 ` Mirco Tischler
2008-10-28 23:06 ` Johannes Berg
2008-10-28 23:35 ` Mirco Tischler
2008-10-29 6:18 ` Zhu Yi
2008-10-30 17:24 ` Mirco Tischler
2008-10-30 17:55 ` reinette chatre
2008-10-31 22:25 ` Mirco Tischler
2008-10-28 2:05 ` Mirco Tischler
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=20081027213217.53558319@infradead.org \
--to=arjan@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mt-ml@gmx.de \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@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;
as well as URLs for NNTP newsgroup(s).