OpenWrt Forum Archive

Topic: Problems with brcm47xx-2.6 on Asus WL-500G Premium and ipw2200 minipci

The content of this topic has been archived on 27 Feb 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,
As an owner of an asus wl-500g premium and tired to be stuck with a 2.4 kernel I tried to substitute the broadcom wifi device with an ipw2200 minipci.
Installed a brcm47xx-2.6 image (k 7.09) and all goes fine. Ethernet is up and running.
So I copied the necessary ipw2200 firmware (ipw2200-bss.fw) in /lib/firmware, insmod ipw2200 and.... segfault:

#---------------------#
$ dmesg
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
PCI: Fixing up device 0000:00:02.0
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Data bus error, epc == c009c4a8, ra == c00a5cfc
Oops[#1]:
Cpu 0
$ 0   : 00000000 1000d800 c00c0000 c00c0000
$ 4   : 81f08b40 00000024 00000001 000000fa
$ 8   : 00000000 800ff4b0 c00c0024 40000000
$12   : 80270000 81873a33 ffffffff 00000000
$16   : 81259000 c00b8730 81f08b40 81f08000
$20   : 81f08b40 81055000 c0105000 c0105010
$24   : 00000000 00000000
$28   : 81872000 81873bb0 00000003 c00a5cfc
Hi    : ecd021c3
Lo    : af603183
epc   : c009c4a8     Tainted: P
ra    : c00a5cfc Status: 1000d803    KERNEL EXL IE
Cause : 0000001c
PrId  : 00029006
Modules linked in: ipw2200 ath_pci wlan_xauth wlan_wep wlan_tkip wlan_ccmp wlan_acl ath_rate_minstrel ath_hal(P) wlan_scan_sta wlan_scan_ap wlan ppp_async ppp_generic slhc crc_ccitt ieee80211_crypt_ccmp ieee80211_crypt_tkip ieee80211_crypt_wep ieee80211 ieee80211_crypt switch_robo switch_core diag
Process insmod (pid: 685, threadinfo=81872000, task=802b3000)
Stack : 00000006 8181bd80 81873c00 c00b9ac0 0000009c 8181bd80 812d5332 8181bd80
        00000006 800b6294 80222f62 00000000 8181bd00 c00b6f54 81873c00 8004ac0c
        1000d801 81055000 00000044 c00b9ac0 c010a916 c0106950 81f08b40 81f08b40
        81f08b40 81f08000 80200000 81055000 810550b0 00000000 0000028c c00a6e30
        0000000a ffffffff ffffffff 00000002 81873c9c 80240740 8181e000 81f08000
        ...
Call Trace:[<800b6294>][<8004ac0c>][<c00a6e30>][<c00b00a4>][<801601ac>][<80048bb0>][<8015dfb8>][<80160218>][<c00b1674>][<c00b0ff8>][<800bce10>][<8008c7e0>][<c007129c>][<8010ed2c>][<8012c2a4>][<801f7f5c>][<800bd85c>][<8012c714>][<8012af2c>][<800f9570>][<8012c5ac>][<8012b098>][<c007129c>][<8012b4b8>][<8010ef44>][<80023454>][<c00bd058>][<80047898>][<8000bc60>]

Code: 00455021  3c0c8027  3c0b4000 <8d420000> 00461024  10460011  8d830d60  24050009  356400b0
#---------------------------#

Same results with Kamikaze 7.07.
Is this a known issue? What can I do?

thanks,
GOo

I see a similar kernel panic if I connect a D-Link DWL-G122 USB wireless adapter (with rt73 chipset/driver, rt2x00 package) to my 500g Premium.

Seems many things are broken in trunk...

(Last edited by forum2006 on 24 Nov 2007, 16:39)

Have you tried svn later than #9285 that fixed random segfaults? It really made a difference in my box compared to 7.09.

I have also been able run original broadcom wifi with b43 driver. It seem to work at least in sta mode. Only weiredness is that I need leave ping going out, otherwise after a while of idle wlan you can not access it over wlan.

The discussion might have continued from here.