Viola!!

Thank you Gustin.  Immediately it all works.  I even learned a thing or two 
along the way.

I haven’t blacklisted the old driver yet but I'm sure that'll work fine too.



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gustin Johnson
Sent: Friday, October 05, 2007 4:29 PM
To: CLUG General
Subject: Re: [clug-talk] wireless woes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

sudo rmmod bcm43xx && sudo rmmod ndiswrapper && sudo modprobe ndiswrapper

Basically, ndiswrapper cannot be used to control the device if it is claimed by 
another driver.

To prevent the bcm43xx driver from being automatically loaded, add the 
following to your /etc/modprobe.d/blacklist file blacklist bcm43xx

I am assuming that you are running a Ubuntu variant, the blacklist procedure is 
likely different for other distros.


Andrew Anderson wrote:
> Hello all:
> 
>  
> 
> I am still trying (feverishly) to get my wireless working on my laptop.
> 
> I am trying (for starters) to connect to my AP with no security enabled.
> 
>  
> 
>  
> 
> I have a Broadcom 4306 running Ubuntu Feisty Fawn.
> 
>  
> 
> I have tried a few different ways around this I am now at the 
> following
> place:
> 
>  
> 
>                 -ndiswrapper seemed to install and configure fine.
> 
>                 -I have commented out all but the lo interface in 
> /etc/network/interfaces
> 
>                 -freshly installed network-manager-gnome
> 
>                 +rebooted and ran modprobe ndiswrapper
> 
>  
> 
>  
> 
> When I run  $sudo ndiswrapper –l
> 
> It shows me the bcmwl5 driver I installed with my device, followed by 
> ‘(alternate driver: bcm43xx)’
> 
>  
> 
> If I look at an lsmod it shows me that ndiswrapper is loaded but used 
> by 0
> 
>  
> 
> If I look at the connection information in Network Manager it shows 
> the driver for Wireless Ethernet (eth1) as bcm43xx
> 
>  
> 
>  
> 
> Am I correct in my assumption that ndiswrapper is not being used by 
> the device, and if so does anyone have suggestions on how to approach 
> the problem?
> 
> 
> ----------------------------------------------------------------------
> --
> 
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBrqqwRXgH3rKGfMRAgnvAJsE7fQJG9eNy5a/Dr4nUqsG8mUuMgCfWi5S
Cie7/iE2SI8ijadePpBeroA=
=nR+5
-----END PGP SIGNATURE-----

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying


_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to