Reboot and now I can sftp and ssh to my university. In addition, sometimes the network connection seems cannot build. Local Loopback inet addr: I suspected something was wrong a weeks ago because my light on the wireless device was orange instead of blue. Wait for my result.
|Date Added:||13 April 2009|
|File Size:||51.89 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
In addition, sometimes the network connection seems cannot build. So no cable LAN with the fix above, but that’s ok for me.
My wireless was still not working: Reboot and now I can sftp and ssh to my university. I chose to link my BCM device to the file pointed to by the link 14E4: In my case Dell Latitude L the ssb black list only works if b44 is blacklisted also, that’s the ush ethernet card, and b44 calls for ssb. When connected, everything goes well.
Grrrr, now I’m suspecting the same problem. Looks like the restricted wl drivers were messing that up as well. I used similar kind of steps several times and finally my wireless light lits up!!
I also updated my kernal but from 2. I’d like to get connected faster. 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.
I got my wireless worked finally after several attempts of the steps above. Cbm4310 still not sure if this step is necessary but I show it anyway.
BCM4310 usb Controller using Dell xps m1530
But last week July 17, I updated my kernel, wich now is 2. Also, before disabling the restricted wl drivers, here’s what lshw -C network was showing: I did need all the blacklists. So I disabled it. I’m not exactly sure what’s going on with your intermitency. I did not need any symbolic links as in step 2. Sometimes it connects but viwta after lot of tries on Network Manager.
Wait for my result. I used instead of because that is how the device is addressed? I had try many time to using bcm44310 method encryption but with no joy. But I filed it under ‘low priority’ since my internet connection was working.
To continue using , please upgrade your browser.
I will try using ndiswrapper with bcmwl5 and remove wl to test encrypted communication. I configured my wireless connection as suggested here: I suppose that if your linux detects and loads b43, you do need to black list it with ssb in order to use ndiswrapper. In my case there was a link 14E4: However this thread at the end shows how to remove ndiswrapper and compile a new version which I ended up doing. I am not pretty sure which method worked: However, after I have install the Ubuntu 8.
The native driver “wl” loaded by OS is working under non-encrypted condition by using NetworkManager. Local Loopback inet addr: