Mar 30, 2009 “This program automatically looks at what Wi-Fi card you have, it disables any wireless driver currently installed, fetches the correct Windows driver from the Internet and installs it with NDISwrapper.”
or, you could just use Windows.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
4 Comments 
becauseyouhatelife, bonghits, ndiswrapper, wtf
What the hell? “Oh, let’s disable whatever perfectly good driver is running and replace it with something totally unreliable”. Whatever happened to diagnosing driver issues? I’ll bet that most wireless driver issues these days are due to missing firmware. Kernel wireless support is excellent now, and -ve not found something unsupported in a long time.
I see a lot of posts regarding ndiswrapper on another distro list and keep feeling like responding “what the hell is wrong with the native driver? Did you even look before you started installing this cruft then complain about stability?”
I recall giving ndiswrapper a spin in the past. World of hurt. Most of what I encountered was it only working with specific (old) versions of drivers. Sure, support was patchy at the time, but that’s why everyone was aware that the first thing you should do before buying is check the supported card list.
This would, sadly, be very useful for a rather large number of people, because the native drivers frequently don’t work as well as using a Windows driver via ndiswrapper. Or, indeed, at all. Sure, it’s messy from a freedom POV, but if you just want to run Linux and use your wireless card, you are often going to wind up using ndiswrapper, unfortunately.
nine: hmm…you haven’t really tried much hardware, I’m guessing.
Most broadcom devices still don’t really perform very fast or reliably with b43. Some just flat out don’t work. wl works rather well, but doesn’t support all chipsets, is a closed first-party driver, and wasn’t an option till recently anyway.
acx100 devices don’t have a really usable native driver available, AFAICT. ath5k and ath9k both still have substantial issues with some hardware. The list goes on. Native drivers are obviously The Way Forward, but normal end users are still often stuck with ndiswrapper as the only usable solution. Hell, I was stuck with ndiswrapper as the only usable solution on my old laptop until wl showed up. b43 was very slow and would drop the connection entirely every two hours or so.
Well the problem here is not that people that need to use NDIS wrapper time to time… the problem is that this sort of script is not going to do anybody any favors.
They are not protraying themselves as “this is what you do when nothing else works” they are saying “This is what you do because Linux drivers are shit”
I’ve seen threads on Ubuntu forums were you have people telling other people that they need to uninstall the native driver and install NDISWrapper for hardware, that I know for a _FACT_ works very well with native drivers. There was something else screwed up, but instead of trying to help the person or try to actually figure out what the real problem is they just plop down the kneejerk reaction and act like they were helpful.
Problems with NDISwrapper include:
* Licensing issues. A end user can use it, but it is impossible for anybody to distribute software or hardware that uses it.
* Loss of data, loss of stability. Shoving Windows driver code into a Linux kernel can cause all sorts of issues. If the C code in the Window driver is not entirely correct it can operate well in a Windows environment, but cause all sorts of problems in Linux… like corrupting file systems, screwing up other hardware, and just general instabilities. If that driver screws up it can easily overwrite any part of the Linux kernel memory space with any sort of data.
* Poor network performance. High latency, performance issues, etc. Generally I have found that working drivers in Linux are superior to their Windows counterparts.
* Excessive memory usage.
* Poor power management. Very likely to cause suspend to ram and suspend to disk to stop working correctly. Causes the hardware to use excessive amounts of energy in a laptop compared to proper native drivers.
* Loss of features. Newer Linux protocol stack offers up a lot more functionality then what you can get from a Windows driver IN Windows, much less what you can get by shoehorning a Windows driver into Linux. Stuff like multiple virtual ethernet devices, ability to monitor networks, working ad-hoc modes, effectively control the power output of the driver, and advanced stuff like packet injection.
So while it is lovely that NDISWrapper exists as a option it is not correct to say that it is “Linux wifi made easy”. It is correct to say “Shitty and ill tempered Linux wifi made easy”. Shitty wifi is better then no wifi, but it is not something that should be encouraged.
You see it is the misrepresentation that makes it so WTF. People actually do use Linux for important stuff and they may not be the the most computer savy people out there and they need good and correct information to operate on. People feeding poor and misleading information out there need to be slapped down.
It is actually much much better to simply tell users that Ndiswrapper may get stuff to work, but if they require stuff to perform correctly in Linux they need to go out and purchase a wireless card that will work correctly.
And if you have a piece of hardware or configuration that does not work well with Linux drivers, but really should, (like the open source Atheros, Ralink, or Intel drivers) then do everything you can to find out what the problem is and do bug reports on it. Spending time hacking on python scripts that make something easy that already had scripts and such is not very productive. It is very likely that the reason those things are performing poorly is because the developers are unaware of that hardware or specific configuration and have not been able to test it using that. A single well-made bug report could solve the problems for hundreds of other users in the next OS update.
Contact
Subscribe
