Power set enable error set 1 get 0

Network configuration/Wireless

The main article on network configuration is Network configuration.

Configuring wireless is a two-part process; the first part is to identify and ensure the correct driver for your wireless device is installed (they are available on the installation media, but often have to be installed explicitly), and to configure the interface. The second is choosing a method of managing wireless connections. This article covers both parts, and provides additional links to wireless management tools.

The #iw section describes how to manually manage your wireless network interface / your wireless LANs using iw . The Network configuration#Network managers section describes several programs that can be used to automatically manage your wireless interface, some of which include a GUI and all of which include support for network profiles (useful when frequently switching wireless networks, like with laptops).

Device driver

The default Arch Linux kernel is modular, meaning many of the drivers for machine hardware reside on the hard drive and are available as modules. At boot, udev takes an inventory of your hardware and loads appropriate modules (drivers) for your corresponding hardware, which will in turn allow creation of a network interface.

Some wireless chipsets also require firmware, in addition to a corresponding driver. Many firmware images are provided by the linux-firmware package; however, proprietary firmware images are not included and have to be installed separately. This is described in #Installing driver/firmware.

Check the driver status

To check if the driver for your card has been loaded, check the output of the lspci -k or lsusb -v command, depending on if the card is connected by PCI(e) or USB. You should see that some kernel driver is in use, for example:

Also check the output of the ip link command to see if a wireless interface was created; usually the naming of the wireless network interfaces starts with the letter «w», e.g. wlan0 or wlp2s0 . Then bring the interface up with:

For example, assuming the interface is wlan0 , this is ip link set wlan0 up .

Check kernel messages for firmware being loaded:

If there is no relevant output, check the messages for the full output for the module you identified earlier ( iwlwifi in this example) to identify the relevant message or further issues:

If the kernel module is successfully loaded and the interface is up, you can skip the next section.

Installing driver/firmware

Check the following lists to discover if your card is supported:

• See the table of existing Linux wireless drivers and follow to the specific driver’s page, which contains a list of supported devices. There is also a List of Wi-Fi Device IDs in Linux [dead link 2022-11-11] .
• The Ubuntu Wiki has a good list of wireless cards and whether or not they are supported either in the Linux kernel or by a user-space driver (includes driver name).
• Linux Wireless Support and The Linux Questions’ Hardware Compatibility List (HCL) also have a good database of kernel-friendly hardware.

Note that some vendors ship products that may contain different chip sets, even if the product identifier is the same. Only the usb-id (for USB devices) or pci-id (for PCI devices) is authoritative.

If your wireless card is listed above, follow the #Troubleshooting drivers and firmware subsection of this page, which contains information about installing drivers and firmware of some specific wireless cards. Then check the driver status again.

If your wireless card is not listed above, it is likely supported only under Windows (some Broadcom, 3com, etc). For these, you can try to use #ndiswrapper.

Utilities

Just like other network interfaces, the wireless ones are controlled with ip from the iproute2 package.

Managing a wireless connection requires a basic set of tools. Either use a network manager or use one of the following directly:

Software	Package	WEXT	nl80211	WEP	WPA/WPA2/WPA3	Archiso[1]
wireless_tools 1	wireless_tools	Yes	No	Yes	No	Yes
iw	iw	No	Yes	Yes	No	Yes
wpa_supplicant	wpa_supplicant	Yes	Yes	No	Yes	Yes
iwd	iwd	No	Yes	No	Yes	Yes

1. Deprecated.

Note that some cards only support WEXT.

iw and wireless_tools comparison

The table below gives an overview of comparable commands for iw and wireless_tools. See iw replaces iwconfig for more examples.

iw command	wireless_tools command	Description
iw dev wlan0 link	iwconfig wlan0	Getting link status.
iw dev wlan0 scan	iwlist wlan0 scan	Scanning for available access points.
iw dev wlan0 set type ibss	iwconfig wlan0 mode ad-hoc	Setting the operation mode to ad-hoc.
iw dev wlan0 connect your_essid	iwconfig wlan0 essid your_essid	Connecting to open network.
iw dev wlan0 connect your_essid 2432	iwconfig wlan0 essid your_essid freq 2432M	Connecting to open network specifying channel.
iw dev wlan0 connect your_essid key 0:your_key	iwconfig wlan0 essid your_essid key your_key	Connecting to WEP encrypted network using hexadecimal key.
iwconfig wlan0 essid your_essid key s:your_key	Connecting to WEP encrypted network using ASCII key.
iw dev wlan0 set power_save on	iwconfig wlan0 power on	Enabling power save.

Examples in this section assume that your wireless device interface is interface and that you are connecting to your_essid WiFi access point. Replace both accordingly.

Get the name of the interface

To get the name of your wireless interface, do:

The name of the interface will be output after the word «Interface». For example, it is commonly wlan0 .

Get the status of the interface

To check link status, use the following command.

You can get statistic information, such as the amount of tx/rx bytes, signal strength etc., with the following command:

Activate the interface

Some cards require that the kernel interface be activated before you can use iw or wireless_tools:

To verify that the interface is up, inspect the output of the following command:

The UP in
is what indicates the interface is up, not the later state DOWN .

Discover access points

To see what access points are available:

The important points to check:

• SSID: the name of the network.
• Signal: is reported in a wireless power ratio in dBm (e.g. from -100 to 0). The closer the negative value gets to zero, the better the signal. Observing the reported power on a good quality link and a bad one should give an idea about the individual range.
• Security: it is not reported directly, check the line starting with capability . If there is Privacy , for example capability: ESS Privacy ShortSlotTime (0x0411) , then the network is protected somehow.
  • If you see an RSN information block, then the network is protected by Robust Security Network protocol, also known as WPA2.
  • If you see an WPA information block, then the network is protected by Wi-Fi Protected Access protocol.
  • In the RSN and WPA blocks, you may find the following information:
    • Group cipher: value in TKIP, CCMP, both, others.
    • Pairwise ciphers: value in TKIP, CCMP, both, others. Not necessarily the same value than Group cipher.
    • Authentication suites: value in PSK, 802.1x, others. For home router, you will usually find PSK (i.e. passphrase). In universities, you are more likely to find 802.1x suite which requires login and password. Then you will need to know which key management is in use (e.g. EAP), and what encapsulation it uses (e.g. PEAP). See #WPA2 Enterprise and Wikipedia:Authentication protocol for details.
  • If you see neither RSN nor WPA blocks but there is Privacy , then WEP is used.

Set operating mode

You might need to set the proper operating mode of the wireless card. More specifically, if you are going to connect an ad-hoc network, you need to set the operating mode to ibss :

Connect to an access point

Depending on the encryption, you need to associate your wireless device with the access point to use and pass the encryption key:

• No encryption
• WEP
  • using a hexadecimal or ASCII key (the format is distinguished automatically, because a WEP key has a fixed length):
  • using a hexadecimal or ASCII key, specifying the third set up key as default (keys are counted from zero, four are possible):
• Other
  • iw can only handle WEP. To connect using other encryption schemes, see the section on #Authentication below.

Regardless of the method used, you can check if you have associated successfully:

Authentication

This article or section needs expansion.

WPA2 Personal

WPA2 Personal, a.k.a. WPA2-PSK, is a mode of Wi-Fi Protected Access.

You can authenticate to WPA2 Personal networks using wpa_supplicant or iwd, or connect using a network manager. If you only authenticated to the network, then to have a fully functional connection, you will still need to assign the IP address(es) and routes either manually or using a DHCP client.

WPA2 Enterprise

WPA2 Enterprise is a mode of Wi-Fi Protected Access. It provides better security and key management than WPA2 Personal, and supports other enterprise-type functionality, such as VLANs and NAP. However, it requires an external authentication server, called RADIUS server, to handle the authentication of users. This is in contrast to Personal mode which does not require anything beyond the wireless router or access points (APs), and uses a single passphrase or password for all users.

The Enterprise mode enables users to log onto the Wi-Fi network with a username and password and/or a digital certificate. Since each user has a dynamic and unique encryption key, it also helps to prevent user-to-user snooping on the wireless network, and improves encryption strength.

This section describes the configuration of network clients to connect to a wireless access point with WPA2 Enterprise mode. See Software access point#RADIUS for information on setting up an access point itself.

For a comparison of protocols, see the following table.

MS-CHAPv2

WPA2-Enterprise wireless networks demanding MSCHAPv2 type-2 authentication with PEAP sometimes require pptpclient in addition to the stock ppp package. netctl seems to work out of the box without ppp-mppe, however. In either case, usage of MSCHAPv2 is discouraged as it is highly vulnerable, although using another method is usually not an option.

eduroam

eduroam is an international roaming service for users in research, higher education and further education, based on WPA2 Enterprise.

Manual/automatic setup

• wpa_supplicant can be configured directly by its configuration file or using its CLI/GUI front ends and used in combination with a DHCP client. See the examples in /usr/share/doc/wpa_supplicant/wpa_supplicant.conf for configuring the connection details.
• iwd#WPA Enterprise
• NetworkManager can create WPA2 Enterprise profiles with nmcli or the graphical front ends. nmtui does not support this (NetworkManager issue 376), but may use existing profiles.
• ConnMan needs a separate configuration file before connecting to the network. See connman-service.config(5) and ConnMan#Connecting to eduroam (802.1X) for details.
• netctl supports wpa_supplicant configuration through blocks included with WPAConfigSection= . See netctl.profile(5) for details.

WPA3 Personal

WPA3 Personal, a.k.a. WPA3-SAE, is a mode of Wi-Fi Protected Access.

Both wpa_supplicant and iwd support WPA3 Personal.

WPA3 Enterprise

WPA3 Enterprise is a mode of Wi-Fi Protected Access.

wpa_supplicant (since version 2:2.10-8) supports WPA3 Enterprise. See FS#65314.

Tips and tricks

Respecting the regulatory domain

The regulatory domain, or «regdomain», is used to reconfigure wireless drivers to make sure that wireless hardware usage complies with local laws set by the FCC, ETSI and other organizations. Regdomains use ISO 3166-1 alpha-2 country codes. For example, the regdomain of the United States would be «US», China would be «CN», etc.

Regdomains affect the availability of wireless channels. In the 2.4GHz band, the allowed channels are 1-11 for the US, 1-14 for Japan, and 1-13 for most of the rest of the world. In the 5GHz band, the rules for allowed channels are much more complex. In either case, consult this list of WLAN channels for more detailed information.

Regdomains also affect the limit on the effective isotropic radiated power (EIRP) from wireless devices. This is derived from transmit power/»tx power», and is measured in dBm/mBm (1dBm=100mBm) or mW (log scale). In the 2.4GHz band, the maximum is 30dBm in the US and Canada, 20dBm in most of Europe, and 20dBm-30dBm for the rest of the world. In the 5GHz band, maximums are usually lower. Consult the wireless-regdb for more detailed information (EIRP dBm values are in the second set of brackets for each line).

Misconfiguring the regdomain can be useful — for example, by allowing use of an unused channel when other channels are crowded, or by allowing an increase in tx power to widen transmitter range. However, this is not recommended as it could break local laws and cause interference with other radio devices.

The kernel loads the database directly when wireless-regdb is installed. For direct loading, the kernel should, for security’s sake, be configured with CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS set to yes to allow for cryptographic verification of the database. This is true of the stock Arch kernel, but if you are using an alternate kernel, or compiling your own, you should verify this. More information is available at this guide.

To configure the regdomain, install wireless-regdb and reboot (to reload the cfg80211 module and all related drivers). Check the boot log to make sure that the database is loaded and key verified by cfg80211 :

The current regdomain can be set to the United States with:

And queried with:

However, setting the regdomain may not alter your settings. Some devices have a regdomain set in firmware/EEPROM, which dictates the limits of the device, meaning that setting regdomain in software can only increase restrictions, not decrease them. For example, a CN device could be set in software to the US regdomain, but because CN has an EIRP maximum of 20dBm, the device will not be able to transmit at the US maximum of 30dBm.

For example, to see if the regdomain is being set in firmware for an Atheros device:

For other chipsets, it may help to search for «EEPROM», «regdomain», or simply the name of the device driver.

To see if your regdomain change has been successful, and to query the number of available channels and their allowed transmit power:

A more permanent configuration of the regdomain can be achieved through editing /etc/conf.d/wireless-regdom and uncommenting the appropriate domain.

wpa_supplicant can also use a regdomain in the country= line of /etc/wpa_supplicant/wpa_supplicant.conf .

It is also possible to configure the cfg80211 kernel module to use a specific regdomain by adding, for example, options cfg80211 ieee80211_regdom=JP as module options. The module option is inherited from the old regulatory implementation and in modern kernels act as a userspace regulatory hint as if it came through nl80211 through utilities like iw and wpa_supplicant .

Rfkill caveat

Many laptops have a hardware button (or switch) to turn off the wireless card; however, the card can also be blocked by the kernel. This can be handled by rfkill. To show the current status:

If the card is hard-blocked, use the hardware button (switch) to unblock it. If the card is not hard-blocked but soft-blocked, use the following command:

Hardware buttons to toggle wireless cards are handled by a vendor specific kernel module. Frequently, these are WMI modules. Particularly for very new hardware models, it happens that the model is not fully supported in the latest stable kernel yet. In this case, it often helps to search the kernel bug tracker for information and report the model to the maintainer of the respective vendor kernel module, if it has not happened already.

Power saving

Troubleshooting

This section contains general troubleshooting tips, not strictly related to problems with drivers or firmware. For such topics, see next section #Troubleshooting drivers and firmware.

Temporary internet access

If you have problematic hardware and need internet access to, for example, download some software or get help in forums, you can make use of Android’s built-in feature for internet sharing via USB cable. See Android tethering#USB tethering for more information.

Observing logs

A good first measure to troubleshoot is to analyze the system’s logfiles first. In order not to manually parse through them all, it can help to open a second terminal/console window and watch the kernels messages with

while performing the action, e.g. the wireless association attempt.

When using a tool for network management, the same can be done for systemd with

Frequently, a wireless error is accompanied by a deauthentication with a particular reason code, for example:

Looking up the reason code might give a first hint. Maybe it also helps you to look at the control message flowchart, the journal messages will follow it.

The individual tools used in this article further provide options for more detailed debugging output, which can be used in a second step of the analysis, if required.

Failed to get IP address

The factual accuracy of this article or section is disputed.

This article or section is out of date.

• If getting an IP address repeatedly fails using the default dhcpcd client, try installing and using dhclient instead. Do not forget to select dhclient as the primary DHCP client in the connection manager.

• If you can get an IP address for a wired interface and not for a wireless interface, try disabling the wireless card’s power saving features (specify off instead of on ).

• If you get a timeout error due to a waiting for carrier problem, then you might have to set the channel mode to auto for the specific device:

Before changing the channel to auto, make sure your wireless interface is down. After it has successfully changed it, you can bring the interface up again and continue from there.

Valid IP address but cannot resolve host

If you are on a public wireless network that may have a captive portal, make sure to query an HTTP page (not an HTTPS page) from your web browser, as some captive portals only redirect HTTP. If this is not the issue, check if you can resolve domain names, it may be necessary to use the DNS server advertised via DHCP.

Setting RTS and fragmentation thresholds

Wireless hardware disables RTS and fragmentation by default. These are two different methods of increasing throughput at the expense of bandwidth (i.e. reliability at the expense of speed). These are useful in environments with wireless noise or many adjacent access points, which may create interference leading to timeouts or failing connections.

Packet fragmentation improves throughput by splitting up packets with size exceeding the fragmentation threshold. The maximum value (2346) effectively disables fragmentation since no packet can exceed it. The minimum value (256) maximizes throughput, but may carry a significant bandwidth cost.

RTS improves throughput by performing a handshake with the access point before transmitting packets with size exceeding the RTS threshold. The maximum threshold (2347) effectively disables RTS since no packet can exceed it. The minimum threshold (0) enables RTS for all packets, which is probably excessive for most situations.

Random disconnections

Cause #1

If your journal says wlan0: deauthenticating from MAC by local choice (reason=3) and you lose your Wi-Fi connection, it is likely that you have a bit too aggressive power-saving on your Wi-Fi card. Try disabling the wireless card’s power saving features (specify off instead of on ).

If your card does not support enabling/disabling power save mode, check the BIOS for power management options. Disabling PCI-Express power management in the BIOS of a Lenovo W520 resolved this issue.

Cause #2

If you are experiencing frequent disconnections and your journal shows messages such as

ieee80211 phy0: wlan0: No probe response from AP xx:xx:xx:xx:xx:xx after 500ms, disconnecting

try changing the channel bandwidth to 20MHz through your router’s settings page.

Cause #3

On some laptop models with hardware rfkill switches (e.g., Thinkpad X200 series), due to wear or bad design, the switch (or its connection to the mainboard) might become loose over time resulting in seemingly random hardblocks/disconnects when you accidentally touch the switch or move the laptop. There is no software solution to this, unless your switch is electrical and the BIOS offers the option to disable the switch. If your switch is mechanical (and most are), there are lots of possible solutions, most of which aim to disable the switch: Soldering the contact point on the mainboard/wifi-card, gluing or blocking the switch, using a screw nut to tighten the switch or removing it altogether.

Cause #4

Another cause for frequent disconnects or a complete failure to connect may also be a sub-standard router, incomplete settings of the router, interference by other wireless devices or low quality signal.

To troubleshoot, first try to connect to the router with no authentication and by getting closer to it.

If that works, enable WPA/WPA2 again but choose fixed and/or limited router settings. For example:

• If the router is considerably older than the wireless device you use for the client, test if it works with setting the router to one wireless mode
• Disable mixed-mode authentication (e.g. only WPA2 with AES, or TKIP if the router is old)
• Try a fixed/free channel rather than «auto» channel (maybe the router next door is old and interfering)
• Disable WPS
• Change the router’s 5 GHz channel(s) to a non-DFS (Dynamic Frequency Selection) channel. Connections on such channels may be dropped or suddenly switched due to interference from nearby weather radar.
• Try setting your client to 2.4 GHz only instead of letting it choose what it thinks is best between 5 GHz and 2.4 GHz (the later has a lower throughput but will provide a more stable connection over longer distances)
• Disable 40MHz channel bandwidth (lower throughput but less likely collisions) with cfg80211.cfg80211_disable_40mhz_24ghz=1
• If the router has quality of service settings, check completeness of settings (e.g. Wi-Fi Multimedia (WMM) is part of optional QoS flow control. An erroneous router firmware may advertise its existence although the setting is not enabled)

Cause #5

On some wireless network adapters (e.g. Qualcomm Atheros AR9485), random disconnects can happen with a DMA error:

A possible workaround is to disable the Intel IOMMU driver (DMA), adding intel_iommu=off to the kernel parameters [3].

