Transition to an operating system Linux Installing a network manager is often accompanied by a desire to optimize computer performance, but the first obstacle for many users is the lack of internet access immediately after installation. Unlike Windows, where drivers are often built-in or installed automatically, in the open source world, manual activation of network interfaces is sometimes required. This is especially true for owners of laptops with specialized network adapters or those using minimalist distributions without a graphical interface. Understanding how network managers work will allow you not only to quickly connect to your router but also to effectively manage your connections in the future.
There are several ways to activate the wireless module, depending on the installed desktop environment and distribution. Graphical interfaces in GNOME or KDE Plasma offer intuitive switches, but they don't always work correctly without proprietary drivers. In such cases, powerful command-line tools like nmcli or iw, which provide complete control over network equipment. Even if you're a beginner, mastering basic commands will be the key to solving 90% of connection problems.
In this article, we'll cover all Wi-Fi activation methods in detail, from simple mouse clicks to in-depth configuration file customization. We'll cover diagnostics when the interface isn't physically visible to the system, and how to install the necessary firmware. It is critical to determine the model of your network adapter before you begin any manipulations., as driver selection depends on this. Follow the instructions carefully, and you're guaranteed a stable connection.
Hardware diagnostics and driver testing
Before attempting to enable data transfer, you need to ensure that the operating system actually "sees" your wireless device. Often, the problem lies not in the settings, but in the lack of the necessary firmware for a specific chipset model. First, it's worth performing a basic hardware check using standard system utilities included with any distribution. This will help determine whether the device is recognized at the kernel level.
Use the command lspci for internal cards or lsusb For external USB adapters, to get a list of connected devices. In the command output, look for lines containing the words Wireless, Network or names of manufacturers like Intel, Realtek, Broadcom, AtherosIf the device is displayed but marked as "Unclaimed" or is simply missing from the list of network interfaces when running ip link, which means the driver is not loaded.
What to do if the adapter is not visible in lspci?
If even the lspci command doesn't show the wireless card, try checking the BIOS/UEFI. The wireless module can often be disabled at the motherboard level. It's also worth checking whether it's blocked by a hardware switch on the laptop case (if present).
For more detailed information about the status of drivers and required firmware, use the utility lshw. It will show which driver exactly (driver) is it used and loaded (configuration). If the driver field is empty, you will need to find and install the firmware package corresponding to your model. On Debian-based systems, these are often packages named firmware-iwlwifi or firmware-realtek.
Using the NetworkManager GUI
In most modern distributions, such as Ubuntu, Linux Mint or Fedora, by default the network manager is used NetworkManagerIt provides a user-friendly graphical interface that hides complex settings from the user. The network icon is typically located in the system tray (upper or lower right corner of the screen). If the icon displays a crossed-out globe or arrows, it means there is no connection, but the interface may still be active.
To turn on Wi-Fi, tap the network icon and find the "Wi-Fi" switch. If it's off, simply toggle it on. The system will begin scanning for available access points. If the list of networks is empty but the switch is enabled, the wireless module may be blocked by software. Network settings often have an "Options" or "Settings" section where you can check if "Turn on Wi-Fi only when a network is available" or a similar restriction is checked.
Sometimes the graphical interface may freeze and not display available networks even with functioning hardware. In this case, restarting the NetworkManager service without rebooting the entire system helps. Open a terminal and enter the command to restart the service. This is a safe operation that often resolves frozen scans.
sudo systemctl restart NetworkManagerAfter restarting the service, check the tray icon again. If networks appear, select yours, enter the password, and test the connection. If the graphical interface is completely absent (which often happens in server builds or lightweight window managers like i3 or Openbox), proceed to using the command line.
Activating Wi-Fi via the terminal (nmcli and nmtui)
The Linux command line is a powerful system management tool, and networking is no exception. The utility nmcli (Network Manager Command Line Interface) allows you to manage all aspects of NetworkManager. To start, check the overall network status with the command nmcli general statusIf the equipment status (DEVICE) shows disconnected or unavailable, you need to enable the wireless radio interface.
To enable the Wi-Fi adapter, use the command to activate the radio module. This is equivalent to pressing the power button in the graphical interface. After this, the device should enter the "On" state. connected or start scanning.
nmcli radio wifi onIf after turning on the radio networks do not appear, it is possible that the interface itself (for example, wlo1 or wlan0) is in the "down" state. Raise it manually using the command ip link set dev <interface_name> upThe interface name can be found through ip linkTo connect to a specific network, use the following structure, where you need to replace the network name and password with your own:
nmcli device wifi connect "Network_Name" password "Your_Password"For those who prefer a pseudo-graphical interface similar to BIOS, there is a utility nmtui. Run it as superuser (sudo nmtui), select "Activate a connection" and follow the on-screen instructions. This is ideal for servers without a graphical shell.
☑️ Checking the connection via nmcli
Control via iw and ip utilities
Unlike nmcli, which works through the NetworkManager daemon, utilities iw And ip interact directly with the Linux kernel. They are useful when NetworkManager is not installed or is not working correctly. First, find out the name of your wireless interface with the command ip link. It is usually called wlan0, wlp2s0 or something similar. Make sure the interface isn't blocked programmatically.
Check the lock status using the utility rfkillIf you see the status blocked: yes For Wi-Fi, unlock it with the command sudo rfkill unblock wifiThis removes any software locks that may have been previously set by the power saving system or the user. Once unlocked, the interface should be accessible for scanning.
To scan available networks, use the command iw dev <interface_name> scan. Please note that the interface must be raised before scanning (ip link set <name> up). The command output will show a list of available SSIDs, channel frequency, and signal strength. Manual connection usually also requires configuration. wpa_supplicant, which makes this method more complex, but also more flexible for non-standard configurations.
Troubleshooting driver and firmware issues
The most common reason Wi-Fi can't be enabled on Linux is the lack of proprietary drivers. This is especially true for adapters. Broadcom and some models RealtekDebian/Ubuntu-based distributions have an "Additional Drivers" mechanism that automatically finds and offers to install the necessary packages. Run software-properties-gtk or find "Device Drivers" in the menu.
If the automatic search doesn't help, you'll have to search for the driver manually. This will require a temporary internet connection via a USB modem (an Android phone in USB tethering mode) or an Ethernet cable. Find the chipset model (via lspci -nn) and look for the driver in the repositories. Installing packages often helps. linux-firmware And dkms, which contain microcodes for a wide range of devices.
>90% work out of the box
Requires DKMS and kernel headers
Drivers from GitHub are often needed.
Excellent support in the kernel
| Manufacturer | Typical driver package | Comment |
|---|---|---|
| Intel | firmware-iwlwifi | |
| Broadcom | bcmwl-kernel-source | |
| Realtek | firmware-realtek | |
| Atheros | firmware-atheros |
When installing drivers from third-party sources (such as GitHub), carefully monitor the kernel versions. A driver compiled for kernel 5.15 may not work on 6.5 without recompiling the module. Use the command uname -r to check the current kernel version before installing any DKMS modules.
Setting up static IP and DNS (optional)
Most home networks use automatic settings acquisition via DHCP, and manual configuration is not required. However, in corporate networks or with specific provider requirements, it may be necessary to specify a static IP address and DNS servers. In the graphical interface, this is done in the connection properties, and in the terminal, by editing the NetworkManager configuration files.
Connection configuration files are stored in the directory /etc/NetworkManager/system-connections/. You can edit the corresponding file (for example, MyWifi.nmconnection) and in the section [ipv4] change method with auto on manual, adding the necessary addresses. Don't forget to restart the NetworkManager service after making changes.
⚠️ Attention: Incorrectly setting up a static IP may result in loss of access to the local network and the Internet. Before changing the settings, write down the current parameters (obtained via
ip addrAndcat /etc/resolv.conf), to be able to roll back.
Common mistakes and how to fix them
Even with proper configuration, specific errors may occur. For example, the system may indicate that Wi-Fi is enabled but not find any networks. This often happens if the region (Country Code) is set incorrectly. Some Wi-Fi channels are restricted in some countries, and if the driver thinks they're in the US and you're in Europe, it may not scan for certain frequencies.
Use the command sudo iw reg set RU (or your country code) to set the correct region. Also, check that Airplane mode isn't enabled at the system level. On some laptops, the Fn+F2 key combination can disable the mode hardware-wide, making it unavailable for software activation until you press it again.
- 🔍 "Secrets were required" error: Incorrect password or encryption type. Try forgetting the network and connecting again.
- 📡 Weak signal: Check if the antenna is shielded by a metal case or other devices.
- 💤 Shutdown after sleep: The laptop may not wake up the Wi-Fi module. Disabling power saving in the TLP or Powertop settings may help.
What should I do if Wi-Fi is slow after turning it on?
Check to see if the adapter has switched to 802.11b/g instead of n/ac/ax. This could be due to interference or router settings. Also, try changing the Wi-Fi channel on your router to a less crowded one (1, 6, or 11 for 2.4 GHz).
Can I use an external USB Wi-Fi adapter?
Yes, Linux works well with most USB adapters. It's recommended to choose devices with Atheros or MediaTek chips, as they have better driver support in the main kernel.
How to save a Wi-Fi password for automatic connection?
When connecting via nmcli add a flag password-flags 0To save your password in the system, simply check "Available to all users" or "Save password" in the graphical interface.
⚠️ Attention: Interfaces and command names may differ slightly depending on the distribution version (for example, the transition from ifconfig to ip, or changes to nmcli in version 1.0+). Always consult the manuals (
man nmcli) for your specific software version.