OpenWrt Forum Archive

Topic: no broadcom wireless with current Kamikaze?

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

With current Kamikaze (svn revision 6850, as of 03-Apr-2007), wireless doesn't work, at least on ASUS WL-500g Deluxe.

Is it known, is there a workaround, bug report etc.?

# lsmod
Module                  Size  Used by
bcm43xx               423280  0
ieee80211softmac       24672  1 bcm43xx
ieee80211              26464  2 bcm43xx,ieee80211softmac
ieee80211_crypt         2624  1 ieee80211

# lspci
00:00.0 Host bridge: Broadcom Corporation BCM5365P Sentry5 Host Bridge
00:02.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:02.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)


# lspci -v
(...)
00:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
        Subsystem: Broadcom Corporation Unknown device 120f
        Flags: fast devsel, IRQ 5
        Memory at 40000000 (32-bit, non-prefetchable) [disabled] [size=8K]
        Capabilities: [40] Power Management version 2

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:15:F2:6A:E8:34
          inet addr:192.168.10.55  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3111 (3.0 KiB)  TX bytes:0 (0.0 b)
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2876 (2.8 KiB)  TX bytes:2876 (2.8 KiB)

# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

(Last edited by mangoo on 3 Apr 2007, 20:37)

use broadcom 2.4 instead of 2.6, wireless is not yet working on 2.6.

It used to work with the old broadcom code though - well, sometimes, on some devices at least smile

Unfortunately, I need some 2.6 features not present in 2.4.

then you are going to have to wait for the broadcom 2.6 branch to mature.

BTW - is there a bug/ticket open for that? So that I could "trace the progress" - instead of asking on the list every two weeks? smile

I tried to find it on trac, but I'm not sure if that's the right one (it's "closed"):

https://dev.openwrt.org/ticket/1247

(Last edited by mangoo on 3 Apr 2007, 20:52)

Well, any update on this subject?

A lot of updated wireless drivers (including the "mac80211" stack) are scheduled for inclusion in the mainstream kernel as of version 2.6.22

To this end I have started work on the patches required to move to this version, as and when it's ready. However, the kamikaze trunk has just been moved to 2.6.21.1, and it will stay there for a while whilst it stabilises, and all the platforms are made to build, before it's moved on again. (In all likelihood)

Caveat: I don't yet understand the differences between the "softmac" and the "mac80211" stacks, and which drivers they affect, so others will be able to give a better description of the current status.

So, it'll be a while, but if you can lend a hand getting the current 2.6.21.1 stable on any more platforms, it might be sooner.

Hi.

I apologize for bringing such an old thread back from the dead, but i couldnt find anything more crrent.
has the new mac80211 stack been incorporated into openwrt kamikaze yet ?

I've been running whiterussian on my wrt54gl for the past year and a half and am considering an upgrade, but i dont know if my wireless will function properly with the broadcom-2.6 version.

The discussion might have continued from here.