Wi‑Fi dropping or refusing to connect on Ubuntu can interrupt work, entertainment, and communication in an instant. While the issue often looks intimidating, most causes are straightforward to diagnose and fix on desktop and server installations alike.
Quick checks before deep troubleshooting
Before opening a terminal, rule out simple environmental factors. Ensure the router is powered on, other devices can reach the internet, and the Ubuntu machine is within reasonable range. Toggle Airplane Mode off from the top panel, and verify that Wi‑Fi is enabled in Settings > Wi‑Fi. These steps eliminate the easiest fixes first.
Confirm your hardware and driver status
Ubuntu relies on correct firmware and drivers for wireless adapters. Many desktop and notebook Wi‑Fi cards require non‑free firmware packages that are not installed by default. Use the following commands to inspect the interface and driver details.
ip link to list network interfaces and confirm your Wi‑Fi device appears (often named wlan0 or similar).
rfkill list to check if the wireless radio is soft‑blocked.
If firmware is missing, you will typically see “firmware loading failed” in dmesg output. Installing the appropriate package, such as linux-firmware or vendor‑specific firmware, often resolves immediate detection problems.
Managing rfkill and radio blocks
A soft or hard block can silently disable Wi‑Fi. Soft blocks are software toggles, often tied to a physical switch or keyboard key. Hard blocks are usually a hardware switch or firmware level disable. Run rfkill list and look for lines marked SOFT or HARD . If you see a soft block, unblock it with sudo rfkill unblock wifi . For persistent issues, check BIOS/UEFI settings to ensure wireless is not disabled at the hardware level.
NetworkManager versus standalone configurations
Ubuntu typically uses NetworkManager for desktop flavors, which provides a user‑friendly GUI but can conflict with manual setups in /etc/network/interfaces or netplan when multiple tools manage the same interface. For desktop users, prefer NetworkManager applets for connecting, editing, and managing Wi‑Fi profiles. On servers or custom configurations, verify netplan files for correct SSID, WPA key, and interface names, then apply with sudo netplan apply . Mismatched configurations often explain why Wi‑Fi shows as connected yet offers no internet.
Driver issues and alternative firmware Some adapters, especially recent chips from vendors like MediaTek, Realtek, or certain Intel variants, need additional firmware not included in the main distribution. On Ubuntu, the ubuntu-drivers tool can suggest proprietary or missing packages. You can also install linux-firmware-nonfree or download vendor firmware manually into /lib/firmware . After adding firmware, reload the driver module with sudo modprobe -r && sudo modprobe and confirm the link quality via iwconfig or GNOME’s network panel. Security protocols and hidden network quirks
Some adapters, especially recent chips from vendors like MediaTek, Realtek, or certain Intel variants, need additional firmware not included in the main distribution. On Ubuntu, the ubuntu-drivers tool can suggest proprietary or missing packages. You can also install linux-firmware-nonfree or download vendor firmware manually into /lib/firmware . After adding firmware, reload the driver module with sudo modprobe -r && sudo modprobe and confirm the link quality via iwconfig or GNOME’s network panel.
