Linux-based operating systems often face the problem of a lack of pre-installed proprietary drivers for wireless network cards. Unlike commercial operating systems, where vendors often provide ready-made solutions, in the open source world, hardware support depends on enthusiasts and the community. Wireless connection is a critical component for most users, and its absence turns a powerful computer into a useless piece of hardware without access to repositories.
The installation process can vary from simply activating the package in the manager to manually compiling kernel modules from source code. It all depends on your adapter's chipset manufacturer and driver support policy. Realtek, Broadcom And MediaTek have varying degrees of support in the main kernel development branches. Understanding the driver architecture will help you avoid mistakes and successfully configure your network.
In this guide, we'll cover every step: from device identification to resolving version conflicts. You'll learn how to use diagnostic tools and understand how the module loading mechanism works. This knowledge is essential for anyone who wants to fully utilize the capabilities of Linux on modern hardware.
Identifying your network adapter and finding information
The first and most important step is to accurately determine the model of your network controller. Often, users only know the name of the USB dongle or laptop, but the driver is selected specifically for the chipset. To obtain this information, use the following utility in the terminal: lspci for internal cards or lsusb For external USB adapters, these commands list all connected devices with their IDs.
You need to find a line containing the words "Wireless," "Network," or "Wi-Fi." Pay special attention to the numeric code, which usually looks like this: VendorID:DeviceID (For example, 10ec:8179). This is exactly it. unique identifier This will allow you to find the required driver online, even if you don't know the model name. Write down these numbers, as you'll need them to find the source code.
If standard utilities don't display the device, the adapter may be in power-saving mode or disabled at the BIOS level. Check your system settings and ensure the device is physically functional. Sometimes a reboot with the adapter connected is required for the system to correctly scan the data bus.
⚠️ Attention: If the teamlspciorlsusbIf the adapter doesn't return any results, check if it's blocked by a hardware switch on the laptop case or a key combination.F1-F12.
Checking if the driver is available in the distribution repositories
Many modern distributions, such as Ubuntu, Linux Mint, or Fedora, have mechanisms for automatically installing proprietary drivers. Before resorting to manual compilation, it's worth checking whether the system offers a ready-made solution. Debian-based systems have a utility for this purpose. ubuntu-drivers or the "Additional Drivers" graphical interface.
Run a check for available packages via the terminal. The system will analyze your hardware and offer to install any missing components. This is the safest option, as packages in the repositories are tested for compatibility with your kernel version. Automatic installation minimizes the risk of configuration errors and library conflicts.
If the system reports that no drivers were found, or the suggested solution doesn't work, you'll have to use the manual method. This often happens with new adapter models, support for which isn't yet included in the stable distribution branches. In this case, we'll need build tools.
To work with source code, you will need to install a basic set of compilation tools. On Ubuntu, this is the package build-essential, and in Fedora - a group Development Tools. Also, the kernel header files must be installed (linux-headers), corresponding to your current version.
Preparing the environment for compiling modules
Installing the driver from source code requires a compiler. gcc and utilities makeWithout them, it is impossible to convert the program text into an executable kernel module. The installation command depends on your distribution: for Debian/Ubuntu, use apt install build-essential linux-headers-$(uname -r), for Arch Linux - pacman -S base-devel linux-headers.
It's critical that the header file version exactly matches the running kernel version. You can check the current version with the command uname -rIf the versions do not match, compilation will fail because the kernel data structures may differ. Version discrepancy — the most common reason for failure during manual installation.
☑️ Preparing for compilation
After installing the tools, it's recommended to reboot the system to ensure the new set of headers is working correctly. Only then can you begin downloading the driver source code. Make sure you have access to a wired network or the ability to transfer files via USB, as Wi-Fi is not yet working.
⚠️ Warning: When updating the system kernel (kernel upgrade), you will have to recompile and install the driver, since binary modules are incompatible between different kernel versions.
Downloading and installing the driver from source code
Driver source code is most often hosted on GitHub or the manufacturer's official website. Find the repository that matches your chipset (e.g., rtl8812au (for Realtek). Download the archive with the code or clone the repository using the utility gitThis will allow you to easily update the driver in the future.
Unzip the archive and navigate to the created directory. It usually contains a file README or INSTALL, containing specific instructions from the author. The standard installation process often boils down to three commands: clearing previous builds, compiling, and installing the module. Run these commands as root.
make cleanmake
sudo make install
After the command has completed successfully make install the module is copied to the system directory /lib/modules/However, it has not yet been loaded. You must manually launch the module with the command modprobe or restart your computer. If no errors occur, a new adapter should appear in the list of network interfaces.
What to do if make gives an error?
Often, this error occurs due to missing dependencies or incompatible compiler versions. Check the make command output carefully—the last lines usually indicate missing header files or undefined symbols.
Comparison of driver installation methods
There are several approaches to resolving the Wi-Fi outage, each with its own advantages. The method you choose depends on your experience and system stability requirements. Below is a table to help you choose the best approach.
| Method | Complexity | Stability | Updatable |
|---|---|---|---|
| Driver Manager | Low | High | Automatic |
| DKMS package | Average | High | Automatic |
| Manual compilation | High | Average | Manually |
| Ready-to-use binaries (.deb/.rpm) | Low | Average | Manually |
The most preferred method for advanced users is to use technology DKMS (Dynamic Kernel Module Support). It automatically recompiles the driver module with each kernel update. This eliminates the need to manually repeat the installation procedure after each system update.
Manual compilation without DKMS is suitable for one-off situations or for testing new driver versions. However, keep in mind that after updating the kernel, Wi-Fi will stop working until you repeat the process. Pre-built binary packages are convenient, but they may contain vulnerabilities or not work on newer versions of the distribution.
Diagnosing and troubleshooting common problems
Even after successful installation, connection issues may still occur. The adapter may see networks but not connect, or the connection may constantly drop. First, check the interface status with the command ip link. Make sure the interface is in the up state. UP and is not blocked by software.
A common problem is driver conflict. An old module may remain in the system, interfering with the new one. Use the command lsmod | grep wifi (replacing wifi with part of your driver name) to see loaded modules. You can unload unnecessary modules with the command rmmod and add to download blacklist.
- 📶 Check your power saving settings: Sometimes the adapter turns off to save power. Disable this setting.
power_savein the NetworkManager configuration. - 🔒 Make sure the problem isn't with your router settings: try connecting to an open network or a network with a different encryption type.
- 🛡️ Check the system logs: commands
dmesg | grep firmwareorjournalctlwill help you find firmware loading errors.
If your adapter is unstable, try changing your wireless region. Some drivers use a limited set of channels by default. iw reg set Allows you to set the correct country code, which can expand the available frequency range and increase signal strength.
⚠️ Note: Interfaces and package names may differ across distributions. Always consult your distribution's official documentation if the standard commands don't work.
Frequently Asked Questions (FAQ)
Do I need to reinstall the driver after every Linux update?
If you used the DKMS method, the driver will be recompiled automatically. If you install manually without DKMS, you'll have to repeat the process after each kernel update.
Where can I get a driver if I don't have internet access on this computer?
Download the driver archive and required dependencies on another device with internet access, save it to a USB drive, and transfer it to the target computer. You can also use your smartphone as a USB modem.
Why does the driver compile, but the module does not load?
This could be due to a missing module signature (Secure Boot), a kernel version conflict, or errors in the driver code itself. Check the system logs. dmesg to get the error code.
Is it safe to use drivers from GitHub?
Drivers from popular repositories with a high star rating and active development are generally safe. However, there is always a risk, so it's recommended to review the code or use trusted sources.