Ubuntu users sometimes notice that their Wi‑Fi connection disappears from the network list, leaving devices isolated even when other connections work nearby. This behavior can stem from driver conflicts, power management settings, or interface glitches rather than faulty hardware.
Below is a quick reference that maps likely causes to targeted fixes, helping you identify why Ubuntu Wi‑Fi not showing and what to adjust next.
| Symptom | Possible Cause | Quick Check | Immediate Action |
|---|---|---|---|
| Wi‑Fi adapter missing in Settings | Driver not loaded or blocked | lsusb, lspci, rfkill list | sudo modprobe |
| Wi‑Fi listed but does not connect | Wrong key, 802.1X config, or security mismatch | Check router SSID and password | Re-enter credentials, try hidden SSID toggle |
| Intermittent drops after suspend | Power saving aggressive | iwconfig, dmesg | grep power | Disable power_save for the interface |
| Wi‑Fi shows connected but no internet | Router DHCP or gateway issue | ping 8.8.8.8, ping google.com | Renew DHCP or set public DNS manually |
Diagnosing Ubuntu Wi‑Fi Not Showing
When your Wi‑Fi adapter seems invisible, start with hardware-level checks before diving into configuration. A quick physical verification and command-line status check will reveal whether the issue is blocked, missing drivers, or a service failure.
First, confirm the device is present to the system. Open a terminal and run sudo lshw -C network or simply lsusb to list USB devices. For PCI devices, use lspci. If the adapter appears but is marked UNCLAIMED or DISABLED, you are likely facing a driver or firmware problem.
Next, check rfkill list to rule out a software block. Soft blocks can be toggled with rfkill unblock wifi, while hard blocks often require a physical switch or function key combination. Ensure airplane mode is off in your desktop environment and that no custom scripts are forcing the interface down.
Driver And Firmware Issues
Many Wi‑Fi chips, especially certain Realtek, MediaTek, and some Intel variants, require specific firmware packages that are not included in the base Ubuntu image. Without the correct firmware, the driver fails to initialize, and the adapter never appears in your Wi‑Fi list.
For Debian-based installs, install firmware packages such as linux-firmware, firmware-iwlwifi for Intel devices, and firmware-realtek or linux-firmware-amd for other chipsets. After installing or updating these packages, reload the driver module with sudo modprobe -r
If the adapter still does not show, verify that no unofficial third-party drivers are conflicting. Proprietary drivers, particularly for Broadcom devices, can clash with the open-source stacks. Use Additional Drivers or ubuntu-drivers devices to review what is in use and consider switching to a tested open-source alternative if instability persists.
Interface And Service Management
NetworkManager manages most desktop Wi‑Fi connections, but a stale state or restart can leave the interface in a limbo where it exists but does not show available networks. Restarting the service often refreshes the scan logic and clears corrupted in-memory config.
Use systemctl status NetworkManager to confirm the daemon is active. If needed, restart it with sudo systemctl restart NetworkManager and then force a rescan using nmcli radio wifi on followed by nmcli device wifi list. For systems using netplan, ensure your YAML files do not contain invalid keys that prevent interface activation. Apply changes with sudo netplan apply and verify ip link and ip addr for expected state.
Sometimes the Wi‑Fi interface is simply down at the link level. Bring it up with sudo ip link set
Advanced Configuration And Secure Settings
Advanced settings like hidden SSID, custom channel widths, or specific 5 GHz preferences can cause Ubuntu Wi‑Fi not showing in expected ways. Hidden networks may fail to appear during passive scans, and aggressive power-saving profiles can prevent reliable discovery, especially on laptops.
Configure connections through the GUI editor or nmcli to verify hidden SSID is enabled when required. For power management, check iwconfig or cat /sys/class/net/
Security mismatches, such as WPA3-only routers with older supplicants, can also prevent connection attempts from surfacing properly. Ensure your NetworkManager version supports the selected security protocol, or temporarily switch to WPA2-PSK for testing. If MAC filtering is enabled on the router, whitelist your device’s MAC address to allow association and reassociate after any changes.
Stable Wi‑Fi Setup On Ubuntu
By methodically addressing driver, service, and configuration factors, you can resolve most cases where Ubuntu Wi‑Fi not showing and maintain a predictable, secure connection.
- Verify adapter presence with lspci, lsusb, and rfkill list
- Install the correct firmware package for your Wi‑Fi chip
- Restart NetworkManager and rescan with nmcli device wifi list
- Disable aggressive power saving for reliable scan results
- Check router security and channel settings for compatibility
- Keep NetworkManager and linux-firmware updated regularly
- Use wired fallback during troubleshooting for stable debugging
FAQ
Reader questions
Why does my Wi‑Fi adapter appear in lspci but not in Ubuntu network settings?
The hardware is detected, but the required firmware or driver is missing or blocked. Install the corresponding firmware package (e.g., firmware-iwlwifi, firmware-realtek), reload the kernel module, and unblock with rfkill unblock wifi to make the interface visible.
Ubuntu shows Wi‑Fi as connected but there is no internet; what should I check first?
Verify that the router has connectivity by pinging 8.8.8.8 from a wired client or another device. On Ubuntu, test with ping 8.8.8.8 and ping google.com; if IP-level pings work but DNS fails, update your DNS servers in NetworkManager or check DHCP lease issues on the router.
Why does Wi‑Fi disappear after resume from suspend on Ubuntu?
Aggressive power saving or a driver state mismatch can bring the interface down. Disable power_save for your Wi‑Fi card via NetworkManager settings or by writing on to /sys/class/net/ /power/control, and create a systemd resume target to restart NetworkManager if needed.
The Wi‑Fi list is empty on a dual‑band router; could channel width be the cause?
Yes, unusual channel widths or DFS‑only 5 GHz channels can prevent scan results from appearing. Check regulatory domain with sudo iw reg get, set it to your region if needed, and try forcing a specific band in NetworkManager. If DFS channels are in use, some clients may skip them, so temporarily using a non‑DFS channel can help discover the SSID.