Wireless Troubleshooting
WiFi issues are influenced by many different factors, including:
- Hardware (WiFi card, access point)
- Settings at both ends of the connection
- The local environment
Basic Troubleshooting
Section titled “Basic Troubleshooting”If you’re having problems, try these steps first:
- Try unplugging the wireless router or modem to reboot it.
- Try airplane mode by pressing Fn+F11, waiting 10s, then disabling.
- Try rebooting the computer.
Some router settings can cause problems. Try adjusting your access point to these settings:
- WPA2-AES is preferred over WPA/WPA2 mixed mode or TKIP.
- A channel width of 20 MHz in the 2.4 GHz band is more stable than automatic 20/40 MHz or fixed 40 MHz.
- Set 2.4Ghz and 5Ghz SSID names differently.
- Pick a fixed channel. Use either 1, 6, or 11 in the 2.4 Ghz band, rather than automatic selection.
- Check if the router is set to N speeds only. Auto B/G/N is preferred.
- Lower the max/burst speeds, turn off channel bonding, and reduce channel width. Setting the speed to 600 Mb/s or 450 Mb/s will use spread frequencies to achieve those speeds and may decrease stability. Try setting it to 289/300 Mb/s (N speed) or or 54 Mb/s (G speed).
- After making these changes, reboot the router.
If the issues started after you applied updates, try running this command to make sure a bad WiFi driver has not been installed, then reboot your computer:
sudo apt remove backport-iwlwifi-dkmsAdvanced Troubleshooting
Section titled “Advanced Troubleshooting”If the above steps aren’t working, or you would like to fine tune and improve you connection, see the following steps.
Regulatory Domain
Section titled “Regulatory Domain”In many cases, it’s recommended to explicitly set the WiFi regulatory domain. Check yours with this command:
sudo iw reg getIf you get 00, that is a one-size-maybe-fits-all setting. Find yours here: ISO_3166.
And set it permanently with this command:
sudo gedit /etc/default/crdaChange the last line to read:
REGDOMAIN=US
Save and close the text editor.
Unless specifically required, you can set IPv6 to Ignore in Network Manager. Go to System Settings → Network and click the orange arrow next to your network, then click Settings → Network → Ethernet → Gear Icon → IPv6 Settings then change Automatic to Disable.
Antenna Aggregation
Section titled “Antenna Aggregation”If these changes do not help, you can try enabling antenna aggregation:
sudo modprobe -r iwlwifisudo modprobe iwlwifi 11n_disable=8Then, test to see if that helps. To make it permanent:
sudo gedit /etc/modprobe.d/iwlwifi.confThen, add this line to the bottom (effective upon reboot):
options iwlwifi 11n_disable=8
N Mode
Section titled “N Mode”You can try disabling N mode completely by using 11n_disable=1 in the previous settings. N mode can be more unstable than G mode, and the speed gained isn’t typically useful as total bandwidth available in/out from/to the Internet is less than N speeds.
Bluetooth Coexistence
Section titled “Bluetooth Coexistence”If you have trouble with a Bluetooth headset and keeping a steady downlink speed, try disabling Bluetooth coexistence in the configuration file above:
options iwlwifi bt_coex_active=0
Power Management
Section titled “Power Management”Another way to help with Wifi issues is to turn off power management for the hardware. To do so, edit the configuration file with this command:
sudo gedit /etc/NetworkManager/conf.d/default-wifi-powersave-on.confAnd change the file to read (effective upon reboot):
[connection]
wifi.powersave = 2
If tlp is installed, take a look at the settings file found here for additional Wifi power saving being enabled:
sudo gedit /etc/default/tlpUseful Programs
Section titled “Useful Programs”The program wavemon can be used to see info about nearby access points, such as power levels, channels, and BSSIDs. It can be installed with this command:
sudo apt install wavemonAnd run with this command:
sudo wavemonUseful Commands
Section titled “Useful Commands”iweventRun this command to watch what the Wifi hardware is doing. Pay attention to the disconnect reasons, and ignore the scans.
sudo systemctl restart NetworkManagerThis command will restart the service that manages all Internet traffic on the computer, which is usually easier than restarting the computer.
dmesg | grep iwlwifiThis will check the hardware startup and driver loading messages.
lspci | grep NetworkThis will check if the hardware is being detected by the kernel.
lsmod | grep iwlwifiThis will check to see if the device driver (module) is loaded.
sudo rm /etc/NetworkManager/system-connections/*This will erase the stored information about all wireless access points.
sudo apt install --reinstall network-managerThis will reinstall network-manager, which can fix some network issues.
NOTE: After reinstalling the above packages, fully shut down the machine and then power it back on, rather than rebooting. This ensures the hardware completely resets.
Additional Info
Section titled “Additional Info”Wifi Speeds and Frequencies:
- 54 Mb/s uses the 802.11g & 802.11b standards.
- 145 Mb/s and 300 Mb/s modes use the 802.11n standard and 20MHz or 40MHz bandwidths.
- 300Mbps / 40Mhz will provide the maximum performance in most cases.
- 145Mbps / 20MHz will work better in areas with more access points.
- 450Mbps uses a 60Mhz channel width and 600Mbps uses a 80Mhz channel width, and is typically less stable.
The name of the Linux driver for Intel Wifi cards is called iwlwifi and is included in the kernel by default. All information about the driver can be found here:
wireless.wiki.kernel.org/en/users/drivers/iwlwifi
The newest version of the linux-firmware package, which contains the iwlwifi driver, can be found here:
mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware
Sometimes the newest version of the firmware will clear up occasional bugs. Please download the newest .deb package.
Windows Dual Boot
Section titled “Windows Dual Boot”If you are dual booting Windows, you may lose access to your wifi card entirely after running driver/OS updates in Windows. You may be able to gain access to your wifi card again by disabling “Fast Startup” in the Windows power options before booting back into Pop!_OS.