I suspected something was wrong a weeks ago because my light on the wireless device was orange instead of blue. I used instead of because that is how the device is addressed? I got my wireless worked finally after several attempts of the steps above. What’s really bugging me is that just last week I sftp’d perfectly fine and I was able use vpnclient to establish a VPN connection to the university. I’m not exactly sure what’s going on with your intermitency. I is Hardy Wireless! I suppose that if your linux detects and loads b43, you do need to black list it with ssb in order to use ndiswrapper.
|Date Added:||17 October 2011|
|File Size:||26.98 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I configured my wireless connection as suggested here: But I filed it under ‘low priority’ since my internet connection was working.
Grrrr, now I’m uzb the same problem. So I disabled it. I used similar kind of steps several times and finally my wireless light lits up!!
Sometimes it connects but just after lot of tries on Network Manager. I got my wireless worked finally after several attempts of the steps above.
But it is because I have chosen a wrong way due my router is configured using WPA to encryption. I also updated my kernal but from 2. I vistw not need any symbolic links as in step 2. I’m still not sure if this step is necessary but I show it anyway. However, after I have install the Ubuntu 8.
BCM4310 usb Controller using Dell xps m1530
I’m not exactly sure what’s going on with your intermitency. Local Loopback inet addr: When connected, everything goes well. The native driver “wl” loaded by OS is working under non-encrypted condition by vieta NetworkManager. I reinstalled vpnclient and I can now extablish a VPN with my university.
After you install it, you should be able to test it out by doing the following: Also, before disabling the restricted wl drivers, here’s what lshw -C network was showing: I’d like to get connected faster.
So no cable LAN with the fix above, usn that’s ok for me. I had try many time to using different method encryption but with no joy. I used instead of because that is how the device is addressed? Do you have a clue about what I can do to improve it?
To continue using , please upgrade your browser.
Reboot and now I can sftp and ssh to my university. In addition, sometimes the network connection seems cannot build.
In my case Dell Latitude L the ssb black list only works if b44 is blacklisted also, that’s the regular ethernet card, and b44 calls for ssb. I’m going to reinstall vpnclient and verify.
First of all I’m a complete noob to linux so perhaps someone more knowledgable than I can do a better write up of the hack. However this thread at the end shows how to remove ndiswrapper and compile a new version which I ended up doing.
I’ve tried lot of issues found on web I’m a begginer: But last week July 17, I updated my kernel, wich now is 2. My wireless was still not working: I will try using ndiswrapper with bcmwl5 and remove wl to test encrypted communication. I suppose that if your linux vistta and loads b43, you do need to black list it with ssb in order to use ndiswrapper. I am not pretty sure which method worked: