From: Buck Golemon <buck@yelp.com>
To: unlisted-recipients:; (no To-header on input)
Cc: lina <lina.lastname@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
Debian Lists <debian-user@lists.debian.org>
Subject: Fwd: bcm4331 firmware installer package
Date: Tue, 17 Jan 2012 12:12:13 -0800 [thread overview]
Message-ID: <CANDQx1oD301Ltd6M3V86Smerp_qcBPrL0ncVb9jtrRpik8pcsA@mail.gmail.com> (raw)
In-Reply-To: <CANDQx1q8cZC8Qz366ET3XQrpAeVJDiurFFiR1NUQ6G0b_ASoZA@mail.gmail.com>
2011/12/22 Rafał Miłecki <zajec5@gmail.com>
>
> W dniu 22 grudnia 2011 09:45 użytkownik lina <lina.lastname@gmail.com> napisał:
> > On Thu, Dec 22, 2011 at 4:34 PM, Rafał Miłecki <zajec5@gmail.com> wrote:
> >> 2011/12/22 lina <lina.lastname@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.
> >>
> >> Your tool is too old (support for BCM4331 is really recent).
> > sorry, here you mean, which tool?
> >>
> >> Just do as I said and use howto for kernel 3.2, not distro-specific
> >> howto. You nede to install b43-fwcutter and manually download file for
> > I can't tell the difference. (I really need detailed instructions,
> > thanks for your patience ahead)
> >
> > I tried to follow what you said before, with the kernel 3.2-rc6
> > install the compate-wireless,
> > but have problem in the following install the firmware-installer.
> >> firmware extraction.
>
> wget http://bu3sch.de/b43/fwcutter/b43-fwcutter-015.tar.bz2
> tar xjf b43-fwcutter-015.tar.bz2
> cd b43-fwcutter-015
> make
> sudo make install
> cd ..
>
> export FIRMWARE_INSTALL_DIR="/lib/firmware"
> wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
> tar xjf broadcom-wl-5.100.138.tar.bz2
> sudo b43-fwcutter -w "$FIRMWARE_INSTALL_DIR"
> broadcom-wl-5.100.138/linux/wl_apsta.o
>
Works for me! Again, this is the first time my wireless has worked!
I nominate this for inclusion on the wiki under heading "Bleeding-edge
kernel quickstart".
Thanks!
-buck
next prev parent reply other threads:[~2012-01-17 20:12 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
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 ` Buck Golemon [this message]
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=CANDQx1oD301Ltd6M3V86Smerp_qcBPrL0ncVb9jtrRpik8pcsA@mail.gmail.com \
--to=buck@yelp.com \
--cc=b43-dev@lists.infradead.org \
--cc=debian-user@lists.debian.org \
--cc=lina.lastname@gmail.com \
--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).