From: Larry Finger <Larry.Finger@lwfinger.net>
To: roman-vl@meta.ua
Cc: linux-wireless@vger.kernel.org
Subject: Re: b43 scans wifi networks with old firmware only.
Date: Thu, 03 Nov 2011 10:12:04 -0500 [thread overview]
Message-ID: <4EB2AF44.7090102@lwfinger.net> (raw)
In-Reply-To: <48883.148.106.128.38.1320319313.metamail@webmail.meta.ua>
On 11/03/2011 06:21 AM, Roman V.Leon. wrote:
> Hello Gents.
> I have problem with b43 driver 5.100.138, it's not scanning networks for
> unknown reason. I have broadcom wifi card PCIID is 14e4:4315, linux kern
> ver. is 3.0. When i'm trying to launch iwlist scan, i'm getting "no scan
> results".
>
> for example:
> sudo ifconfig wlan0 up
> sudo iwlist wlan0 scan
> No scan results.
>
> With the older driver 5.10.56.2808, i see normal scan results. If you need
> any more information, i will send.
The condition you report is known. Broadcom changed the TX/RX header structure
with firmware versions greater than 600, as shown by a 'dmesg | grep firmware'.
Those changes are not implemented in b43 until kernel 3.2.
These numbers are not b43 driver numbers, nor are they firmware numbers reported
by b43. They are the versions of Broadcom drivers.
If you look at
http://wireless.kernel.org/en/users/Drivers/b43#firmwareinstallation, you will
see that firmware should be extracted from Broadcom driver 5.100.138 "if you are
using kernel 3.2 or newer". For older kernels you should extract firmware from
the 5.10.56.27.3 of the Broadcom proprietary driver. Of course, 5.10.56.2808
will also work.
You could also get those changes by employing a bleeding-edge version of
compat-wireless. In that case, firmware from 5.100.138 would work.
Larry
next prev parent reply other threads:[~2011-11-03 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 11:21 b43 scans wifi networks with old firmware only Roman V.Leon.
2011-11-03 15:12 ` Larry Finger [this message]
2011-11-03 20:22 ` Roman V.Leon.
2011-11-03 22:37 ` Rafał Miłecki
2011-11-04 0:37 ` Larry Finger
2011-11-04 10:27 ` Rafał Miłecki
2011-11-04 20:32 ` Greg KH
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=4EB2AF44.7090102@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=roman-vl@meta.ua \
/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).