All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Michael Buesch <mb@bu3sch.de>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	Celejar <celejar@gmail.com>
Subject: Re: Fwd: 4318 misbehaving with bleeding edge kernels
Date: Fri, 10 Jul 2009 11:06:03 -0400	[thread overview]
Message-ID: <20090710150602.GB2825@tuxdriver.com> (raw)
In-Reply-To: <1247237986.3210.10.camel@mj>

On Fri, Jul 10, 2009 at 10:59:46AM -0400, Pavel Roskin wrote:
> On Fri, 2009-07-10 at 11:31 +0200, Michael Buesch wrote:
> 
> > I have a 4318 (rev 02), which has been working fine with b43.
> > Recently, with 2.6.31-rc2 kernels from the wireless-testing git repo,
> > I've been having trouble.  Sometimes the card simply fails to associate
> > after doing 'iwconfig eth0 essid xxxx'.  It doesn't even seem to try;
> > i.e., when it does associate, I see log entries like these:
> 
> I believe is that the ESSID support in the wext compatibility layer is
> seriously broken.  It's not shown originally at all.  Once it's set, it
> cannot be changed.

What kernel are you using?  I don't see this behavior...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.
			¡Viva Honduras Libre!

  reply	other threads:[~2009-07-10 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10  9:31 Fwd: 4318 misbehaving with bleeding edge kernels Michael Buesch
2009-07-10 14:59 ` Pavel Roskin
2009-07-10 15:06   ` John W. Linville [this message]
2009-07-10 15:40     ` Pavel Roskin

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=20090710150602.GB2825@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=celejar@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=proski@gnu.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.