This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Feature: Reviews

KNDISwrapper is half-done, but far from half-baked

By Bruce Byfield on December 03, 2008 (4:00:00 PM)

Share    Print    Comments   

If any process ever cried out for a graphical interface, it is using NDISwrapper to enable wireless devices to run on GNU/Linux using Windows drivers. The process is often torturous, especially for first-time users, who are unsure whether any problems are due to NDISwrapper's limitations or their own inexperience. By organizing and explaining the process, KNDISwrapper promises to remove much of the labor. But, so far, it only partly delivers on that promise by neglecting the hardest part of working with NDISwrapper -- finding the right Windows driver.

Now at version 0.3.6, KNDISwrapper is in rapid development. You can find packages for Mandriva and SUSE 10.3, and source code is also available. However, before installing, you also need at least the minimal libraries for KDE 3.5x, which requires installing a few extra megabytes if you are using KDE 4.x. In addition, you need NDISwrapper, which, depending on your distribution's policies about including free software that works with proprietary code, may require you to enable non-official repositories (on Fedora, for example, you need to set up the RPMFusion repository).

As KNDISwrapper opens, it offers you a chance to set your language, then detects whether you have loaded NDISwrapper into the kernel. If you haven't yet, it offers to do so for you. If you don't agree, there's not much point to continuing, except perhaps to poke through the program. Still, the fact that the program provides a confirmation dialog rather than automatically changing your system suggests that the developer at least has the right idea, especially since you can only run KNDISwrapper as root.

After NDISwrapper is enabled, KNDISwrapper opens on a well-organized window. On the left is a clearly written help pane, although its use of italics reduces readability. In the middle it displays current information or dialogs. On the right are function buttons, arranged in the order that you will want them.

An initial stumbling block

Almost immediately, you find that KNDISwrapper does not automate the first and hardest part of the process -- finding the driver that you need. The help pane does explain that you must look for a file with an .inf extension, and that the best place to find it is either on a Windows system or its installation files or CD, but this information won't help you much if you have no access to such things.

If you don't, this is a bad time to be hunting for Windows drivers -- though the developer of KNDISwrapper is not to blame. It used to be that you could identify your wireless device's card by running lspci, then using the first column entry for the device to determine the chipset via the third or fourth column of the results of lspci -n. Armed with this information, you could check the list of supported chipsets on the NDISwrapper site, so you could at least note what you are looking for.

Unfortunately, as I write, this list is unavailable as the Ndiswrapper project reorganizes its Web page. Instead, you need to find the Windows XP driver for your device and download it from the manufacturer's site. In most cases, it will be in the form of an executable compressed file, from which you can extract the necessary .inf file using most archive tools without decompressing the entire driver.

A fast comeback

Once you have a likely driver, KNDISwrapper makes everything simple. When you click the Install Driver button you can use your desktop file manager to navigate to your .inf file. Installation takes less than 20 seconds, and the driver appears in the middle pane, along with a notation about whether it is valid for the selected device.

The next three buttons below Install Driver imply an implicit acknowledgement of how hard finding the correct driver can be. You get a Remove Driver button, followed by Reload List, which gives you a second chance of trying the driver. Below that is the Restore Driver button, which re-installs a removed driver from the archived copy that KNDISwrapper keeps in the /.kndiswrapper folder of the /root directory.

When you're happy with the driver you've installed, clicking the Config Network button opens a dialog that you can use to configure your Internet connection and the default wireless connection. Some of the choices here may be beyond the knowledge of newer users, but the help pane provides a reasonable summary of the possible choices.

So far as it goes

For the parts of the process that it covers, KNDISwrapper offers one of the best graphical interfaces I've seen in an administrative utility. However, unless it can be more help with the difficulties of hunting down the driver, it will remain less useful than it could be.

Granted, helping track down the driver would require some well-organized code. Yet it should not be impossible for the program to help you detect the device and navigate to a Windows partition or CD. Granted, helping you find the manufacturer's site would require more research by the developers. And perhaps, too, the different versions of Windows XP and of drivers, to say nothing of the constant shifting of download pages on the Internet, might mean that the program could only make suggestions. Still, the effort might be worth a try.

By offering such assistance, KNDISwrapper could complete the process of simplification that it has already undertaken. Without it, KNDISwrapper is a good start, but only does half of what users actually need.

Bruce Byfield is a computer journalist who writes regularly for Linux.com.

Share    Print    Comments   

Comments

on KNDISwrapper is half-done, but far from half-baked

Note: Comments are owned by the poster. We are not responsible for their content.

Mandriva has a wizard for that

Posted by: Anonymous [ip: 216.123.208.30] on December 03, 2008 06:02 PM
Mandriva Linux has wizards for *everything* and has for many years. You can set up Ndiswrapper with WiFi in about two clicks of a mouse.

#

Re: Mandriva has a wizard for that

