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:
>
> 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.
[...]
> $ sudo iwlist eth1 scan
> eth1 No scan results
> $ sudo rmmod bcm43xx
> $ sudo modprobe ndiswrapper
> $ sudo iwlist wlan0 scan
> wlan0 Scan completed :
> Cell 01 - Address: *
> ESSID:"*"
> ...
> Cell 02 - Address: *
> ESSID:"*"
> ...
> Cell 03 - Address: *
> ESSID:"*"
> ...
> $
>
> (yes, ndiswrapper sees it as wlan0, bcm43xx as eth1)
>
> I believe that the reason is that bcm43xx doesn't correctly recognize the MAC
> address:
>
> bcm43xx -> 00:00:00:AA:BB:CC
> ndiswrapper -> 00:AA:BB:CC:*:*
>
> (masking the address ;) )
>
> It seems like bcm43xx is "shifting" the MAC address of two bytes :s. Any idea?
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...
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".
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
