Differences between revisions 19 and 25 (spanning 6 versions)
Revision 19 as of 2008-02-14 21:08:31
Size: 6304
Comment: minor
Revision 25 as of 2008-07-01 16:27:29
Size: 7214
Editor: WillOrr
Comment: Added driver section
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Some vendors do not release specifications of the hardware, and don't provide a linux driver for their wireless network cards. Ndiswrapper project provides a linux kernel module that loads and runs Windows kernel API and NDIS (Network Driver Interface Specification) API drivers supplied by the vendors within the Linux kernel. A Windows driver for wireless network card is then linked to this implementation so that the driver runs natively, as though it is in Windows, without binary emulation.  Some vendors do not release specifications of the hardware, and don't provide a linux driver for their wireless network cards. Ndiswrapper project provides a linux kernel module that loads and runs Windows kernel API and NDIS (Network Driver Interface Specification) API drivers supplied by the vendors within the Linux kernel. A Windows driver for wireless network card is then linked to this implementation so that the driver runs natively, as though it is in Windows, without binary emulation.
Line 7: Line 7:
Make sure the following packages are installed:
Line 8: Line 9:
Make sure the following packages are installed:

* packages DebPkg:ndiswrapper 
 * packages ndiswrapper-${arch}-[default|smp|xen] 
 * DebPkg:ndiswrapper-utils -Userspace utilities for ndiswrapper. You will also need the kernel module package. 
 * wireless-tools (If you use a with wireless card)
 * packages DebPkg:ndiswrapper
 * packages ndiswrapper-${arch}-[default|smp|xen]
 * DebPkg:ndiswrapper-utils -Userspace utilities for ndiswrapper. You will also need the kernel module package.
 * DebPkg:wireless-tools (If you use a with wireless card)
Line 17: Line 15:
You can also use DebPkg:ndisgtk , a graphical frontend for ndiswrapper .

== Drivers ==
You also need to have the appropriate Windows driver for your card. The first place you should check is the [http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/ ndiswrapper compatiblity list]. It lists many models of wireless cards that are usuable with ndiswrapper and the driver that works the best.

If you can't find it there, the [http://www.linuxant.com/driverloader/drivers.php Linuxant Windows Driver] page has many drivers that work with ndiswrapper. It also has drivers for some 64 bit cards that don't offer native 64 bit drivers on the manufacturer's web page.

The final place you should go is your CD or the manufacturer's web page. These often work, but sometimes they're broken or don't offer you full functionality. It's best to go with the ones listed on the ndiswrapper web page.
Line 19: Line 25:

