Differences

This shows you the differences between two versions of the page.

--- install_drivers [2008/07/14 18:08] – darkaudax
+++ install_drivers [2009/08/14 19:24] – use dokuwiki internal link mister_x
@@ Line 1: / Line 1: @@
 ====== Installing Drivers ======
 ===== Linux =====
 As of now, Aireplay-ng only supports injection on Prism2, PrismGT (FullMAC), Atheros, Broadcom (with the b43 driver), RTL8180, RTL8187, Ralink, ACX1xx and Zydas. Injection on** Hermes, Aironet and Marvell** is not supported because of firmware and/or driver limitations.
@@ Line 23: / Line 20: @@
 Note: if you're using drivers provided by your distribution, they are NOT patched.
 \\
+General information about patching drivers plus troubleshooting tips can be found in the [[patching|How To Patch Drivers Tutorial]].
 The following are detailed instructions for installing/patching the ieee80211 versions of the drivers:
@@ Line 39: / Line 37: @@
   * [[rt2500]]
   * [[rt2570]]
+  * [[rt2870]]
   * [[rt61]]
   * [[rt73]]
@@ Line 51: / Line 50: @@
 The mac80211 link above also contains information regarding which mac80211 drivers work with the aircrack-ng suite.
-In addition, the following mac80211 drivers require extra patches to enable or improve monitoring or injection support:
+In addition, the following mac80211 drivers require extra patches to enable or improve monitoring or injection support (purpose of the patch is in parentheses):
-  * [[b43]] and b43legacy
+  * [[iwlagn]] (allow injection in 2.6.25/.26, formerly called iwl4965)
-  * [[iwl3945]]
+  * [[rtl8187]] (improve injection speed)
-  * [[iwl4965]]
+  * [[zd1211rw-mac80211]] (fully disable packet filtering in monitor mode)
-  * [[zd1211rw-mac80211]]
 \\
@@ Line 157: / Line 155: @@
 Run "modinfo <kernel module name>".  This will confirm the module is actually in the modules tree.  As well, confirm it is the correct version.  Do a "ls -l <file location per modinfo>" and confirm the date matches when you compiled it.  It is not uncommon that you are not running the correct module version.
@@ Line 165: / Line 164: @@
 A common problem on newer kernels is that the new mac80211 version of the driver gets loaded instead of the older legacy driver, or vice versa.  If that is the case, then you need to blacklist the wrong modules by editing /etc/modprobe.d/blacklist.  First, determine the broken module names and add them to the blacklist file as "blacklist <module name>".
-Specifically for madwifi-ng, do a locate or find for ath5k.ko.  If ath5k.ko exists then add "blacklist ath5k" to /etc/modprobe.d/blacklist and reboot. Ath5k is heavily experimental, and it isn't yet tested to work with aircrack-ng.
+Specifically for madwifi-ng, do a locate or find for ath5k.ko.  If ath5k.ko exists then add "blacklist ath5k" to /etc/modprobe.d/blacklist and reboot.
+Same for the other way around: if you want to load ath5k, but madwifi-ng gets loaded instead, add "blacklist ath_pci" to /etc/modprobe.d/blacklist.
@@ Line 242: / Line 242: @@
 If you have conflicts due to running both drivers, then decide which one you want and blacklist the other one.
+==== dmesg error "failed with error -71" for USB device  ====
+When using an USB device and you get a message similar to this from dmesg:
+   rt73: Firmware loading error
+   rt73: Failed to load Firmware.
+   rt73: probe of 1-7:1.0 failed with error -71
+Note: Although the example shows RT73, this applies to any USB driver.
+Here are a few things to check:
+  * Ensure you have the firmware installed on your system and in the correct location.
+  * You can try downloading a fresh copy of the driver and installing it again.
+  * Try connecting your USB device directly to your computer without a cable.  Cables can be defective and/or too long.  If they are too long then the signal may degrade or there is insufficient power.
+  * If you have multiple USB devices connected to your computer then remove them all except the wireless device and retry.