All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, jketreno@linux.intel.com
Subject: Re: 2.6.19-rc2 ipw2200 breakage with wpa_supplicant
Date: Mon, 23 Oct 2006 11:35:17 +0800	[thread overview]
Message-ID: <1161574517.19188.32.camel@debian.sh.intel.com> (raw)
In-Reply-To: <45399521.30502@shaw.ca>

On Fri, 2006-10-20 at 21:33 -0600, Robert Hancock wrote:
> Robert Hancock wrote:
> > Something changed between 2.6.18-mm1 and 2.6.19-rc2 to cause my laptop's 
> > ipw2200 to be unable to associate with the access point using 
> > NetworkManager and wpa_supplicant. I keep seeing this kind of thing over 
> > and over in the wpa_supplicant output:
> 
> It looks like the bad patch is this one. Reverting it makes it work 
> again. Either there's a bug in here or it's a change breaking working 
> userspace, either way, no good:
> 
> [PATCH] WE-21 for ipw2200
> 
> author	Jean Tourrilhes <jt@hpl.hp.com>
> 	Wed, 30 Aug 2006 01:01:40 +0000 (18:01 -0700)
> committer	John W. Linville <linville@tuxdriver.com>
> 	Mon, 25 Sep 2006 20:52:16 +0000 (16:52 -0400)
> commit	919ee6ddcd3fcff09dee90c11af17a802196ad1f
> tree	c45e35201d7a3f2c998fc316898f902fd85fdfd2
> parent	b978d0278c3a4c41bda806743c6ef5dca86b4c61
> 
> [PATCH] WE-21 for ipw2200
> 
> Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>

This is a wpa_supplicant WE-21 incompatibility problem. Using iwconfig
directly works. Don't know if upgrading wpa_supplicant helps.

Thanks,
-yi

      parent reply	other threads:[~2006-10-23  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21  3:14 2.6.19-rc2 ipw2200 breakage with wpa_supplicant Robert Hancock
2006-10-21  3:33 ` Robert Hancock
2006-10-21  4:29   ` Andrew Morton
2006-10-23  3:35   ` Zhu Yi [this message]

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=1161574517.19188.32.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=hancockr@shaw.ca \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.