OpenWrt Forum Archive

Topic: WHEN do we get kamikaze with 2.6.25 b43 for wrt54gl?!

The content of this topic has been archived between 23 Aug 2014 and 28 Apr 2018. Unfortunately there are posts – most likely complete pages – missing.

mangoo wrote:

Can b43 work in access point mode with 2.6.28?

For me it works fine, except for the above mentioned problems. If you only want to have wireless access to the internet and don't want to use any services (samba etc) that run on the router wirelessly, than it should be ok. Others might disagree on this, as some people report freezes when transferring large amounts of data wirelessly.

Forgive me if this seems like a silly question, I'm new here.

From reading this thread, I get the impression that this Kamikaze you've all been talking about is an embedded linux for a wireless router. Is that correct?

I was directed here by Pat Erley (http://wireless.erley.org/stable.html) in the hope that your patches might work for me.

In my desktop, I have a broadcom bcm4306(rev 3) PCI card that I salvaged from a dead Netcomm NB9W router. The card works fine in ad-hoc, managed and even monitor mode. I don't know what kind of radio is on the card.

My problem is that I cannot seem to get the card to work in master mode. I followed the instructions that Pat posted on his web site (above) I downloaded and installed all the software which seemed to go OK but it still doesn't work. I don't need to tell you that I need master mode to setup an AP.


When I do:

~ # hostapd -dd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=1
Opening raw packet socket for ifindex 0
BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
Allowed channel: mode=1 chan=1 freq=2412 MHz
Allowed channel: mode=1 chan=2 freq=2417 MHz
Allowed channel: mode=1 chan=3 freq=2422 MHz
Allowed channel: mode=1 chan=4 freq=2427 MHz
Allowed channel: mode=1 chan=5 freq=2432 MHz
Allowed channel: mode=1 chan=6 freq=2437 MHz
Allowed channel: mode=1 chan=7 freq=2442 MHz
Allowed channel: mode=1 chan=8 freq=2447 MHz
Allowed channel: mode=1 chan=9 freq=2452 MHz
Allowed channel: mode=1 chan=10 freq=2457 MHz
Allowed channel: mode=1 chan=11 freq=2462 MHz
Hardware does not support configured mode
wlan0: IEEE 802.11 Hardware does not support configured mode (0)
Could not select hw_mode and channel. (-1)
wlan0: Unable to setup interface.
rmdir[ctrl_interface]: No such file or directory



Which is really strange bcause:



~ # iwconfig wlan0
wlan0     IEEE 802.11bg  Mode:Master  Frequency:2.412 GHz  Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0



And:



~ # dmesg
input: b43-phy0 as /class/input/input5
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
b43-phy0 debug: Wireless interface started
b43-phy0: Radio turned on by software
b43-phy0 debug: Adding Interface type 3
b43-phy0 debug: Removing Interface type 3
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-30 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_VO: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00



Even stranger is if I then do:



~ # /etc/init.d/net.wlan0 start
* Starting wlan0
*   Configuring wireless network for wlan0
*     wlan0 connected to ESSID "Odysseus" at 00:00:00:00:00:00
*     in ad-hoc mode on channel 1 (WEP disabled)
*   Bringing up wlan0
*     12.0.1.1                                                                                                                                                                                           [ ok ]
*   Running postup function



Which puts the card back into ad-hoc mode, and then:



~ # ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:16:38:c6:b7:a8
          inet addr:12.0.1.1  Bcast:12.0.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1900 (1.8 KiB)

wmaster0  Link encap:UNSPEC  HWaddr 00-16-38-C6-B7-A8-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 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:0 (0.0 B)  TX bytes:0 (0.0 B)


The interface wmaster0 doesn't appear until AFTER I have tried to start wlan0 manually. Hostapd doesn't create this interface when I start it, nor does it start wlan0. I noticed also that wmaster0 also has a very long hardware address. Much longer than I have ever seen for any virtual device. Could this be related to the problem?
I have tried patches from several sources but none seem to do the trick. The above was generated with the unpatched kernel drivers supplied in 2.6.28. The results from patching these drivers don't differ all that much.


Any clues? Is it possible that your patches will work for me? If so, how do I go about patching the kernel drivers? Would the easiest way would be to compile Kamikaze for x86 and then copy the compiled drivers to my /lib/kernels directories? I saw that suggested two pages back.


Regards,

Ben.

PS. sorry for such a long post ;-)


