But last week July 17, I updated my kernel, wich now is 2. I configured my wireless connection as suggested here: In addition, sometimes the network connection seems cannot build. I chose to link my BCM device to the file pointed to by the link 14E4: Broadcom Corporation physical id: Reboot and now I can sftp and ssh to my university.
|Date Added:||7 February 2007|
|File Size:||55.62 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Reboot and now I can sftp and ssh to my university.
But last week July 17, I updated my kernel, wich now is 2. I am not pretty sure which method worked: I did not need any symbolic links as in step 2.
I used instead of because that is how the device is addressed? I’m going to reinstall vpnclient and verify.
In addition, sometimes the network connection seems cannot build. Sometimes it connects but just after lot of tries on Network Manager. So I disabled it.
I reinstalled vpnclient and I can now extablish a VPN with my university. In my case there was a link 14E4: 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. Wait for my result.
Today, I tried to sftp to my university and I was getting hung!?! I used similar kind of steps several times and finally my wireless light lits up!! I suspected something was wrong visya weeks ago because my light on the wireless device was orange instead of blue.
After you install it, you vieta be able to test it out by doing the following: My wireless was still not working: Do you have a clue about what I can do to improve it?
I is Hardy Wireless! I chose to link my BCM device to the bc4m310 pointed to vieta the link 14E4: I suppose that if your linux detects and loads b43, you do need to black list it with ssb in order to use ndiswrapper. I did get my wireless working however I have no wep or wpa security only open connectionsIf you are using kernel 2. The native driver “wl” loaded by OS is working under non-encrypted condition by using NetworkManager.
BCM4310 usb Controller using Dell xps m1530
However this thread bmc4310 the end shows how to remove ndiswrapper and compile a new version which I ended up doing. Looks like the restricted wl drivers were messing that up as well. I’d like to get connected faster.
Grrrr, now I’m suspecting the same problem.
BCM usb Controller using Dell xps m – Tech Support Forum
I’m not exactly sure what’s going on with your intermitency. Local Loopback inet addr: I also updated my kernal but from 2.
I did need all the blacklists. I’m still not sure if this step is necessary but I show it anyway. Also, before disabling the restricted wl drivers, here’s what bcm4301 -C network was showing: However, after I have install the Ubuntu 8. In another case Dell Vostro I didn’t need to blacklist anything, since b43 was not automatically loaded When connected, everything goes well.