From: "John W. Linville" <linville@tuxdriver.com>
To: Marcus Better <marcus@better.se>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl3945 not associating on 2.6.35
Date: Mon, 16 Aug 2010 10:52:21 -0400 [thread overview]
Message-ID: <20100816145221.GB2656@tuxdriver.com> (raw)
In-Reply-To: <i485ou$qmb$1@dough.gmane.org>
On Sun, Aug 15, 2010 at 09:42:15AM +0200, Marcus Better wrote:
> Hi,
>
> after upgrading from 2.6.34 to either 2.6.35 or 2.6.35.1, wpasupplicant will
> no longer associate to my WPA2 access point. The log is full of "Failed to
> initiate AP scan" messages.
>
> Is this a known issue? I couldn't quite find out by sifting through the
> archives... The system is a Thinkpad T61, x86_64, Debian sid, network-
> manager and wpasupplicant 0.6.10-2.
>
> Cheers,
>
> Marcus
I'm not aware of this issue. Please open a bug at bugzilla.kernel.org.
Please include dmesg output for starters.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-08-16 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 7:42 iwl3945 not associating on 2.6.35 Marcus Better
2010-08-16 14:52 ` John W. Linville [this message]
2010-08-17 7:10 ` Marcus Better
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=20100816145221.GB2656@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcus@better.se \
/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).