| Hangdog42 |
09-20-2007 02:47 PM |
Quote:
ndiswrapper -l
bcmwl5 : driver installed
device (14E4:4318) present (alternate driver: ssb)
so ssb is the mod that I need to take out and then need to make sure that ndiswrapper is put in.
|
If you've blacklisted b43/ssb, then no, you don't have to do anything else. That message from ndiswrapper -l is a little misleading, it only means that an alternate driver exists, not that it is loaded.
Quote:
nothing happens when I run modprobe ndiswrapper it just goes back to a prompt.
|
Actually, that's good. Modprobe only gives feedback when something goes wrong. If it all worked, then it is silent.
Quote:
When I ran 'rmmod ssb' I got ERROR: Module ssb does not exist in /proc/modules. I am slowly learning the command line as I go along but I thought I issued the right command to remove the alternate driver.
|
That should have deleted the module. Maybe you ran it already? However, as long as ssb doesn't load (check lsmod to be sure) you don't have to worry about it. I've got both ndiswrapper and bcm43xx on my laptop, but I only use one at a time.
Quote:
not sure what happened but it works now.
|
Congrats!
Quote:
tried connecting to my offices' wireless network with the shared key enabled and put in the network key but it wouldn't let me on.
|
Are we talking WEP, WPA or what here? How did you enable the key?
Quote:
My only question is do I have to do the 'modprobe ndiswrapper' everytime I boot my machine up and want to use my wireless card?
|
Yup, you do. There are a couple of ways to automate this however. Check out this post by Lenard. I know he is a CentOS user, so this is probably better than anything I'll come up with. |
