Linked by Thom Holwerda on Wed 19th Jul 2006 21:16 UTC
Thread beginning with comment 144883
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-24
If you are running a broadcom chipset and were using ndiswrapper, you simply have to blacklist the bcm43xx module in /etc/modprobe.d/blacklists
The presence of the native driver will foil your ndiswrapper attempts. It's good that they are pushing for native drivers, but most people still seem to like the ndiswrapper method with that chipset.
See this thread on the Ubuntu forums for more info, and a nice script that does everything necessary including setting up ndiswrapper.
http://www.ubuntuforums.org/showthread.php?t=197102&highlight=bcm43...