Cause #6

If you are using a device with iwlwifi and iwlmvm for wireless connectivity, and your Wi-Fi card appears to disappear when on battery power (perhaps after a reboot or resuming from suspend), this can be fixed by configuring power saving settings in iwlmvm.

Create the file /etc/modprobe.d/iwlmvm.conf if it does not exist already, then add the following line to it:

A power_scheme of 1 sets iwlmvm to «Always Active.» Available options are:

Value	Description
1	Always Active
2	Balanced
3	Low-power

This fix was discovered at [4].

Cause #7

If your device undergoes long periods of inactivity (e.g. a file server), the disconnection may be due to power saving, which will block incoming traffic and prevent connections. Try disabling power saving for the interface:

You can create a udev rule to do this on boot, see Power management#Network interfaces.

Wi-Fi networks invisible because of incorrect regulatory domain

If the computer’s Wi-Fi channels do not match those of the user’s country, some in-range Wi-Fi networks might be invisible because they use wireless channels that are not allowed by default. The solution is to configure the regulatory domain correctly; see #Respecting the regulatory domain.

Troubleshooting drivers and firmware

This section covers methods and procedures for installing kernel modules and firmware for specific chipsets, that differ from generic method.

See Kernel modules for general information on operations with modules.

Ralink/Mediatek

rt2x00

Unified driver for Ralink chipsets (it replaces rt2500 , rt61 , rt73 , etc). This driver has been in the Linux kernel since 2.6.24, you only need to load the right module for the chip: rt2400pci , rt2500pci , rt2500usb , rt61pci or rt73usb which will autoload the respective rt2x00 modules too.

A list of devices supported by the modules is available at the project’s homepage.

Additional notes

• Since kernel 3.0, rt2x00 includes also these drivers: rt2800pci , rt2800usb .
• Since kernel 3.0, the staging drivers rt2860sta and rt2870sta are replaced by the mainline drivers rt2800pci and rt2800usb [5].
• Some devices have a wide range of options that can be configured with iwpriv . These are documented in the source tarballs available from Ralink.

rt3090

For devices which use the rt3090 chipset, it should be possible to use the rt2800pci driver; however, it does not work with this chipset very well (e.g. sometimes it is not possible to use higher rate than 2Mb/s).

rt3290

The rt3290 chipset is recognised by the kernel rt2800pci module. However, some users experience problems and reverting to a patched Ralink driver seems to be beneficial in these cases.

rt3573

New chipset as of 2012. It may require proprietary drivers from Ralink. Different manufacturers use it; see the Belkin N750 DB wireless usb adapter forums thread.

mt7612u

New chipset as of 2014, released under their new commercial name Mediatek. It is an AC1200 or AC1300 chipset. Manufacturer provides drivers for Linux on their support page. As of kernel 5.5 it should be supported by the included mt76 driver.

Realtek

See [6] [dead link 2022-11-10] for a list of Realtek chipsets and specifications.

rtl8192cu

The driver is now in the kernel, but many users have reported being unable to make a connection although scanning for networks does work.

8192cu-dkms AUR includes many patches; try this if it does not work fine with the driver in kernel.

rtl8723ae/rtl8723be

The rtl8723ae and rtl8723be modules are included in the mainline Linux kernel.

Some users may encounter errors with powersave on this card. This is shown with occasional disconnects that are not recognized by high level network managers (netctl, NetworkManager). This error can be confirmed by running dmesg -w as root or journalctl -f as root and looking for output related to powersave and the rtl8723ae / rtl8723be module. If you have this issue, use the fwlps=0 kernel option which should prevent the WiFi card from automatically sleeping and halting connection. See Kernel module#Setting module options.

If you have poor signal, perhaps your device has only one physical antenna connected, and antenna autoselection is broken. You can force the choice of antenna with ant_sel=1 or ant_sel=2 kernel option. [7]

rtl88xxau

Realtek chipsets rtl8811au, rtl8812au, rtl8814au and rtl8821au designed for various USB adapters ranging from AC600 to AC1900. Several packages provide various kernel drivers, these require DKMS (the dkms package and the kernel headers installed):

Chipset	Package	Notes
rtl8811au, rtl8812au, rtl8821au	rtl88xxau-aircrack-dkms-git AUR	Aircrack-ng kernel module for 8811au, 8812au and 8821au chipsets with monitor mode and injection support.
rtl8812au	rtl8812au-dkms-git AUR	Latest official Realtek driver version for rtl8812au only.
rtl8811au, rtl8821au	rtl8821au-dkms-git AUR	Newer driver version for rtl8821au.
rtl8814au	rtl8814au-dkms-git AUR	Possibly works for rtl8813au too.

rtl8811cu/rtl8821cu

rtl8821cu-dkms-git AUR provides a kernel module for the Realtek 8811cu and 8821cu chipset.

This requires DKMS, so make sure you have your proper kernel headers installed.

If no wireless interface shows up even though the 8821cu module is loaded, you may need to manually specify the rtw_RFE_type option [8][9]. Try e.g. rtw_RFE_type=0x26 , other values might also work. See Kernel module#Setting module options for details.

rtl8821ce

rtl8821ce-dkms-git AUR provides a kernel module for the Realtek 8821ce chipset found in the Asus X543UA.

This requires DKMS, so make sure you have your proper kernel headers installed.

rtl8822bu

rtl88x2bu-dkms-git AUR provides a kernel module for the Realtek 8822bu chipset found in the Edimax EW7822ULC USB3, Asus AC53 Nano USB 802.11ac and TP-Link Archer T3U adapter.

This requires DKMS, so make sure you have your proper kernel headers installed.

rtl8xxxu

This article or section needs expansion.

Issues with the rtl8xxxu mainline kernel module may be solved by compiling a third-party module for the specific chipset. The source code can be found in GitHub repositories.

Some drivers may be already prepared in the AUR, e.g. rtl8723bu-dkms-git AUR .

RTW88

An RTW88 kernel module patchset has been recently posted to the kernel mailing list, which should hopefully make it into the mainstream kernel.

Upstream kernels or those with the patchset will support most RTW88 chip devices if configured and compiled to do so. linux-zen and linux-zen-git AUR both include these patches, with the packaged version already having the module built.

The driver supports: 882BE, 8822BU, 8822CE, 8822CU, 8723DE, 8723DU, 8821CE, and 8821CU.

Atheros

The MadWifi team currently maintains three different drivers for devices with Atheros chipset:

• madwifi is an old, obsolete driver. Not present in Arch kernel since 2.6.39.1[11].
• ath5k is a newer driver which replaces the madwifi driver. Currently a better choice for some chipsets, but not all chipsets are supported (see below)
• ath9k is the newest of these three drivers. It is intended for newer Atheros chipsets. All of the chips with 802.11n capabilities are supported.

There are some other drivers for some Atheros devices. See Linux Wireless documentation for details.

ath5k

If you find web pages randomly loading very slow, or if the device is unable to lease an IP address, try to switch from hardware to software encryption by loading the ath5k module with nohwcrypt=1 option. See Kernel modules#Setting module options for details.

Some laptops may have problems with their wireless LED indicator flickering red and blue. To solve this problem, do:

For alternatives, see this bug report.

ath9k

As of Linux 3.15.1, some users have been experiencing a decrease in bandwidth. In some cases, this can fixed by setting the nohwcrypt=1 option for the ath9k module. See Kernel module#Setting module options.

An ath9k mailing list exists for support and development related discussions.

Power saving

Although Linux Wireless says that dynamic power saving is enabled for Atheros ath9k single-chips newer than AR9280, for some devices (e.g. AR9285), powertop might still report that power saving is disabled. In this case, enable it manually.

On some devices (e.g. AR9285), enabling the power saving might result in the following error:

The solution is to set the ps_enable=1 option for the ath9k module; see Kernel module#Setting module options.

Intel

iwlegacy

iwlegacy is the wireless driver for Intel’s 3945 and 4965 wireless chips. The firmware is included in the linux-firmware package.

udev should load the driver automatically, otherwise load iwl3945 or iwl4965 manually. See Kernel modules for details.

If you have problems connecting to networks in general (e.g. random failures with your card on bootup or your link quality is very poor), try to disable 802.11n:

If the failures persist during bootup and you are using Nouveau driver, try enabling early KMS to prevent the conflict [12].

iwlwifi

iwlwifi is the wireless driver for Intel’s current wireless chips, such as 5100AGN, 5300AGN, and 5350AGN. See the full list of supported devices. The firmware is included in the linux-firmware package. The linux-firmware-iwlwifi-git AUR may contain some updates sooner.

If you have problems connecting to networks in general or your link quality is very poor, try to disable 802.11n, and perhaps also enable software encryption:

If you have a problem with slow uplink speed in 802.11n mode, for example 20Mbps, try to enable antenna aggregation:

Do not be confused with the option name, when the value is set to 8 it does not disable anything but re-enables transmission antenna aggregation.[13] [14]

In case this does not work for you, you may try disabling power saving for your wireless adapter.

Some have never gotten this to work. Others found salvation by disabling N in their router settings after trying everything. This is known to have been the only solution on more than one occasion. The second link there mentions a 5ghz option that might be worth exploring.

If you have an 802.11ax (WiFi 6) access point and have problems detecting the beacons or an unreliable connection, review Intel Article 54799.

Bluetooth coexistence

If you have difficulty connecting a bluetooth headset and maintaining good downlink speed, try disabling bluetooth coexistence [15]:

Firmware issues

You may have some issue where the driver outputs stack traces & errors, which can cause some stuttering.

To confirm it is the cause of the issues, downgrade the package linux-firmware .

If confirmed, move the buggy firmware files so that an older version is loaded (to be able to have an up to date linux-firmware since it is not only providing firmware updates for your Intel WiFi card):

To avoid having to repeat these steps manually after each update, use the NoExtract array in pacman.conf with a wildcard to block their installation. See pacman#Skip files from being installed to system.

Adapter not detected after booting from Windows

If the WiFi adapter is not getting detected after finishing a session in Windows, this might be due to Windows’ Fast Startup feature which is enabled by default. Try disabling Fast Startup. The iwlwifi kernel driver wiki has an entry for this.

Disabling LED blink

The default settings on the module are to have the LED blink on activity. Some people find this extremely annoying. To have the LED on solid when Wi-Fi is active, you can use the systemd-tmpfiles:

Run systemd-tmpfiles —create phy0-led.conf for the change to take effect, or reboot.

To see all the possible trigger values for this LED:

Broadcom

Other drivers/devices

Tenda w322u

Treat this Tenda card as an rt2870sta device. See #rt2x00.

orinoco

This should be a part of the kernel package and be installed already.

Some Orinoco chipsets are Hermes II. You can use the wlags49_h2_cs driver instead of orinoco_cs and gain WPA support. To use the driver, blacklist orinoco_cs first.

prism54

The driver p54 is included in kernel, but you have to download the appropriate firmware for your card from this site and install it into the /usr/lib/firmware directory.

zd1211rw

zd1211rw is a driver for the ZyDAS ZD1211 802.11b/g USB WLAN chipset, and it is included in recent versions of the Linux kernel. See [16] for a list of supported devices. You only need to install the firmware for the device, provided by the zd1211-firmware AUR package.

hostap_cs

Host AP is a Linux driver for wireless LAN cards based on Intersil’s Prism2/2.5/3 chipset. The driver is included in Linux kernel.

ndiswrapper

Ndiswrapper is a wrapper script that allows you to use some Windows drivers in Linux. You will need the .inf and .sys files from your Windows driver.

Follow these steps to configure ndiswrapper.

1. Install ndiswrapper-dkms .
2. Install the driver to /etc/ndiswrapper/ :
3. List all installed drivers for ndiswrapper:
4. Let ndiswrapper write its configuration in /etc/modprobe.d/ndiswrapper.conf :

The ndiswrapper install is almost finished; you can load the module at boot.

Test that ndiswrapper will load now:

and wlan0 should now exist. If you have problems, some help is available at: ndiswrapper howto and ndiswrapper FAQ.

Источник

Here is the WhatsMiner checklist of error code and we strongly recommend every WhatsMiner user to keep it because almost 80% of the problems can be solved by corresponding solutions.

We hope it is helpful for all WhatsMiner users. For rest of the problems, Kindly reach us and we’re willing to help.

Meaning of Error Code and Corresponding Solutions on WhatsM liner Tool 1
Error Code	Meaning	Corresponding Solutions
110	Inlet fan detcction speed error	Check whether the fan connction is normal, or replace the power supply, or replace the fan
111	Outlet fan detection speed error
120	Inlet fan speed error（Deviation 2000+）
121	Outlet fan speed error（Deviation 2000+）
130	Inlet fan speed error
131	Outlet fan spced error
140	Fan speed is too high	Please check the environment temperature
200	Power detection error	Detecting the power output cable, or updating the latest firmware, or replacing the power supply
201	Power does not match the configuration file	Updating to the latest software
202	Power output voltage error	Updating to the latest software or check the power supply
203	Power supply protection	Please check the environment temperature
204	Power supply current protection
205	Power current error	Inspection of power supply in power grid
206	Power input voltage is low	Improve power supply conditions and input voltage
207	Power input current protecting
210	Power status error	Check the power failure code
213	Power input voltage and current do not match the power	Replace the PSU
216	Power remained unchanged for a long time
217	Power set enable error
218	Power input voltage is lower than 230V for high power mode	Increase input voltage，replace power supply
233	Overtemperature Protection of Power Output	Plcase check the environment temperature
234	Overtemperature Protection of Power Output
235	Overtemperature Protection of Power Output
236	Overcurrent Protection of Power Output	Please check the environment temperature and the copper wire screw(Recommend to use the protable electric screwdriver)
237	Overcurrent Protection of Power Output
238	Overcurrent Protection of Power Output
239	Overvoltage Protection of Power Output	Check grid power
240	Low Voltage Protection for Power Output
241	Power output current imbalance	Replace the power
243	Over-tempcrature Protection for Power Input	Please check the environment temperature
244	Over-temperature Protection for Power Input
245	Over-tempcrature Protection for Power Input
246	Overcurrent Protection for Power Input
247	Overcurrent Protection for Power Input
248	Overvoltage Protection for Power Input	Check grid power
249	Overvoltage Protection for Power Input
250	Undervoltage Protection for Power Input
251	Undervoltage Protection for Power Input
253	Power Fan Error	Replace the power supply
254	Power Fan Error
255	Protection of over power output	Please check the environment temperature
256	Protection of over power output
257	Input over current protection of power supply primary side	Try to power off and restart, no effect to replace the power supply
263	Power communication warning	Check whether the screws of the control board are locked
264	Power communication error
267	Power watchdog protection	Contact the technician in time
268	Power output over-current protection	Check the ambient temperature, check the copper bar screw
269	Power input over-current protection	Improve power supply conditions and input voltage
270	Power input over-voltage protection	Inspection of input voltage in power grid
271	Power input under-voltage protection
272	Warning of excessive power output of power supply	Please check the environment temperature
273	Power input power too high warning
274	Power fan warning	Check if the power fan is blocked and may need to be replaced
275	Power over temperature warning	Please check the environment temperature