Line 23: Line 27:
To download and install ndiswrapper tools and modules with debian ( provided you have the standard debian kernel )  To download and install ndiswrapper tools and modules with debian ( provided you have the standard debian kernel )
Line 25: Line 29:
 {{{
apt-get install module-assistant ndiswrapper-utils ndiswrapper-source 
 . {{{
apt-get install module-assistant ndiswrapper-utils ndiswrapper-source
Line 30: Line 34:
}}}   }}}
Line 37: Line 40:
 {{{
$mkdir /usr/local/i4965/ 

 .
{{{
$mkdir /usr/local/i4965/
Line 43: Line 47:
Alternatively, You might refer directly to any windows owned folder. If the way to this folder (the pathname) contains white spaces, e.g. "Program Files", it is recommended first to move with ["cd"] to the folder containing the required ''*.inf'' file:
Line 44: Line 49:
Alternatively, You might refer directly to any windows owned folder. If the way to this folder (the pathname) contains white spaces, e.g. "Program Files", it is recommended first to move with ["cd"] to the folder containing the required ''*.inf'' file:  . {{{
cd '/windows/where the inf file is'
ndiswrapper -i this_and_that.inf
}}}
Let's make sure it's configured :
Line 46: Line 55:
 {{{
cd '/windows/where the inf file is'
ndiswrapper -i this_and_that.inf
}}}


Let's make sure it's configured :
 {{{
 . {{{
Line 58: Line 60:
Then add ndiswrapper in /etc/modules
Line 59: Line 62:
Then add ndiswrapper in /etc/modules
 {{{
 . {{{
Line 62: Line 64:
ndiswrapper  ndiswrapper
Line 64: Line 66:
Line 69: Line 70:
== Uninstallation ==
To uninstall a driver, you need to type:
Line 70: Line 73:
== Uninstallation ==

To uninstall a driver, you need to type:

 {{{
 . {{{
Line 77: Line 76:
An additional check can be to look at
Line 78: Line 78:
An additional check can be to look at  . {{{
/etc/ndiswrapper
}}}
if a directory named as the installed driver is there available.
Line 80: Line 83:
 {{{
/etc/ndiswrapper
}}}

if a directory named as the installed driver is there available.
 
== bConfigure interface ==
== Configure interface ==
Line 91: Line 87:
Line 102: Line 97:
http://www.linuxquestions.org/questions/showthread.php?t=360483
http://sourceforge.net/mailarchive/message.php?msg_id=6713442
http://www.linuxquestions.org/questions/showthread.php?t=360483 http://sourceforge.net/mailarchive/message.php?msg_id=6713442
Line 111: Line 105:
== See Also ==
 * Ndiswrapper
  * [http://ndiswrapper.sourceforge.net/ Homepage]
  * [http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/ Wiki],
  * [http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/ ndiswrapper compatiblity list].
 * ["WiFi"]

 
=== Cab ===
You can try unpacking *.cab files with any of the following:
== Cab ==
You can try unpacking *.cab files with any of the following:
Line 124: Line 110:
== See Also ==
 * Ndiswrapper
  * [http://ndiswrapper.sourceforge.net/ Homepage]
  * [http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/ Wiki],
  * [http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/ ndiswrapper compatiblity list].
 * WiFi
Line 125: Line 117:
CategoryHardware  . CategoryHardware

Some vendors do not release specifications of the hardware, and don't provide a linux driver for their wireless network cards. Ndiswrapper project provides a linux kernel module that loads and runs Windows kernel API and NDIS (Network Driver Interface Specification) API drivers supplied by the vendors within the Linux kernel. A Windows driver for wireless network card is then linked to this implementation so that the driver runs natively, as though it is in Windows, without binary emulation.

Ndiswrapper uses the Windows *.inf driver files that came with your hardware to operate your wireless card on Linux. Most likely you will need to uncompress a *.cab file which contains your drivers.

Packages

Make sure the following packages are installed:

  • packages ndiswrapper

  • packages ndiswrapper-${arch}-[default|smp|xen]
  • ndiswrapper-utils -Userspace utilities for ndiswrapper. You will also need the kernel module package.

  • wireless-tools (If you use a with wireless card)

Choose the proper kernel module package (${arch}) for your architecture. Most people will just need to use "ndiswrapper-${arch}-default".

You can also use ndisgtk , a graphical frontend for ndiswrapper .

Drivers

You also need to have the appropriate Windows driver for your card. The first place you should check is the [http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,list/ ndiswrapper compatiblity list]. It lists many models of wireless cards that are usuable with ndiswrapper and the driver that works the best.

If you can't find it there, the [http://www.linuxant.com/driverloader/drivers.php Linuxant Windows Driver] page has many drivers that work with ndiswrapper. It also has drivers for some 64 bit cards that don't offer native 64 bit drivers on the manufacturer's web page.

The final place you should go is your CD or the manufacturer's web page. These often work, but sometimes they're broken or don't offer you full functionality. It's best to go with the ones listed on the ndiswrapper web page.

Installation

Download the module's source and build a module binary package :

To download and install ndiswrapper tools and modules with debian ( provided you have the standard debian kernel )

  • apt-get install module-assistant  ndiswrapper-utils ndiswrapper-source
    m-a prepare
    m-a update
    module-assistant auto-install ndiswrapper

You find more instruction in /usr/share/doc/ndiswrapper*/README*

The drivers you find may be packaged as ZIP, or an executable file. Some of the EXE files are just ["zip"] files, so you can run ["unzip"] and obtain driver files. Some EXE files are CAB files, so run cabextract and/or unshield on CAB file, typically named data2.cab

Assuming you have downloaded the Windows driver in ~/Desktop/Downloads/V11.1.1.0_XP_DRIVERS.ZIP :

  • $mkdir /usr/local/i4965/
    $cd /usr/local/i4965/
    $unzip -q ~/Desktop/Downloads/V11.1.1.0_XP_DRIVERS.ZIP
    $ndiswrapper -i /usr/local/i4965/NETw4x32.INF

Alternatively, You might refer directly to any windows owned folder. If the way to this folder (the pathname) contains white spaces, e.g. "Program Files", it is recommended first to move with ["cd"] to the folder containing the required *.inf file:

  • cd '/windows/where the inf file is'
    ndiswrapper -i this_and_that.inf

Let's make sure it's configured :

  • $ndiswrapper -l
    installed drivers:
    netw4x32                driver installed, hardware (8086:4233) present

Then add ndiswrapper in /etc/modules

  • # added ndiswrapper to load XXXXX Network driver.
    ndiswrapper

You can either reboot you system to get the module loaded... or simply run modprobe ndiswrapper this time ;).

This should be it.

Uninstallation

To uninstall a driver, you need to type:

  • ndiswrapper -e <then the name of the driver to uninstall>

An additional check can be to look at

  • /etc/ndiswrapper

if a directory named as the installed driver is there available.

Configure interface

Use ["iwconfig"] to configure wireless network interface.

Configure on insert / Hotplug

According to a DebianEtch entry on the ndiswrapper wiki, an 'allow-hotplug wlan0' entry in /etc/network/interfaces is about all it takes to get the card to be automatically configured and brought up when inserted (beyond the required steps to configure the card for manually bringing the interface up.)

http://ndiswrapper.sourceforge.net/mediawiki/index.php/InstallDebianEtch

On Sarge this does not appear to be the case. Adding that line does not make hotplug 'just work'. This is most likely due to the lack of an entry for ndiswrapper in /lib/modules/<kernel version>/modules.pcimap. According to the hotplug overview when new hardware is detected the MODULE_DEVICE_TABLE map is consulted to determine which module is responsible for the device. Without that entry or some other help hotplug will not 'just work' for the device.

The easiest workaround is to require the ndiswrapper module at boot so that it is always loaded and ready to claim the hardware. Just add it to the list in /etc/modules.

The most difficult workaround (for many) may be to edit the ndiswrapper source and recompile so that it will make MODULE_DEVICE_TABLE entries for your hardware.

http://www.linuxquestions.org/questions/showthread.php?t=360483 http://sourceforge.net/mailarchive/message.php?msg_id=6713442

An inbetween workaround may be to modifiy /etc/hotplug/pci.agent to parse an /etc/hotplug/pci.handmap and have it include the hardware details necessary to load ndiswrapper when your card is inserted, like you can do with usb.handmap. This step and the re-coding are probably best left to the developers which leaves us with /etc/modules.

There seems to be a couple different ways documented to enable hotplugging on interfaces (once hotplugging is working for ndiswrapper). Mentioned in the DebianEtch page on the ndiswrapper wiki is the line allow-hotplug wlan0. The man page for the interfaces file confirms that this is the intended way to enable hotplug. In /etc/hotplug/net.agent, you are directed to include mapping hotplug stanzas in /etc/network/interfaces.

On a Debian 3.1 / Dell Inspiron 1200 system the allow-hotplug entry did not seem to be necessary. The map stanza seemed to be enough, once ndiswrapper was already loaded. YMMV.

Cab

You can try unpacking *.cab files with any of the following:

  • cabextract - a program to extract Microsoft Cabinet files

  • unshield - extracts CAB files from ?InstallShield installers (If it doesn't succeed, you might want to try using i5comp or i6comp under Windows. search it in google)

See Also