On Wednesday 01 August 2007 18:19:59 Andrig T. Miller wrote: > I have been playing with the bcm43xx driver since the beginning, and I > thought I would post what I now see under Fedora 7. > > First, Fedora seems to only have the bcm43xx-mac80211 driver now, and so I > am using the v4 firmware from the link you guys have provided. > > The driver loads, and here is what I get in dmesg: > > 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: Switching to ChipCommon core, index 0 > ssb: Switching to PCI core, index 2 > ssb: Sonics Silicon Backplane found on PCI device 0000:06:02.0 > bcm43xx-phy0: Broadcom 4318 WLAN found > ssb: Switching to IEEE 802.11 core, index 1 > bcm43xx-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7 > bcm43xx-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 > bcm43xx-phy0 debug: Radio turned off > wmaster0: Selected rate control algorithm 'simple' > > ifconfig reports the following: > > wlan0 Link encap:Ethernet HWaddr 00:14:A5:B2:AF:40 > inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::214:a5ff:feb2:af40/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1684 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1648 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:702701 (686.2 KiB) TX bytes:395884 (386.6 KiB) > > wmaster0 Link encap:UNSPEC HWaddr > 00-14-A5-B2-AF-40-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) > > iwconfig reports the following: > > wmaster0 no wireless extensions. > > wlan0 IEEE 802.11g ESSID:"NetGearAndrigAtHome" > Mode:Managed Frequency:2.462 GHz Access Point: > 00:09:5B:B8:BD:75 > Bit Rate=1 Mb/s > Retry min limit:7 RTS thr:off Fragment thr=2346 B > Encryption > key:C61C-1152-BB6D-7512-45B7-F4FA-0165-E96D-8D7B-5920-B634-7DA7-B8EA-991C-14C2-193F > [2] > Link Quality=106/100 Signal level=-38 dBm Noise level=-73 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > iwlist wlan0 scanning reports: > > Cell 02 - Address: 00:09:5B:B8:BD:75 > ESSID:"NetGearAndrigAtHome" > Mode:Master > Channel:11 > Frequency:2.462 GHz (Channel 11) > Quality=37/100 Signal level=-46 dBm Noise level=-72 > dBm > Encryption key:on > IE: WPA Version 1 > Group Cipher : TKIP > Pairwise Ciphers (1) : TKIP > Authentication Suites (1) : PSK > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s > 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s > 48 Mb/s; 54 Mb/s > Extra:tsf=000000000084cc27 > > I left out my neighbors access point, but this shows mine, and I am > successfully connnecting with WPA Personal. > > The performance is very poor, as it is only connecting at 1 Mb/s, and the > signal strength varies wildly between around 30% to 100% at times. Also, > NetworkManager reports that the driver is bcm43xx-pci, if you look at the > connection information. Not sure what that means, but lsmod reports the > following: > > lsmod | grep bcm > bcm43xx_mac80211 417697 0 > ssb 43461 1 bcm43xx_mac80211 > mac80211 165705 2 rc80211_simple,bcm43xx_mac80211 > > So, in short the driver is working, but the bitrate is very low, and it > makes using it nearly impossible. If there is other information I can > provide that would be helpful in improving this, please let me know, and I > will carve out some time to collect it for you. > > By the way, thanks for all the hard work on the driver. It is really > getting better, and if I can get the performance issue solved, I would be > using it instead of my additional PCMCIA card with the Atheros chip set.
That's a known bug and I am currently trying to find out why it fails to tune the power to higher levels. Even adjusting power manually doesn't have any effect. So it's not a bug in the power scaling algorithm, but deeper in the attenuation adjustment. Might be some broken table upload. -- Greetings Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