System:

3.0GHz P4
1GB RAM
Broadcom BCM4306 (rev 3) PCI
Kernel-2.6.28
Kernel-headers-2.6.28-r1
libnl-1.1-r1
hostapd-0.6.6
crda-0.9.5
iw-0.9.7
compat-wireless-2009-01-11
wireless-regdb-20081117


References:

http://hostap.epitest.fi/gitweb/gitweb. … stapd.conf
http://linuxwireless.org/en/users/Drivers/b43
http://en.gentoo-wiki.com/wiki/Wireless … ur_drivers
http://www.gentoo.org/doc/en/handbook/h … amp;chap=4
http://hostap.epitest.fi/gitweb/gitweb. … icant.conf
http://wireless.erley.org/stable.html
http://wireless.erley.org/git.html
http://wireless.kernel.org/download/
http://www.gentoo-wiki.info/Broadcom_43xx
http://aircrack-ng.org/doku.php?id=mac8 … eec7a5f6da
http://johannes.sipsolutions.net/patche … ll/LATEST/
http://linuxwireless.org/en/users/Drivers/b43/faq
http://www.myscienceisbetter.info/2008/ … eless.html
http://forum.openwrt.org/viewtopic.php?id=15443&p=3

I'm trying to build Kamikaze with kernel 2.6.28, it's working fine on Linksys WRT54G2 (BCM5354 rev 3/2Mb flash), but I can't include b43/b43_legacy drivers when I do make menuconfig - it's missing in menu.
I'm select BCM47xx(2.6) and Broadcom Wi-fi target profile.

progdimon wrote:

I'm trying to build Kamikaze with kernel 2.6.28, it's working fine on Linksys WRT54G2 (BCM5354 rev 3/2Mb flash), but I can't include b43/b43_legacy drivers when I do make menuconfig - it's missing in menu.
I'm select BCM47xx(2.6) and Broadcom Wi-fi target profile.

Please see ticket #4596

Hi guys!
I have router WL-500gP V2 and I'm unable to compile openwrt. Could sb upload compiled trx file? I'm sure many peoples will appreciate his work. I can share some space in my server for this file.
Thanks in advanced.

today 4.03.2009
tested kamikaze 8.09 on wrt54gl 
http://downloads.x-wrt.org/xwrt/kamikaz … uashfs.bin

everything seemed to work .. except wireless speed was below 100kb/sec .. so I declared kamikaze 8.09 useless and returned to original linksys firmware

DeadZed wrote:

today 4.03.2009
tested kamikaze 8.09 on wrt54gl 
http://downloads.x-wrt.org/xwrt/kamikaz … uashfs.bin

everything seemed to work .. except wireless speed was below 100kb/sec .. so I declared kamikaze 8.09 useless and returned to original linksys firmware

Maybe you should try bcrm-2.4 instead... It's already been stated over and over that 2.6 kernel WiFi is not ready for production.

I wonder anyone has tried b43 in client mode lately? sbrown got a Buffalo WHR-HP-G54 running on kernel 2.6.25.4 with ~r114xx, but I couldn't get much going with recent revisions, namely r14492 (2.6.25.20) and r14917 (2.6.28.8), on my patched WHR-HP-G54 (Broadcom 5352 WLAN). Using no encryption, I don't get any activity. That's 0 Rx/Tx packets on wlan0 shown by both ifconfig and iwconfig. Anything I miss in my configs?

/etc/config/network

# VLAN configuration 
config switch eth0
        option vlan0    "1 2 3 4 5*"
        option vlan1    "0 5"

# Loopback
config interface loopback
        option ifname   "lo"
        option proto    static
        option ipaddr   127.0.0.1
        option netmask  255.0.0.0

# Wired LAN
config interface lan
        option ifname   "eth0.0"
        option proto    static
        option ipaddr   192.168.2.1
        option netmask  255.255.255.128

# Wireless WAN
config interface        wan
        option ifname   wlan0
        option proto    dhcp

/etc/config/wireless

config wifi-device wlan0
        option  type            mac80211
        option  channel         5
        option  disabled        0

config wifi-iface wan
        option  device          wlan0
        option  network         wan
        option  mode            sta
        option  ssid            WirelessISP
        option  encryption      none
        option  txpower         16

