[Voyage-linux] Adding Broadcom 4318 Wireless card to Alix board

Frank Parker (spam-protected)
Sun Apr 19 20:56:11 HKT 2009


Punky, Thanks for the pointer.  My card is 4318 and needs the b43
driver, as shown on that page.

voyage:~# lspci -vnn | grep 14e4
00:0c.0 Network controller [0280]: Broadcom Corporation BCM4318
[AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev
02)

As you can see from my posts below, the b43 driver was installed with
"apt-get install b43-fwcutter" and dmesg seems to show the b43 driver
loading successfully at boot time (i think).

-parker


On Sun, Apr 19, 2009 at 2:26 AM, Punky Tse <punkytse at punknix.com> wrote:
> Frank,
>
> May be here can give you some information:
>   http://linuxwireless.org/en/users/Drivers/b43
>
> Does the firmware version not match?
>
> Regards,
> Punky
>
>
> Frank Parker wrote:
>>
>> I also notice this in dmesg:
>>
>> voyage:~# grep -i -e "b43" -e "broadcom" -e "wlan" /var/log/dmesg
>> b43-phy0: Broadcom 4318 WLAN found
>> Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
>> input: b43-phy0 as /class/input/input1
>> firmware: requesting b43/ucode5.fw
>> firmware: requesting b43/pcm5.fw
>> firmware: requesting b43/b0g0initvals5.fw
>> firmware: requesting b43/b0g0bsinitvals5.fw
>> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
>> Registered led device: b43-phy0::tx
>> Registered led device: b43-phy0::rx
>> Registered led device: b43-phy0::assoc
>> Registered led device: b43-phy0::radio
>> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>
>>
>> -parker
>>
>>
>>
>> On Sat, Apr 18, 2009 at 9:09 PM, Frank Parker <mr.frank.parker at gmail.com>
>> wrote:
>>
>>>
>>> Sean, thanks for the quick reply.  I've read the README, but I think
>>> the problem is here:
>>>
>>> voyage:~# iwconfig wlan0 essid OpenWifi mode Master
>>> Error for wireless request "Set Mode" (8B06) :
>>>   SET failed on device wlan0 ; Invalid argument.
>>>
>>> It will only accept "mode Ad-Hoc" or "mode Managed".
>>>
>>> I did "apt-get install install b43-fwcutter" and the kernel module is
>>> inserted.
>>>
>>> voyage:~# lspci | grep Broadcom
>>> 00:0c.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
>>> 54g] 802.11g Wireless LAN Controller (rev 02)
>>>
>>> voyage:~# lsmod | grep b43
>>> b43                   109212  0
>>> rfkill                  4756  2 rfkill_input,b43
>>> rng_core                3588  2 b43,geode_rng
>>> mac80211              114448  1 b43
>>> led_class               3332  2 leds_alix,b43
>>> input_polldev           3208  1 b43
>>> ssb                    30852  1 b43
>>> pcmcia                 27892  2 b43,ssb
>>> pcmcia_core            28176  3 b43,ssb,pcmcia
>>>
>>>
>>> Anyone know what I am missing here?
>>>
>>> -parker
>>>
>>>
>>>
>>> On Sat, Apr 18, 2009 at 7:30 PM, Sean <knife at toaster.net> wrote:
>>>
>>>>
>>>> You would need to at least do this:
>>>>
>>>> iwconfig wlan0 essid OpenWifi mode Master
>>>>
>>>> Master mode starts the access point functionality.
>>>>
>>>> You should read the readme. It has lots of good info on how to set it up
>>>> as
>>>> an access point, bridging, etc.
>>>>
>>>>
>>>> http://svn.voyage.hk/repos/voyage/branches/voyage-live/0.6.1/config/chroot_local-includes/README
>>>>
>>>> Sean
>>>>
>>>> Frank Parker wrote:
>>>>
>>>>>
>>>>> Apologies for the simple question.  I have searched for hours and read
>>>>> a lot of confusing documentation, but I'm afraid I still need help
>>>>> with this.
>>>>>
>>>>> I am adding a Broadcom 4319 Min-PCI wireless card to my ALIX 2D3 board.
>>>>>
>>>>> voyage:~# dmesg | grep -i broadcom
>>>>> b43-phy0: Broadcom 4318 WLAN found
>>>>> Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
>>>>>
>>>>> Can someone point to the proper directions for configuration?
>>>>>
>>>>> Requirements:
>>>>>
>>>>> 1) This device needs to be an open Access Point, no encryption.
>>>>> 2) wlan0, eth1, eth2 should be configured as a bridge.
>>>>> 3) eth0 is already configured as the WAN uplink.
>>>>>
>>>>> I did "ifconfig wlan0 up" followed by "iwconfig wlan essid OpenWifi"
>>>>> but it doesn't appear to be sending any signal (signal level 0).
>>>>>
>>>>> voyage:~# iwconfig wlan0
>>>>> wlan0     IEEE 802.11  ESSID:"OpenWifi"
>>>>>         Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
>>>>>         Tx-Power=20 dBm
>>>>>         Retry min limit:7   RTS thr:off   Fragment thr=2352 B
>>>>>         Encryption key:off
>>>>>         Link Quality:0  Signal level:0  Noise level:0
>>>>>         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>>>>         Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> -parker
>>>>>
>>>>> _______________________________________________
>>>>> Voyage-linux mailing list
>>>>> Voyage-linux at list.voyage.hk
>>>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Voyage-linux mailing list
>>>> Voyage-linux at list.voyage.hk
>>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>>>
>>>>
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
>
>




More information about the Voyage-linux mailing list