I can't get b43 to work. I did a git of b43 a few weeks ago and after I was told what rate control control algorithm (rc80211_simple). That in hand I am still having some issues. First sysfs is off but udev is changing things in funny ways. I boot the box unload all the modules mac80211, cfg80211, ssb, b43, etc. Then I modprobe rc80211_simple which loads mac80211 & cfg80211.
Here is some of my dmesg after the reload.... ACPI: PCI interrupt for device 0000:01:00.0 disabled ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LK2E] -> GSI 19 (level, high) -> IRQ 19 PCI: Setting latency timer of device 0000:01:00.0 to 64 ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x11, vendor 0x4243) ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0A, vendor 0x4243) ssb: Core 2 found: USB 1.1 Host (cc 0x817, rev 0x03, vendor 0x4243) ssb: Core 3 found: PCI-E (cc 0x820, rev 0x01, vendor 0x4243) ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0 b43-phy1: Broadcom 4311 WLAN found b43-phy1 debug: Found PHY: Analog 4, Type 2, Revision 8 b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 phy1: Selected rate control algorithm 'simple' udev: renamed network interface wmaster0 to eth1 Then I modprobe b43. udev renames the interface from wmaster0 to eth1 which I can't bring up..... SIOCSIFFLAGS: Operation not supported So that is out but I have this other interface that just appears out of no where called wlan0_rename. I can bring it up. b43-phy2 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) b43-phy2 debug: Chip initialized b43-phy2 debug: 32-bit DMA initialized input: Unspecified device as /devices/virtual/input/input7 b43-phy2 debug: Wireless interface started b43-phy2 debug: Adding Interface type 2 ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready HW CONFIG: channel=1 freq=2412 phymode=2 phy2: TX to low-level driver (len=42) FC=0x0040 DUR=0x0000 A1=ff:ff:ff:ff:ff:ff A2=00:14:a5:b7:54:15 A3=ff:ff:ff:ff:ff:ff HW CONFIG: channel=2 freq=2417 phymode=2 I can wlist wlan0_rename scan but it has issues and seems to alter eth1. Now I haven't yet tried this at a location with good signal quality. I just want to understand what is happening with the interface name(s). -- http://www.coe.neu.edu/~efoss/ http://evanfoss.googlepages.com/ _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