When turning on encryption,

config wifi-iface wan
        option  device          wlan0
        option  network         wan
        option  mode            sta
        option  ssid            WirelessISP
        option  encryption      8021X
        option  eap_type        PEAP TLS
        option  identity        'uuuuuuuuu'
        option  password        'ppppppppp'

I get authenticated, a bit of frozen console, and then repeated authentication, but no ip address:

Jan  1 00:03:01 OpenWrt user.debug kernel: wlan0: disassociating by local choice (reason=3)
Jan  1 00:03:03 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:03 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:03:03 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:03 OpenWrt user.debug kernel: wlan0: RX ReassocResp from aa:bb:aa:bb:aa:bb (capab=0x11 status=0 aid=250)
Jan  1 00:03:03 OpenWrt user.debug kernel: wlan0: associated
Jan  1 00:03:43 OpenWrt user.debug kernel: wlan0: disassociating by local choice (reason=3)
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: RX ReassocResp from aa:bb:aa:bb:aa:bb (capab=0x11 status=0 aid=250)
Jan  1 00:03:44 OpenWrt user.debug kernel: wlan0: associated
Jan  1 00:03:47 OpenWrt user.debug kernel: wlan0: disassociating by local choice (reason=3)
Jan  1 00:03:48 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:48 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:48 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:48 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:03:48 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:48 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:49 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:03:49 OpenWrt user.debug kernel: wlan0: RX ReassocResp from aa:bb:aa:bb:aa:bb (capab=0x11 status=0 aid=250)
Jan  1 00:03:49 OpenWrt user.debug kernel: wlan0: associated
Jan  1 00:04:57 OpenWrt user.debug kernel: wlan0: disassociating by local choice (reason=3)
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: RX ReassocResp from aa:bb:aa:bb:aa:bb (capab=0x11 status=0 aid=250)
Jan  1 00:04:58 OpenWrt user.debug kernel: wlan0: associated
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: disassociating by local choice (reason=3)
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: authenticate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: authenticated
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: associate with AP aa:bb:aa:bb:aa:bb
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: RX ReassocResp from aa:bb:aa:bb:aa:bb (capab=0x11 status=0 aid=250)
Jan  1 00:05:02 OpenWrt user.debug kernel: wlan0: associated
Jan  1 00:05:38 OpenWrt user.debug kernel: wlan0: disassociating by local choice (reason=3)

I have also tried all 3 versions/types of wireless driver in kernel 2.26.28.8 (r14917), both b43 drivers can't even get to the authenticated state. The OpenFWWF driver gets authenticated, but a "b43-phy0 ERROR: PHY transmission error" starts another round of driver firmware loading, which takes a long time (~2 minutes for each /devices/virtual/input/inputX).

What else can I try or where to look for the cause of trouble?

(Last edited by buildster on 18 Mar 2009, 21:54)

umiki wrote:
yaadgiri wrote:

If wifi is working w/ V1 then it is already a known news right? I thought V1 comes w/ Atheros - is it correct?  I want to buy V1 but  don't know where to get it. It will be really great if it works on a V2 but I hear there are some (un?)surmountable issues? Still, a good job from the developers. Keep up the good work.We appreciate it!!!

V1 has MiniPCI Broadcom 802.11b/g BCM4318 802.11 Wireless LAN Controller, while V2 has Onboard BCM5354 802.11b/g. So both of them uses B43, but the LP-PHY of V2 is not yet supported by B43, that is why V2 does not work under 2.6.

Will it work in future?

Hi. I have a WL-500gP V2 currently working with the bcrm-2.4 Kamikaze image but am interested in moving to a 2.6 kernel. Is there any update on the WLAN support in the B43 driver for the V2 ?

RCoward wrote:

Hi. I have a WL-500gP V2 currently working with the bcrm-2.4 Kamikaze image but am interested in moving to a 2.6 kernel. Is there any update on the WLAN support in the B43 driver for the V2 ?

I will let someone else answer your question. From myside, I have purchased a WIFI dongle (~15 dollars) and have wireless support with 2.6.

Hi, I have had to install the B43 diver in Ubuntu on Dell Inspiron 1525 before to get wireless to work but I cant work out how I did this any help appreciated!

(Last edited by Karcher on 22 Jun 2012, 10:05)

The discussion might have continued from here.