Few hardware hurdles in Linux are as immediately frustrating as launching Ubuntu after a clean installation or routine kernel update only to find that your wireless networking has vanished. Opening the GNOME network menu displays the disheartening message: No Wi-Fi Adapter Found, accompanied by an empty wireless settings pane and no available access points.
This issue rarely indicates a dead physical network card. On modern laptops and desktop motherboards, Wi-Fi hardware—especially chipsets manufactured by Realtek, Broadcom, or MediaTek—frequently requires proprietary firmware blobs or Dynamic Kernel Module Support (DKMS) drivers that are not bundled with standard open-source Linux kernels. Additionally, UEFI Secure Boot enforcement can block unsigned third-party drivers from loading. Following these structured troubleshooting steps will help you detect your adapter and restore your wireless connection.
Identify Your Wireless Network Hardware
Before installing drivers blindly, you must determine the exact manufacturer and chipset model of your Wi-Fi interface. Open your terminal (press Ctrl + Alt + T) and run the following command to inspect PCI-connected wireless cards:
lspci -nnk | grep -iA3 net
If you are using a USB Wi-Fi dongle, query your connected USB bus instead:
lsusb
In the terminal output, examine the entries for your Network Controller. Look specifically for the Subsystem name and the four-digit hexadecimal vendor and product IDs (for instance, [10ec:c821] for a Realtek RTL8821CE card, or [14e4:43a0] for a Broadcom BCM4360 card). Take note of whether the line Kernel driver in use: appears; if this line is missing, the Linux kernel has recognised the hardware but lacks an active driver to operate it.
Step 1: Check for Software and Hardware Radio Blocks
Before attempting driver compilation, verify that your wireless radio has not been disabled by a hardware switch, an accidental hotkey combination, or an operating system software block.
Run the rfkill query tool:
rfkill list all
Examine the output under Wireless LAN:
- Soft blocked: yes: The wireless radio was turned off by software. Run
sudo rfkill unblock wifito restore it. - Hard blocked: yes: A physical toggle switch on your laptop chassis or an Fn-key combination (such as Fn + F2 or Fn + F12) has cut power to the adapter. Toggle the physical switch or key combination to unblock the card.
Step 2: Enable Proprietary Drivers via Additional Drivers
Ubuntu includes an automated utility that searches canonical and restricted repositories for proprietary drivers matching your detected hardware. To use this feature, connect your computer temporarily to the internet using an Ethernet cable or smartphone USB tethering.
- Open the Ubuntu application launcher and launch Software & Updates.
- Navigate to the Additional Drivers tab.
- Allow Ubuntu several seconds to query your connected hardware.
- If an available proprietary driver is detected (such as the Broadcom 802.11 Linux STA wireless driver source), select the radio button: Using [Driver Name] (proprietary).
- Click Apply Changes. If prompted, authenticate with your administrator password and wait for the package manager to download and compile the module.
- Restart your computer once installation finishes.
Step 3: Resolve UEFI Secure Boot and MOK Verification Issues
If you installed a proprietary driver but the wireless adapter still fails to initialise, UEFI Secure Boot is the most probable cause. Secure Boot strictly forbids the Linux kernel from loading third-party kernel modules (such as DKMS drivers) unless they are signed with an authenticated Machine Owner Key (MOK).
To verify if Secure Boot is actively blocking your driver, run:
sudo dmesg | grep -iE 'secureboot|lockdown|signature'
If the kernel reports module verification failures, you have two reliable options:
- Enrol the MOK Key: During driver installation, Ubuntu will often prompt you to create a temporary Secure Boot password. When you restart your computer, a blue Perform MOK management screen appears. Select Enroll MOK, choose Continue, select Yes, enter the password you chose, and select Reboot.
- Temporarily Disable Secure Boot: If you are comfortable managing your firmware, reboot into your computer’s UEFI/BIOS settings (typically by pressing F2 or Del during boot), locate the Security or Boot tab, and set Secure Boot to Disabled. Save and reboot.
Step 4: Install Common Realtek and Broadcom Drivers via Terminal
If the graphical Additional Drivers tool did not populate compatible packages, you can install the official DKMS drivers directly through the terminal while connected via Ethernet or tethered mobile data.
For Broadcom wireless cards (BCM43xx series):
sudo apt update
sudo apt install --reinstall bcmwl-kernel-source
sudo modprobe wl
For Realtek wireless cards (such as RTL8821CE or RTL8812AU):
sudo apt update
sudo apt install rtl8821ce-dkms
For newer Realtek chipsets (such as RTL8852AE or RTL8852BE often found in Wi-Fi 6 laptops), ensure you are running the latest Ubuntu HWE (Hardware Enablement) kernel, which incorporates modern vendor drivers upstream:
sudo apt install --install-recommends linux-generic-hwe-24.04
Diagnostic Reference for Common Ubuntu Wi-Fi Chipsets
The table below provides a quick reference for the most common wireless chipsets and their corresponding driver packages:
| Manufacturer & Model | Identification String | Required Ubuntu Package |
|---|---|---|
| Broadcom BCM43142 / BCM4360 | 14e4:4365 / 14e4:43a0 |
bcmwl-kernel-source |
| Realtek RTL8821CE | 10ec:c821 |
rtl8821ce-dkms |
| Realtek RTL8812AU (USB) | 0bda:8812 |
rtl8812au-dkms |
| Intel Wireless (AX200 / AX210) | 8086:2723 / 8086:7af0 |
linux-firmware (Kernel Built-in) |
Verifying Network Manager Service Health
Once your drivers are compiled and loaded, confirm that Ubuntu’s networking daemon is running smoothly:
sudo systemctl restart NetworkManager
Open your GNOME Settings, navigate to Wi-Fi, and your wireless card should now scan and display local Wi-Fi networks normally. By properly identifying your hardware, unblocking radios, and handling Secure Boot signatures, you can reliably overcome wireless adapter detection failures in Ubuntu.