Re: [gentoo-amd64] bcm43xx setup

[Beso]

from dmesg i can see that you get no firmware error so your chip loads it
well.
from pci id and chip detection i can see that your chip is:
4306 PCI/Cardbus Supported
for what i've seen it seems that you have an amilo1650 which has an annoying
radio switch to turn on. the fsaa1655g does the trick for mine laptop. but i
think that you would use that radio switch with ndiswrapper too. if it's not
the case then i'd need to have some more info. do a dmesg > dmesg.txt and
append it. then do a cat /var/log/messages > message.txt and append it too.
it seems that there's something happening when loading the module.
the wext module is a misunderstood. i should have define it better: its not
a kernel module, but it stands for linux Wireless EXTenensions. i've called
it module doing a bad thing for you've nisunderstood. so you won't see it in
the lsmod simply because it's not a kernel module.
the wlan0 has wireless extensions but you have some problems with the core
going up. so the interface you'd use is wlan0. the problem is that bcm43xx
module fails to startup the core and keeps the wireless channel off. so we
have to first see what happens when it tries to load the module and know why
it doesn't start.
and there would also be a good thing doing a lspci and then find the slot of
your broadcom board and do a lspci -vs the slot number.
here i give you an example:
this is part of lspci output:

> 08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>
and this is lspci -vs 08:0d.0 output:

> 08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>         Subsystem: Fujitsu Siemens Computer GmbH Unknown device 10a4
>         Flags: bus master, medium devsel, latency 64, IRQ 17
>         I/O ports at a000 [size=256]
>         Memory at c0210800 (32-bit, non-prefetchable) [size=256]
>         Capabilities: [50] Power Management version 2


i'd like to know if lspci detects the same  board as does the bcm driver.
so, in conclusion: i need a full dmesg output, the kernel log, lspci verbose
on the slot of your broadcom board and to know if you have some software
wireless switch (that normally were included into fujitsu notebooks).



2007/10/11, Mark Haney <mhaney@××××××××××××.org>:
>
> Beso wrote:
> > i think that you've forgottonen to install the firmware.... remember
> that
> > you have to download the firmware (i've appended it to this email), then
> > install bcm43xx-fwcutter from portage, cut the firmware with the
> command:
> > bcm43xx-fwcutter wl_apsta.o and then copy the files with the extension
> .fw
> > that you can you'll have in the directory that contains wl_apsta.o into
> the
> > /lib/firmware directory. this directory is protected so you'll need root
> > priviledges to copy the files in there. after you've copied the .fw
> files
> > into the directory do this:
> >
> >> chmod +r+x /lib/firmware/*.fw
>
> I did have the firmware included I just neglected to mention it.  Sorry
> about that.
> >
> >
> > do a dmesg | grep bcm43xx and see if it gives you errors or similar
> things
> > and then do a iwconfig that will list all your network interfaces. now
> > search for wlan or eth interfaces and see which one of them has wireless
> > extensions. the interface that has wireless extensions is the one you're
> > searching for.
> > broadcom module uses the wext (linux wireless extensions) so if you need
> to
> > configure the wireless you'll do it through the wext module.
> >
> >
> When I look at dmesg I get this:
>
> octavian Mark # dmesg | grep bcm43xx
> bcm43xx driver
> bcm43xx: Chip ID 0x4306, rev 0x3
> bcm43xx: Number of cores: 5
> bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
> bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
> bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
> bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
> bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
> bcm43xx: PHY connected
> bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2
> bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
> bcm43xx: Radio turned off
> bcm43xx: Radio turned off
> bcm43xx driver
> bcm43xx: Chip ID 0x4306, rev 0x3
> bcm43xx: Number of cores: 5
> bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
> bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
> bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
> bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
> bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
> bcm43xx: PHY connected
> bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2
> bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
> bcm43xx: Radio turned off
> bcm43xx: Radio turned off

And when I do iwconfig I get this:
>
> octavian Mark # iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> sit0      no wireless extensions.
>
> wlan0     IEEE 802.11b/g  ESSID:off/any  Nickname:"Broadcom 4306"
>            Mode:Managed  Access Point: Invalid
>            RTS thr:off   Fragment thr:off
>            Encryption key:off
>            Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
>            Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>            Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> But when I do 'iwlist wlan0 scanning' I get:
>
> wlan0     Interface doesn't support scanning : No such device
>
> Now, you meantion the wext module, that isn't one I"m familiar with and
> one I don't have loaded.  These are the ones I /do/ have loaded relevant
> to this:
>
> bcm43xx               441888  0
> ieee80211softmac       35328  1 bcm43xx
> ieee80211              51188  2 bcm43xx,ieee80211softmac
> ieee80211_crypt         7680  1 ieee80211
>
>
> I'm obviously close, but not close enough.  Thoughts?
>
>
>
> --
> Recedite, plebes! Gero rem imperialem!
>
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> [phone]
>
> Call (866) ERC-7110 for after hours support
> --
> gentoo-amd64@g.o mailing list
>
>


-- 
dott. ing. beso