The install went perfectly — and now there is no Wi-Fi. This is the most common first-day problem on Linux Lite, it is usually a five-minute driver job, and the tool to fix it is already installed. Here is the order that works.
Linux carries drivers for most Wi-Fi chips inside the system itself. The famous exceptions — many Broadcom cards and some newer Realtek chips — need a proprietary driver that Ubuntu-based systems offer separately, for legal rather than technical reasons. So the fix is rarely about skill — it is about getting online once by another route and letting the built-in driver tool do its one job.
👆 Example output for a common Broadcom chip. Your chip name and driver will differ — the method is identical.
Before installing anything, rule out the embarrassing causes. Many laptops have a physical Wi-Fi switch or an Fn key combination that kills the radio — and an OS reinstall is exactly when someone last touched it. Check the airplane-mode key, then look honestly — does the PC see no networks at all, or does it see networks but fail to connect? No networks at all points to the driver or the radio. Networks visible but connection failing points to the password, the router, or security settings — a different problem entirely, and this page is about the first one.
Driver fixes download a driver, so you need any working connection first. In order of convenience —
With any of these live, the next step usually solves the problem in one click.
Terminal equivalent — ubuntu-drivers devices shows what is offered, and sudo ubuntu-drivers autoinstall installs the recommended set. Identify your exact chip any time with lspci | grep -i net for internal cards or lsusb for USB ones — the chip name is what any forum answer will ask you for first.
A small number of very new, very old or obscure Wi-Fi chips have no proper Linux driver, and no setting will change that today. Work through the real options in order — wait and update (newer kernels add hardware support, so keep the system updated and recheck after a few weeks), use a supported USB Wi-Fi adapter (the pragmatic fix for a desktop PC — choose one advertised as Linux-compatible), or keep that machine on Windows if the adapter is internal and the machine matters. What not to do — do not install random driver files from file-sharing sites, and do not follow guides that replace your kernel with an unknown one. A working cable beats a broken system.
Watch the complete Linux Lite setup in the video — including the first-boot checks that catch this early.
▶️ Watch Full VideoThe live session and the installed system load the same drivers, so results are usually identical — but an offered proprietary driver is only added when you install it, so a chip can behave differently before and after the Install Drivers step. This is why the complete setup guide tells you to test Wi-Fi in the live session first — you learn what you are dealing with before anything is wiped.
Check Secure Boot first — it can refuse to load the new driver module. Enrol the key from the blue MOK screen shown at the next restart, or disable Secure Boot in the BIOS on your own machine. Then confirm the chip itself with the lspci command; if the driver is loaded and the hardware is seen, the problem has moved to connection settings, not the driver.
For a desktop PC with a stubborn internal card, a Linux-compatible USB adapter is a cheap, honest fix. For a laptop, try the driver route and a few weeks of kernel updates first — support for newer chips regularly arrives that way. Only buy when the machine must have Wi-Fi now.