All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Recent results with BCM4312 on Netbook
Date: Tue, 22 Jun 2010 13:29:32 -0500	[thread overview]
Message-ID: <4C21010C.2090506@lwfinger.net> (raw)
In-Reply-To: <4C20FC9F.8040607@polymtl.ca>

On 06/22/2010 01:10 PM, William Bourque wrote:
> 
> Interresting information.
> 
> Using "qos=0" and "nohwcrypt=1" effectively fixes the problem I had to
> connect to some access points. I could test it for two AP I knew to be
> wrong and I am now able to connect.
> 
> The strange part is that I was having a similar problem with broadcom
> proprietary driver, it is possible that the misbehave of b43 was messing
> up something in a way that even wl wasn't able to operate then?  All
> modules were unloaded before trying, but I didn't bother to cold reboot
> the notebook.
> It is also a bit weird that the problem was only on some AP.

I had the problem with both my APs. One is a Netgear 802.11n router
running the vendor's firmware with WPA2 encryption, and the other is a
Linksys running openWRT with WPA encryption.

The hardware encryption option might not be needed for WEP, but I have not
tested.

I cannot connect with wl on my machine. In fact, it cannot even scan, but
I'm only interested in its initialization.

Larry

  reply	other threads:[~2010-06-22 18:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 15:36 Recent results with BCM4312 on Netbook Larry Finger
2010-06-22 16:31 ` Michael Büsch
2010-06-22 16:31   ` Michael Büsch
2010-06-22 18:10 ` William Bourque
2010-06-22 18:29   ` Larry Finger [this message]
2010-06-22 22:47 ` Gábor Stefanik
2010-06-22 22:47   ` Gábor Stefanik
2010-06-23 12:42   ` Michael Büsch
2010-06-23 12:42     ` Michael Büsch
2010-06-23 20:49     ` Larry Finger
2010-06-23 20:49       ` Larry Finger

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=4C21010C.2090506@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.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.