User Tools

Site Tools


compatibility_drivers

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
compatibility_drivers [2018/07/19 20:20]
mister_x [Determine the chipset] fixed typo
compatibility_drivers [2018/07/20 23:16] (current)
mister_x italics for "Details" pane
Line 41: Line 41:
  
 ====== Determine the driver ====== ====== Determine the driver ======
-Once you have determined the chipset, ​check the [[compatibility_drivers#​drivers|driver]] section for which software driver you needSoftware drivers connect ​the operating system ​to the hardware. The drivers ​are different for each operating system. There are also notes regarding limitations.+ 
 +Once you have determined the chipset, ​chances are you already have identified the driver on Linux. If not, match the chipset against the "other resources"​ above to figure out the driver.  
 + 
 +On Linux, there can be multiple drivers: 
 +- Vendor driver: those do not and will not support monitor mode 
 +- Peer-modified vendor driver: In some cases, they may support monitor mode but there could be caveats 
 +- Staging driver: Standalone driver has been added to the [[http://​www.kroah.com/​log/​linux/​linux-staging-update.html|Linux Staging tree]]. However, quality of the driver is unknown and needs more work to be included in the kernel 
 +- Kernel/​mac80211 driver: In this case, chances ​are, monitor mode is supportedInjection may or may not be supported
  
 If you are deciding on which card to purchase, check the "​[[faq#​what_is_the_best_wireless_card_to_buy|What is the best wireless card to buy?​]]"​ section on this page. There are many considerations that should go into your purchase decision: If you are deciding on which card to purchase, check the "​[[faq#​what_is_the_best_wireless_card_to_buy|What is the best wireless card to buy?​]]"​ section on this page. There are many considerations that should go into your purchase decision:
Line 62: Line 69:
 It also lists the IDs (**0bda:​8812**) which is what would be returned on Linux with the //lsusb// command, right next to **ID**. It also lists the IDs (**0bda:​8812**) which is what would be returned on Linux with the //lsusb// command, right next to **ID**.
  
-If it were on Windows, even if the drivers were not installed, looking in the device manager, that ID would be found in Details pane of the device itself, in the property "​Hardware IDs". This is also displayed in WikiDevi: **USB\VID_0BDA&​PID_8812** (this is the same as the IDs on Linux, they'​re just uppercase and they contain some text around: USB device, VID stands for Vendor ID, PID stands for product ID).+If it were on Windows, even if the drivers were not installed, looking in the device manager, that ID would be found in //Details// pane of the device itself, in the property "​Hardware IDs". This is also displayed in WikiDevi: **USB\VID_0BDA&​PID_8812** (this is the same as the IDs on Linux, they'​re just uppercase and they contain some text around: USB device, VID stands for Vendor ID, PID stands for product ID).
  
 {{:​awus036ac_wikidevi_2.png?​200 |}} {{:​awus036ac_wikidevi_2.png?​200 |}}
compatibility_drivers.1532024449.txt.gz · Last modified: 2018/07/19 20:20 by mister_x