OpenWrt Forum Archive

Topic: What is current status of Kamikaze with 2.6 kernel on Broadcom WiFi?

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

When I tried to compile the Kamikaze (r10627) with 2.6 version of the kernel, it booted correctly until it detected the Broadcom WiFi card:

br-lan: port 1(eth0.0) entering forwarding state                                         
BFL_ENETADM not set in boardflags. Use force=1 to ignore.                                
b43-phy0: Broadcom 5354 WLAN found

Then the system hung and no other messages have been displayed via the serial console.
Is the cause of the problems associated with b43 known?
Has anybody any suggestions regarding the isolation and solving of that problem?

What is the exact difference between kmod-net-bcm43xx and kmod-b43 ?
Which one is more reliable?
Update
Maybe the previous problem was caused by the fact, taht I have compiled both b43 and bcm43xx drivers.
Now I have compiled as a module, and installed only the b43 module.
Now the system doesn't hang but reboots repetedly after detection of the Wi-Fi interface...

(Last edited by wzab on 20 Mar 2008, 22:25)

I was trying to compile the newest version of the b43.ko module (taken from http://linuxwireless.org/download/compa … .6.tar.bz2).
After some minor adjustments the code compiled cleanly, but anyway it exhibits the same behaviour.
The system reboots, no message is displayed neither on the serial console nor via the syslogd (I have run the " syslogd -l 8 -L -R 192.168.1.2:5514 -n  " after killing the original syslogd).
I have even compiled kernel with the addtional "debug=8" parameter.
Has someone any ideas how to isolate the problem?
PS. To avoid continuous rebooting, I have installed not the kmod-b43_2.6.23.16~m47xx-1_mipsel.ipk package, but only the data.tar.gz extracted from it. Then I have moved the b43.ko to the /home directory. Otherwise, after each reboot the router insmoded the b43.ko automatically and rebooted cyclically.

(Last edited by wzab on 24 Mar 2008, 00:33)

Not working. Still takes its time...

The discussion might have continued from here.