Meaning of Error Code and Corresponding Solutions on WhatsMiner Tool 2
Error Code	Meaning	Corresponding Solutions
300	SM0 temperature sensor detection error	Check the connection of the hash board
301	SM1 temperature sensor detection error
302	SM2 temperature sensor detection error
320	SM0 board temperature sensor communication error	Check if the control panel screws are locked, check the adapter plate and the cable contacts
321	SM1 board temperature sensor communication error
322	SM2 board temperature sensor communication error
329	Control board temperature sensor communication error	Replace the power supply
350	SM0 tempcrature protection	Check the environment temperature (Recommend to use the GS320 infrared thermometer）
351	M1 tempcrature protection
352	SM2 tempcrature protection
360	The temperature of the hash board is overheating
410	SMO detect eeprom error	Check adapter plate and cable contact
411	SM1 detect eeprom error
412	SM2 detect eeprom error
420	SM0 parser eeprom error	Upgrade firmware
421	SM1 parser eeprom error
422	SM2 parser eeprom error
430	SM0 chip bin type error
431	SM1 chip bin type error
432	SM2 chip bin type error
440	SM0 eeprom chip num X error
441	SM1 eeprom chip num X error
442	SM2 eeprom chip num X error
450	SM0 eeprom xfer error	Check adapter board and wiring contacts.Upgrade firmware
451	SM1 eeprom xfer error
452	SM2 eeprom xfer error
510	SM0 miner type error	The version and type of hashboard are inconsistent, replace the correct hashboard
511	SM1 miner type error
512	SM2 miner type error
520	SM0 bin type error	If the chip type of the hash board is inconsistent, replace the correct hash board.
521	SM1 bin type error
522	SM2 bin type error
530	SM0 board is not detected	Check the adapter board wiring and cablc, or replace the control board to check whether the hash board connector is soldered
531	SM1 board is not detected
532	SM2 board is not detected
540	The number of SM0 chips is incomplete	Check adapter plate and cable contact
541	The number of SM1 chips is incomplete
542	The number of SM2 chips is incomplete
550	SM0 has bad chips	Replace the bad chip in the print position
551	SM1 has bad chips
552	SM2 has bad chips
560	SM0 loss balance	Plug in the adapter plate, and then screw in the power connection hash board again
561	SM1 loss balance
562	SM2 loss balance
590	SM0 frequency is too low	Replace the hash board and place the hash boards which reported the same error together
591	SM1 frequency is too low
592	SM2 frequency is too low
600	Environment temperature is too high	Check the environment temperature
610	If the ambient temperature is too high in high performance mode, return to normal mode	Check the ambient temperature, high performance mode needs to be ontrolled below 30 ℃
701	Control board no support chip	Upgrade the corresponding type of firmware
710	Control board error	Update to the latest firmware
712	Control board rebooted as exception	Updating the latest firmware.Check whether the control board screw is locked properly
800	cgminer checksum error	Re-upgrade firmware
801	system-monitor checksum error
802	system-monitor checksum error
2000	No pool information configured	Check pool configuration
2010	All mining pool connections failed	Check the network or mining pools setting
2020	Mining pool0 connection failed
2021	Mining pool1 connection failed
2022	Mining pool2 connection failed
2030	Mining pool rejcction rate is too high	Check the network or mining pool setting, and the mining setting of the cryptocurrency
2040	The pool does not support the asicboost mode	Check pool configuration
2310	Hash rate is too low	Check input voltage, network environment, and ambient temperature
2320	Hash rate is too low
2340	The loss of hash rate is too high
2350	The loss of hash rate is too high
5070	SM0 water velocity is abnormal	Check if the water flow is normal
5071	SM1 water velocity is abnormal
5072	SM2 water velocity is abnormal
5110	SM0 Frequency Up Timeout	reboot
5111	SM1 Frequency Up Timeout
5112	SM2 Frequency Up Timeout
8410	Software version error (M2x miner with M3x firmware, or M3x with M2x firmware)	Upgrade to the correct firmware version
100001	/antiv/signature Illegal	Upgrade the latest firmware or burn the card
100002	/antiv/dig/initd.dig Illegal
100003	/antiv/dig/pf_partial.dig Illegal

PSU Error code	Reason	processing method
0x0001	Input undervoltage	Check the power supply
0x0002	Temperature sampling over temperature protection of power radiator	Power on again after 10 minutes of power failure. If it occurs again, replace the power supply
0x0004	Temperature sampling over temperature protection of power radiator
0x0008	Over temperature protection of environmental emperature sampling in power supply
0x0010	Primary side over current	Power on again after 10 minutes of power failure. If it occurs again, replace the power supply
0x0020	Output undervoltage	Check the power supply
0x0040	Output over current (continuous load 320A for more than 2S)	Tighten the copper bar screw again
0x0080	Primary side over current	Power on again after 10 minutes of power failure. If it occurs again, replace the power supply
0x0100	Single circuit overcurrent (protection point 120a)	Check the PSU
0x0200	Single circuit overcurrent (protection point 120a)
0x0400	Single circuit overcurrent (protection point 120a)
0x0800	Fan failure	Replace the PSU
0x1000	Output over current (continuous load of 310A for more than 5min)	Check the PSU
0x2000	Output over current (continuous load 295A for more than 10min)

We hope it is helpful for all WhatsMiner users. For rest of the problems, Kindly reach us and we’re willing to help.

Ошибки Видеокарты При Майнинге

Зарабатывай на чужих сделках на бирже BingX. Подробнее — тут.

UNABLE TO ENUM CUDA GPUS: INVALID DEVICE ORDINAL

UNABLE TO ENUM CUDA GPUS: INSUFFICIENT CUDA DRIVER: 5000

NBMINER MINING PROGRAM UNEXPECTED EXIT.CODE: -1073740791, REASON: PROCESS CRASHED

NBMINER CUDA ERROR: OUT OF MEMORY (ERR_NO=2) — как исправить?

GMINER ERROR ON GPU: OUT OF MEMORY STOPPED MINING ON GPU0

Socket error. the remote host closed the connection, в майнере Nbminer

Server not responded on share, на майнере Gminer

DAG has been damaged check overclocking settings, в майнере Gminer

ERROR: Can’t start T-Rex, failed to initialize device map: can’t get busid, code -6

Ошибки настройки памяти с кодом -6 обычно указывают на проблему с драйвером.

Если у вас Windows, используйте программу DDU (DisplayDriverUninstaller), чтобы полностью удалить все драйверы Nvidia.
Перезагрузите систему.
Установите новый драйвер прямо с сайта Nvidia.
Перезагрузите систему снова.
Если у вас HiveOS/RaveOS — накатите чистый образ системы. Чтобы наверняка. 🙂

TREX: Can’t unlock GPU

Полный текст ошибки:
TREX: Can’t unlock GPU [ID=1, GPU #1], error code 15
WARN: Miner is going to shutdown.
WARN: NVML: can’t get fan speed for GPU #1, error code 15
WARN: NVML: can’t get power for GPU #1, error code 15
WARN: NVML: can’t get mem/core clock for GPU #1, error code 17

Решение:

1. Проверьте все кабельные соединения видеокарты и райзера, особенно кабеля питания.
2. Если с первый пунктом все ок, попробуйте поменять райзер на точно рабочий.
3. Если ошибка остается, вставьте видеокарту в разъем х16 напрямую в материнскую плату.

CAN’T START MINER, FAILED TO INITIALIZE DEVIS MAP, CAN’T GET BUSID, CODE -6

Зарабатывай на чужих сделках на бирже BingX. Подробнее — тут.

ОШИБКА 511 ГРАДУСОВ НА ВИДЕОКАРТА

GPU driver error, no temps в HiveOS — что делать?

Вероятнее всего, вы получили эту ошибку, майнив на HiveOS. Причин ее появления может быть несколько — как софтовая, так и аппаратная (например райзер).
Можно попробовать обойтись малой кровью и вбить в HiveOS команду:
hive-replace -y —stable
Система по новой накатит стабильную версию HiveOS.

Если ошибка не уйдет — проверьте райзер.

GPU are lost, rebooting

Это не ошибка, а ее последствие. Что узнать какая ошибка приводит к перезагрузке карт, сделайте следующее:

Включите сохранение логов (по умолчанию они выключены) командой

И перезагрузите риг.
После того как ошибка повторится можно будет скачать логи командами ниже.
Вы можете использовать следующую команду, чтобы загрузить логи майнера прямо с панели мониторинга;

message file «miner.log» -f=/var/log/miner/minername/minername.log

Итак, скажем, например, мне нужны логи TeamRedMiner
message file «teamredminer.log» -f=/var/log/miner/teamredminer/teamredminer.log

Отправленная командная строка будет выделена синим цветом. Загружаемый файл будет отображаться белым цветом. Нажав на него, вы сможете его скачать.
Эта команда позволит скачать лог системы

message file «syslog» -f=/var/log/syslog

exitcode=3 в HiveOS

Вероятнее всего, вы получили эту ошибку, майнив на HiveOS. Причин ее появления может быть несколько — как софтовая, так и аппаратная (например райзер).
Можно попробовать обойтись малой кровью и вбить в HiveOS команду:
hive-replace -y —stable
Система по новой накатит стабильную версию HiveOS.

Если ошибка не уйдет — проверьте райзер.

exitcode=1 в HiveOS

Данная ошибка возникает когда есть проблема с датой в биосе материнской платы (сбитое время) и (или) есть проблема с интернетом.
Если сбито время, то удаленно вы не сможете подключиться.
Тем не менее, обновление драйверов Nvidia должно пройти командой:

gpu fault detected 146

Waiting interface to come up — не работает VPN на HiveOS

Как узнать ip адрес воркера hive os

Repository update failed в HiveOS

Rave os не запускается. Boot aborted Rave os

Перепроверьте все настройки ПК и БИОСа материнской платы:
— Установите загрузочное устройство HDD/SSD/M2/USB в зависимости от носителя с ОС.
— Включите 4G decoding.
— Установите поддержку PCIe на Auto.
— Включите встроенную графику.
— Установите предпочтительный режим загрузки Legacy mode.
— Отключите виртуализацию.

Если после данных настроек не определяется часть карт, то выполните следующие настройки в BIOS (после каждого пункта требуется полная перезагрузка):

— Отключите 4G decoding
— Перезагрузка
— Отключите CSM
— Перезагрузка
— Включите 4G decoding, установите PCI-E Gen2/3, а при отсутствии Gen2/3, можно выбрать Gen1

Failed to allocate memory Raveos

Эта же ошибка может называться как:
failed to allocate initramfs memory bailing out, failed to load idlinux c.32
или
failed to allocate memory for kernel boot parameter block
или
failed to allocate initramfs memory raveos bailing

Но решение у нее одно — вы должны правильно настроить БИОС материнской платы.

gpu_driver_fault, GPU #0 fault в RaveOS

gpu_driver_fault, GPU #0 fault в RaveOS

Gpu driver fault. All tasks have been stopped. Worker will be rebooted after 5 minutes в RaveOS

Miner restarted after error RaveOS

Miner restart limit reached. Worker rebooting by flag auto в RaveOS

Miner cannot be started, ОС RaveOS

Непосредственно перед этой ошибкой обычно пишется еще другая, которая и вызывает эту проблему. Но если ничего нет, то:

1. Поставьте майнер на паузу, перезагрузите риг и в консоли выполните команды clear-miners clear-logs и fix-fs. Запустите майнинг.
2. Если ошибка не ушла, перепишите образ RaveOS.

Overclock can’t be applied в RaveOS

Error installing hive miners

Можно попробовать обойтись малой кровью и вбить в HiveOS команду:
hive-replace -y —stable
Система по новой накатит стабильную версию HiveOS.

Если ошибка не уйдет — физически перезапишите образ. Если у вас флешка, то скорее всего она умерла. Купите SSD. 🙂

Warning: Nvidia settings applied with errors

Nvtool error или Danger: nvtool error

Перестал отображаться кулер видеокарты HiveOS

ERROR: parsing JSON failed

Необходимо выполнить на риге локально (с клавиатурой и монитором) следующую команду:
net-test

Данная команда покажет ваше текущее состояние подключения к разным зеркалам API серверов HiveOS.
Посмотрите, к какому API у вас наименьшая задержка (ping), и когда воркер снова появится в панели, измените стандартное зеркало на то, что ближе к вам.
После смены зеркала, в обязательном порядке перезагрузите ваш воркер.
Изменить сервер API вы можете командой nano /hive-config/rig.conf
После смены нажмите ctrl + o и ентер для того чтобы сохранить файл.
После этого выйдите в консоль командой ctrl + x, f10 и выполните команду hello

NVML: can’t get fan speed for GPU #5, error code 999 hive os

Can’t get power for GPU #2

Как правило эта ошибка встречается рядом вместе с другими:
Attribute ‘GPUGraphicsClockOffset’ was already set to 0
Attribute ‘GPUMemoryTransferRateOffset’ was already set to 2200
Attribute ‘GPUFanControlState’ (hive1660s_ETH:0[gpu:2]) assigned value
0.

20211029 12:40:50 WARN: NVML: can’t get fan speed for GPU #2, error code 999
20211029 12:40:50 WARN: NVML: can’t get power for GPU #2, error code 999
20211029 12:40:50 WARN: NVML: can’t get mem/core clock for GPU #2, error code 999

Решение:

Проверьте корректность установки драйвера на видеокарте.
Убедитесь что нет проблем с драйвером, если все в порядке, то попробуйте другой параметр разгона. Например уменьшить разгон по памяти.

GPU1 search error: unspecified launch failure

Warning: Autofan: unable to set fan speed, rebooting

Найдите логи майнера, посмотрите какие ошибки майнер пишет в логах. Например:

kernel: [12112.410046][ T7358] NVRM: GPU at PCI:0000:0c:00: GPU-236e3bef-2e03-6cdb-0518-7ac01eb8736d
kernel: [12112.410049][ T7358] NVRM: Xid (PCI:0000:0c:00): 62, pid=7317, 0000(0000) 00000000 00000000
kernel: [12112.433831][ T7358] NVRM: Xid (PCI:0000:0c:00): 45, pid=7317, Ch 00000010
CRON[21094]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

Исходя из логов, мы видим что есть проблема с видеокартой на слоте PCIE 0c:00 (под номером Gpu пишется номер PCIE слота) с ошибками 45 и 62
Коды ошибок (других, которые также могут быть там) и что с ними делать:

• 13, 43, 45: ошибки памяти, снизить MEM
• 8, 31, 32, 61, 62: снизить CORE, возможно и MEM
• 79: снизить CORE, проверить райзер

Источник

Network configuration/Wireless

The main article on network configuration is Network configuration.

Configuring wireless is a two-part process; the first part is to identify and ensure the correct driver for your wireless device is installed (they are available on the installation media, but often have to be installed explicitly), and to configure the interface. The second is choosing a method of managing wireless connections. This article covers both parts, and provides additional links to wireless management tools.

The #iw section describes how to manually manage your wireless network interface / your wireless LANs using iw . The Network configuration#Network managers section describes several programs that can be used to automatically manage your wireless interface, some of which include a GUI and all of which include support for network profiles (useful when frequently switching wireless networks, like with laptops).

Device driver

The default Arch Linux kernel is modular, meaning many of the drivers for machine hardware reside on the hard drive and are available as modules. At boot, udev takes an inventory of your hardware and loads appropriate modules (drivers) for your corresponding hardware, which will in turn allow creation of a network interface.

Some wireless chipsets also require firmware, in addition to a corresponding driver. Many firmware images are provided by the linux-firmware package; however, proprietary firmware images are not included and have to be installed separately. This is described in #Installing driver/firmware.

Check the driver status

To check if the driver for your card has been loaded, check the output of the lspci -k or lsusb -v command, depending on if the card is connected by PCI(e) or USB. You should see that some kernel driver is in use, for example:

Also check the output of the ip link command to see if a wireless interface was created; usually the naming of the wireless network interfaces starts with the letter «w», e.g. wlan0 or wlp2s0 . Then bring the interface up with:

For example, assuming the interface is wlan0 , this is ip link set wlan0 up .

Check kernel messages for firmware being loaded:

If there is no relevant output, check the messages for the full output for the module you identified earlier ( iwlwifi in this example) to identify the relevant message or further issues:

If the kernel module is successfully loaded and the interface is up, you can skip the next section.

Installing driver/firmware

Check the following lists to discover if your card is supported:

• See the table of existing Linux wireless drivers and follow to the specific driver’s page, which contains a list of supported devices. There is also a List of Wi-Fi Device IDs in Linux [dead link 2022-11-11] .
• The Ubuntu Wiki has a good list of wireless cards and whether or not they are supported either in the Linux kernel or by a user-space driver (includes driver name).
• Linux Wireless Support and The Linux Questions’ Hardware Compatibility List (HCL) also have a good database of kernel-friendly hardware.

Note that some vendors ship products that may contain different chip sets, even if the product identifier is the same. Only the usb-id (for USB devices) or pci-id (for PCI devices) is authoritative.

If your wireless card is listed above, follow the #Troubleshooting drivers and firmware subsection of this page, which contains information about installing drivers and firmware of some specific wireless cards. Then check the driver status again.

If your wireless card is not listed above, it is likely supported only under Windows (some Broadcom, 3com, etc). For these, you can try to use #ndiswrapper.

Utilities

Just like other network interfaces, the wireless ones are controlled with ip from the iproute2 package.

Managing a wireless connection requires a basic set of tools. Either use a network manager or use one of the following directly:

Software	Package	WEXT	nl80211	WEP	WPA/WPA2/WPA3	Archiso[1]
wireless_tools 1	wireless_tools	Yes	No	Yes	No	Yes
iw	iw	No	Yes	Yes	No	Yes
wpa_supplicant	wpa_supplicant	Yes	Yes	No	Yes	Yes
iwd	iwd	No	Yes	No	Yes	Yes

1. Deprecated.

Note that some cards only support WEXT.

iw and wireless_tools comparison

The table below gives an overview of comparable commands for iw and wireless_tools. See iw replaces iwconfig for more examples.

iw command	wireless_tools command	Description
iw dev wlan0 link	iwconfig wlan0	Getting link status.
iw dev wlan0 scan	iwlist wlan0 scan	Scanning for available access points.
iw dev wlan0 set type ibss	iwconfig wlan0 mode ad-hoc	Setting the operation mode to ad-hoc.
iw dev wlan0 connect your_essid	iwconfig wlan0 essid your_essid	Connecting to open network.
iw dev wlan0 connect your_essid 2432	iwconfig wlan0 essid your_essid freq 2432M	Connecting to open network specifying channel.
iw dev wlan0 connect your_essid key 0:your_key	iwconfig wlan0 essid your_essid key your_key	Connecting to WEP encrypted network using hexadecimal key.
iwconfig wlan0 essid your_essid key s:your_key	Connecting to WEP encrypted network using ASCII key.
iw dev wlan0 set power_save on	iwconfig wlan0 power on	Enabling power save.

Examples in this section assume that your wireless device interface is interface and that you are connecting to your_essid WiFi access point. Replace both accordingly.

Get the name of the interface

To get the name of your wireless interface, do:

The name of the interface will be output after the word «Interface». For example, it is commonly wlan0 .

Get the status of the interface

To check link status, use the following command.

You can get statistic information, such as the amount of tx/rx bytes, signal strength etc., with the following command:

Activate the interface

Some cards require that the kernel interface be activated before you can use iw or wireless_tools:

To verify that the interface is up, inspect the output of the following command:

The UP in
is what indicates the interface is up, not the later state DOWN .

Discover access points

To see what access points are available:

The important points to check:

• SSID: the name of the network.
• Signal: is reported in a wireless power ratio in dBm (e.g. from -100 to 0). The closer the negative value gets to zero, the better the signal. Observing the reported power on a good quality link and a bad one should give an idea about the individual range.
• Security: it is not reported directly, check the line starting with capability . If there is Privacy , for example capability: ESS Privacy ShortSlotTime (0x0411) , then the network is protected somehow.
  • If you see an RSN information block, then the network is protected by Robust Security Network protocol, also known as WPA2.
  • If you see an WPA information block, then the network is protected by Wi-Fi Protected Access protocol.
  • In the RSN and WPA blocks, you may find the following information:
    • Group cipher: value in TKIP, CCMP, both, others.
    • Pairwise ciphers: value in TKIP, CCMP, both, others. Not necessarily the same value than Group cipher.
    • Authentication suites: value in PSK, 802.1x, others. For home router, you will usually find PSK (i.e. passphrase). In universities, you are more likely to find 802.1x suite which requires login and password. Then you will need to know which key management is in use (e.g. EAP), and what encapsulation it uses (e.g. PEAP). See #WPA2 Enterprise and Wikipedia:Authentication protocol for details.
  • If you see neither RSN nor WPA blocks but there is Privacy , then WEP is used.

Set operating mode

You might need to set the proper operating mode of the wireless card. More specifically, if you are going to connect an ad-hoc network, you need to set the operating mode to ibss :

Connect to an access point

Depending on the encryption, you need to associate your wireless device with the access point to use and pass the encryption key:

• No encryption
• WEP
  • using a hexadecimal or ASCII key (the format is distinguished automatically, because a WEP key has a fixed length):
  • using a hexadecimal or ASCII key, specifying the third set up key as default (keys are counted from zero, four are possible):
• Other
  • iw can only handle WEP. To connect using other encryption schemes, see the section on #Authentication below.

Regardless of the method used, you can check if you have associated successfully:

Authentication

This article or section needs expansion.

WPA2 Personal

WPA2 Personal, a.k.a. WPA2-PSK, is a mode of Wi-Fi Protected Access.

You can authenticate to WPA2 Personal networks using wpa_supplicant or iwd, or connect using a network manager. If you only authenticated to the network, then to have a fully functional connection, you will still need to assign the IP address(es) and routes either manually or using a DHCP client.

WPA2 Enterprise

WPA2 Enterprise is a mode of Wi-Fi Protected Access. It provides better security and key management than WPA2 Personal, and supports other enterprise-type functionality, such as VLANs and NAP. However, it requires an external authentication server, called RADIUS server, to handle the authentication of users. This is in contrast to Personal mode which does not require anything beyond the wireless router or access points (APs), and uses a single passphrase or password for all users.

The Enterprise mode enables users to log onto the Wi-Fi network with a username and password and/or a digital certificate. Since each user has a dynamic and unique encryption key, it also helps to prevent user-to-user snooping on the wireless network, and improves encryption strength.

This section describes the configuration of network clients to connect to a wireless access point with WPA2 Enterprise mode. See Software access point#RADIUS for information on setting up an access point itself.

For a comparison of protocols, see the following table.

MS-CHAPv2

WPA2-Enterprise wireless networks demanding MSCHAPv2 type-2 authentication with PEAP sometimes require pptpclient in addition to the stock ppp package. netctl seems to work out of the box without ppp-mppe, however. In either case, usage of MSCHAPv2 is discouraged as it is highly vulnerable, although using another method is usually not an option.

eduroam

eduroam is an international roaming service for users in research, higher education and further education, based on WPA2 Enterprise.

Manual/automatic setup

• wpa_supplicant can be configured directly by its configuration file or using its CLI/GUI front ends and used in combination with a DHCP client. See the examples in /usr/share/doc/wpa_supplicant/wpa_supplicant.conf for configuring the connection details.
• iwd#WPA Enterprise
• NetworkManager can create WPA2 Enterprise profiles with nmcli or the graphical front ends. nmtui does not support this (NetworkManager issue 376), but may use existing profiles.
• ConnMan needs a separate configuration file before connecting to the network. See connman-service.config(5) and ConnMan#Connecting to eduroam (802.1X) for details.
• netctl supports wpa_supplicant configuration through blocks included with WPAConfigSection= . See netctl.profile(5) for details.

WPA3 Personal

WPA3 Personal, a.k.a. WPA3-SAE, is a mode of Wi-Fi Protected Access.

Both wpa_supplicant and iwd support WPA3 Personal.

WPA3 Enterprise

WPA3 Enterprise is a mode of Wi-Fi Protected Access.

wpa_supplicant (since version 2:2.10-8) supports WPA3 Enterprise. See FS#65314.

Tips and tricks

Respecting the regulatory domain

The regulatory domain, or «regdomain», is used to reconfigure wireless drivers to make sure that wireless hardware usage complies with local laws set by the FCC, ETSI and other organizations. Regdomains use ISO 3166-1 alpha-2 country codes. For example, the regdomain of the United States would be «US», China would be «CN», etc.

Regdomains affect the availability of wireless channels. In the 2.4GHz band, the allowed channels are 1-11 for the US, 1-14 for Japan, and 1-13 for most of the rest of the world. In the 5GHz band, the rules for allowed channels are much more complex. In either case, consult this list of WLAN channels for more detailed information.

Regdomains also affect the limit on the effective isotropic radiated power (EIRP) from wireless devices. This is derived from transmit power/»tx power», and is measured in dBm/mBm (1dBm=100mBm) or mW (log scale). In the 2.4GHz band, the maximum is 30dBm in the US and Canada, 20dBm in most of Europe, and 20dBm-30dBm for the rest of the world. In the 5GHz band, maximums are usually lower. Consult the wireless-regdb for more detailed information (EIRP dBm values are in the second set of brackets for each line).

Misconfiguring the regdomain can be useful — for example, by allowing use of an unused channel when other channels are crowded, or by allowing an increase in tx power to widen transmitter range. However, this is not recommended as it could break local laws and cause interference with other radio devices.

The kernel loads the database directly when wireless-regdb is installed. For direct loading, the kernel should, for security’s sake, be configured with CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS set to yes to allow for cryptographic verification of the database. This is true of the stock Arch kernel, but if you are using an alternate kernel, or compiling your own, you should verify this. More information is available at this guide.

To configure the regdomain, install wireless-regdb and reboot (to reload the cfg80211 module and all related drivers). Check the boot log to make sure that the database is loaded and key verified by cfg80211 :

The current regdomain can be set to the United States with:

And queried with:

However, setting the regdomain may not alter your settings. Some devices have a regdomain set in firmware/EEPROM, which dictates the limits of the device, meaning that setting regdomain in software can only increase restrictions, not decrease them. For example, a CN device could be set in software to the US regdomain, but because CN has an EIRP maximum of 20dBm, the device will not be able to transmit at the US maximum of 30dBm.

For example, to see if the regdomain is being set in firmware for an Atheros device:

For other chipsets, it may help to search for «EEPROM», «regdomain», or simply the name of the device driver.

To see if your regdomain change has been successful, and to query the number of available channels and their allowed transmit power:

A more permanent configuration of the regdomain can be achieved through editing /etc/conf.d/wireless-regdom and uncommenting the appropriate domain.

wpa_supplicant can also use a regdomain in the country= line of /etc/wpa_supplicant/wpa_supplicant.conf .

It is also possible to configure the cfg80211 kernel module to use a specific regdomain by adding, for example, options cfg80211 ieee80211_regdom=JP as module options. The module option is inherited from the old regulatory implementation and in modern kernels act as a userspace regulatory hint as if it came through nl80211 through utilities like iw and wpa_supplicant .

Rfkill caveat

Many laptops have a hardware button (or switch) to turn off the wireless card; however, the card can also be blocked by the kernel. This can be handled by rfkill. To show the current status:

If the card is hard-blocked, use the hardware button (switch) to unblock it. If the card is not hard-blocked but soft-blocked, use the following command:

Hardware buttons to toggle wireless cards are handled by a vendor specific kernel module. Frequently, these are WMI modules. Particularly for very new hardware models, it happens that the model is not fully supported in the latest stable kernel yet. In this case, it often helps to search the kernel bug tracker for information and report the model to the maintainer of the respective vendor kernel module, if it has not happened already.

Power saving

Troubleshooting

This section contains general troubleshooting tips, not strictly related to problems with drivers or firmware. For such topics, see next section #Troubleshooting drivers and firmware.

Temporary internet access

If you have problematic hardware and need internet access to, for example, download some software or get help in forums, you can make use of Android’s built-in feature for internet sharing via USB cable. See Android tethering#USB tethering for more information.

Observing logs

A good first measure to troubleshoot is to analyze the system’s logfiles first. In order not to manually parse through them all, it can help to open a second terminal/console window and watch the kernels messages with

while performing the action, e.g. the wireless association attempt.

When using a tool for network management, the same can be done for systemd with

Frequently, a wireless error is accompanied by a deauthentication with a particular reason code, for example:

Looking up the reason code might give a first hint. Maybe it also helps you to look at the control message flowchart, the journal messages will follow it.

The individual tools used in this article further provide options for more detailed debugging output, which can be used in a second step of the analysis, if required.

Failed to get IP address

The factual accuracy of this article or section is disputed.

This article or section is out of date.

• If getting an IP address repeatedly fails using the default dhcpcd client, try installing and using dhclient instead. Do not forget to select dhclient as the primary DHCP client in the connection manager.

• If you can get an IP address for a wired interface and not for a wireless interface, try disabling the wireless card’s power saving features (specify off instead of on ).

• If you get a timeout error due to a waiting for carrier problem, then you might have to set the channel mode to auto for the specific device:

Before changing the channel to auto, make sure your wireless interface is down. After it has successfully changed it, you can bring the interface up again and continue from there.

Valid IP address but cannot resolve host

If you are on a public wireless network that may have a captive portal, make sure to query an HTTP page (not an HTTPS page) from your web browser, as some captive portals only redirect HTTP. If this is not the issue, check if you can resolve domain names, it may be necessary to use the DNS server advertised via DHCP.

Setting RTS and fragmentation thresholds

Wireless hardware disables RTS and fragmentation by default. These are two different methods of increasing throughput at the expense of bandwidth (i.e. reliability at the expense of speed). These are useful in environments with wireless noise or many adjacent access points, which may create interference leading to timeouts or failing connections.

Packet fragmentation improves throughput by splitting up packets with size exceeding the fragmentation threshold. The maximum value (2346) effectively disables fragmentation since no packet can exceed it. The minimum value (256) maximizes throughput, but may carry a significant bandwidth cost.

RTS improves throughput by performing a handshake with the access point before transmitting packets with size exceeding the RTS threshold. The maximum threshold (2347) effectively disables RTS since no packet can exceed it. The minimum threshold (0) enables RTS for all packets, which is probably excessive for most situations.

Random disconnections

Cause #1

If your journal says wlan0: deauthenticating from MAC by local choice (reason=3) and you lose your Wi-Fi connection, it is likely that you have a bit too aggressive power-saving on your Wi-Fi card. Try disabling the wireless card’s power saving features (specify off instead of on ).

If your card does not support enabling/disabling power save mode, check the BIOS for power management options. Disabling PCI-Express power management in the BIOS of a Lenovo W520 resolved this issue.

Cause #2

If you are experiencing frequent disconnections and your journal shows messages such as

ieee80211 phy0: wlan0: No probe response from AP xx:xx:xx:xx:xx:xx after 500ms, disconnecting

try changing the channel bandwidth to 20MHz through your router’s settings page.

Cause #3

On some laptop models with hardware rfkill switches (e.g., Thinkpad X200 series), due to wear or bad design, the switch (or its connection to the mainboard) might become loose over time resulting in seemingly random hardblocks/disconnects when you accidentally touch the switch or move the laptop. There is no software solution to this, unless your switch is electrical and the BIOS offers the option to disable the switch. If your switch is mechanical (and most are), there are lots of possible solutions, most of which aim to disable the switch: Soldering the contact point on the mainboard/wifi-card, gluing or blocking the switch, using a screw nut to tighten the switch or removing it altogether.

Cause #4

Another cause for frequent disconnects or a complete failure to connect may also be a sub-standard router, incomplete settings of the router, interference by other wireless devices or low quality signal.

To troubleshoot, first try to connect to the router with no authentication and by getting closer to it.

If that works, enable WPA/WPA2 again but choose fixed and/or limited router settings. For example:

• If the router is considerably older than the wireless device you use for the client, test if it works with setting the router to one wireless mode
• Disable mixed-mode authentication (e.g. only WPA2 with AES, or TKIP if the router is old)
• Try a fixed/free channel rather than «auto» channel (maybe the router next door is old and interfering)
• Disable WPS
• Change the router’s 5 GHz channel(s) to a non-DFS (Dynamic Frequency Selection) channel. Connections on such channels may be dropped or suddenly switched due to interference from nearby weather radar.
• Try setting your client to 2.4 GHz only instead of letting it choose what it thinks is best between 5 GHz and 2.4 GHz (the later has a lower throughput but will provide a more stable connection over longer distances)
• Disable 40MHz channel bandwidth (lower throughput but less likely collisions) with cfg80211.cfg80211_disable_40mhz_24ghz=1
• If the router has quality of service settings, check completeness of settings (e.g. Wi-Fi Multimedia (WMM) is part of optional QoS flow control. An erroneous router firmware may advertise its existence although the setting is not enabled)

Cause #5

On some wireless network adapters (e.g. Qualcomm Atheros AR9485), random disconnects can happen with a DMA error:

A possible workaround is to disable the Intel IOMMU driver (DMA), adding intel_iommu=off to the kernel parameters [3].

Cause #6

If you are using a device with iwlwifi and iwlmvm for wireless connectivity, and your Wi-Fi card appears to disappear when on battery power (perhaps after a reboot or resuming from suspend), this can be fixed by configuring power saving settings in iwlmvm.

Create the file /etc/modprobe.d/iwlmvm.conf if it does not exist already, then add the following line to it:

A power_scheme of 1 sets iwlmvm to «Always Active.» Available options are:

Value	Description
1	Always Active
2	Balanced
3	Low-power

This fix was discovered at [4].

Cause #7

If your device undergoes long periods of inactivity (e.g. a file server), the disconnection may be due to power saving, which will block incoming traffic and prevent connections. Try disabling power saving for the interface:

You can create a udev rule to do this on boot, see Power management#Network interfaces.

Wi-Fi networks invisible because of incorrect regulatory domain

If the computer’s Wi-Fi channels do not match those of the user’s country, some in-range Wi-Fi networks might be invisible because they use wireless channels that are not allowed by default. The solution is to configure the regulatory domain correctly; see #Respecting the regulatory domain.

Troubleshooting drivers and firmware

This section covers methods and procedures for installing kernel modules and firmware for specific chipsets, that differ from generic method.

See Kernel modules for general information on operations with modules.

Ralink/Mediatek

rt2x00

Unified driver for Ralink chipsets (it replaces rt2500 , rt61 , rt73 , etc). This driver has been in the Linux kernel since 2.6.24, you only need to load the right module for the chip: rt2400pci , rt2500pci , rt2500usb , rt61pci or rt73usb which will autoload the respective rt2x00 modules too.

A list of devices supported by the modules is available at the project’s homepage.

Additional notes

• Since kernel 3.0, rt2x00 includes also these drivers: rt2800pci , rt2800usb .
• Since kernel 3.0, the staging drivers rt2860sta and rt2870sta are replaced by the mainline drivers rt2800pci and rt2800usb [5].
• Some devices have a wide range of options that can be configured with iwpriv . These are documented in the source tarballs available from Ralink.

rt3090

For devices which use the rt3090 chipset, it should be possible to use the rt2800pci driver; however, it does not work with this chipset very well (e.g. sometimes it is not possible to use higher rate than 2Mb/s).

rt3290

The rt3290 chipset is recognised by the kernel rt2800pci module. However, some users experience problems and reverting to a patched Ralink driver seems to be beneficial in these cases.

rt3573

New chipset as of 2012. It may require proprietary drivers from Ralink. Different manufacturers use it; see the Belkin N750 DB wireless usb adapter forums thread.

mt7612u

New chipset as of 2014, released under their new commercial name Mediatek. It is an AC1200 or AC1300 chipset. Manufacturer provides drivers for Linux on their support page. As of kernel 5.5 it should be supported by the included mt76 driver.

Realtek

See [6] [dead link 2022-11-10] for a list of Realtek chipsets and specifications.

rtl8192cu

The driver is now in the kernel, but many users have reported being unable to make a connection although scanning for networks does work.

8192cu-dkms AUR includes many patches; try this if it does not work fine with the driver in kernel.

rtl8723ae/rtl8723be

The rtl8723ae and rtl8723be modules are included in the mainline Linux kernel.

Some users may encounter errors with powersave on this card. This is shown with occasional disconnects that are not recognized by high level network managers (netctl, NetworkManager). This error can be confirmed by running dmesg -w as root or journalctl -f as root and looking for output related to powersave and the rtl8723ae / rtl8723be module. If you have this issue, use the fwlps=0 kernel option which should prevent the WiFi card from automatically sleeping and halting connection. See Kernel module#Setting module options.

If you have poor signal, perhaps your device has only one physical antenna connected, and antenna autoselection is broken. You can force the choice of antenna with ant_sel=1 or ant_sel=2 kernel option. [7]

rtl88xxau

Realtek chipsets rtl8811au, rtl8812au, rtl8814au and rtl8821au designed for various USB adapters ranging from AC600 to AC1900. Several packages provide various kernel drivers, these require DKMS (the dkms package and the kernel headers installed):

Chipset	Package	Notes
rtl8811au, rtl8812au, rtl8821au	rtl88xxau-aircrack-dkms-git AUR	Aircrack-ng kernel module for 8811au, 8812au and 8821au chipsets with monitor mode and injection support.
rtl8812au	rtl8812au-dkms-git AUR	Latest official Realtek driver version for rtl8812au only.
rtl8811au, rtl8821au	rtl8821au-dkms-git AUR	Newer driver version for rtl8821au.
rtl8814au	rtl8814au-dkms-git AUR	Possibly works for rtl8813au too.

rtl8811cu/rtl8821cu

rtl8821cu-dkms-git AUR provides a kernel module for the Realtek 8811cu and 8821cu chipset.

This requires DKMS, so make sure you have your proper kernel headers installed.

If no wireless interface shows up even though the 8821cu module is loaded, you may need to manually specify the rtw_RFE_type option [8][9]. Try e.g. rtw_RFE_type=0x26 , other values might also work. See Kernel module#Setting module options for details.

rtl8821ce

rtl8821ce-dkms-git AUR provides a kernel module for the Realtek 8821ce chipset found in the Asus X543UA.

This requires DKMS, so make sure you have your proper kernel headers installed.

rtl8822bu

rtl88x2bu-dkms-git AUR provides a kernel module for the Realtek 8822bu chipset found in the Edimax EW7822ULC USB3, Asus AC53 Nano USB 802.11ac and TP-Link Archer T3U adapter.

This requires DKMS, so make sure you have your proper kernel headers installed.

rtl8xxxu

This article or section needs expansion.

Issues with the rtl8xxxu mainline kernel module may be solved by compiling a third-party module for the specific chipset. The source code can be found in GitHub repositories.

Some drivers may be already prepared in the AUR, e.g. rtl8723bu-dkms-git AUR .

RTW88

An RTW88 kernel module patchset has been recently posted to the kernel mailing list, which should hopefully make it into the mainstream kernel.

Upstream kernels or those with the patchset will support most RTW88 chip devices if configured and compiled to do so. linux-zen and linux-zen-git AUR both include these patches, with the packaged version already having the module built.

The driver supports: 882BE, 8822BU, 8822CE, 8822CU, 8723DE, 8723DU, 8821CE, and 8821CU.

Atheros

The MadWifi team currently maintains three different drivers for devices with Atheros chipset:

• madwifi is an old, obsolete driver. Not present in Arch kernel since 2.6.39.1[11].
• ath5k is a newer driver which replaces the madwifi driver. Currently a better choice for some chipsets, but not all chipsets are supported (see below)
• ath9k is the newest of these three drivers. It is intended for newer Atheros chipsets. All of the chips with 802.11n capabilities are supported.

There are some other drivers for some Atheros devices. See Linux Wireless documentation for details.

ath5k

If you find web pages randomly loading very slow, or if the device is unable to lease an IP address, try to switch from hardware to software encryption by loading the ath5k module with nohwcrypt=1 option. See Kernel modules#Setting module options for details.

Some laptops may have problems with their wireless LED indicator flickering red and blue. To solve this problem, do:

For alternatives, see this bug report.

ath9k

As of Linux 3.15.1, some users have been experiencing a decrease in bandwidth. In some cases, this can fixed by setting the nohwcrypt=1 option for the ath9k module. See Kernel module#Setting module options.

An ath9k mailing list exists for support and development related discussions.

Power saving

Although Linux Wireless says that dynamic power saving is enabled for Atheros ath9k single-chips newer than AR9280, for some devices (e.g. AR9285), powertop might still report that power saving is disabled. In this case, enable it manually.

On some devices (e.g. AR9285), enabling the power saving might result in the following error:

The solution is to set the ps_enable=1 option for the ath9k module; see Kernel module#Setting module options.

Intel

iwlegacy

iwlegacy is the wireless driver for Intel’s 3945 and 4965 wireless chips. The firmware is included in the linux-firmware package.

udev should load the driver automatically, otherwise load iwl3945 or iwl4965 manually. See Kernel modules for details.

If you have problems connecting to networks in general (e.g. random failures with your card on bootup or your link quality is very poor), try to disable 802.11n:

If the failures persist during bootup and you are using Nouveau driver, try enabling early KMS to prevent the conflict [12].

iwlwifi

iwlwifi is the wireless driver for Intel’s current wireless chips, such as 5100AGN, 5300AGN, and 5350AGN. See the full list of supported devices. The firmware is included in the linux-firmware package. The linux-firmware-iwlwifi-git AUR may contain some updates sooner.

If you have problems connecting to networks in general or your link quality is very poor, try to disable 802.11n, and perhaps also enable software encryption:

If you have a problem with slow uplink speed in 802.11n mode, for example 20Mbps, try to enable antenna aggregation:

Do not be confused with the option name, when the value is set to 8 it does not disable anything but re-enables transmission antenna aggregation.[13] [14]

In case this does not work for you, you may try disabling power saving for your wireless adapter.

Some have never gotten this to work. Others found salvation by disabling N in their router settings after trying everything. This is known to have been the only solution on more than one occasion. The second link there mentions a 5ghz option that might be worth exploring.

If you have an 802.11ax (WiFi 6) access point and have problems detecting the beacons or an unreliable connection, review Intel Article 54799.

Bluetooth coexistence

If you have difficulty connecting a bluetooth headset and maintaining good downlink speed, try disabling bluetooth coexistence [15]:

Firmware issues

You may have some issue where the driver outputs stack traces & errors, which can cause some stuttering.

To confirm it is the cause of the issues, downgrade the package linux-firmware .

If confirmed, move the buggy firmware files so that an older version is loaded (to be able to have an up to date linux-firmware since it is not only providing firmware updates for your Intel WiFi card):

To avoid having to repeat these steps manually after each update, use the NoExtract array in pacman.conf with a wildcard to block their installation. See pacman#Skip files from being installed to system.

Adapter not detected after booting from Windows

If the WiFi adapter is not getting detected after finishing a session in Windows, this might be due to Windows’ Fast Startup feature which is enabled by default. Try disabling Fast Startup. The iwlwifi kernel driver wiki has an entry for this.

Disabling LED blink

The default settings on the module are to have the LED blink on activity. Some people find this extremely annoying. To have the LED on solid when Wi-Fi is active, you can use the systemd-tmpfiles:

Run systemd-tmpfiles —create phy0-led.conf for the change to take effect, or reboot.

To see all the possible trigger values for this LED:

Broadcom

Other drivers/devices

Tenda w322u

Treat this Tenda card as an rt2870sta device. See #rt2x00.

orinoco

This should be a part of the kernel package and be installed already.

Some Orinoco chipsets are Hermes II. You can use the wlags49_h2_cs driver instead of orinoco_cs and gain WPA support. To use the driver, blacklist orinoco_cs first.

prism54

The driver p54 is included in kernel, but you have to download the appropriate firmware for your card from this site and install it into the /usr/lib/firmware directory.

zd1211rw

zd1211rw is a driver for the ZyDAS ZD1211 802.11b/g USB WLAN chipset, and it is included in recent versions of the Linux kernel. See [16] for a list of supported devices. You only need to install the firmware for the device, provided by the zd1211-firmware AUR package.

hostap_cs

Host AP is a Linux driver for wireless LAN cards based on Intersil’s Prism2/2.5/3 chipset. The driver is included in Linux kernel.

ndiswrapper

Ndiswrapper is a wrapper script that allows you to use some Windows drivers in Linux. You will need the .inf and .sys files from your Windows driver.

Follow these steps to configure ndiswrapper.

1. Install ndiswrapper-dkms .
2. Install the driver to /etc/ndiswrapper/ :
3. List all installed drivers for ndiswrapper:
4. Let ndiswrapper write its configuration in /etc/modprobe.d/ndiswrapper.conf :

The ndiswrapper install is almost finished; you can load the module at boot.

Test that ndiswrapper will load now:

and wlan0 should now exist. If you have problems, some help is available at: ndiswrapper howto and ndiswrapper FAQ.

Источник

Коды ошибок асик майнера WhatsMiner

0 ErrSucc ОК ОК — обычный
21 ErrNotPlugged 1 или более хеш-плат не обнаружены Сигнал Hashboard PLUG не обнаружен Номер обнаруженной платы питания, если их более одной, разделенные пробелами 1. Проверьте правильность подключения кабеля SPI (по сравнению с обычной машиной) и снова подключите кабель. 2. Замените плату управления. 3. Замените проблемную доску хешрейта (переделайте доску головоломки).
22 ErrPsuI2cFail Аномальная связь по управлению питанием Неправильная связь I2C источника питания — 1. Заменить блок питания. 2. Замените плату управления.
23 ErrEncoreAllFail Все хэш-платы не могут быть включены SPI недоступен для всех плат хешрейта — 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Заменить блок питания. 3. Замените плату управления. 4. Отремонтируйте всю машину.
24 ErrEncoreFail Некоторые платы не включаются SPI недоступен на некоторых хэш-досках Номер хэшборда, для которого произошел сбой связи по SPI, если их несколько, разделенных пробелами 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Заменить блок питания. 3. Замените плату управления. 4. Замените проблемную хеш-доску (переделайте доску-головоломку).
25 ErrSetPllFail Не удалось поднять частоту хэш-платы Не удалось поднять частоту хэш-платы Номер хэшборда: частота ошибок 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Заменить блок питания. 3. Замените плату управления. 4. Замените проблемную хеш-доску (переделайте доску-головоломку).
26 ErrSetVolFail Не удалось установить напряжение Не удалось установить напряжение Номер хэшборда: 1/2 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Заменить блок питания. 3. Замените плату управления. 4. Заменить проблемную хеш-доску (присоединиться)
27 ErrBistFail Тест чипа BIST не пройден Тест чипа BIST не пройден Номер хэшборда: 1/2 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Заменить проблемную хеш-доску (присоединиться к плате)
28 ErrSpiFail Ненормальная связь платы хешрейта не может быть автоматически восстановлена ??во время работы Ненормальное соединение SPI платы хешрейта не может быть автоматически восстановлено во время работы Номер хэшборда 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Замените проблемную хеш-доску (переделайте доску-головоломку)
29 ErrI2cFail Ненормальная связь по питанию во время работы не может быть восстановлена ??автоматически Связь I2C с ненормальным источником питания не может быть автоматически восстановлена ??во время работы — 1. Заменить блок питания. 2. Замените плату управления.
30 ErrNetwork Подключение к майнинговому пулу прервано Подключение к майнинговому пулу прервано — Если эта проблема возникает на большом количестве или на всех майнинговых машинах с одним и тем же коммутатором: 1. Проверьте правильность настроек пула для майнинга. 2. Проверьте конфигурацию сетевой среды (например, конфигурацию DHCP, конфигурацию DNS, порт и т. Д.). Если проблемы возникают только на одной или нескольких машинах для майнинга: 1. Проверьте правильность настроек пула для майнинга. 2. Проверить подключения к сетевому порту майнера. 3. Замените сетевой кабель на работающую майнинговую машину. 4. Замените плату управления.
31 ErrBadChip Повреждение отдельных микросхем, что приводит к искусственно завышенной вычислительной мощности Повреждение отдельных микросхем, что приводит к искусственно завышенной вычислительной мощности Номер поврежденной микросхемы: номер хеш-платы, если их более одной, разделенные пробелами В ремонт
32 ErrOverheat Hashboard перегрелся Hashboard перегрелся Номер хэшборда 1. Проверьте, вращаются ли передний и задний вентиляторы, если они не вращаются, сначала замените вентиляторы, а затем замените плату управления / блок питания. 2. Убедитесь, что направление ветра спереди и сзади согласовано, согласуется ли оно с другими машинами, если нет, измените направление вентилятора. 3. Если температура воздуха на входе горной машины превышает 40 градусов, необходимо улучшить температурную среду в шахте. 4. Если определенная плата хешрейта часто перегревается, вы можете заменить проблемную плату хешрейта (переделайте головоломку).
33 ErrInvTemp Невозможно прочитать температуру чипа Невозможно прочитать температуру чипа Номер хэшборда 1. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 2. Заменить блок питания. 3. Замените плату управления. 4. Замените проблемную хеш-доску (переделайте доску-головоломку).
34 ErrMisPlugged Неправильное подключение кабеля связи платы управления Ненормальное подключение кабеля SPI платы управления Номер хэшборда 1. Проверьте, совместим ли метод (последовательность) подключения кабеля SPI хэш-платы с другими машинами той же модели. 2. Замените плату управления.
35 ErrPsuFail Аномальный источник питания Аномальный источник питания 1. Обратите внимание на то, что если нет явного отклонения от нормы вычислительной мощности всей машины (не отключается плата), то перезагрузить 2. Убедитесь, что винты на обоих концах клеммы питания и соединения кабеля SPI не ослаблены. 3. Заменить блок питания.
36 ErrInvCorenum Некоторые чипы не работают должным образом Количество хороших фишек ненормальное Номер хэшборда: номер чипа 1. Обратите внимание на то, что если нет явного отклонения от нормы вычислительной мощности всей машины (не отключается плата), то перезагрузить 2. Перезапустите майнер, чтобы увидеть, появляется ли по-прежнему та же ошибка. 3. Замените проблемную хеш-плату.
37 ErrInvVidtype Тип платы управления / версия прошивки / количество микросхем не совпадает Тип платы управления / версия прошивки / количество микросхем не совпадает vidtype, minertype, subtype, chipnum После накопления нескольких единиц (> 10) обратитесь в ремонт.
38 ErrBadRearChips Наконец, у некоторых чипов низкая вычислительная мощность. Последние несколько уровней чипов имеют низкую вычислительную мощность В ремонт
39 ErrInvTuneParam Аномальные параметры старения Напряжение начальной частоты старения неверно В ремонт

Errcode	Scope of application	Explanation	Troubleshooting steps
0	Whole miner	Normal	Normal
21	hashboard	one or more hashboards can’t be detected	1. check and see whether the SPI cables are firmly and correctly connected (compared the connection of cables with working miners), reconnect the SPI cables, don’t change sequence of connection 2. replace control board with other well functional one 3. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
22	Whole miner	PSU communication is abnormal	1. replace PSU with other well functional one 2. replace control board with other well functional one
23	Whole miner	All hashboards can’t be powered up	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace PSU with other well functional one 3. replace control board with other well functional one 4. whole miner should be returned for repair
24	hashboard	one or more hashboards can’t be powered up	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace PSU with other well functional one 3. replace control board with other well functional one 4. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
25	hashboard	frequency increase of hashboards fails	1. check hashrate of the miner, if there is nothing obviously abnormal (no missing hashboard), no action should be taken 2. check and see whether screws on the PSU side and SPI connection are loose 3. replace PSU with other well functional one 4. replace control board with other well functional one 5. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
26	hashboard	voltage setting fails	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace PSU with other well functional one 3. replace control board with other well functional one 4. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
27	hashboard	chip BIST test fails	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
28	hashboard	abnormal communication of hashboard, it can’t be automatically recovered when running	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
29	Whole miner	abnormal communication of PSU can’t be automatically recovered when running	1. replace PSU with other well functional one 2. replace control board with other well functional one
30	Whole miner	pool disconnect	If the problem occurs in a large number of miners or all of the mines under the same switch: 1. please first check whether pool setting is correct 2. then check network configuration (such as DHCP configuration, DNS configuration, ports, etc.) If the problem occurs in only one or just a small number of miners under the same switch: 1. please first check whether pool setting is correct 2. then check whether network cable is firmly connected 3. replace network cable with other one from other well working miner 4. replace control board with other well functional one
31	hashboard	damage of some individual chip causes inflated high hashrate of the miner	no action should be taken
32	hashboard	hashboard overheat	1. check and see whether both fans are spinning, if not, replace fan with other functional one, if still not, then replace control board or PSU 2. check and see whether wind direction of both fans are the same, whether wind direction are the same with other miners, if not, exchange fans 3. meter the inlet temperature of the miner, if above 40 °C, cooling system of the mining farm should be improved 4. if some hashboard is overheated frequently, that hashboard should be replaced (returned for repair)
33	hashboard	chip temperature can’t be read	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace PSU with other well functional one 3. replace control board with other well functional one 4. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
34		cables of control board is connected incorrectly	1. check hashrate of the miner, if there is nothing obviously abnormal (no missing hashboard), no action should be taken 2. check whether hashboard SPI cables are conneted in the same way (sequence) as other miners of same model 3. replace control board with other well functional one
35	hashboard	PSU voltage is too low	1. check hashrate of the miner, if there is nothing obviously abnormal (no missing hashboard), no action should be taken 2.check and see whether screws on the PSU side and SPI connection is loose 3. replace PSU with other well functional one
36	hashboard	working or some chips is abnormal	1. check hashrate of the miner, if there is nothing obviously abnormal (no missing hashboard), no action should be taken 2. reboot the miner to see whether the same error is given 3. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
37	Whole miner	mismatch of control board version/firmware version/quantity of chips	if there are more than 10 miners with same error, please contact engineers
38	hashboard	low hashrate of last few chips	no action should be taken
39	hashboard	testing parameter is abnormal	no action should be taken
40	hashboard	PSU load is insufficient	1. check and see whether screws on the PSU side and SPI connection are loose 2. replace PSU with other well functional one 3. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
41	hashboard	startup voltage of PSU is too low	1. check hashrate of the miner, if there is nothing obviously abnormal (no missing hashboard), no action should be taken 2. check and see whether screws on the PSU side and SPI connection are loose 3. replace PSU with other well functional one 4. replace control board with other well functional one
42	hashboard	implementation of plan B fails when hashboard frequency increases	1. check hashrate of the miner, if there is nothing obviously abnormal (no missing hashboard), no action should be taken 2. check and see whether screws on the PSU side and SPI connection are loose 3. replace PSU with other well functional one 4. replace control board with other well functional one 5. replace defective hashboard(s) with other well functional one(s) (defective one should be returned for repair/replacement)
			Attention: 1. The miner should be powered up again to see whether it is back to normal after every step is taken 2. If the problem is not solve after replacement the part, the part should go back to its original unit 3. Error code and brief description of the problem should be attached to the hashboard that is confirmed defective and that will be returned for repair

Error

code

Reason Processing method

110 Fanin detect speed error

Check whether the fan connection is normal,

or replace the power supply, or replace the

fan

111 Fanout detect speed error

Check whether the fan connection is normal,

or replace the power supply, or replace the

fan

130 Fanin speed error

Check whether the fan connection is normal,

or replace the power supply, or replace the

fan

131 Fanout speed error

Check whether the fan connection is normal,

or replace the power supply, or replace the

fan

140 Fan speed is too high Please check the environment temperature

200

Power probing error, no

power found

Detecting power output wiring, updating the

latest firmware, or replacing power supply

201

Power supply and

configuration file

mismatch

Replace the correct PSU

203 Power protecting Please check the environment temperature

204 Power current protecting Please check the environment temperature

205 Power current error Inspection of power supply in power grid

206 Power input voltage is low

Improve power supply conditions and input

voltage

207

Power input current

protecting

Improve power supply conditions and input

voltage

210 Power error status Check power failure code

213

Power input voltage and

current do not match the

power

Replace the PSU

233

Power output over

temperature protection

Please check the environment temperature

234

Power output over

temperature protection

Please check the environment temperature

235

Power output over

temperature protection

Please check the environment temperature

236

Overcurrent Protection of

Power Output

Please check the environment temperature,

check copper row screw

237

Overcurrent Protection of

Power Output

Please check the environment temperature,

check copper row screw

238

Overcurrent Protection of

Power Output

Please check the environment temperature,

check copper row screw

239

Overvoltage Protection of

Power Output

Inspection of power supply in power grid

240

Low Voltage Protection for

Power Output

Inspection of power supply in power grid

241

Power output current

imbalance

Replace the power

243

Over-temperature

Protection for Power Input

Please check the environment temperature

244

Over-temperature

Protection for Power Input

Please check the environment temperature

245

Over-temperature

Protection for Power Input

Please check the environment temperature

246

Overcurrent Protection for

Power Input

Please check the environment temperature

247

Overcurrent Protection for

Power Input

Please check the environment temperature

248

Overvoltage Protection for

Power Input

Inspection of input voltage in power grid

249

Overvoltage Protection for

Power Input

Inspection of input voltage in power grid

250

Undervoltage Protection

for Power Input

Inspection of input voltage in power grid

251

Undervoltage Protection

for Power Input

Inspection of input voltage in power grid

253 Power Fan Error Replace the PSU

254 Power Fan Error Replace the PSU

255

Protection of over power

output

Please check the environment temperature

256

Protection of over power

output

Please check the environment temperature

257

Input over current

protection of power supply

primary side

Try to power off and restart, no effect to

replace the power supply

263

Power communication

warning

Check whether the screws of the control

board are locked

264 Power communication error

Check whether the screws of the control

board are locked

267 Power watchdog protection Contact the technician in time

268

Power output over-current

protection

Check the ambient temperature, check the

copper bar screw

269

Power input over-current

protection

Improve power supply conditions and input

voltage

270

Power input over-voltage

protection

Inspection of input voltage in power grid

271

Power input under-voltage

protection

Inspection of input voltage in power grid

272

Warning of excessive power

output of power supply

Please check the environment temperature

273

Power input power too high

warning

Please check the environment temperature

274 Power fan warning

Check if the power fan is blocked and may

need to be replaced

275

Power over temperature

warning

Please check the environment temperature

300

SM0 temperature sensor

detection error

Check the connection of the hashboard

301

SM1 temperature sensor

detection error

Check the connection of the hashboard

302

SM2 temperature sensor

detection error

Check the connection of the hashboard

320

SM0 temperature reading

error

Check whether the control board screw is

locked properly, check the connection board

and the arrangement contact

321

SM1 temperature reading

error

Check whether the control board screw is

locked properly, check the connection board

and the arrangement contact

322

SM2 temperature reading

error

Check whether the control board screw is

locked properly, check the connection board

and the arrangement contact

329

Control board temperature

sensor communication error

Replace the power supply

350 SM0 temperature protecting Please check the environment temperature

351 SM1 temperature protecting Please check the environment temperature

352 SM2 temperature protecting Please check the environment temperature

410 SM0 detect eeprom error Check adapter board and wiring contact

411 SM1 detect eeprom error Check adapter board and wiring contact

412 SM2 detect eeprom error Check adapter board and wiring contact

420 SM0 parser eeprom error Contact the technician in time

421 SM1 parser eeprom error Contact the technician in time

422 SM2 parser eeprom error Contact the technician in time

430 SM0 chip bin type error Contact the technician in time

431 SM1 chip bin type error Contact the technician in time

432 SM2 chip bin type error Contact the technician in time

440

SM0 eeprom chip num X

error

Contact the technician in time

441

SM1 eeprom chip num X

error

Contact the technician in time

442

SM2 eeprom chip num X

error

Contact the technician in time

510 SM0 miner type error

The version and type of hashboard are

inconsistent, replace the correct hashboard

511 SM1 miner type error

The version and type of hashboard are

inconsistent, replace the correct hashboard

512 SM2 miner type error

The version and type of hashboard are

inconsistent, replace the correct hashboard

530 SM0 not found

Check the connection and arrangement of the

adapter board, or replace the control

board, check whether the hash board

connector is empty welded

531 SM1 not found

Check the connection and arrangement of the

adapter board, or replace the control

board, check whether the hash board

connector is empty welded

532 SM2 not found

Check the connection and arrangement of the

adapter board, or replace the control

board, check whether the hash board

connector is empty welded

540 SM0 reading chip id error

Check adapter board and wiring contact,

Clean the dust on the hashboard

541 SM1 reading chip id error

Check adapter board and wiring contact,

Clean the dust on the hashboard

542 SM2 reading chip id error

Check adapter board and wiring contact,

Clean the dust on the hashboard

550 SM0 have bad chips Replacement of bad chips

551 SM1 have bad chips Replacement of bad chips

552 SM2 have bad chips Replacement of bad chips

560 SM0 loss balance

Plug in the adapter plate, and then screw

in the power connection hashboard again

561 SM1 loss balance

Plug in the adapter plate, and then screw

in the power connection hashboard again

562 SM2 loss balance

Plug in the adapter plate, and then screw

in the power connection hashboard again

600

Environment temperature is

high

Please check the environment temperature

610

If the ambient temperature

is too high in high

performance mode, return

to normal mode

Check the ambient temperature, high

performance mode needs to be controlled

below 30 ?

710

Control board rebooted as

exception

Updating the latest firmware.Check whether

the control board screw is locked properly

800 cgminer checksum error Re-upgrade firmware

801

system-monitor checksum

error

Re-upgrade firmware

802

remote-daemon checksum

error

Re-upgrade firmware

2010 All pools are disable Please check the network or pools configure

2020 Pool0 connect failed Please check the network or pools configure

2021 Pool1 connect failed Please check the network or pools configure

2022 Pool2 connect failed Please check the network or pools configure

2030

High rejection rate of

pool

Please check the network or pools

configure.Setting of mining currency

2040

The pool does not support

the asicboost mode

Check pool configuration

5110 SM0 Frequency Up Timeout reboot

5111 SM1 Frequency Up Timeout reboot

5112 SM2 Frequency Up Timeout reboot

8410

Software version error

(M2x miner with M3x

firmware, or M3x with M2x

firmware).

Upgrade to the correct firmware version

PSU

Error

code

Reason processing method

0x0001 Input undervoltage Check the power supply

0x0002

Temperature sampling over

temperature protection of

power radiator

Power on again after 10 minutes of power

failure. If it occurs again, replace the

power supply

0x0004

Temperature sampling over

temperature protection of

power radiator

Power on again after 10 minutes of power

failure. If it occurs again, replace the

power supply

0x0008

Over temperature

protection of

environmental temperature

sampling in power supply

Power on again after 10 minutes of power

failure. If it occurs again, replace the

power supply

0x0010 Primary side over current

Power on again after 10 minutes of power

failure. If it occurs again, replace the

power supply

0x0020 Output undervoltage Check the power supply

0x0040

Output over current

(continuous load 320A for

more than 2S)

Tighten the copper bar screw again

0x0080 Primary side over current

Power on again after 10 minutes of power

failure. If it occurs again, replace the

power supply

0x0100

Single circuit overcurrent

(protection point 120a)

Check the PSU

0x0200

Single circuit overcurrent

(protection point 120a)

Check the PSU

0x0400

Single circuit overcurrent

(protection point 120a)

Check the PSU

0x0800 Fan failure Replace the PSU

0x1000

Output over current

(continuous load of 310A

for more than 5min)

Check the PSU

0x2000

Output over current

(continuous load 295A for

more than 10min)

Check the PS

Error code Reason Processing method 110 Fanin detect speed error Check whether the fan connection is normal, or replace the power supply, or replace the fan 111 Fanout detect speed error Check whether the fan connection is normal, or replace the power supply, or replace the fan 130 Fanin speed error Check whether the fan connection is normal, or replace the power supply, or replace the fan 131 Fanout speed error Check whether the fan connection is normal, or replace the power supply, or replace the fan 140 Fan speed is too high Please check the environment temperature 200 Power probing error, no power found Detecting power output wiring, updating the latest firmware, or replacing power supply 201 Power supply and configuration file mismatch Replace the correct PSU 203 Power protecting Please check the environment temperature 204 Power current protecting Please check the environment temperature 205 Power current error Inspection of power supply in power grid 206 Power input voltage is low Improve power supply conditions and input voltage 207 Power input current protecting Improve power supply conditions and input voltage 210 Power error status Check power failure code 213 Power input voltage and current do not match the power Replace the PSU 233 Power output over temperature protection Please check the environment temperature 234 Power output over temperature protection Please check the environment temperature 235 Power output over temperature protection Please check the environment temperature 236 Overcurrent Protection of Power Output Please check the environment temperature， check copper row screw 237 Overcurrent Protection of Power Output Please check the environment temperature， check copper row screw 238 Overcurrent Protection of Power Output Please check the environment temperature， check copper row screw 239 Overvoltage Protection of Power Output Inspection of power supply in power grid 240 Low Voltage Protection for Power Output Inspection of power supply in power grid 241 Power output current imbalance Replace the power 243 Over-temperature Protection for Power Input Please check the environment temperature 244 Over-temperature Protection for Power Input Please check the environment temperature 245 Over-temperature Protection for Power Input Please check the environment temperature 246 Overcurrent Protection for Power Input Please check the environment temperature 247 Overcurrent Protection for Power Input Please check the environment temperature 248 Overvoltage Protection for Power Input Inspection of input voltage in power grid 249 Overvoltage Protection for Power Input Inspection of input voltage in power grid 250 Undervoltage Protection for Power Input Inspection of input voltage in power grid 251 Undervoltage Protection for Power Input Inspection of input voltage in power grid 253 Power Fan Error Replace the PSU 254 Power Fan Error Replace the PSU 255 Protection of over power output Please check the environment temperature 256 Protection of over power output Please check the environment temperature 257 Input over current protection of power supply primary side Try to power off and restart, no effect to replace the power supply 263 Power communication warning Check whether the screws of the control board are locked 264 Power communication error Check whether the screws of the control board are locked 267 Power watchdog protection Contact the technician in time 268 Power output over-current protection Check the ambient temperature, check the copper bar screw 269 Power input over-current protection Improve power supply conditions and input voltage 270 Power input over-voltage protection Inspection of input voltage in power grid 271 Power input under-voltage protection Inspection of input voltage in power grid 272 Warning of excessive power output of power supply Please check the environment temperature 273 Power input power too high warning Please check the environment temperature 274 Power fan warning Check if the power fan is blocked and may need to be replaced 275 Power over temperature warning Please check the environment temperature 300 SM0 temperature sensor detection error Check the connection of the hashboard 301 SM1 temperature sensor detection error Check the connection of the hashboard 302 SM2 temperature sensor detection error Check the connection of the hashboard 320 SM0 temperature reading error Check whether the control board screw is locked properly, check the connection board and the arrangement contact 321 SM1 temperature reading error Check whether the control board screw is locked properly, check the connection board and the arrangement contact 322 SM2 temperature reading error Check whether the control board screw is locked properly, check the connection board and the arrangement contact 329 Control board temperature sensor communication error Replace the power supply 350 SM0 temperature protecting Please check the environment temperature 351 SM1 temperature protecting Please check the environment temperature 352 SM2 temperature protecting Please check the environment temperature 410 SM0 detect eeprom error Check adapter board and wiring contact 411 SM1 detect eeprom error Check adapter board and wiring contact 412 SM2 detect eeprom error Check adapter board and wiring contact 420 SM0 parser eeprom error Contact the technician in time 421 SM1 parser eeprom error Contact the technician in time 422 SM2 parser eeprom error Contact the technician in time 430 SM0 chip bin type error Contact the technician in time 431 SM1 chip bin type error Contact the technician in time 432 SM2 chip bin type error Contact the technician in time 440 SM0 eeprom chip num X error Contact the technician in time 441 SM1 eeprom chip num X error Contact the technician in time 442 SM2 eeprom chip num X error Contact the technician in time 510 SM0 miner type error The version and type of hashboard are inconsistent, replace the correct hashboard 511 SM1 miner type error The version and type of hashboard are inconsistent, replace the correct hashboard 512 SM2 miner type error The version and type of hashboard are inconsistent, replace the correct hashboard 530 SM0 not found Check the connection and arrangement of the adapter board, or replace the control board, check whether the hash board connector is empty welded 531 SM1 not found Check the connection and arrangement of the adapter board, or replace the control board, check whether the hash board connector is empty welded 532 SM2 not found Check the connection and arrangement of the adapter board, or replace the control board, check whether the hash board connector is empty welded 540 SM0 reading chip id error Check adapter board and wiring contact， Clean the dust on the hashboard 541 SM1 reading chip id error Check adapter board and wiring contact， Clean the dust on the hashboard 542 SM2 reading chip id error Check adapter board and wiring contact， Clean the dust on the hashboard 550 SM0 have bad chips Replacement of bad chips 551 SM1 have bad chips Replacement of bad chips 552 SM2 have bad chips Replacement of bad chips 560 SM0 loss balance Plug in the adapter plate, and then screw in the power connection hashboard again 561 SM1 loss balance Plug in the adapter plate, and then screw in the power connection hashboard again 562 SM2 loss balance Plug in the adapter plate, and then screw in the power connection hashboard again 600 Environment temperature is high Please check the environment temperature 610 If the ambient temperature is too high in high performance mode, return to normal mode Check the ambient temperature, high performance mode needs to be controlled below 30 ℃ 710 Control board rebooted as exception Updating the latest firmware.Check whether the control board screw is locked properly 800 cgminer checksum error Re-upgrade firmware 801 system-monitor checksum error Re-upgrade firmware 802 remote-daemon checksum error Re-upgrade firmware 2010 All pools are disable Please check the network or pools configure 2020 Pool0 connect failed Please check the network or pools configure 2021 Pool1 connect failed Please check the network or pools configure 2022 Pool2 connect failed Please check the network or pools configure 2030 High rejection rate of pool Please check the network or pools configure.Setting of mining currency 2040 The pool does not support the asicboost mode Check pool configuration 5110 SM0 Frequency Up Timeout reboot 5111 SM1 Frequency Up Timeout reboot 5112 SM2 Frequency Up Timeout reboot 8410 Software version error (M2x miner with M3x firmware, or M3x with M2x firmware). Upgrade to the correct firmware version PSU Error code Reason processing method 0x0001 Input undervoltage Check the power supply 0x0002 Temperature sampling over temperature protection of power radiator Power on again after 10 minutes of power failure. If it occurs again, replace the power supply 0x0004 Temperature sampling over temperature protection of power radiator Power on again after 10 minutes of power failure. If it occurs again, replace the power supply 0x0008 Over temperature protection of environmental temperature sampling in power supply Power on again after 10 minutes of power failure. If it occurs again, replace the power supply 0x0010 Primary side over current Power on again after 10 minutes of power failure. If it occurs again, replace the power supply 0x0020 Output undervoltage Check the power supply 0x0040 Output over current (continuous load 320A for more than 2S) Tighten the copper bar screw again 0x0080 Primary side over current Power on again after 10 minutes of power failure. If it occurs again, replace the power supply 0x0100 Single circuit overcurrent (protection point 120a) Check the PSU 0x0200 Single circuit overcurrent (protection point 120a) Check the PSU 0x0400 Single circuit overcurrent (protection point 120a) Check the PSU 0x0800 Fan failure Replace the PSU 0x1000 Output over current (continuous load of 310A for more than 5min) Check the PSU 0x2000 Output over current (continuous load 295A for more than 10min) Check the PS

my air zhimi,airpurifier.v1 firmware version is 1.4.0

pi@stevenhomesmart:~/Git/temp $ node air.js
AirPurifier {
domain: null,
_events: {},
_eventsCount: 0,
_maxListeners: undefined,
id: undefined,
type: ‘air-purifier’,
model: ‘zhimi.airpurifier.v1’,
capabilities: [ ‘power’, ‘mode’, ‘sensor’, ‘temperature’, ‘humidity’, ‘aqi’ ],
address: ‘192.168.88.23’,
port: 54321,
writeOnly: false,
packet:
Packet {
header: <Buffer 21 31 00 80 00 00 00 00 00 00 ce 32 00 00 d8 68 3e 3e f1 97 3c 76 37 f3 02 aa b0 b6 e1 c1 23 7b>,
_serverStampTime: 1495860174359,
_token: <Buffer 0c c7 49 b4 c2 12 4f c6 7f 43 5e 93 c0 04 53 78>,
_tokenKey: <Buffer 26 50 49 f0 bf 8d ec 89 96 fe fb da 46 4d 3b 93>,
_tokenIV: <Buffer 85 e2 5b de f3 92 ba d2 d1 33 74 e1 fe 38 a9 4b>,
data: <Buffer 7b 22 72 65 73 75 6c 74 22 3a 5b 6e 75 6c 6c 2c 22 69 64 6c 65 22 2c 6e 75 6c 6c 2c 6e 75 6c 6c 2c 6e 75 6c 6c 2c 34 31 2c 31 36 37 2c 36 30 2c 6e 75 … >,
_serverStamp: 55400 },
socket:
Socket {
domain: null,
_events: { message: [Function: bound _onMessage] },
_eventsCount: 1,
_maxListeners: undefined,
_handle:
UDP {
fd: 12,
lookup: [Function: lookup4],
owner: [Circular],
onmessage: [Function: onMessage] },
_receiving: true,
_bindState: 2,
type: ‘udp4’,
fd: -42,
_reuseAddr: undefined,
_queue: undefined },
_id: 1,
_promises: {},
_hasFailedToken: false,
_properties:
{ power: false,
mode: ‘idle’,
favoriteLevel: null,
temperature: 0,
humidity: null,
aqi: 41,
bright: 167,
filterLifeRemaining: 60,
filterHoursUsed: null,
useTime: null,
led: false,
ledBrightness: ‘unknown’,
buzzer: true },
_propertiesToMonitor:
[ ‘power’,
‘mode’,
‘favorite_level’,
‘temp_dec’,
‘humidity’,
‘aqi’,
‘bright’,
‘filter1_life’,
‘f1_hour_used’,
‘use_time’,
‘led’,
‘led_b’,
‘buzzer’ ],
_propertyDefinitions:
{ power: { mapper: [Function] },
mode: { mapper: [Function: IDENTITY_MAPPER] },
favorite_level: { name: ‘favoriteLevel’, mapper: [Function: IDENTITY_MAPPER] },
temp_dec: { name: ‘temperature’, mapper: [Function: mapper] },
humidity: { mapper: [Function: IDENTITY_MAPPER] },
aqi: { mapper: [Function: IDENTITY_MAPPER] },
bright: { mapper: [Function: IDENTITY_MAPPER] },
filter1_life:
{ name: ‘filterLifeRemaining’,
mapper: [Function: IDENTITY_MAPPER] },
f1_hour_used: { name: ‘filterHoursUsed’, mapper: [Function: IDENTITY_MAPPER] },
use_time: { name: ‘useTime’, mapper: [Function: IDENTITY_MAPPER] },
led: { mapper: [Function: mapper] },
led_b: { name: ‘ledBrightness’, mapper: [Function: mapper] },
buzzer: { mapper: [Function: mapper] } },
_reversePropertyDefinitions:
{ favoriteLevel: ‘favorite_level’,
temperature: ‘temp_dec’,
filterLifeRemaining: ‘filter1_life’,
filterHoursUsed: ‘f1_hour_used’,
useTime: ‘use_time’,
ledBrightness: ‘led_b’ },
_loadProperties: [Function: bound _loadProperties],
management: DeviceManagement { device: [Circular] },
debug:
{ [Function: debug]
namespace: ‘miio.device.[192.168.88.23]’,
enabled: false,
useColors: true,
color: 5,
inspectOpts: {} },
setPower: [Function],
_propertyMonitor:
Timeout {
_called: false,
_idleTimeout: 30000,
_idlePrev:
TimersList {
_idleNext: [Circular],
_idlePrev: [Circular],
_timer: [Object],
_unrefed: false,
msecs: 30000,
nextTick: false },
_idleNext:
TimersList {
_idleNext: [Circular],
_idlePrev: [Circular],
_timer: [Object],
_unrefed: false,
msecs: 30000,
nextTick: false },
_idleStart: 645,
_onTimeout: [Function: bound _loadProperties],
_timerArgs: undefined,
_repeat: 30000 },
_lastToken: 1495860172177 }

The main article on network configuration is Network configuration.

Configuring wireless is a two-part process; the first part is to identify and ensure the correct driver for your wireless device is installed (they are available on the installation media, but often have to be installed explicitly), and to configure the interface. The second is choosing a method of managing wireless connections. This article covers both parts, and provides additional links to wireless management tools.

The #iw section describes how to manually manage your wireless network interface / your wireless LANs using iw. The Network configuration#Network managers section describes several programs that can be used to automatically manage your wireless interface, some of which include a GUI and all of which include support for network profiles (useful when frequently switching wireless networks, like with laptops).

Device driver

The default Arch Linux kernel is modular, meaning many of the drivers for machine hardware reside on the hard drive and are available as modules. At boot, udev takes an inventory of your hardware and loads appropriate modules (drivers) for your corresponding hardware, which will in turn allow creation of a network interface.

Some wireless chipsets also require firmware, in addition to a corresponding driver. Many firmware images are provided by the linux-firmware package; however, proprietary firmware images are not included and have to be installed separately. This is described in #Installing driver/firmware.

Note: If the proper module is not loaded by udev on boot, simply load it manually. If udev loads more than one driver for a device, the resulting conflict may prevent successful configuration. Make sure to blacklist the unwanted module.

Check the driver status

To check if the driver for your card has been loaded, check the output of the lspci -k or lsusb -v command, depending on if the card is connected by PCI(e) or USB. You should see that some kernel driver is in use, for example:

$ lspci -k

06:00.0 Network controller: Intel Corporation WiFi Link 5100
	Subsystem: Intel Corporation WiFi Link 5100 AGN
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

Note: If the card is a USB device, running dmesg | grep usbcore as root should give something like usbcore: registered new interface driver rtl8187 as output.

Also check the output of the ip link command to see if a wireless interface was created; usually the naming of the wireless network interfaces starts with the letter «w», e.g. wlan0 or wlp2s0. Then bring the interface up with:

# ip link set interface up

For example, assuming the interface is wlan0, this is ip link set wlan0 up.

Check kernel messages for firmware being loaded:

# dmesg | grep firmware

[   7.148259] iwlwifi 0000:02:00.0: loaded firmware version 39.30.4.1 build 35138 op_mode iwldvm

If there is no relevant output, check the messages for the full output for the module you identified earlier (iwlwifi in this example) to identify the relevant message or further issues:

# dmesg | grep iwlwifi

[   12.342694] iwlwifi 0000:02:00.0: irq 44 for MSI/MSI-X
[   12.353466] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138 op_mode iwldvm
[   12.430317] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
...
[   12.430341] iwlwifi 0000:02:00.0: Detected Intel(R) Corporation WiFi Link 5100 AGN, REV=0x6B

If the kernel module is successfully loaded and the interface is up, you can skip the next section.

Installing driver/firmware

Check the following lists to discover if your card is supported:

• See the table of existing Linux wireless drivers and follow to the specific driver’s page, which contains a list of supported devices. There is also a List of Wi-Fi Device IDs in Linux^{[dead link 2022-11-11]}.
• The Ubuntu Wiki has a good list of wireless cards and whether or not they are supported either in the Linux kernel or by a user-space driver (includes driver name).
• Linux Wireless Support and The Linux Questions’ Hardware Compatibility List (HCL) also have a good database of kernel-friendly hardware.

Note that some vendors ship products that may contain different chip sets, even if the product identifier is the same. Only the usb-id (for USB devices) or pci-id (for PCI devices) is authoritative.

If your wireless card is listed above, follow the #Troubleshooting drivers and firmware subsection of this page, which contains information about installing drivers and firmware of some specific wireless cards. Then check the driver status again.

If your wireless card is not listed above, it is likely supported only under Windows (some Broadcom, 3com, etc). For these, you can try to use #ndiswrapper.

Utilities

Just like other network interfaces, the wireless ones are controlled with ip from the iproute2 package.

Managing a wireless connection requires a basic set of tools. Either use a network manager or use one of the following directly:

Software	Package	WEXT	nl80211	WEP	WPA/WPA2/WPA3	Archiso [1]
wireless_tools1	wireless_tools	Yes	No	Yes	No	Yes
iw	iw	No	Yes	Yes	No	Yes
wpa_supplicant	wpa_supplicant	Yes	Yes	No	Yes	Yes
iwd	iwd	No	Yes	No	Yes	Yes

1. Deprecated.

Note that some cards only support WEXT.

iw and wireless_tools comparison

The table below gives an overview of comparable commands for iw and wireless_tools. See iw replaces iwconfig for more examples.

iw command	wireless_tools command	Description
iw dev wlan0 link	iwconfig wlan0	Getting link status.
iw dev wlan0 scan	iwlist wlan0 scan	Scanning for available access points.
iw dev wlan0 set type ibss	iwconfig wlan0 mode ad-hoc	Setting the operation mode to ad-hoc.
iw dev wlan0 connect your_essid	iwconfig wlan0 essid your_essid	Connecting to open network.
iw dev wlan0 connect your_essid 2432	iwconfig wlan0 essid your_essid freq 2432M	Connecting to open network specifying channel.
iw dev wlan0 connect your_essid key 0:your_key	iwconfig wlan0 essid your_essid key your_key	Connecting to WEP encrypted network using hexadecimal key.
iwconfig wlan0 essid your_essid key s:your_key	Connecting to WEP encrypted network using ASCII key.
iw dev wlan0 set power_save on	iwconfig wlan0 power on	Enabling power save.

iw

Examples in this section assume that your wireless device interface is interface and that you are connecting to your_essid WiFi access point. Replace both accordingly.

Get the name of the interface

To get the name of your wireless interface, do:

$ iw dev

The name of the interface will be output after the word «Interface». For example, it is commonly wlan0.

Get the status of the interface

To check link status, use the following command.

$ iw dev interface link

You can get statistic information, such as the amount of tx/rx bytes, signal strength etc., with the following command:

$ iw dev interface station dump

Activate the interface

Tip: Usually this step is not required.

Some cards require that the kernel interface be activated before you can use iw or wireless_tools:

# ip link set interface up

Note: If you get errors like RTNETLINK answers: Operation not possible due to RF-kill, make sure that hardware switch is on. See #Rfkill caveat for details.

To verify that the interface is up, inspect the output of the following command:

$ ip link show interface

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether 12:34:56:78:9a:bc brd ff:ff:ff:ff:ff:ff

The UP in <BROADCAST,MULTICAST,UP,LOWER_UP> is what indicates the interface is up, not the later state DOWN.

Discover access points

To see what access points are available:

# iw dev interface scan | less

Note: If it displays Interface does not support scanning, then you probably forgot to install the firmware. In some cases, this message is also displayed when not running iw as root.

Tip: Depending on your location, you might need to set the correct regulatory domain in order to see all available networks.

The important points to check:

• SSID: the name of the network.
• Signal: is reported in a wireless power ratio in dBm (e.g. from -100 to 0). The closer the negative value gets to zero, the better the signal. Observing the reported power on a good quality link and a bad one should give an idea about the individual range.
• Security: it is not reported directly, check the line starting with capability. If there is Privacy, for example capability: ESS Privacy ShortSlotTime (0x0411), then the network is protected somehow.
  • If you see an RSN information block, then the network is protected by Robust Security Network protocol, also known as WPA2.
  • If you see an WPA information block, then the network is protected by Wi-Fi Protected Access protocol.
  • In the RSN and WPA blocks, you may find the following information:
    • Group cipher: value in TKIP, CCMP, both, others.
    • Pairwise ciphers: value in TKIP, CCMP, both, others. Not necessarily the same value than Group cipher.
    • Authentication suites: value in PSK, 802.1x, others. For home router, you will usually find PSK (i.e. passphrase). In universities, you are more likely to find 802.1x suite which requires login and password. Then you will need to know which key management is in use (e.g. EAP), and what encapsulation it uses (e.g. PEAP). See #WPA2 Enterprise and Wikipedia:Authentication protocol for details.
  • If you see neither RSN nor WPA blocks but there is Privacy, then WEP is used.

Set operating mode

You might need to set the proper operating mode of the wireless card. More specifically, if you are going to connect an ad-hoc network, you need to set the operating mode to ibss:

# iw dev interface set type ibss

Note: Changing the operating mode on some cards might require the wireless interface to be down (ip link set interface down).

Connect to an access point

Depending on the encryption, you need to associate your wireless device with the access point to use and pass the encryption key:

• No encryption

  # iw dev interface connect "your_essid"

• WEP
  • using a hexadecimal or ASCII key (the format is distinguished automatically, because a WEP key has a fixed length):

    # iw dev interface connect "your_essid" key 0:your_key

  • using a hexadecimal or ASCII key, specifying the third set up key as default (keys are counted from zero, four are possible):

    # iw dev interface connect "your_essid" key d:2:your_key

• Other
  • iw can only handle WEP. To connect using other encryption schemes, see the section on #Authentication below.

Regardless of the method used, you can check if you have associated successfully:

# iw dev interface link

Authentication

WPA2 Personal

WPA2 Personal, a.k.a. WPA2-PSK, is a mode of Wi-Fi Protected Access.

You can authenticate to WPA2 Personal networks using wpa_supplicant or iwd, or connect using a network manager. If you only authenticated to the network, then to have a fully functional connection, you will still need to assign the IP address(es) and routes either manually or using a DHCP client.

WPA2 Enterprise

WPA2 Enterprise is a mode of Wi-Fi Protected Access. It provides better security and key management than WPA2 Personal, and supports other enterprise-type functionality, such as VLANs and NAP. However, it requires an external authentication server, called RADIUS server, to handle the authentication of users. This is in contrast to Personal mode which does not require anything beyond the wireless router or access points (APs), and uses a single passphrase or password for all users.

The Enterprise mode enables users to log onto the Wi-Fi network with a username and password and/or a digital certificate. Since each user has a dynamic and unique encryption key, it also helps to prevent user-to-user snooping on the wireless network, and improves encryption strength.

This section describes the configuration of network clients to connect to a wireless access point with WPA2 Enterprise mode. See Software access point#RADIUS for information on setting up an access point itself.

Note: Enterprise mode requires a more complex client configuration, whereas Personal mode only requires entering a passphrase when prompted. Clients likely need to install the server’s CA certificate (plus per-user certificates if using EAP-TLS), and then manually configure the wireless security and 802.1X authentication settings.

For a comparison of protocols, see the following table.

Warning: It is possible to use WPA2 Enterprise without the client checking the server CA certificate. However, you should always seek to do so, because without authenticating the access point, the connection can be subject to a man-in-the-middle attack. This may happen because while the connection handshake itself may be encrypted, the most widely used setups transmit the password itself either in plain text or the easily breakable #MS-CHAPv2. Hence, the client might send the password to a malicious access point which then proxies the connection.

MS-CHAPv2

WPA2-Enterprise wireless networks demanding MSCHAPv2 type-2 authentication with PEAP sometimes require pptpclient in addition to the stock ppp package. netctl seems to work out of the box without ppp-mppe, however. In either case, usage of MSCHAPv2 is discouraged as it is highly vulnerable, although using another method is usually not an option.

eduroam

eduroam is an international roaming service for users in research, higher education and further education, based on WPA2 Enterprise.

Manual/automatic setup

• wpa_supplicant can be configured directly by its configuration file or using its CLI/GUI front ends and used in combination with a DHCP client. See the examples in /usr/share/doc/wpa_supplicant/wpa_supplicant.conf for configuring the connection details.
• iwd#WPA Enterprise
• NetworkManager can create WPA2 Enterprise profiles with nmcli or the graphical front ends. nmtui does not support this (NetworkManager issue 376), but may use existing profiles.
• ConnMan needs a separate configuration file before connecting to the network. See connman-service.config(5) and ConnMan#Connecting to eduroam (802.1X) for details.
• netctl supports wpa_supplicant configuration through blocks included with WPAConfigSection=. See netctl.profile(5) for details.

Tip: Custom certificates can be specified by adding the line 'ca_cert="/path/to/special/certificate.cer"' in WPAConfigSection.

WPA3 Personal

WPA3 Personal, a.k.a. WPA3-SAE, is a mode of Wi-Fi Protected Access.

Both wpa_supplicant and iwd support WPA3 Personal.

WPA3 Enterprise

WPA3 Enterprise is a mode of Wi-Fi Protected Access.

wpa_supplicant (since version 2:2.10-8) supports WPA3 Enterprise. See FS#65314.

Tips and tricks

Respecting the regulatory domain

The regulatory domain, or «regdomain», is used to reconfigure wireless drivers to make sure that wireless hardware usage complies with local laws set by the FCC, ETSI and other organizations. Regdomains use ISO 3166-1 alpha-2 country codes. For example, the regdomain of the United States would be «US», China would be «CN», etc.

Regdomains affect the availability of wireless channels. In the 2.4GHz band, the allowed channels are 1-11 for the US, 1-14 for Japan, and 1-13 for most of the rest of the world. In the 5GHz band, the rules for allowed channels are much more complex. In either case, consult this list of WLAN channels for more detailed information.

Regdomains also affect the limit on the effective isotropic radiated power (EIRP) from wireless devices. This is derived from transmit power/»tx power», and is measured in dBm/mBm (1dBm=100mBm) or mW (log scale). In the 2.4GHz band, the maximum is 30dBm in the US and Canada, 20dBm in most of Europe, and 20dBm-30dBm for the rest of the world. In the 5GHz band, maximums are usually lower. Consult the wireless-regdb for more detailed information (EIRP dBm values are in the second set of brackets for each line).

Misconfiguring the regdomain can be useful — for example, by allowing use of an unused channel when other channels are crowded, or by allowing an increase in tx power to widen transmitter range. However, this is not recommended as it could break local laws and cause interference with other radio devices.

The kernel loads the database directly when wireless-regdb is installed. For direct loading, the kernel should, for security’s sake, be configured with CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS set to yes to allow for cryptographic verification of the database. This is true of the stock Arch kernel, but if you are using an alternate kernel, or compiling your own, you should verify this. More information is available at this guide.

To configure the regdomain, install wireless-regdb and reboot (to reload the cfg80211 module and all related drivers). Check the boot log to make sure that the database is loaded and key verified by cfg80211:

# dmesg | grep cfg80211

The current regdomain can be set to the United States with:

# iw reg set US

And queried with:

$ iw reg get

Note: Your device may be set to country «00», which is the «world regulatory domain» and contains generic settings. If this cannot be unset, check your configuration as detailed bellow.

However, setting the regdomain may not alter your settings. Some devices have a regdomain set in firmware/EEPROM, which dictates the limits of the device, meaning that setting regdomain in software can only increase restrictions, not decrease them. For example, a CN device could be set in software to the US regdomain, but because CN has an EIRP maximum of 20dBm, the device will not be able to transmit at the US maximum of 30dBm.

For example, to see if the regdomain is being set in firmware for an Atheros device:

# dmesg | grep ath:

For other chipsets, it may help to search for «EEPROM», «regdomain», or simply the name of the device driver.

To see if your regdomain change has been successful, and to query the number of available channels and their allowed transmit power:

$ iw list | grep -A 15 Frequencies:

A more permanent configuration of the regdomain can be achieved through editing /etc/conf.d/wireless-regdom and uncommenting the appropriate domain.

wpa_supplicant can also use a regdomain in the country= line of /etc/wpa_supplicant/wpa_supplicant.conf.

It is also possible to configure the cfg80211 kernel module to use a specific regdomain by adding, for example, options cfg80211 ieee80211_regdom=JP as module options. The module option is inherited from the old regulatory implementation and in modern kernels act as a userspace regulatory hint as if it came through nl80211 through utilities like iw and wpa_supplicant.

Rfkill caveat

Many laptops have a hardware button (or switch) to turn off the wireless card; however, the card can also be blocked by the kernel. This can be handled by rfkill. To show the current status:

$ rfkill

ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

If the card is hard-blocked, use the hardware button (switch) to unblock it. If the card is not hard-blocked but soft-blocked, use the following command:

# rfkill unblock wifi

Note: It is possible that the card will go from hard-blocked and soft-unblocked state into hard-unblocked and soft-blocked state by pressing the hardware button (i.e. the soft-blocked bit is just switched no matter what). This can be adjusted by tuning some options of the rfkill kernel module.

Hardware buttons to toggle wireless cards are handled by a vendor specific kernel module. Frequently, these are WMI modules. Particularly for very new hardware models, it happens that the model is not fully supported in the latest stable kernel yet. In this case, it often helps to search the kernel bug tracker for information and report the model to the maintainer of the respective vendor kernel module, if it has not happened already.

See also [2].

Power saving

See Power saving#Network interfaces.

Troubleshooting

This section contains general troubleshooting tips, not strictly related to problems with drivers or firmware. For such topics, see next section #Troubleshooting drivers and firmware.

Temporary internet access

If you have problematic hardware and need internet access to, for example, download some software or get help in forums, you can make use of Android’s built-in feature for internet sharing via USB cable. See Android tethering#USB tethering for more information.

Observing logs

A good first measure to troubleshoot is to analyze the system’s logfiles first. In order not to manually parse through them all, it can help to open a second terminal/console window and watch the kernels messages with

# dmesg -w

while performing the action, e.g. the wireless association attempt.

When using a tool for network management, the same can be done for systemd with

# journalctl -f 

Frequently, a wireless error is accompanied by a deauthentication with a particular reason code, for example:

wlan0: deauthenticating from XX:XX:XX:XX:XX:XX by local choice (reason=3)

Looking up the reason code might give a first hint. Maybe it also helps you to look at the control message flowchart, the journal messages will follow it.

The individual tools used in this article further provide options for more detailed debugging output, which can be used in a second step of the analysis, if required.

Failed to get IP address

• If getting an IP address repeatedly fails using the default dhcpcd client, try installing and using dhclient instead. Do not forget to select dhclient as the primary DHCP client in the connection manager.

• If you can get an IP address for a wired interface and not for a wireless interface, try disabling the wireless card’s power saving features (specify off instead of on).

• If you get a timeout error due to a waiting for carrier problem, then you might have to set the channel mode to auto for the specific device:

# iwconfig wlan0 channel auto

Before changing the channel to auto, make sure your wireless interface is down. After it has successfully changed it, you can bring the interface up again and continue from there.

Valid IP address but cannot resolve host

If you are on a public wireless network that may have a captive portal, make sure to query an HTTP page (not an HTTPS page) from your web browser, as some captive portals only redirect HTTP.
If this is not the issue, check if you can resolve domain names, it may be necessary to use the DNS server advertised via DHCP.

Setting RTS and fragmentation thresholds

Wireless hardware disables RTS and fragmentation by default. These are two different methods of increasing throughput at the expense of bandwidth (i.e. reliability at the expense of speed). These are useful in environments with wireless noise or many adjacent access points, which may create interference leading to timeouts or failing connections.

Packet fragmentation improves throughput by splitting up packets with size exceeding the fragmentation threshold. The maximum value (2346) effectively disables fragmentation since no packet can exceed it. The minimum value (256) maximizes throughput, but may carry a significant bandwidth cost.

# iw phy0 set frag 512

RTS improves throughput by performing a handshake with the access point before transmitting packets with size exceeding the RTS threshold. The maximum threshold (2347) effectively disables RTS since no packet can exceed it. The minimum threshold (0) enables RTS for all packets, which is probably excessive for most situations.

# iw phy0 set rts 500

Note: phy0 is the name of the wireless device as listed by iw phy.

Random disconnections

Cause #1

If your journal says wlan0: deauthenticating from MAC by local choice (reason=3) and you lose your Wi-Fi connection, it is likely that you have a bit too aggressive power-saving on your Wi-Fi card. Try disabling the wireless card’s power saving features (specify off instead of on).

If your card does not support enabling/disabling power save mode, check the BIOS for power management options. Disabling PCI-Express power management in the BIOS of a Lenovo W520 resolved this issue.

Cause #2

If you are experiencing frequent disconnections and your journal shows messages such as

ieee80211 phy0: wlan0: No probe response from AP xx:xx:xx:xx:xx:xx after 500ms, disconnecting

try changing the channel bandwidth to 20MHz through your router’s settings page.

Cause #3

On some laptop models with hardware rfkill switches (e.g., Thinkpad X200 series), due to wear or bad design, the switch (or its connection to the mainboard) might become loose over time resulting in seemingly random hardblocks/disconnects when you accidentally touch the switch or move the laptop.
There is no software solution to this, unless your switch is electrical and the BIOS offers the option to disable the switch.
If your switch is mechanical (and most are), there are lots of possible solutions, most of which aim to disable the switch: Soldering the contact point on the mainboard/wifi-card, gluing or blocking the switch, using a screw nut to tighten the switch or removing it altogether.

Cause #4

Another cause for frequent disconnects or a complete failure to connect may also be a sub-standard router, incomplete settings of the router, interference by other wireless devices or low quality signal.

To troubleshoot, first try to connect to the router with no authentication and by getting closer to it.

If that works, enable WPA/WPA2 again but choose fixed and/or limited router settings. For example:

• If the router is considerably older than the wireless device you use for the client, test if it works with setting the router to one wireless mode
• Disable mixed-mode authentication (e.g. only WPA2 with AES, or TKIP if the router is old)
• Try a fixed/free channel rather than «auto» channel (maybe the router next door is old and interfering)
• Disable WPS
• Change the router’s 5 GHz channel(s) to a non-DFS (Dynamic Frequency Selection) channel. Connections on such channels may be dropped or suddenly switched due to interference from nearby weather radar.
• Try setting your client to 2.4 GHz only instead of letting it choose what it thinks is best between 5 GHz and 2.4 GHz (the later has a lower throughput but will provide a more stable connection over longer distances)
• Disable 40MHz channel bandwidth (lower throughput but less likely collisions) with cfg80211.cfg80211_disable_40mhz_24ghz=1
• If the router has quality of service settings, check completeness of settings (e.g. Wi-Fi Multimedia (WMM) is part of optional QoS flow control. An erroneous router firmware may advertise its existence although the setting is not enabled)

Cause #5

On some wireless network adapters (e.g. Qualcomm Atheros AR9485), random disconnects can happen with a DMA error:

# journalctl -xb

ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020 DMADBG_7=0x0000a400
wlp1s0: authenticate with 56:e7:ee:7b:55:bc
wlp1s0: send auth to 56:e7:ee:7b:55:bc (try 1/3)
wlp1s0: send auth to 56:e7:ee:7b:55:bc (try 2/3)
wlp1s0: send auth to 56:e7:ee:7b:55:bc (try 3/3)
wlp1s0: authentication with 56:e7:ee:7b:55:bc timed out

A possible workaround is to disable the Intel IOMMU driver (DMA), adding intel_iommu=off to the kernel parameters [3].

Note: The Intel IOMMU driver is needed for some advanced virtual machine features, like PCI pass-through.

Cause #6

If you are using a device with iwlwifi and iwlmvm for wireless connectivity, and your Wi-Fi card appears to disappear when on battery power (perhaps after a reboot or resuming from suspend), this can be fixed by configuring power saving settings in iwlmvm.

Create the file /etc/modprobe.d/iwlmvm.conf if it does not exist already, then add the following line to it:

/etc/modprobe.d/iwlmvm.conf

options iwlmvm power_scheme=1

A power_scheme of 1 sets iwlmvm to «Always Active.» Available options are:

Value	Description
1	Always Active
2	Balanced
3	Low-power

This fix was discovered at [4].

Cause #7

If your device undergoes long periods of inactivity (e.g. a file server), the disconnection may be due to power saving, which will block incoming traffic and prevent connections. Try disabling power saving for the interface:

# iw dev interface set power_save off

You can create a udev rule to do this on boot, see Power management#Network interfaces.

Cause #8

If you notice occasional interruptions when connected to a mesh network (e.g., WiFi6) and notice a message such as:

# journalctl -b

kernel: wlan0: disconnect from AP aa:bb:cc:dd:ee:ff for new auth to 11:22:33:44:55:66

You are experiencing roaming issues. Depending on your mean of connection and the issue at hand, one could:

• Lock the BSSID (the aa:bb:cc:dd:ee:ff show above) in NetworkManager if roaming is not desired (see NetworkManager#Regular network disconnects, latency and lost packets (WiFi)).
• Adjust the bgscan setting in Wpa_supplicant#Roaming

Wi-Fi networks invisible because of incorrect regulatory domain

If the computer’s Wi-Fi channels do not match those of the user’s country, some in-range Wi-Fi networks might be invisible because they use wireless channels that are not allowed by default. The solution is to configure the regulatory domain correctly; see #Respecting the regulatory domain.

Troubleshooting drivers and firmware

This section covers methods and procedures for installing kernel modules and firmware for specific chipsets, that differ from generic method.

See Kernel modules for general information on operations with modules.

Ralink/Mediatek

rt2x00

Unified driver for Ralink chipsets (it replaces rt2500, rt61, rt73, etc). This driver has been in the Linux kernel since 2.6.24, you only need to load the right module for the chip: rt2400pci, rt2500pci, rt2500usb, rt61pci or rt73usb which will autoload the respective rt2x00 modules too.

A list of devices supported by the modules is available at the project’s homepage.

Additional notes

• Since kernel 3.0, rt2x00 includes also these drivers: rt2800pci, rt2800usb.
• Since kernel 3.0, the staging drivers rt2860sta and rt2870sta are replaced by the mainline drivers rt2800pci and rt2800usb [5].
• Some devices have a wide range of options that can be configured with iwpriv. These are documented in the source tarballs available from Ralink.

rt3090

For devices which use the rt3090 chipset, it should be possible to use the rt2800pci driver; however, it does not work with this chipset very well (e.g. sometimes it is not possible to use higher rate than 2Mb/s).

rt3290

The rt3290 chipset is recognised by the kernel rt2800pci module. However, some users experience problems and reverting to a patched Ralink driver seems to be beneficial in these cases.

rt3573

New chipset as of 2012. It may require proprietary drivers from Ralink. Different manufacturers use it; see the Belkin N750 DB wireless usb adapter forums thread.

mt7612u

New chipset as of 2014, released under their new commercial name Mediatek. It is an AC1200 or AC1300 chipset. Manufacturer provides drivers for Linux on their support page. As of kernel 5.5 it should be supported by the included mt76 driver.

Realtek

See [6]^{[dead link 2022-11-10]} for a list of Realtek chipsets and specifications.

rtl8192cu

The driver is now in the kernel, but many users have reported being unable to make a connection although scanning for networks does work.

8192cu-dkms^AUR includes many patches; try this if it does not work fine with the driver in kernel.

rtl8723ae/rtl8723be

The rtl8723ae and rtl8723be modules are included in the mainline Linux kernel.

Some users may encounter errors with powersave on this card. This is shown with occasional disconnects that are not recognized by high level network managers (netctl, NetworkManager). This error can be confirmed by running dmesg -w as root or journalctl -f as root and looking for output related to powersave and the rtl8723ae/rtl8723be module. If you have this issue, use the fwlps=0 kernel option which should prevent the WiFi card from automatically sleeping and halting connection. See Kernel module#Setting module options.

If you have poor signal, perhaps your device has only one physical antenna connected, and antenna autoselection is broken. You can force the choice of antenna with ant_sel=1 or ant_sel=2 kernel option. [7]

rtl88xxau

Realtek chipsets rtl8811au, rtl8812au, rtl8814au and rtl8821au designed for various USB adapters ranging from AC600 to AC1900. Several packages provide various kernel drivers, these require DKMS (the dkms package and the kernel headers installed):

Chipset	Package	Notes
rtl8811au, rtl8812au, rtl8821au	rtl88xxau-aircrack-dkms-gitAUR	Aircrack-ng kernel module for 8811au, 8812au and 8821au chipsets with monitor mode and injection support.
rtl8812au	rtl8812au-dkms-gitAUR	Latest official Realtek driver version for rtl8812au only.
rtl8811au, rtl8821au	rtl8821au-dkms-gitAUR	Newer driver version for rtl8821au.
rtl8814au	rtl8814au-dkms-gitAUR	Possibly works for rtl8813au too.

rtl8811cu/rtl8821cu

rtl8821cu-dkms-git^AUR provides a kernel module for the Realtek 8811cu and 8821cu chipset.

This requires DKMS, so make sure you have your proper kernel headers installed.

If no wireless interface shows up even though the 8821cu module is loaded, you may need to manually specify the rtw_RFE_type option [8][9]. Try e.g. rtw_RFE_type=0x26, other values might also work. See Kernel module#Setting module options for details.

rtl8821ce

rtl8821ce-dkms-git^AUR provides a kernel module for the Realtek 8821ce chipset found in the Asus X543UA.

This requires DKMS, so make sure you have your proper kernel headers installed.

Note: It has been reported [10] that the default rtl8821ce module provided by Realtek is broken for Linux kernel ≥ 5.9, which may lead to low connectivity. The AUR version above should be preferred. See the statement on GitHub. Use lspci -k to check whether the default kernel driver (rtw88_8821ce) is in use. If it is, blacklist it and reboot your system.

rtl8822bu

rtl88x2bu-dkms-git^AUR provides a kernel module for the Realtek 8822bu chipset found in the Edimax EW7822ULC USB3, Asus AC53 Nano USB 802.11ac and TP-Link Archer T3U adapter.

This requires DKMS, so make sure you have your proper kernel headers installed.

rtl8xxxu

Issues with the rtl8xxxu mainline kernel module may be solved by compiling a third-party module for the specific chipset. The source code can be found in GitHub repositories.

Some drivers may be already prepared in the AUR, e.g. rtl8723bu-dkms-git^AUR.

RTW88

An RTW88 kernel module patchset has been recently posted to the kernel mailing list, which should hopefully make it into the mainstream kernel.

Upstream kernels or those with the patchset will support most RTW88 chip devices if configured and compiled to do so. linux-zen and linux-zen-git^AUR both include these patches, with the packaged version already having the module built.

The driver supports: 882BE, 8822BU, 8822CE, 8822CU, 8723DE, 8723DU, 8821CE, and 8821CU.

Atheros

The MadWifi team currently maintains three different drivers for devices with Atheros chipset:

• madwifi is an old, obsolete driver. Not present in Arch kernel since 2.6.39.1[11].
• ath5k is a newer driver which replaces the madwifi driver. Currently a better choice for some chipsets, but not all chipsets are supported (see below)
• ath9k is the newest of these three drivers. It is intended for newer Atheros chipsets. All of the chips with 802.11n capabilities are supported.

There are some other drivers for some Atheros devices. See Linux Wireless documentation for details.

ath5k

External resources:

• https://wireless.wiki.kernel.org/en/users/drivers/ath5k
• Debian:ath5k

If you find web pages randomly loading very slow, or if the device is unable to lease an IP address, try to switch from hardware to software encryption by loading the ath5k module with nohwcrypt=1 option. See Kernel modules#Setting module options for details.

Some laptops may have problems with their wireless LED indicator flickering red and blue. To solve this problem, do:

# echo none > /sys/class/leds/ath5k-phy0::tx/trigger
# echo none > /sys/class/leds/ath5k-phy0::rx/trigger

For alternatives, see this bug report.

ath9k

External resources:

• https://wireless.wiki.kernel.org/en/users/drivers/ath9k
• Debian:ath9k

As of Linux 3.15.1, some users have been experiencing a decrease in bandwidth. In some cases, this can fixed by setting the nohwcrypt=1 option for the ath9k module. See Kernel module#Setting module options.

Note: Use the command lsmod to see what modules are in use and change ath9k if it is named differently (e.g. ath9k_htc).

An ath9k mailing list exists for support and development related discussions.

Power saving

Although Linux Wireless says that dynamic power saving is enabled for Atheros ath9k single-chips newer than AR9280, for some devices (e.g. AR9285), powertop might still report that power saving is disabled. In this case, enable it manually.

On some devices (e.g. AR9285), enabling the power saving might result in the following error:

# iw dev wlan0 set power_save on

command failed: Operation not supported (-95)

The solution is to set the ps_enable=1 option for the ath9k module; see Kernel module#Setting module options.

Intel

iwlegacy

iwlegacy is the wireless driver for Intel’s 3945 and 4965 wireless chips. The firmware is included in the linux-firmware package.

udev should load the driver automatically, otherwise load iwl3945 or iwl4965 manually. See Kernel modules for details.

If you have problems connecting to networks in general (e.g. random failures with your card on bootup or your link quality is very poor), try to disable 802.11n:

/etc/modprobe.d/iwl4965.conf

options iwl4965 11n_disable=1

If the failures persist during bootup and you are using Nouveau driver, try enabling early KMS to prevent the conflict [12].

iwlwifi

iwlwifi is the wireless driver for Intel’s current wireless chips, such as 5100AGN, 5300AGN, and 5350AGN. See the full list of supported devices. The firmware is included in the linux-firmware package. The linux-firmware-iwlwifi-git^AUR may contain some updates sooner.

If you have problems connecting to networks in general or your link quality is very poor, try to disable 802.11n, and perhaps also enable software encryption:

/etc/modprobe.d/iwlwifi.conf

options iwlwifi 11n_disable=1 swcrypto=1

If you have a problem with slow uplink speed in 802.11n mode, for example 20Mbps, try to enable antenna aggregation:

/etc/modprobe.d/iwlwifi.conf

options iwlwifi 11n_disable=8

Do not be confused with the option name, when the value is set to 8 it does not disable anything but re-enables transmission antenna aggregation.[13] [14]

In case this does not work for you, you may try disabling power saving for your wireless adapter.

Some have never gotten this to work. Others found salvation by disabling N in their router settings after trying everything. This is known to have been the only solution on more than one occasion. The second link there mentions a 5ghz option that might be worth exploring.

If you have an 802.11ax (WiFi 6) access point and have problems detecting the beacons or an unreliable connection, review Intel Article 54799.

Note: Using 11n_disable=0 will also prevent 802.11ac and only allow connection with slower protocols (802.11a in the 5GHz band or 802.11b/g in the 2.4 GHz band).

Bluetooth coexistence

If you have difficulty connecting a bluetooth headset and maintaining good downlink speed, try disabling bluetooth coexistence [15]:

/etc/modprobe.d/iwlwifi.conf

options iwlwifi bt_coex_active=0

Note: Since kernel version 5.8, the bt_coex_active and sw_crypto module options have been disabled for the hardware handled by the iwlmvm kernel module. For older hardware handled by the iwldvm module, the options are still enabled.

Firmware issues

You may have some issue where the driver outputs stack traces & errors, which can cause some stuttering.

# dmesg

Microcode SW error detected.  Restarting 0x2000000.

Alternatively, you may simply experience miscellaneous issues (e.g. connection issues on 5GHz, random disconnections, no connection on resume).

To confirm it is the cause of the issues, downgrade the package linux-firmware.

If confirmed, move the buggy firmware files so that an older version is loaded (to be able to have an up to date linux-firmware since it is not only providing firmware updates for your Intel WiFi card):

# for i in {64..73} ; do mv /usr/lib/firmware/iwlwifi-ty-a0-gf-a0-$i.ucode.xz /usr/lib/firmware/iwlwifi-ty-a0-gf-a0-$i.ucode.xz.bak ; done

To avoid having to repeat these steps manually after each update, use the NoExtract array in pacman.conf with a wildcard to block their installation. See pacman#Skip files from being installed to system.

Adapter not detected after booting from Windows

If the WiFi adapter is not getting detected after finishing a session in Windows, this might be due to Windows’ Fast Startup feature which is enabled by default. Try disabling Fast Startup. The iwlwifi kernel driver wiki has an entry for this.

Disabling LED blink

Note: This works with the iwlegacy and iwlwifi drivers.

The default settings on the module are to have the LED blink on activity. Some people find this extremely annoying. To have the LED on solid when Wi-Fi is active, you can use the systemd-tmpfiles:

/etc/tmpfiles.d/phy0-led.conf

w /sys/class/leds/phy0-led/trigger - - - - phy0radio

Run systemd-tmpfiles --create phy0-led.conf for the change to take effect, or reboot.

To see all the possible trigger values for this LED:

# cat /sys/class/leds/phy0-led/trigger

Tip: If you do not have /sys/class/leds/phy0-led, you may try to use the led_mode="1" module option. It should be valid for both iwlwifi and iwlegacy drivers.

Broadcom

See Broadcom wireless.

Other drivers/devices

Tenda w322u

Treat this Tenda card as an rt2870sta device. See #rt2x00.

orinoco

This should be a part of the kernel package and be installed already.

Some Orinoco chipsets are Hermes II. You can use the wlags49_h2_cs driver instead of orinoco_cs and gain WPA support. To use the driver, blacklist orinoco_cs first.

prism54

The driver p54 is included in kernel, but you have to download the appropriate firmware for your card from this site and install it into the /usr/lib/firmware directory.

Note: There is also an older, deprecated driver prism54, which might conflict with the newer driver (p54pci or p54usb). Make sure to blacklist prism54.

zd1211rw

zd1211rw is a driver for the ZyDAS ZD1211 802.11b/g USB WLAN chipset, and it is included in recent versions of the Linux kernel. See [16] for a list of supported devices. You only need to install the firmware for the device, provided by the zd1211-firmware^AUR package.

hostap_cs

Host AP is a Linux driver for wireless LAN cards based on Intersil’s Prism2/2.5/3 chipset. The driver is included in Linux kernel.

Note: Make sure to blacklist the orinico_cs driver, it may cause problems.

ndiswrapper

Ndiswrapper is a wrapper script that allows you to use some Windows drivers in Linux. You will need the .inf and .sys files from your Windows driver.

Note: Be sure to use drivers appropriate to your architecture (x86 vs. x86_64).

Tip: If you need to extract these files from an .exe file, you can use cabextract.

Follow these steps to configure ndiswrapper.

1. Install ndiswrapper-dkms.
2. Install the driver to /etc/ndiswrapper/:

   # ndiswrapper -i filename.inf

3. List all installed drivers for ndiswrapper:

   $ ndiswrapper -l

4. Let ndiswrapper write its configuration in /etc/modprobe.d/ndiswrapper.conf:

   # ndiswrapper -m
   # depmod -a

The ndiswrapper install is almost finished; you can load the module at boot.

Test that ndiswrapper will load now:

# modprobe ndiswrapper
# iwconfig

and wlan0 should now exist. If you have problems, some help is available at:
ndiswrapper howto and ndiswrapper FAQ.

See also

• The Linux Wireless project
• Aircrack-ng guide on installing drivers
• Wireless Device Database Wiki (This fork is hosted by wi-cat.ru since the original wiki has shut down. There are two less complete versions available: TechInfoDepot, deviwiki)