[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

bcm43xx support in Debian etch



Hello,

I installed a US Robotics MAXg PCI Adapter in a Debian etch machine with a 
2.6.17.12 kernel.

grieve:~# lspci -n |grep 4318
00:08.0 0280: 14e4:4318 (rev 02)
grieve:~# 
00:08.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 
802.11g Wireless LAN Controller (rev 02)

I installed bcm43xx-fwcutter which downloaded the firmware and installed it 
in /lib/firmware

grieve:~# /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh
--16:09:48--  http://svit.epfl.ch/stuff/wl_apsta.o
           => `wl_apsta.o'
Auflösen des Hostnamen »svit.epfl.ch«.... 128.178.192.9
Verbindungsaufbau zu svit.epfl.ch|128.178.192.9|:80... verbunden.
HTTP Anforderung gesendet, warte auf Antwort... 200 OK
Länge: 652.866 (638K) [text/plain]

100%[==============================================================>] 652.866      
123.00K/s    ETA 00:00

16:09:54 (121.30 KB/s) - »wl_apsta.o« gespeichert [652866/652866]

bcm43xx-fwcutter can cut the firmware out of wl_apsta.o

  filename :  wl_apsta.o
  version  :  3.130.20.0
  MD5      :  e08665c5c5b66beb9c3b2dd54aa80cb3

extracting bcm43xx_microcode2.fw ...
extracting bcm43xx_microcode4.fw ...
extracting bcm43xx_microcode5.fw ...
extracting bcm43xx_microcode11.fw ...
*****: Sorry, it's not possible to extract "bcm43xx_microcode13.fw".
*****: Extracting firmware from an old driver is bad. Choose a more recent 
one.
*****: Luckily bcm43xx driver doesn't include microcode11 uploads at the 
moment.
*****: But this can be added in the future...
extracting bcm43xx_pcm4.fw ...
extracting bcm43xx_pcm5.fw ...
extracting bcm43xx_initval01.fw ...
extracting bcm43xx_initval02.fw ...
extracting bcm43xx_initval03.fw ...
extracting bcm43xx_initval04.fw ...
extracting bcm43xx_initval05.fw ...
extracting bcm43xx_initval06.fw ...
extracting bcm43xx_initval07.fw ...
extracting bcm43xx_initval08.fw ...
extracting bcm43xx_initval09.fw ...
extracting bcm43xx_initval10.fw ...
grieve:~# 

Loading the module bcm43xx almost made it working, I can see the WLAN network 
I want to connect to (unencrypted to start with)

grieve:~# iwlist eth1 scanning
eth1      Scan completed :
          Cell 01 - Address: 00:15:0C:8E:F4:34
                    ESSID:"Herbert"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Encryption key:off
                    Bit Rates:54 Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
                    Quality=100/100  Signal level=-181 dBm
                    Extra: Last beacon: 28ms ago

But now it got tough:

-> dhcp client timed out

grieve:~# dhclient eth1
There is already a pid file /var/run/dhclient.pid with pid 5477
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:14:c1:00:9f:a5
Sending on   LPF/eth1/00:14:c1:00:9f:a5
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
grieve:~#


-> although the server works well for other devices, I tried to do a manual 
setup

I added to /etc/network/interfaces:

iface eth1 inet static
 address 192.168.2.29
 netmask 255.255.255.0
 network 192.168.2.0
 broadcast 192.168.2.255
 gateway 192.168.2.1

but ping timed out

grieve:~# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes

--- 192.168.2.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
grieve:~#


Not sure where to continue to debug here. Any hint is very welcome.




I add some information from /var/log/syslog (dumped after modprobe bcm43xx)

Oct  1 16:13:31 grieve kernel: bcm43xx driver
Oct  1 16:13:31 grieve kernel: PCI: Found IRQ 10 for device 0000:00:08.0
Oct  1 16:13:31 grieve kernel: bcm43xx: Chip ID 0x4318, rev 0x2
Oct  1 16:13:31 grieve kernel: bcm43xx: Number of cores: 4
Oct  1 16:13:31 grieve kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 
0x4243, enabled
Oct  1 16:13:31 grieve kernel: bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 
0x4243, enabled
Oct  1 16:13:31 grieve kernel: bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 
0x4243, enabled
Oct  1 16:13:31 grieve kernel: bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 
0x4243, enabled
Oct  1 16:13:31 grieve kernel: bcm43xx: PHY connected
Oct  1 16:13:31 grieve kernel: bcm43xx: Detected PHY: Version: 3, Type 2, 
Revision 7
Oct  1 16:13:31 grieve kernel: bcm43xx: Detected Radio: ID: 8205017f (Manuf: 
17f Ver: 2050 Rev: 8)
Oct  1 16:13:31 grieve kernel: bcm43xx: Radio turned off
Oct  1 16:13:31 grieve kernel: bcm43xx: Radio turned off
Oct  1 16:13:32 grieve ifplugd.agent[6596]: Invoking ifplugd for eth1
Oct  1 16:13:32 grieve ifplugd(eth1)[6606]: ifplugd 0.28 initializing.
Oct  1 16:13:32 grieve kernel: bcm43xx: PHY connected
Oct  1 16:13:32 grieve kernel: bcm43xx: Radio turned on
Oct  1 16:13:32 grieve kernel: bcm43xx: ASSERTION FAILED (radio_attenuation < 
10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm4
3xx_find_lopair()
Oct  1 16:13:32 grieve kernel: bcm43xx: WARNING: Writing invalid LOpair (low: 
48, high: 99, index: 134)
Oct  1 16:13:32 grieve kernel:  <c8c904b7> bcm43xx_phy_lo_adjust+0x256/0x27a 
[bcm43xx]  <c8c8fdfd> bcm43xx_phy_initb6+0x6d9/0x7f9 [bcm43xx
]
Oct  1 16:13:32 grieve kernel:  <c8c9105b> bcm43xx_phy_initg+0xf0/0xd56 
[bcm43xx]  <b0104fe6> do_IRQ+0x1e/0x24
Oct  1 16:13:32 grieve kernel:  <b0103592> common_interrupt+0x1a/0x20  
<b010bc46> delay_tsc+0xb/0x13
Oct  1 16:13:32 grieve kernel:  <b01b2c9d> __delay+0x9/0xa  <c8c92dcd> 
bcm43xx_phy_init+0x64f/0x671 [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <c8c83a84> bcm43xx_chip_init+0x618/0x8de 
[bcm43xx]  <c8c855f0> bcm43xx_init_board+0x3af/0xada [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <b01b28b5> vsnprintf+0x41e/0x45b  <b021d216> 
dev_open+0x2b/0x62
Oct  1 16:13:32 grieve kernel:  <b021bf8a> dev_change_flags+0x47/0xe6  
<b02545f2> devinet_ioctl+0x257/0x564
Oct  1 16:13:32 grieve kernel:  <b021409a> sock_ioctl+0x193/0x1b5  <b0213f07> 
sock_ioctl+0x0/0x1b5
Oct  1 16:13:32 grieve kernel:  <b0161e08> do_ioctl+0x1c/0x5d  <b0162093> 
vfs_ioctl+0x24a/0x25c
Oct  1 16:13:32 grieve kernel:  <b01620ed> sys_ioctl+0x48/0x5f  <b0102b4f> 
syscall_call+0x7/0xb
Oct  1 16:13:32 grieve kernel: bcm43xx: ASSERTION FAILED (radio_attenuation < 
10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm4
3xx_find_lopair()
Oct  1 16:13:32 grieve kernel: bcm43xx: WARNING: Writing invalid LOpair (low: 
48, high: 99, index: 134)
Oct  1 16:13:32 grieve kernel:  <c8c904b7> bcm43xx_phy_lo_adjust+0x256/0x27a 
[bcm43xx]  <c8c91ba4> bcm43xx_phy_initg+0xc39/0xd56 [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <c8c92dcd> bcm43xx_phy_init+0x64f/0x671 
[bcm43xx]  <c8c83a84> bcm43xx_chip_init+0x618/0x8de [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <c8c855f0> bcm43xx_init_board+0x3af/0xada 
[bcm43xx]  <b01b28b5> vsnprintf+0x41e/0x45b
Oct  1 16:13:32 grieve kernel:  <b021d216> dev_open+0x2b/0x62  <b021bf8a> 
dev_change_flags+0x47/0xe6
Oct  1 16:13:32 grieve kernel:  <b02545f2> devinet_ioctl+0x257/0x564  
<b021409a> sock_ioctl+0x193/0x1b5
Oct  1 16:13:32 grieve kernel:  <b0213f07> sock_ioctl+0x0/0x1b5  <b0161e08> 
do_ioctl+0x1c/0x5d
Oct  1 16:13:32 grieve kernel:  <b0162093> vfs_ioctl+0x24a/0x25c  <b01620ed> 
sys_ioctl+0x48/0x5f
Oct  1 16:13:32 grieve kernel:  <b0102b4f> syscall_call+0x7/0xb
Oct  1 16:13:32 grieve kernel: bcm43xx: ASSERTION FAILED (radio_attenuation < 
10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm4
3xx_find_lopair()
Oct  1 16:13:32 grieve kernel: bcm43xx: WARNING: Writing invalid LOpair (low: 
48, high: 99, index: 134)
Oct  1 16:13:32 grieve kernel:  <c8c904b7> bcm43xx_phy_lo_adjust+0x256/0x27a 
[bcm43xx]  <c8c8f03f> bcm43xx_phy_init_pctl+0x22d/0x241 [bcm4
3xx]
Oct  1 16:13:32 grieve kernel:  <c8c91c63> bcm43xx_phy_initg+0xcf8/0xd56 
[bcm43xx]  <c8c92dcd> bcm43xx_phy_init+0x64f/0x671 [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <c8c83a84> bcm43xx_chip_init+0x618/0x8de 
[bcm43xx]  <c8c855f0> bcm43xx_init_board+0x3af/0xada [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <b01b28b5> vsnprintf+0x41e/0x45b  <b021d216> 
dev_open+0x2b/0x62
Oct  1 16:13:32 grieve kernel:  <b021bf8a> dev_change_flags+0x47/0xe6  
<b02545f2> devinet_ioctl+0x257/0x564
Oct  1 16:13:32 grieve kernel:  <b021409a> sock_ioctl+0x193/0x1b5  <b0213f07> 
sock_ioctl+0x0/0x1b5
Oct  1 16:13:32 grieve kernel:  <b0161e08> do_ioctl+0x1c/0x5d  <b0162093> 
vfs_ioctl+0x24a/0x25c
Oct  1 16:13:32 grieve kernel:  <b01620ed> sys_ioctl+0x48/0x5f  <b0102b4f> 
syscall_call+0x7/0xb
Oct  1 16:13:32 grieve kernel: bcm43xx: Chip initialized
Oct  1 16:13:32 grieve kernel: bcm43xx: DMA initialized
Oct  1 16:13:32 grieve kernel: bcm43xx: 80211 cores initialized
Oct  1 16:13:32 grieve kernel: bcm43xx: Keys cleared
Oct  1 16:13:32 grieve kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  1 16:13:32 grieve kernel: bcm43xx: ASSERTION FAILED (radio_attenuation < 
10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm4
3xx_find_lopair()
Oct  1 16:13:32 grieve kernel: bcm43xx: WARNING: Writing invalid LOpair (low: 
48, high: 99, index: 134)
Oct  1 16:13:32 grieve kernel:  <c8c904b7> bcm43xx_phy_lo_adjust+0x256/0x27a 
[bcm43xx]  <c8c90c8b> bcm43xx_phy_lo_g_measure+0x7b0/0xa90 [b
cm43xx]
Oct  1 16:13:32 grieve kernel:  <c8c93030> 
bcm43xx_power_saving_ctl_bits+0x48/0x5f [bcm43xx]  <c8c82fc8> 
bcm43xx_periodic_task_handler+0xc
e/0x2bd [bcm43xx]
Oct  1 16:13:32 grieve kernel:  <c8c82efa> 
bcm43xx_periodic_task_handler+0x0/0x2bd [bcm43xx]  <b01241b1> 
run_timer_softirq+0x10b/0x153
Oct  1 16:13:32 grieve kernel:  <b0120a52> __do_softirq+0x58/0xc2  <b0120aea> 
do_softirq+0x2e/0x32
Oct  1 16:13:32 grieve kernel:  <b0104fe6> do_IRQ+0x1e/0x24  <b0103592> 
common_interrupt+0x1a/0x20
Oct  1 16:13:32 grieve kernel:  <b0271cf3> _spin_unlock_irqrestore+0x6/0x7  
<c897e6f6> ieee80211softmac_scan+0x33/0xfd [ieee80211softmac]
Oct  1 16:13:32 grieve kernel:  <b0129593> run_workqueue+0x72/0xaf  <c897e6c3> 
ieee80211softmac_scan+0x0/0xfd [ieee80211softmac]
Oct  1 16:13:32 grieve kernel:  <b0129d55> worker_thread+0x0/0x107  <b0129e2a> 
worker_thread+0xd5/0x107
Oct  1 16:13:32 grieve kernel:  <b0116f2d> default_wake_function+0x0/0xc  
<b012c1e6> kthread+0x9f/0xcb
Oct  1 16:13:32 grieve kernel:  <b012c147> kthread+0x0/0xcb  <b0101005> 
kernel_thread_helper+0x5/0xb
Oct  1 16:13:32 grieve ifplugd(eth1)[6606]: Using interface 
eth1/00:14:C1:00:9F:A5 with driver <bcm43xx> (version: 2.6.17-2-686)
Oct  1 16:13:32 grieve ifplugd(eth1)[6606]: Using detection mode: SIOCETHTOOL
Oct  1 16:13:32 grieve ifplugd(eth1)[6606]: Initialization complete, link beat 
not detected.

--
Rainer Dorsch
rdorsch@jabber.org



Reply to: