Larry Finger wrote:
> Andrig T. Miller wrote:
>   
>> I booted a new Fedora kernel this morning, and it loaded the new b43 
>> driver, and I still had the v4 firmware in /lib/firmware.  The first 
>> time I connected it connected at 2 Mb/s, versus the 1 Mb/s that it used 
>> to connect at.  I had needed to reboot a second time for an unrelated 
>> reason, and when it connected the next time I connected at 5 Mb/s, and I 
>> have been happily using my internal Broadcom 4318 wireless networking 
>> all day, without issue.
>>
>> Thanks for all the hard work, it is really paying off!
>>     
>
> It is connecting at 1 Mbs every time, the increases are the natural ramp-up 
> of the rates. Why it 
> differed from boot to boot is probably a matter of when you happened to check 
> and how many 
> transmissions happened before you looked.
>
> If your V4 firmware is still in /lib/firmware, then the Fedora kernel is a 
> little behind the 
> wireless-dev tree. Once the code that uses the new naming scheme hits their 
> kernel, your wireless 
> will probably stop working. Be prepared.
>
> Yes, the new driver is very solid.
>
> Larry
> _______________________________________________
> Bcm43xx-dev mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
>
>
>   
It's not that 'solid' on my chipset, at least not the one present in the 
Fedora kernel. I have a BCM4309 14e4:4324 (rev 02) chipset and it drops 
connection from time to time with this driver.

It connects fine at 1Mbps, really quick link establishment, but maybe 
half an hour later it drops and reconnects again. There are lots of 
messages in the kernel log, I'm including here what I think is useful:

this is what I get when it first initialises:

b43-phy1: Broadcom 4306 WLAN found
b43-phy1 debug: Found PHY: Analog 1, Type 2, Revision 1
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy1 debug: Radio turned off
wmaster0: Selected rate control algorithm 'simple'
b43-phy1 debug: Ignoring unconnected 802.11 core
b43-phy1 debug: Adding Interface type 2
b43-phy1 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy1 debug: Radio turned on
b43-phy1 debug: Radio enabled by hardware
b43-phy1 ERROR: bbatt(11) >= size of LO array
b43-phy1 debug: Chip initialized
b43-phy1 debug: 30-bit DMA initialized
b43-wlan: TODO: Incomplete code in keymac_write() at 
drivers/net/wireless/b43/main
.c:753 *<---- repeated several times*
b43-phy1 debug: Wireless interface started
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:30:bd:fe:23:83
wlan0: RX authentication from 00:30:bd:fe:23:83 (alg=0 transaction=2 
status=0)
wlan0: authenticated
wlan0: associate with AP 00:30:bd:fe:23:83
wlan0: RX AssocResp from 00:30:bd:fe:23:83 (capab=0x411 status=0 aid=10)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:30:bd:fe:23:83)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

when it drops connection I get the following messages in dmesg:

wlan0: No ProbeResp from current AP 00:30:bd:fe:23:83 - assume out of range
b43-phy1 debug: Using software based encryption for keyidx: 0, mac: 
00:30:bd:fe:23
:83
wlan0: No STA entry for own AP 00:30:bd:fe:23:83
wlan0: No STA entry for own AP 00:30:bd:fe:23:83
wlan0: No STA entry for own AP 00:30:bd:fe:23:83
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
b43-phy1 debug: Removing Interface type 2
b43-phy1 ERROR: MAC suspend failed
b43-phy1 debug: Wireless interface stopped
b43-phy1 debug: DMA-32 0x0260 (RX) max used slots: 1/64
b43-phy1 debug: DMA-32 0x0200 (RX) max used slots: 2/64
b43-phy1 debug: DMA-32 0x02A0 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0280 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0260 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0240 (TX) max used slots: 0/128
b43-phy1 debug: DMA-32 0x0220 (TX) max used slots: 92/128
b43-phy1 debug: DMA-32 0x0200 (TX) max used slots: 0/128
b43-phy1 debug: Radio turned off
b43-phy1 debug: Radio turned off
b43-phy1 debug: Adding Interface type 2

this is the link quality info:
Bit Rate=1 Mb/s
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Link Quality=73/100 Signal level=-56 dBm Noise level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

is the SNR low? Is that why it drops the connection ? The router sits 3 
meters away from my laptop, direct sight.


thanks
-Ioannis



_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to