Mandriva Madwifi
From DSO Wiki
urpmi kernel-source (uname -r)
The kernel source is written to /usr/src/linux-*. Make the symbolic link /usr/src/linux from that directory, and another symlink to /lib/modules/linux-*/build Again, please note, You will need to substitute your own version numbers where the example has linux-2.6.12-12mdk. ln -s /usr/src/kernel-source-*/ /usr/src/linux ln -s /usr/src/kernel-source-*/ /lib/modules/*/build
As root, next key in (exactly as written): urpmi gcc cvs cd /usr/src/linux make distclean cp /boot/config .config make oldconfig make make modules
Note that you do not need to make install the kernel or modules.
Please also note that a more explicit make and make install command is available that will overcome small kernel version issues (this is a cheat & can only be used when the kernel source has little or no difference from that used to make the running kernel). If you have kernel version vs madwifi module version mismatch issues substitute these two lines for the last two above: make KERNELRELEASE=$(uname -r) MODULEPATH=/lib/modules/$(uname -r) make modules KERNELRELEASE=$(uname -r) MODULEPATH=/lib/modules/$(uname -r)
This completes the kernel source setup, now you are ready to build the madwifi drivers. Download the Madwifi drivers. http://madwifi.org/ ifi codebase,
Before you build the drivers see the README file in /usr/src/madwifi and "Creating Interfaces in Madwifi:" in the wiki (UserDocs/GettingMadwifi). If you have a prior madwifi installation, see the note at the bottom of this page.
Build the Drivers: cd /usr/src/madwifi make clean make make install If the above fails, use make KERNELRELEASE=$(uname -r) MODULEPATH=/lib/modules/$(uname -r)/kernel/net; make install KERNELRELEASE=$(uname -r) MODULEPATH=/lib/modules/$(uname -r)/kernel/net
After You Build the Drivers: modprobe ath_pci if you ifconfig -a right now, you should see ath0. For pre R1408 NG code, see: UserDocs/Distro/Mandrake/interregnum_NGmake You may be able to use the GUI Mandrake Control Center to manage the first VAP on the card. This is unlikly because the Mandriva Control Center does not recognize that madwifi is installed since mandriva is RPM based and madwifi is compiled from source. wlanconfig should now work to add a VAP to the default station, for example, wlanconfig ath create wlandev wifi0 wlanmode AP nosbeacon NOTE: this is incorrect syntax. nosbeacon only applies to stations. create the AP vap then create the station VAP with nosbeacon on revs prior to r3476, and omit the nosbeacon after that. The order must be AP, then station, then optionally more APs, WDS and/or a monitor VAPs. Autostarting a Station
Modprobe ath_pci automatically creates ath0 (see UserDocs/autocreate. Only one station per card is currently (2/06) permitted. You may want to destroy the station interface to re-acquire the resource for another VAP (wlanconfig ath0 destroy). You can control the autostarting behavior of modprobe ath_pci by argument. If you are using MadWifi releases prior to r1408, see UserDocs/Distro/Mandrake/interregnum_auto Autostarting an AP
To 'autostart' ath0 as an AP, (vs the default Station) add the following lines to /etc/modprobe.conf: alias ath0 ath_pci install ath0 /sbin/modprobe ath_pci autocreate=ap remove ath0 /usr/local/bin/wlanconfig ath0 destroy; /sbin/modprobe -r ath_pci options ath_pci autocreate=ap
Now, when your machine restarts, you should have an AP on ath0 already running under madwifi.
If you are using MadWifi releases prior to r1408, please see UserDocs/Distro/Mandrake/interregnum_APauto
See UserDocs/802.11i and UserDocs/WPA_PSK_on_Both_Ends if you want to set up WPA security on your madwifi interface. If the interface appears to exist but cannot connect or ping, check your firewall settings to assure it is not blocking ath0.
