Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revisionLast revision | |||
— | slackware:ndiswrapper [2008/09/11 11:33] – Be more specific about how to configure wpa with ndiswrapper. alien | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Using ndiswrapper for unsupported wireless cards ====== | ||
+ | Wireless card support in linux is pretty good nowadays, as more and more vendors realize there is not per definition evil in using and releasing Open Source Software, or in co-operation with Open Source developers. For the old-style 11Mbit PCMCIA cards, drivers have existed for some time now (hostap, linux-wlan) and a few 54 Mbit card drivers have even made it into the kernel (prism54 and ipw2200/ | ||
+ | |||
+ | Still, there are many other wireless cards for which no driver exists at all. An Open Source project, [[http:// | ||
+ | Also, ndiswrapper-driven cards tend to crash the kernel in high-load situations and even though you should run a Linux kernel with at least 8K stack size (which is the default in Slackware), some NDIS drivers seem to need stack sizes as high as 32K to properly function.\\ | ||
+ | The 32K stack size is not something you can configure in an unpatched kernel, and since I have only read about these large kernel stack sizes in non-Slackware mailing lists, I'd say: stick to the default stack size of 8K you find in Slackware kernel, unless you experience strange kernel crashes that you can trace back to the ndiswrapper module... | ||
+ | |||
+ | For now, rest assured that you probably will not need to change anything to your running kernel to get ndiswrapper support for your wireless card. The rest of the page will concern itself with detailing how to obtain the ndiswrapper source code, how to build and install the software, how to install a Windows driver, and how to configure your card. WPA encryption is discussed in the final paragraph. | ||
+ | |||
+ | ===== Obtaining the source ===== | ||
+ | |||
+ | Ndiswrapper releases can be downloaded from [[http:// | ||
+ | |||
+ | ===== Building and installing ndiswrapper ===== | ||
+ | |||
+ | Note that at some point, the developers seem to have dropped support for the older GCC 3.3 compiler. I can not build the 1.16 release on Slackware 10.2 for instance. | ||
+ | You can either compile the downloaded source package yourself, by running < | ||
+ | tar -zxvf ndiswrapper-< | ||
+ | cd ndiswrapper-< | ||
+ | make distclean | ||
+ | make install | ||
+ | </ | ||
+ | mkdir ndiswrapper | ||
+ | cd ndiswrapper | ||
+ | lftp -c "open http:// | ||
+ | cd build | ||
+ | ./ | ||
+ | </ | ||
+ | installpkg / | ||
+ | |||
+ | ===== Installing a Windows driver ===== | ||
+ | |||
+ | You can use the Windows driver that came with your card, and I have not had problems doing so yet, but the ndiswrapper Wiki states that it is better to look up your card's PCI-ID in the [[http:// | ||
+ | |||
+ | * Look up the PCI ID for your card by first running the command < | ||
+ | |||
+ | * Next, look up the starting numbers of that line in the output of the command < | ||
+ | |||
+ | * If the download is a Windows installer, you might need a tool like [[http:// | ||
+ | |||
+ | * Once you finally have the extracted Windows NDIS driver in the form of two .INF and .SYS files and possibly .BIN or other files containing firmware, all together in your current directory, proceed with installing them so they can be used by ndiswrapper. Run the ndiswrapper helper application like this: < | ||
+ | ndiswrapper -i filename.INF | ||
+ | </ | ||
+ | |||
+ | * You can check if this was done correctly by running < | ||
+ | ndiswrapper -l</ | ||
+ | Installed drivers: | ||
+ | rt2500 | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Activating the card on boot ===== | ||
+ | |||
+ | The ndiswrapper kernel module will not load automatically. You can add the following line to the file ''/ | ||
+ | / | ||
+ | |||
+ | If you want to have the network interface be known as //wlan0// then you can either run < | ||
+ | |||
+ | |||
+ | ===== Network configuration ===== | ||
+ | |||
+ | Your card will be loaded with the name **wlan0**. Detailed information about how to configure your wlan0 interface can be found in my [[: | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== WPA encryption for your wireless network ===== | ||
+ | |||
+ | For more information about how to configure WPA using [[http:// | ||
+ | |||
+ | < | ||
+ | WLAN_WPADRIVER[1]=" |