All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Jerry McBride <mcbrides9@comcast.net>, linux-wireless@vger.kernel.org
Subject: Re: B43 randomly and silently dropping connections...
Date: Wed, 29 Oct 2008 17:24:42 -0700	[thread overview]
Message-ID: <1225326282.5496.5.camel@brick> (raw)
In-Reply-To: <20081030001739.GG3485@tuxdriver.com>

On Wed, 2008-10-29 at 20:17 -0400, John W. Linville wrote:
> On Wed, Oct 29, 2008 at 08:10:06PM -0400, Jerry McBride wrote:
> 
> > SHORT STORY:
> > -- Kernel 2.6.25.x with BCM43XX, firmware 4.80.53.0.. just perfect.
> > 
> > -- Kernels 2.6.26 or higher with B43 and firware 4.150.10.5 good negotiations, 
> > but fragile connections that drop randomly and without complaint. B43LEGACY 
> > does nothing.
> > 
> > Any help would be appreciated. I'd really like to get this ironed out. I 
> > highly desire to use current kernels.
> 
> Are you running a distro kernel?  Or one you have built yourself?
> 
> If the latter, have you opened a bug at bugzilla.kernel.org?
> Otherwise, have you opened a bug with your distro's bug tracking
> system?
> 
> Do you have wireshark captures taken with another device in monitor
> mode that show these connection drops?
> 
> Are you using NetworkManager or wpa_supplicant?  Or just configuring
> your connection with iwconfig?  If the latter, consider the former.
> If you are using NM, does the connection get re-established
> automatically?  Or is NM unable to reestablish the connection?
> Use wpa_supplicant directly if NM just doesn't work for you.
> 
> It seems clear that posting the same message to the mailing lists
> again and again is not resolving the issue for you.  Please perform
> the actions requested above (including opening a bug at the appropriate
> place) and collect some useable data for us.

In addition, have you tried updated firmware that was pointed to
http://thread.gmane.org/gmane.linux.kernel.wireless.general/22790

No idea if it will fix it or not.

Harvey


  reply	other threads:[~2008-10-30  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  0:10 B43 randomly and silently dropping connections Jerry McBride
2008-10-30  0:17 ` John W. Linville
2008-10-30  0:24   ` Harvey Harrison [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-21  1:44 Jerry McBride
2008-10-19 21:25 Jerry McBride
2008-10-17 22:36 Jerry McBride
2008-10-16 23:59 Jerry McBride
2008-10-19 12:53 ` metin
2008-10-19 16:51   ` Larry Finger
2008-10-13 23:39 Jerry McBride
2008-10-14 14:15 ` John W. Linville

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=1225326282.5496.5.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcbrides9@comcast.net \
    /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.