iwlwifi is the wireless driver for Intel's current wireless chips.
- 1 Kernel
- 2 Firmware
- 3 Network device names
- 4 Testing
- 5 Troubleshooting
- 6 See also
- 7 External resources
To make it work some kernel configuration is needed. The driver supports 802.11a/b/g/n/ac (depending on the device), so IEEE 802.11 should be enabled.
[*] Networking support ---> [*] Wireless ---> <M/*> cfg80211 - wireless configuration API [ ] nl80211 testmode command [ ] enable developer warnings [ ] cfg80211 regulatory debugging [ ] cfg80211 certification onus [*] enable powersave by default [ ] cfg80211 DebugFS entries [ ] use statically compiled regulatory rules database [ ] cfg80211 wireless extensions compatibility <M/*> Generic IEEE 802.11 Networking Stack (mac80211) [*] Minstrel [*] Minstrel 802.11n support [ ] Minstrel 802.11ac support Default rate control algorithm (Minstrel) ---> [ ] Enable mac80211 mesh networking (pre-802.11s) support -*- Enable LED triggers [ ] Export mac80211 internals in DebugFS [ ] Trace all mac80211 debug messages [ ] Select mac80211 debugging features ----
Device driver iwlwifi
Device Drivers ---> [*] Network device support ---> --- Network device support [*] Wireless LAN ---> --- Wireless LAN [ ] mac80211-based legacy WDS support [ ] ADMtek devices [ ] Atheros/Qualcomm devices [ ] Atmel devices [ ] Broadcom devices [ ] Cisco devices [*] Intel devices < > Intel PRO/Wireless 2100 Network Connection < > Intel PRO/Wireless 2200BG and 2915ABG Network Connection < > Intel Wireless WiFi 4965AGN (iwl4965) < > Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945) <M> Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) <M> Intel Wireless WiFi DVM Firmware support <M> Intel Wireless WiFi MVM Firmware support Debugging Options ---> [ ] Intersil devices [ ] Marvell devices [ ] MediaTek devices [ ] Ralink devices [ ] Realtek devices [ ] Redpine Signals Inc devices [ ] STMicroelectronics devices [ ] Texas Instrument devices [ ] ZyDAS devices [ ] Quantenna wireless cards support < > Simulated radio testing tool for mac80211 < > Wireless RNDIS USB support
In case the driver is built into the kernel (
<*>) instead as a module (
<M>), also the firmware needs to be built into the kernel. See the section When using built-in configuration.
After changes on kernel configuration do not forget to rebuild the kernel.
After rebuilding the kernel and rebooting with this kernel, the selected options can be verified as follows:
Support for the /proc/config.gz pseudo-file is enabled through the Kernel/IKCONFIG_Support feature.
zgrep 'IWLWIFI\|IWLDVM\|IWLMVM' /proc/config.gz
emerge --ask sys-kernel/linux-firmware
When using built-in configuration
In case the driver is built into the kernel (
<*>) instead as a module (
<M>), also the firmware needs to be built into the kernel.
Device Drivers ---> Generic Driver Options ---> Firmware loader ---> -*- Firmware loading facility (iwlwifi-xxxx.ucode) Build named firmware blobs into the kernel binary (/lib/firmware) Firmware blobs root directory [ ] Enable the firmware sysfs fallback mechanism
In this case replace
iwlwifi-xxxx.ucode with the exact firmware name. Some attention seems to be needed for FW_LOADER_USER_HELPER_FALLBACK.
savedconfig USE flag could be set for Linux firmware in order to remove unneeded stuff from /lib/firmware/. As for example the
Intel® Centrino® Advanced-N 6205 needs iwlwifi-6000g2a-ucode while anything else may be commented out.
Network device names
Network device names such as eth0 or wlan0 as provided by the kernel are normally changed on system boot (see dmesg) by the /lib/udev/rules.d/80-net-name-slot.rules udev rule.
To keep the classic naming this rule can be overwritten with an equally named empty file in the /etc/udev/rules.d directory:
After a reboot with the new kernel or after loading the modules, the device can be checked for availability by using following methods:
/sys file system
Get the device name by listing the /sys/class/net directory contents using ls -al or the tree command (provided by the app-text/tree package):
/sys/class/net/ ├── enp2s14 -> ../../devices/pci0000:00/0000:00:1e.0/0000:02:0e.0/net/enp2s14 ├── lo -> ../../devices/virtual/net/lo ├── sit0 -> ../../devices/virtual/net/sit0 └── wlp8s0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:08:00.0/net/wlp8s0
To obtain the device name and verify that the wireless card is detected, execute the following ip command:
3: wlan0: ...
The ifconfig command is provided through the sys-apps/net-tools package. Use ifconfig -a to list all detected network cards, even those that are not enabled/active yet:
A network card can be activated as follows:
ifconfig -v wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill WARNING: at least one error occurred. (-1)
In this example, enabling the wireless card failed as a radio frequency kill state is set (usually to keep power consumption at bay and not connect by accident to a wireless network).
If the wireless network card driver supports the nl80211 stack, then the iw command as offered by the net-wireless/iw package can show the detected wireless cards:
phy#0 Interface wlan0 ifindex 4 type managed
modprobe and modinfo
modprobe should return nothing:
Most information about the driver module can be obtained by modinfo iwlwifi:
lspci should display
iwlwifi for both
Kernel driver in use: and
lspci -nnkv | sed -n '/Network/,/^$/p'
03:00.0 Network controller : Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0082] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1321] Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f7d00000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities:  Advanced Error Reporting Capabilities:  Device Serial Number confidential Kernel driver in use: iwlwifi Kernel modules: iwlwifi
xx:xx.x identifier will be useful for grepping specific information from dmesg.
dmesg | grep -i -E '03:00.0|wlp|iwl|80211'
[ 0.269955] pci 0000:03:00.0: [8086:0082] type 00 class 0x028000 [ 0.270091] pci 0000:03:00.0: reg 0x10: [mem 0xf7d00000-0xf7d01fff 64bit] [ 0.270764] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold [ 2.013147] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 2.014322] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 2.027273] cfg80211: failed to load regulatory.db [ 4.733442] iwlwifi 0000:03:00.0: enabling device (0100 -> 0102) [ 4.733572] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control [ 4.738660] iwlwifi 0000:03:00.0: loaded firmware version 220.127.116.11 op_mode iwldvm [ 4.742454] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled [ 4.742456] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled [ 4.742457] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 4.742458] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0 [ 4.777103] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 4.778301] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0 [ 7.288925] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 7.582127] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 7.661669] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 10.898640] wlp3s0: authenticate with my WLAN AP [ 10.902618] wlp3s0: send auth to my WLAN AP1 (try 1/3) [ 10.907440] wlp3s0: authenticated [ 10.907627] wlp3s0: waiting for beacon from my WLAN AP [ 10.969957] wlp3s0: associate with my WLAN AP (try 1/3) [ 10.976142] wlp3s0: RX AssocResp from my WLAN AP (capab=0x1431 status=0 aid=2) [ 10.996247] wlp3s0: associated [ 11.024074] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 11.071257] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised my WLAN AP
Kernel not loaded
Check if the correct kernel is loaded. This can be accomplished as follows (depends on the IKCONFIG feature):
zgrep CONFIG_IWL /proc/config.gz
- For systems using udev or systemd, it is imperative to configure the kernel to load binary blobs. In this case the wireless card's firmware is the firmware that needs loaded. More information on configuring the kernel in this manner can be found in the following thread on the Gentoo forums: FW_LOADER_USER_HELPER_FALLBACK.
Wireless not working
- Intel Corporation Wireless 8260 (rev 3a) can't access the RSA semaphore it is write protected
- Intel Wireless-AC 9560 iwlwifi not working kernel 5.4.0
No internet connection
If you can connect to an access point, but still can't connect to any server or get any connection to the internet it might be worth a try to disable 802.11n and/or enable software encryption. You can pass the
swcrypto=1 option to the
iwlwifi module. In order to pass the option automatically on module load create the file /etc/modprobe.d/iwlwifi.conf as follows:
options iwlwifi 11n_disable=1 swcrypto=1
In newer kernels, inspected as of 5.3.7, setting 11n_disable=1 (or masked with 0x01) will result in 802.11ac being disabled. This will limit the device to a maximum of 54Mbit throughput.
- Wifi — describes the setup of a WiFi (wireless) network device.
- Wpa_supplicant — a wifi supplicant to handle network authentication.
- Network management using DHCPCD — explains how to use dhcpcd for complete network stack management.
- Netifrc — Gentoo's default framework for configuring and managing network interfaces.
- Troubleshooting — provide users, in particular new ones, with a set of techniques and tools to allow them to troubleshoot and fix problems with their Gentoo setups on their own.