Does someone know, wether the above mentioned Target System is working?
If yes, which revision of kamikaze did you checked out, which hardware you're using and/or which (special) settings/steps are neccesary?

Or on the other hand, who has similar problems? Are our dmesg outputs the same?

I totally stuck in that issue, since I need this combination to become the built-in bcm43xx-Wifi-Device and the zd1211-USB-Wifi-device working.

Does someone know about the broadcom-rewrite driver? It appears after selecting Advanced Configuration -> Show broken platforms/packages
The ssb-Systemboard driver doesn't compile. But that was only a try because the standard Broadcom BCM947xx/953xx [2.6] didn't work for me.

The symptoms on a compiled firmware are:
- eth1 (Asus-WL500gD Wifi-Device) is shown in iwconfig
- "ifconfig eth1 up" lets the kernel crash and the router reboots
- "iwlist scan" results in "eth1      Interface doesn't support scanning : No such device"
- dmesg | grep bcm output is
01: bcm43xx driver
02: bcm43xx: Chip ID 0x5365, rev 0x1
03: bcm43xx: Number of cores: 0
04: bcm43xx: Core 0: ID 0x800, rev 0x5, vendor 0x4243, enabled
05: bcm43xx: Error: No 80211 core found!
06: bcm43xx: Chip ID 0x4306, rev 0x3
07: bcm43xx: Number of cores: 5
08: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled
09: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled
10: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled
11: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled
12: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled
13: bcm43xx: PHY connected
14: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2
15: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
16: bcm43xx: Radio turned off
17: bcm43xx: Radio turned off
Who can explain these lines?

Thanks for help and/or developing,
Sven

(Last edited by szsoftware on 24 Jan 2007, 00:42)