From: lina <lina.lastname@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Debian Lists <debian-user@lists.debian.org>,
"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: Re: bcm4331 firmware installer package
Date: Thu, 22 Dec 2011 15:47:39 +0800 [thread overview]
Message-ID: <CAG9cJmmnEsLQxxbi41v6nM8D+L_cOSQE73qJmDDYhXPnopn+MA@mail.gmail.com> (raw)
In-Reply-To: <CACna6rxvmFptSR9WF8Whj1A0ATyygQ9Eo0nUY8n6MugQ0bjP7g@mail.gmail.com>
On Thu, Dec 22, 2011 at 3:07 PM, Rafał Miłecki <zajec5@gmail.com> wrote:
> 2011/12/22 lina <lina.lastname@gmail.com>:
>> I am still a bit confused. (First thanks for the links all of you
>> provided, but I have visited those web before).
>>
>> Here is the thing:
>> BCM4331 802.11a/b/g/n fit for
>> BCM4331 b/g HT (r1)
>>
>> What does the 802.11a for?
>
> Well, your card can operate in 5GHz band (frequencies). But I'm not
> really sure why you ask about this at all.
>
> If you want to try experimental BCM4331 support you have to:
> 1) Install kernel 3.2-rc3 or newer
I have the 3.2.0-rc6
> or
> 2) Install compat wireless
>
> After that you've do install firmware (check for wiki howto for kernel
> 3.2 and newer).
after installation of the compat-wireless,
from
http://wireless.kernel.org/en/users/Drivers/b43#firmware
# aptitude install firmware-b43-installer
Setting up b43-fwcutter (1:015-9) ...
Setting up firmware-b43-installer (1:015-9) ...
No chroot environment found. Starting normal installation
Unsupported device(s) found: PCI id 14e4:4331
Aborting.
I don't know which part is wrong here.
Thanks
>
> P.S.
> Please, don't top post.
>
> --
> Rafał
next prev parent reply other threads:[~2011-12-22 7:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 10:59 bcm4331 firmware installer package lina
2011-12-21 17:38 ` Arend van Spriel
2011-12-21 18:52 ` Rafał Miłecki
2011-12-22 6:57 ` lina
2011-12-22 7:07 ` Rafał Miłecki
2011-12-22 7:47 ` lina [this message]
2011-12-22 7:57 ` lina
2011-12-22 8:09 ` lina
2011-12-22 8:34 ` Rafał Miłecki
2011-12-22 8:45 ` lina
2011-12-22 8:49 ` Rafał Miłecki
2011-12-22 8:57 ` lina
2011-12-22 9:09 ` lina
[not found] ` <CANDQx1q8cZC8Qz366ET3XQrpAeVJDiurFFiR1NUQ6G0b_ASoZA@mail.gmail.com>
2012-01-17 20:12 ` Fwd: " Buck Golemon
2011-12-22 8:55 ` Arend van Spriel
2011-12-21 18:01 ` 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=CAG9cJmmnEsLQxxbi41v6nM8D+L_cOSQE73qJmDDYhXPnopn+MA@mail.gmail.com \
--to=lina.lastname@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=debian-user@lists.debian.org \
--cc=linux-wireless@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 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).