On Tue, 29 Jan 2008 22:40:16 +0100
Florian Kulzer <[EMAIL PROTECTED]> wrote:

> On Tue, Jan 29, 2008 at 21:20:25 +0100, David Paleino wrote:
> > Il giorno Tue, 29 Jan 2008 20:46:56 +0100 Florian Kulzer ha scritto:
> > 
> > > According to /usr/share/misc/pci.ids your chip should have the vendor-ID
> > > 0x14e4 and the prodcut-ID 0x4311. Check with "lspci -nn" if this is
> > > correct; you should see these numbers listed as "[14e4:4311]" right
> > > after the name of the card/chip. This would mean that you need the
> > > bcm43xx module if I read the kernel sources correctly. (Note: I don't
> > > have any direct experience with this particular chip/card.)
> > 
> > I've got 14e4:4312, and bcm43xx doesn't work (I'm actually using 
> > ndiswrapper).
> > I know I need to get the firmware:

Don't use bcm43xx; see below.

> > apt-get install bcm43xx-fwcutter
> > 
> > it asks if I want to fetch and extract the firmware: YES! Ok, everything's
> > in /lib/firmware now. Well:
> > 
> > $ sudo modprobe bcm43xx
> > $ ifconfig eth1
> > eth1      Link encap:Ethernet  HWaddr 00:00:00:1a:73:a5  
> >           inet addr:192.168.1.41  Bcast:192.168.1.255  Mask:255.255.255.0
> 
> [...]
> 
> > $ iwconfig eth1
> > eth1      IEEE 802.11b/g  ESSID:off/any  Nickname:"Broadcom 4311"
> >           Mode:Managed  Frequency=2.472 GHz  Access Point: Invalid   
>                                                              ^^^^^^^
> I think that this might already be a sign of trouble.

With the bcm43xx or b43 drivers, that generally means that the card is
not associated.


[snip]

> OK, it turns out that I had overlooked a few things when I wrote
in my
> previous mail.  For a start, this is in the changelog for
> 2.6.24~rc8-1~experimental.1:
> 
> * Disable bcm43xx, deprecated by upstream. Enable B43 (needs v4
>   firmware) and B43LEGACY (needs v3 firmware).
> 
> So it seems that with 2.6.24 kernel you should indeed try b43 or
> b43legacy, as the OP had stated. (When looking at the sources in a
> hurry, I mistook the SSB_* identifiers for PCI_* ones - sorry!)
> Unfortunately I have no idea how to debug this SBB bus. In any case,
> most of my previous email can safely be ignored...

b43[legacy] is the completely rewritten driver for Broadcom chips.  The
devs have been literally deprecating bcm43xx for quite a while, stating
that it is no longer developed or supported, and that everyone should
use b43[legacy] instead.

> The two b43* modules depend on the mac80211 stack instead of the
> ieee80211 one; with a self-compiled kernel and an older "inherited"
> configuration file you might first have to activate the new stack in
> "Networking > Wireless" to be able to select the b43* modules in "Device
> driver > Network device support > Wireless LAN".

The b43 devs hang out on the bcm43xx (it's still called that) ML at:
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Both dev and support work occurs there.  The devs will help, but make
sure you RTFM, cooperate with their suggestions and stay polite.

>           Florian   |

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to