This is the list of questions most commonly asked by the newcomers to the Linux wireless networking land, along with the answers.
A: Forget about XXX, what really matters is PCI or USB (depending on the bus your device uses) ID pair: VID:PID. So to find out if your device is supported, use
to learn the ID pair.
Then navigate to Google and type the request in the form
"VID PID" site:cateee.net/lkddb/
"14e4 170c" site:cateee.net/lkddb/
). If there is a hit, this will allow you to learn which driver to use for your device. If there is no, the device is most probably unsupported (though if you are really sure some driver should support it, you can try modifying the driver source to add the ID, or use
sysfs node for USB devices).
A: Follow this checklist:
output carefully, paying extra attention to firmware-related messages.
to see if there are any rfkill-related issues, there must be no kind of blocks present for you wireless interface. Sometimes there is a mechanical switch that needs toggling for leveraging “hard” block.
A: Please use iw and wpa_supplicant instead.
is using deprecated way of communication with the kernel which is supported only in compatibility mode, has some limitations and might be removed altogether at some point.
A: Use hostapd and a driver supporting AP mode for running in master/AP mode. Setting a device into master mode with iwconfig is not supported by modern drivers.
A: Every card sold was certified to work in a particular regulatory environment (that being set of channels, maximum allowed power, other special flags etc). On Intel cards these restrictions are enforced by firmware, Atheros's equipment has regdomain code in EEPROM which is read on startup by the driver and then (if it's not “world” regdomain) CRDA is contacted to get a set of regulatory requirements.
A: If you are using drivers directly from vendor (and not from upstream Linux or compat-wireless) please ask your vendor for support through its support channels, linux-wireless has nothing to do with that.