Difference between revisions of "How to install ndiswrapper for the IBM 11a/b/g WLAN adaptor"

From ThinkWiki
Jump to: navigation, search
(Enable wireless status led =)
(Enable wireless status led)
Line 15: Line 15:
 
When you load ndiswrapper it tells you through syslog which config file it uses.
 
When you load ndiswrapper it tells you through syslog which config file it uses.
  
dmesg:wlan0: ndiswrapper ethernet device XX:XX:XX:XX:XX:XX using driver net5211, configuration file XXX:XXX.X.conf
+
"wlan0: ndiswrapper ethernet device XX:XX:XX:XX:XX:XX using driver net5211, configuration file XXX:XXX.X.conf"
  
 
Changing 'gpioPinFunc1|1' to 'gpioPinFunc1|0' in the configuration file should enable the wireless status led.
 
Changing 'gpioPinFunc1|1' to 'gpioPinFunc1|0' in the configuration file should enable the wireless status led.

Revision as of 14:56, 12 November 2005

Usage of the IBM 11 a/b/g adapter with ndiswrapper:

Because I had massive problems getting the madwifi driver running on kernel 2.6.13 I gave ndiswrapper a try - with impressive success:

Reference system

Configuration of Ndiswrapper

Enable wireless status led

I once had the problem that the wireless led status doesn't come up with loading the driver. After a while I figured out that the driver could be configured through a config file. When you load ndiswrapper it tells you through syslog which config file it uses.

"wlan0: ndiswrapper ethernet device XX:XX:XX:XX:XX:XX using driver net5211, configuration file XXX:XXX.X.conf"

Changing 'gpioPinFunc1|1' to 'gpioPinFunc1|0' in the configuration file should enable the wireless status led.

Advantages of Ndiswrapper

  • full power management support (madwifi has no powermanagement support)
  • connection to access points establishes fast (madwifi has problems here / especially with dhcp)

There are also some drawbacks of Ndiswrapper against madwifi. Some features that madwifi allready provides are missing in ndiswrapper.

Installation instructions

Note: You can also install the driver from an existing windows system. Mount your windows partition and locate the *.INF file of the windows driver: find -name NET5211.INF