Dear All,
I am using Kamikaze r6846 on my WL-500B, It can boot, but I cannot find the wireless interface eth2, there are only br-lan0, eth0 and eth1.
Can anyone has a idea to solve this? Thanks!
Alex
Topic: Kamikaze on WL-500B, Wifi cannot work!
The content of this topic has been archived on 13 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
Page 1 of 1
After I researched the dmesgs and /proc/pci. I found something different between kamikaze(wifi dont work) and whiterassuan(wifi work).
On kamikaze: cat /proc/pci
Bus 1, device 2, function 0:
Class 0280: PCI device 14e4:4301 (rev 2).
IRQ 6.
Non-prefetchable 32 bit memory at 0x40002000 [0x40003fff].On whiterassuan: cat /proc/pci
Bus 1, device 2, function 0:
Class 0280: PCI device 14e4:4301 (rev 2).
IRQ 6.
Master Capable. Latency=64.
Non-prefetchable 32 bit memory at 0x40002000 [0x40003fff].On whiteRassuan: >dmesg
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1
On Kamikaze: > dmesg
PCI: Initializing host (NOTE: I think it's a big difference!)
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Setting latency timer of device 01:00.0 to 64
PCI: Fixing up bus 1On WhiteRassaun: > dmesg:
device eth2 entered promiscuous mode
eth2: attempt to add interface with same source address.
On Kamikaze: dont have this message.Is it possible the PCI driver is initializing wrongly to cause kernel cannot find wifi card? Could anyone give me some feedbacks? Thanks!!!!!!!!!!!!!!!!!!!!!!!!!!
(Last edited by heha on 5 Apr 2007, 03:42)
if you are using the 2.6 kernel, wireless does not work on it yet, you need to use the 2.4 kernel to get wireless to work on broadcom.
Both 2.4 and 2.6 are not working. I am using KAMIKAZE (bleeding edge, r6846).
And the messages above are from 2.4.34 Kamikaze and 2.4.30 WhiteRassuan.
The discussion might have continued from here.
Page 1 of 1