Working in a Linux operating system often requires a deeper understanding of the hardware than users familiar with Windows or macOS. One of the first and most critical issues when installing the system or troubleshooting network problems is identifying the wireless module. Standard graphical interfaces often hide the exact chipset model, displaying only the general device name or connection status, making it difficult to find the right drivers.
Understanding that, which chipset exactly The specifications installed in your laptop are key to a stable internet connection. Many laptop manufacturers use different components within the same model, switching suppliers depending on factory availability. Therefore, knowing the exact specifications is essential for selecting proprietary drivers or configuring operating modes.
In this article, we'll cover all available wireless diagnostic methods in detail. You'll learn how to use the terminal to obtain comprehensive information about the Vendor ID and Device ID, allowing you to accurately identify the manufacturer and model of your adapter even without a network connection.
Using the lspci utility for internal modules
The most common and reliable way to obtain information about devices connected to the PCI bus is the command lspciMost internal Wi-Fi adapters in laptops connect via the PCIe interface, even though they physically look like small Mini-PCIe or M.2 cards. To list all devices, open a terminal and enter a basic command that will display a long list of devices.
To avoid searching for a needle in a haystack, filter the utility's output. The keywords "Network" or "Wireless" will help you immediately identify the desired block of information. It's important to pay attention not only to the name but also to the numerical identifiers at the beginning of the line, as they are the device's unique identifier in the system.
If the standard output contains too little information, such as just "Network controller", the switch should be used. -v (verbose) or -nn to display vendor and device numeric identifiers. This is especially relevant for adapters. Realtek or Broadcom, which are often defined by the system's Generic names without model detail.
lspci -nn | grep -i networkThe data obtained such as [14e4:4365], allow you to accurately identify the chipset in the PCI ID database, even if the driver has not yet been installed. This is a critical step before attempting to install proprietary software, as installing the wrong driver can lead to kernel conflicts.
⚠️ Attention: If the team
lspciIf your Wi-Fi adapter isn't showing up in the list, this could mean the device is disabled at the BIOS/UEFI level or blocked by a physical switch on the laptop case. In rare cases, the module could be faulty.
For a more detailed study of a specific device, you can use the flag -s, specifying the device address obtained from the previous output. This will provide comprehensive technical information directly from the system kernel, including the IRQs and memory areas used.
Diagnosing USB Wi-Fi adapters with lsusb
The situation with external wireless modules connected via a USB port is radically different from internal cards. Such devices do not appear in the output. lspci, as they use the Universal Serial Bus. A utility is used to detect them. lsusb, which queries the USB controller and returns a list of all connected peripheral devices.
Running the command without arguments will return a short list, where each line corresponds to a single USB device. It's important to look for lines containing the words "Wireless," "Wi-Fi," "802.11," or the names of well-known network interface manufacturers, such as MediaTek, Ralink or TP-LinkOften the adapter may be identified simply as "802.11 n WLAN", which requires further analysis.
- 📡 Vendor ID: The first 4 characters after the ID (e.g. 0bda) indicate the chipset manufacturer, in this case Realtek.
- 🔌 Product ID: The next 4 characters identify a specific device model within the manufacturer's line.
- 💻 Device version: The "bcdDevice" field may indicate the chip revision, which is important when searching for drivers for older models.
- 🏷️ Description: The text string at the end often contains a marketing name, but not always the exact chip model.
As with PCI, the Vendor and Product ID numbers are critical for USB devices. These are used to search for drivers online, especially for chip-based adapters. Realtek, which often require manual compilation of kernel modules in Linux distributions.
lsusb -v | grep -A 5 -i wirelessUsing the flag -v (verbose) will provide more detailed information, including maximum bus speed, current consumption, and interface configuration. However, for quick model identification, the standard output, filtered by keywords, is usually sufficient.
Analyzing network interfaces with the ip and ifconfig commands
When the driver is already installed and the device is recognized by the system at the software level, but you don't know its exact name or characteristics, network interface management utilities come to the rescue. The traditional command ifconfig is gradually becoming a thing of the past, giving way to more powerful tools from the package iproute2, however, both are useful for initial diagnosis.
Team ip link will show all network interfaces, including physical and virtual ones. Wireless adapters usually have names starting with "wl" (e.g. wlp2s0 or wlan0), as opposed to wired "en" or "eth". The presence of such an interface in the list means that the Linux kernel has successfully loaded the driver module for your hardware.
To obtain more specific information about wireless capabilities, such as supported frequencies, signal strength and Wi-Fi standards, use the utility iw. Team iw dev will display a list of wireless interfaces and their current status, including MAC address and connection type.
iw dev wlan0 infoIf the system sees the interface but cannot connect to the network, the problem may not be in the driver, but in the blocking settings. Command rfkill list will show the wireless module blocking status (soft block or hard block). This is a common situation where Wi-Fi doesn't work after installing Linux alongside Windows due to the module's status.
⚠️ Attention: If the interface shows as "DOWN" in the output
ip link, this doesn't always indicate a malfunction. The interface may simply be software-disabled. Try running the commandip link set dev wlan0 upto activate it.
Using the flag -a with the team ip addr This will allow you to see all interfaces, including those that are currently inactive. This helps diagnose situations where the driver has loaded, but the interface hasn't been automatically brought up by the network manager.
Obtaining detailed information through lshw
Utility lshw (List Hardware) is a powerful tool that collects hardware configuration information from all available sources in the system. It can provide a structured report on network adapters, including not only the model and vendor, but also the driver version used by the kernel and their operating status.
To work with lshw Superuser rights are often required because the utility queries deep kernel data. The command sudo lshw -class network will filter the output to show only information about network devices, making the report much easier to read. In the output, you'll see the "product," "vendor," "configuration," and "capabilities" fields.
Pay special attention to the "driver" field. If the driver name is specified there (for example, iwlwifi for Intel or ath9k (For Atheros), the device is fully supported and functional. If the field is empty or contains the value "unclaimed," the driver is missing or not loaded.
| Parameter | Description | Example of meaning |
|---|---|---|
| product | Device model name | Wireless 7260 |
| vendor | Chipset manufacturer | Intel Corporation |
| driver | The kernel module used | iwlwifi |
| capabilities | Supported technologies | pm msi bus_master cap_list ethernet physical wireless |
| configuration | Current settings and status | driver=iwlwifi latency=0 link=no |
The output format can be changed to HTML or XML by adding flags -html or -xml, which is convenient for saving reports or automated analysis using scripts. However, for quick review, the text format remains the most readable and informative.
Specialized utilities for wireless networks
Linux distributions aimed at advanced users or pentesters (such as Kali or Parrot) often have a package pre-installed. wireless-tools and utility iwlist. Although iw is considered a modern replacement, iwlist Still useful for scanning available networks and getting detailed information about supported frequencies and signal qualities.
Team iwlist scanning Allows you to see not only the SSIDs of available access points but also technical details such as the encryption protocol used, signal quality, and channel frequency. This helps you determine whether the adapter sees 5 GHz networks or only 2.4 GHz, which indirectly confirms its model and capabilities.
Another useful tool is inxiThis is a system informer that collects data about the processor, memory, graphics, and network. The command inxi -N will display a brief summary of network devices, indicating the model and driver in one sentence, which is very convenient for a quick check.
- 🔍 Scanning:
iwlist wlan0 scanningwill show all available networks around. - 📡 Frequencies: Checking the frequencies helps you determine if you have a dual-band adapter.
- 🛠️ Driver: Utility
modinfowith the module name will tell you about the driver version and parameters. - 📜 Logs: Team
dmesg | grep firmwarewill show firmware loading errors.
For users who prefer a graphical interface, the utility HardInfo (System Profiler and Benchmark) provides a convenient visualization of all components, including network adapters, with the ability to copy reports. This is a great option for those who don't want to memorize terminal commands.
⚠️ Attention: Interfaces and available commands may vary depending on the distribution and kernel version. Some utilities may not be installed by default on minimalist Linux distributions and will need to be installed through a package manager.
Search for drivers by hardware IDs
Once you know the Vendor ID and Device ID (for example, 8086:08b1), the most important step begins: finding and installing the correct driver. These hexadecimal codes are a universal key. By entering them into a search engine along with the word "Linux driver," you'll find precise information about device kernel support or whether proprietary software is required.
There are databases such as Linux Wireless or the PCI ID Repository where you can check the device's support status. If the device is new, it may not yet be supported by the stable kernel branch and will require installing drivers from the repository. backports or build from source code from GitHub.
modinfo iwlwifi | grep -i firmwareTeam modinfo It's also useful for checking which firmware files are required for a driver to work. Often, the "Wi-Fi not working" issue is resolved by simply installing the package. linux-firmware or specific firmware that is missing from the system.
☑️ Check before installing the driver
Without these packages, installation of third-party drivers will not be possible, and the system will return an error upon startup. make.
What to do if a driver conflicts with the kernel?
If the system fails to boot or Wi-Fi is unstable after installing the driver, try rolling back the changes. Remove recently installed packages or boot into Recovery Mode and disable the new module in the modprobe configuration. Blacklists in /etc/modprobe.d/ can help prevent the problematic driver from loading.
Frequently Asked Questions (FAQ)
How can I find out the model of my Wi-Fi adapter if I don't have internet access to install drivers?
Use commands lspci -nn or lsusb, which operate at the BIOS/UEFI and kernel levels without requiring installed device drivers. The resulting ID codes can be rewritten and used to search for the driver on another device with network access.
Why doesn't the lspci command show my Wi-Fi adapter?
This could mean the adapter is physically disabled (via a switch on the case), locked in the BIOS, in a deep power-saving state, or completely failed. The adapter could also be USB, not PCI, in which case you'll need to use lsusb.
Where can I find a driver if it is not in the repository?
You should search the official website of the chipset manufacturer (Intel, Realtek, Broadcom) or GitHub. Enthusiasts often post up-to-date driver versions there for new devices that haven't yet made it into the stable Linux kernel.
Can Windows drivers be used on Linux?
Directly, no. However, there is a project ndiswrapper, which allows you to run some Windows drivers (.sys files) on Linux. This is unstable and considered a temporary solution; it's better to look for a native Linux driver.
How do I know if my adapter supports monitor mode?
Use the command iw listThe "Supported interface modes" section should list "monitor." If it doesn't, the adapter or driver doesn't support this mode, which is necessary for network auditing.