Pavel Roskin wrote: > On Mon, 2007-04-09 at 17:52 -0700, Ehud Gavron wrote: >> Removed module.symvers. Make; make install. rmmod bcm43xx hung (yes I >> forgot to ifconfig down ;) reboot... module now works perfectly. > > This means that you already have CONFIG_BCM43XX_DEBUG defined > in .config, right? I guess you had to recompile the kernel anyway, or > at least reconfigure it. That's not how a _standalone_ driver should > work, in my opinion.
That was a typo. >> I am unable to see the behavior I saw before: namely ifconfig rxcount >> goes to 0, txcount goes low, radio off, radio on, rxcount+, txcount+++, >> dhcp works, give it a second, down again. repeats. >> >> Right now what I'm seeing is a perfectly working system. I have moved >> different APs within the same ESSID (WEP enabled) and no problems are >> evident. >> I'm getting TCP throughput of 7Mbps (on my Comcast 6Mbps link) and I >> haven't configured any in-LAN testing facilities (yet. The night is young.) > > Yes, the current bcm43xx is pretty good at data transfer. And it > doesn't crash my Mac anymore, even though I put my oldest card there, > just to make things harder. And it works with a bizarre Linksys AP to > which bcm43xx_mac80211 won't connect. Do you think that is a Linksys AP problem? I cannot get mac80211 to connect to my WRT54G V5 AP? > Just be careful with rates of 48 and 54 Mbps, they are still unstable. > The default 24 Mbps is a good default for me. The sweet spot for my 4311 is at 36 Mbs, but 24 is better for most cards. That is why it is the default. Larry _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
