The content of this topic has been archived on 22 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
On http://downloads.openwrt.org/kamikaze/7.09/release.txt it says:
brcm47xx-2.6 - Netgear WGT634U, Broadcom Devices without Broadcom wifi
(you can use this instead of brcm-2.4 but wifi won't work)
Does this mean that wireless will not work on linksys wrt54g v2 if I use brcm47xx-2.6? Must I use kernel 2.4 for wireless to work on this device?
I'm a first-time user of openwrt.
You have it exactly right. To add to the problem, even the Kamikaze 2.4 kernel version on Broadcom has much lacking that we've become accustomed in Whiterussian. Keep in mind all the firmware projects on these devices are a 2.4 kernel, too. (Someone jump in if that's wrong, please?)
I suggest anyone wanting good wireless support and functionality on Broadcom hardware (like LinkSys WRT54G/GS) go with Whiterussian. Kamikaze just isn't there yet. (You cannot even set power level without forming your own startup script).
On the other hand, Kamikaze is cutting edge into the 2.6 kernel and quite the frontier for those so inclined. The true nature of Broadcom's policies emerge going forward. I personally think Broadcom will be hurt in the long run because, frankly, their closed policies are killing efforts using their stuff.
(Last edited by Bill_MI on 19 Nov 2007, 02:11)
currently stalled at
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243)
ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:00:02.0
b43-phy2: Broadcom 4318 WLAN found
b43-phy2 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy2 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
b43-phy2 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy2: Selected rate control algorithm 'simple'
PCI: Fixing up device 0000:00:02.0
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243)
ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:00:02.0
b43-phy3: Broadcom 4318 WLAN found
b43-phy3 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy3 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
b43-phy3 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy3: Selected rate control algorithm 'simple'
b43-phy3 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy3 debug: Chip initialized
b43-phy3 debug: 32-bit DMA initialized
b43-phy3 debug: Wireless interface started
b43-phy3 debug: Adding Interface type 1
b43-phy3 debug: Removing Interface type 1
b43-phy3 debug: Wireless interface stopped
b43-phy3 debug: DMA-32 0x0200 (RX) max used slots: 0/64
b43-phy3 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0220 (TX) max used slots: 0/128
b43-phy3 debug: DMA-32 0x0200 (TX) max used slots: 0/128
root@OpenWrt:~# hostapd -dd /var/run/hostapd-wlan0.conf
Configuration file: /var/run/hostapd-wlan0.conf
Opening raw packet socket for ifindex 22
BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
Failed to set channel flag (mode=1 chan=1 flag=0x7)
Failed to set channel flag (mode=1 chan=2 flag=0x7)
Failed to set channel flag (mode=1 chan=3 flag=0x7)
Failed to set channel flag (mode=1 chan=4 flag=0x7)
Failed to set channel flag (mode=1 chan=5 flag=0x7)
Failed to set channel flag (mode=1 chan=6 flag=0x7)
Failed to set channel flag (mode=1 chan=7 flag=0x7)
Failed to set channel flag (mode=1 chan=8 flag=0x7)
Failed to set channel flag (mode=1 chan=9 flag=0x7)
Failed to set channel flag (mode=1 chan=10 flag=0x7)
Failed to set channel flag (mode=1 chan=11 flag=0x7)
Failed to set channel flag (mode=1 chan=12 flag=0x0)
Failed to set channel flag (mode=1 chan=13 flag=0x0)
Failed to set channel flag (mode=1 chan=14 flag=0x0)
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.
handle_read: too short (64)
Flushing old station entries
Could not connect to kernel driver.
Deauthenticate all stationsDidn't i read in one of these forums that the new open source driver was going to be made available soon (to be added to kernel)
You have it exactly right. To add to the problem, even the Kamikaze 2.4 kernel version on Broadcom has much lacking that we've become accustomed in Whiterussian. Keep in mind all the firmware projects on these devices are a 2.4 kernel, too. (Someone jump in if that's wrong, please?)
I suggest anyone wanting good wireless support and functionality on Broadcom hardware (like LinkSys WRT54G/GS) go with Whiterussian. Kamikaze just isn't there yet. (You cannot even set power level without forming your own startup script).
On the other hand, Kamikaze is cutting edge into the 2.6 kernel and quite the frontier for those so inclined. The true nature of Broadcom's policies emerge going forward. I personally think Broadcom will be hurt in the long run because, frankly, their closed policies are killing efforts using their stuff.
Useful info, shame about Broadcom effort or lack of it!
I've got a WRT54G v2.2 and don't need to do too much to the wireless config other than configure it as an AP. I'm unsure of whether to resort back to Whiterussian or use the 2.4 version of Kamikaze. I'm unsure as to whether the advantages of moving to kamikaze are outweighed by lack of wifi support.
Any advice or experiences appreciated.
Thanks
I've got a WRT54G v2.2 and don't need to do too much to the wireless config other than configure it as an AP. I'm unsure of whether to resort back to Whiterussian or use the 2.4 version of Kamikaze. I'm unsure as to whether the advantages of moving to kamikaze are outweighed by lack of wifi support.
As an AP, Whiterussian seems to have much more capability and much easier settings. Little things adding up like power control and multi-encryption for WPA. Kamikaze brcm2.4 can probably do lots stuff but it's not as simple as a config setting.
But I can only imagine what will break loose once the 2.6 drivers get going. I fiddled with b43/2.6 and very quickly rediscovered why I'm NOT a developer. :-)
One question: Can I now use 2.6 based kernel on my wrt54GS (v4) or I have to stay with 2.4 based whiterussian? Doc is rather hard to view (dead links) 
If you want ot be safe, stay with 2.4. But you can upgrade from whiterussian to kamikaze 8.09.1, use the brcm-2.4 branch. Or you can try current trunk and 2.6.
The discussion might have continued from here.