linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: lina <lina.lastname@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Debian Lists" <debian-user@lists.debian.org>,
	Camaleón <noelamac@gmail.com>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: Re: bcm4331 firmware installer package
Date: Wed, 21 Dec 2011 18:38:11 +0100	[thread overview]
Message-ID: <4EF21983.1020107@broadcom.com> (raw)
In-Reply-To: <CAG9cJm=YkvHY56LoBoUf3fuh=xb7m+c0GgUzMZX+QyG1+CBCMg@mail.gmail.com>

On 12/21/2011 11:59 AM, lina wrote:
> Hi,
> 
> I don't know which one (else) can be fit for bcm4331 802.11a/b/g/n (rev 02)
> 
> From http://wiki.debian.org/bcm43xx#b43_and_b43legacy
> 
> I tried:
> 
> 1] aptitude install firmware-b43-lpphy-installer
> 
> No chroot environment found. Starting normal installation
> No supported card found.
> Use proper b43 or b43legacy firmware.
> Aborting.
> 
> 2] # aptitude install firmware-b43-installer
> 
> No chroot environment found. Starting normal installation
> Unsupported device(s) found: PCI id 14e4:4331
> Aborting.
> 
> both of the listed are not working,
>

The bcm4331 support in b43 is pretty new so I do not expect distros are
providing packages for it. Your best bet is to get linux-firmware repo
from git.kernel.org. Probably the b43 developers can point you to the
specific firmware file you need to use for that phy.

> [29546.428819] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 9, Type
> 7, Revision 1)

Gr. AvS


  reply	other threads:[~2011-12-21 17:38 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 [this message]
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                   ` 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=4EF21983.1020107@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=debian-user@lists.debian.org \
    --cc=lina.lastname@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=noelamac@gmail.com \
    /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).