This guide walks through the most common causes of Wi-Fi and Bluetooth failures after installing Ubuntu, from missing drivers to blocked firmware, and gives you clear steps to get both working again. You will need an internet connection for most fixes, so keep an Ethernet cable or phone tethering handy before you start.
What You’ll Need
- A working internet connection (Ethernet cable or USB tethering from a phone)
- Terminal access (Ctrl+Alt+T)
- Your Ubuntu installation media or a USB drive with Ubuntu (for offline driver installs)
- Administrative (sudo) password
Step-by-Step
- Check if the hardware is detected. Open a terminal and run
lspci -nnk | grep -iA3 netfor Wi-Fi andlsusbfor USB Bluetooth adapters. If you see your device listed but with a line like “Kernel driver in use: none”, the driver is missing. If nothing appears, the hardware may be disabled in the BIOS or physically blocked. - Verify the radio isn’t soft-blocked. Run
rfkill list. If you see “Soft blocked: yes” or “Hard blocked: yes”, runsudo rfkill unblock alland check again. A hard block means a physical switch or key combination (often F2, F12, or a dedicated key) is off — toggle that first. - Update the kernel and install standard drivers. With internet access, run
sudo apt update && sudo apt upgradeand thensudo apt install linux-firmware. Reboot and test. This resolves a large percentage of cases where the default install used a slightly older kernel missing support for newer chips. - Install proprietary drivers if available. Go to Software & Updates → Additional Drivers tab. If a proprietary driver is listed for your Wi-Fi or Bluetooth chip, select it and click Apply Changes. Reboot after it finishes.
- For Realtek chips, install the rtl8821ce or rtl88x2bu driver manually. Many Realtek Wi-Fi adapters lack in-kernel drivers. Identify your exact chip with
lspci -nn | grep -i realtek. Then, from a terminal with internet, run:sudo apt install git dkms build-essential, thengit clone https://github.com/tomaspinho/rtl8821ce.git,cd rtl8821ce,sudo ./dkms-install.sh. For rtl88x2bu, use the repositoryhttps://github.com/morrownr/8821bu-20210916.gitand follow its README. Reboot afterward. - For Intel chips, update the iwlwifi firmware. If your Wi-Fi is Intel and shows errors in
dmesg | grep iwlwifi, runsudo apt install linux-firmwareagain, then check if your kernel is older than 6.2. If so, consider installing a newer HWE kernel withsudo apt install linux-generic-hwe-22.04(on 22.04) or the equivalent for your version. Reboot. - Fix Bluetooth specifically. For Bluetooth, first ensure the service is running:
systemctl status bluetooth. If inactive, runsudo systemctl start bluetoothandsudo systemctl enable bluetooth. Then checkdmesg | grep -i bluetoothfor firmware errors. If you see “Direct firmware load failed”, the firmware file is missing — installlinux-firmwareas in step 3. For Intel Bluetooth, you may need to copy firmware files from thelinux-firmwaregit repository into/lib/firmware/intel/. - Use NetworkManager to reconnect. After any driver fix, restart networking with
sudo systemctl restart NetworkManager. Then click the network icon in the top bar and select your Wi-Fi network. For Bluetooth, use Settings → Bluetooth to pair your device again. - If nothing works, install the backported driver. Run
sudo apt install backport-iwlwifi-dkms(for Intel) or search for a DKMS package matching your chip viaapt search backport. Reboot after installation.
Common Mistakes
- Forgetting to reboot after installing firmware — many driver loads only happen at boot.
- Using the wrong driver repository for your exact Realtek chip model (e.g., rtl8821ce vs rtl8822ce).
- Disabling secure boot without also signing the DKMS module — if secure boot is on, you must enroll the key or disable it entirely.
- Assuming the problem is software when the Wi-Fi kill switch on the laptop is physically off.
- Running
rfkill unblockas a normal user (it needs sudo).
Tips
- Always check
dmesgoutput after a failed attempt — it usually names the missing firmware file or the driver that failed to load. - Keep a USB Wi-Fi adapter that uses an Atheros or Intel chip as a fallback; these have the best in-kernel support.
- If you’re on a laptop, try booting with the AC adapter plugged in — some power management profiles disable radios on battery.
- Write down your chip model (from
lspci) before searching forums; generic “Wi-Fi not working” queries rarely help. - Consider using the HWE kernel if you’re on an LTS release — it adds support for newer hardware.
Troubleshooting
If the steps above don’t resolve the issue, try these in order:
- Check kernel logs for the exact error: Run
dmesg | grep -i firmwareanddmesg | grep -i error. The missing file name will often appear. Search for that filename online to find the correct package. - Test with a live USB of a newer Ubuntu version. If the live session has working Wi-Fi, the problem is your installed kernel, not the hardware. Install the newer version or its HWE kernel.
- Try a different network manager. If NetworkManager is crashing, install and use
network-manager-gnomeorwpa_supplicantmanually viasudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf. - Check for conflicting drivers. Run
lsmod | grep -E 'rtl|iwl|ath'and look for two drivers claiming the same device. Blacklist one with a file in/etc/modprobe.d/. - Reset the BIOS. Some laptops ship with Wi-Fi disabled in BIOS. Reboot, enter BIOS (usually F2 or Del), and look for “Wireless” or “WLAN” options — ensure they’re enabled.
Frequently Asked Questions
Why did Wi-Fi work on the live USB but not after installation?
The live USB often uses a newer kernel or includes extra firmware packages that the installed system lacks. Installing linux-firmware and updating the kernel usually fixes this.
My Bluetooth pairs but disconnects after a few seconds — what now?
This is typically a power management issue. Run sudo sed -i 's/^#*AutoEnable=false/AutoEnable=true/' /etc/bluetooth/main.conf and restart Bluetooth. Also disable Bluetooth power saving with sudo systemctl mask bluetooth only if you’re sure — otherwise try echo 'options btusb enable_autosuspend=n' | sudo tee /etc/modprobe.d/btusb.conf and reboot.
Do I need to disable Secure Boot?
Only if you’re installing third-party DKMS drivers (like Realtek). With Secure Boot on, Ubuntu will prompt you to enroll a key during installation — you can do that instead of disabling it. Intel and Atheros drivers work fine with Secure Boot.
Can I use a Windows driver for my Wi-Fi card?
Yes, via ndiswrapper, but it’s a last resort. It’s unstable and breaks on kernel updates. Prefer a native Linux driver or a cheap USB adapter.
How do I find my exact Wi-Fi chip model?
Run lspci -nn | grep -i network or lsusb for USB adapters. The output will show a vendor and device ID, like 10ec:c821 — that’s Realtek rtl8821ce. Search that ID online for the correct driver.
Will a kernel update fix my Bluetooth?
Often yes. Newer kernels include better Bluetooth firmware loading and power management. Run sudo apt upgrade and reboot — if your Ubuntu version is older, consider upgrading to the latest LTS.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Show User Library in macOS High Sierra & Sierra
- Device Manager Shortcut: Windows 10 Desktop
- How to Remove Forgotten Passcode from iPhone
- Fix Slow Wi-Fi Problem iPhone X: 9 Steps
- How to Check if a Candidate Accepts Crypto Donations
- How to Listen to Deleted Voicemails on iPhone