Please don't misunderstand the following comments. I am not disparaging the great work done by the bcm43xx team, but the fact is that a reverse engineered driver will never be as good as a driver for which the original source code or specs are released by the manufacturer. I mostly lurk on this list because my linksys routers all use broadcom chips and there is no easy way to replace them. When given a choice of 802.11g cards to purchase for general-purpose use I always go with cards that have Ralink chipsets. Ralink is a taiwanese manufacturer who releases their driver source code under the GPL, and is the only company that I am aware of that does so. As a result, support for their chips in Linux is just superb; I use the in-kernel driver and it consistently works perfectly. I have a g MIMO card that "just works" right OOB (when firmware is installed) and I just can't sing Ralink's praises enough. If you want a card that will work perfectly in all situations, go with a card that has a Ralink chipset.
On Sun, Jun 22, 2008 at 11:08 AM, Larry Finger <[EMAIL PROTECTED]> wrote: > Age Jan (John) Stap wrote: >> Hi Larry, >> >> Thanks for your input. >> >> Suggesting I go with Suze 11, is not the way I want. I have worked with >> all of them over the last three years (must have thrown away 100 plus >> live and install cd's). I want Debian and may have to die before I find >> my solution but so be it. >> >> Even though I removed NDISWRAPPER from the box (or so I thought!) I do >> notice that on the wireless properties in the network manager I still >> find ndiswrapper as the driver although the fw-cutter/broadcom 43 have >> been installed the latest..... >> >> Any suggestions on how to go about removing ndiswrapper completely? > > Please do not drop the CC to the list. This discussion may be useful > to someone else. > > To get rid of ndiswrapper, you could either unload the Windows driver > from ndiswrapper, or do the following: > > sudo echo "blacklist ndiswrapper" >> /etc/modprobe.d/blacklist > > I don't understand your need to stay with Debian, but that is your > choice. On average, I probably generate at least one new kernel per > day, and update kernel modules even more frequently. Having to go > through the steps required to generate a .deb and installing it for > every change would take 3-4 hours away from my productivity. > > Larry > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
