Despite the warnings that it probably would not work. Hopefully that all makes sense! I think it may died a couple of times too. If you didn’t then you haven’t actually installed anything, which is why it’s not saying that your hardware has been detected. I tried adding the 3 words in the grub, with no luck: I have a new wireless problem.
|Date Added:||13 July 2016|
|File Size:||12.63 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
If you had have installed a newer version of Ubuntu ie. Broadcom Corporation Unknown mnii-pci rev 03 ndiswrapper: Then I rebooted and it hasn’t worked since. Then I got the build essential updates following the same instructions listed by the OP, including the dell drivers. Sorry for such a long post.
Dell WLAN Wireless Yh774 Mini PCI E Card WiFi DW 1390 Broadcom 1525 D630 D820
Thanks for the help. I regret not saving the error report, but when I enter sudo ndiswrapper -l, the second brozdcom fails. Don’t post in both though! But, yeah, if it ain’t broke, don’t fix it! Thanks guys and gals!
I have a new wireless problem. How do I go back to the previous driver? I thought that doing sudo -s at carv beginning would make everything easier. So you tried that and it’s disappearing everytime you log out and back in again? So yes you’ll still be able to see the networks and connect to them, just not to their full potential.
Find More Posts by hughedavid1. Appreciate your help Mnatobian a friend who also uses Ubunto 7. If u can helo me please let me know what output data you need.
The alternative is to either run the entire command as root “sudo -s” turns the terminal into a root shell, you’ll notice the command prompt becomes “root machinename: The light doesn’t turn on and the wireless adapter is gone from the network settings. You do need to blacklist the driver still and then after a reboot everything should be working.
Once you have the light off, it will not light up again until you follow the rest of the how-to and run “sudo modprobe ndiswrapper” at which point you tell the kernel to use muni-pci ndiswrapper alan enabling the driver you just installed. I am definitely a believer.
Thank you very much for this post. Sign up using Email and Password.
With Gutsy’s kernel, installing some firmware will get the driver functioning, it’s not as good as it’s ndiwrapper counterpart, but I think Ubuntu’s “Restricted Drivers Manager” will do it all for you. I thought I’d trashed everything that I’d unpacked when I realized the task was too daunting for me but perhaps I missed something? This was my largest hurdle in my move from Windows to Kubuntu.
To continue using , please upgrade your browser.
And just to verify your installation ran correctly what are the outputs of the following two commands? The package page should tell you what dependancies it has so just download and save all the. I’ve also tryed to disable static connections so network manager has found networks, and than again set for static ip and click OK but it can’t connect: Last edited by hughedavid1; at I have just ran “ndiswrapper -v” and it returned Version 1. Which is strange if Iwas able to connect just yesterday with classih ubuntu network manager P.
Please don’t type all in caps.