GPL-only symbols and ndiswrapper
Posted Oct 25, 2006 21:39 UTC (Wed) by gmaxwell
In reply to: GPL-only symbols and ndiswrapper
Parent article: GPL-only symbols and ndiswrapper
> that many people use ndiswrapper, simply because they don't have a choice
From spending time giving free linux support to linux newbies on IRC I've found that the majority of people trying to use ndiswrapper today are trying to use hardware for which there currently exists free drivers (and in somecases, like Intel 2100, very good free drivers). The reason they are trying to use ndiswrapper is because when they googled for their hardware old mentions of ndiswrapper is what came up first. .. Worse, some distributions advocate ndiswrapper for drivers long after solid free drivers are available.
>- Buy another laptop (yeah, right)
Although most people don't realize it, almost all laptop's wireless cards are on mini-pci and are removable as a result. Linux compatible mini-pci cards can be purchased for fairly low prices, and cards are available with far better recieve sensitivity and higher transmit power than what probably shipped with their laptop. So while not an ideal solution, it isn't unreasonable to suggest that someone change their hardware.
>- Use Windows (yeah, right)
>- Patch the kernel to remove the restriction.
The best option is to use a free driver.
The next best option is to change to Linux supported hardware even ignoring that much of the better hardware is Linux supported, it will simply work better because you need not worry about bugs introduced by running a windows driver in an unintended enviroment.
Using ndiswrapper? ... well Why do you suggest people us Windows drivers after discarding out the option of using Windows itself? There are several nice VMs that Linux works well in, ... If the user is going to have propritary code in their kernel, why not go all the way?
to post comments)