Posted by: Anonymous [ip: 216.48.59.163] on December 03, 2008 07:22 PM
2 Things. First NDISwrapper is not hard! I hate it when every one keeps saying that its this terrible program. I had never used it until Dell replaced my laptop with one that had a broadcom card. Jumping in (without reading anything but the Archlinux wiki information on howto install and setup) i failed. Why? Cause i didnt read the documentation that said i can only use XP drivers! Once i downloaded the XP drivers instead, it was 4 commands. thats it! and they werent even long and drawn out. Point ndiswrapper to the driver you want to use. load it. set up alias for the module. done.

2nd) LinuxMint already has a tool.

I expect better from you guys!

#

Re: Mandriva has a wizard for that

Posted by: Anonymous [ip: 206.192.231.187] on December 04, 2008 01:10 AM
Yea, but thats Mandriva, this tool is for nonperfect distos that don't already have an amazing gui. :)
-Mandriva User Anonymous

#

Posted by: Anonymous [ip: 10.12.31.35] on December 03, 2008 07:47 PM

[Modified by: Nathan Willis on December 03, 2008 02:33 PM]

#

KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 98.212.101.225] on December 03, 2008 11:44 PM
Zenwalk linux has had a gui for ndiswrapper since I started using it. I don't know how long before that. It's simple. Shouldn't be that hard to make one. With zenwalk you click the ndiswrapper option in one of the menes, click install driver, find it, and then ok. It tells you right away if is present or not then lets you configure the network with Wicd

#

KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 98.203.239.242] on December 04, 2008 02:58 AM
This will help all users of the KDE desktop. If your favorite distro already has a distro good for you. If you like the commandline so much, you should use a terminal - no X for you!

Secondly, the screenshot at kde-apps promises to not just install the driver, but to also configure your wireless device. I have ubuntu fiesty (gnome) on two machines with wireless devices and it was a pain to configure the devices.Ndiswrapper was not too bad, but WPA2 setup was difficult. If this app does it all in one swoop, that would make life easy for a lot of people.

I'm fairly technically competent and have been using linux as my primary OS since '96. However, there are only so many hours in a day ...so good on KNDISwrapper!

#

KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 90.128.104.61] on December 04, 2008 09:33 AM
How can you demand of Kndiswrapper what no tool in windows can supply?

Microsoft has that Windows Update driver storage, but there's still hardly anything in it.

All it could do is maybe search a cd or folders for drivers, but that would already go further than what windows does for you.

#

KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 78.32.26.49] on December 04, 2008 02:38 PM
ndisgtk works for me, (ubuntu on Acer Aspire One to get the LEDs working). Hope this works as well for all the KDE users who need ndis. Installing ndiswrapper via the shell is not hard, but sometimes it is nice to be lazy.

#

Re: KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 206.192.231.187] on December 04, 2008 11:39 PM
Ndisgtk is almost as good as mandriva's tool. I've used both. Why don't these KDE people actually make a good desktop environment before they make software for it? I love mandriva, but I use the Gnome edition.
Mandriva user and KDE hater anonymous

#

Re(1): KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 83.146.33.39] on December 05, 2008 02:54 PM
"Why don't these KDE people actually make a good desktop environment before they make software for it? I love mandriva, but I use the Gnome edition.
Mandriva user and KDE hater anonymous"

Yep, Gnome was written for idiots and you fulfill the criteria as a prime example.

#

KNDISwrapper is half-done, but far from half-baked

Posted by: Anonymous [ip: 216.239.86.114] on December 05, 2008 10:25 PM
Great article.
I also agree with your opening sentence "If any process ever cried out for a graphical interface" so how about doing a list of others like it?
I still cant believe that some distros (Im looking at your Ubuntu) still use that ugly monochrome boot loader for dual booting Windows and Linux.
If there is anything than screams "Yeah, this is Linux... we do everything still in the command line." that is it. But there are a few more like these.

ive gotten to love the command line and even my wife knows how to sudo shutdown on her Dell Mini 9 but it scares people.

#

KNDISwrapper comment

Posted by: Anonymous [ip: 69.28.36.135] on December 06, 2008 06:12 AM
I personally don't have an issue with working with ndiswrapper from the command-line. However, I do understand that a GUI would work better for some people. I, personally, would pay money for a GUI to configure dual-monitor support.

#

Not sure of the Legal Ramifications

Posted by: Anonymous [ip: 209.205.152.198] on December 08, 2008 03:42 PM
PCLinuxOS MiniMe and Tinyme (descendants of the Mandriva Family) both actually include a package of windows Drivers in the NDISWrapper directory, one only has to select one from those listed. I'm not sure of the legal ramifications of this, being "nonfree" drivers, but they do it, and have included this feature for nearly a year(that I know of).

Seems like a perfect solution to the problem of locating the drivers themselves.

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya