Many users face the need for a thorough diagnosis of their wireless module when standard drivers stop working or require the installation of specific software for monitor mode. Often, the device specifications or the box only list an abstract model number like "AC1200" or "AX3000," which provides no information about the actual hardware. chipset (controller) determines compatibility with operating systems, support for encryption protocols and the ability to fine-tune.
Knowing the exact controller model is critical when searching for alternative drivers, especially for older devices or specific operating systems like Kali Linux or FreeBSD. Adapter manufacturers often change the hardware platform within the same device model, so relying solely on the model name on the sticker is risky. In this article, we'll discuss proven methods for identifying hardware without opening the case.
There are several levels of identification: from simply viewing properties in the system to analyzing low-level hardware identifiers. Windows And Linux They provide various tools for these purposes, and using them allows you to solve 99% of compatibility issues. Let's look at how to obtain this data most effectively.
Analysis via Windows Device Manager
The most accessible method, which doesn't require installing third-party software, is found in a standard Windows system tool. However, simply opening the adapter's properties often only displays a generic name that duplicates the information on the box. To obtain the actual data, you need to delve deeper into the properties of a specific piece of hardware and find its unique codes.
Open device Manager via the Start menu or a key combination Win + XFind the "Network Adapters" section, expand it, and select your Wi-Fi module. Right-click, select "Properties," then go to the "Details" tab. From the "Property" drop-down list, select Equipment ID (Hardware ID).
You will see lines like this PCI\VEN_8086&DEV_08B1&SUBSYS...All the necessary information is hidden here. Abbreviation VEN stands for Vendor ID, and DEV — Device ID. These hexadecimal codes allow for the unambiguous identification of the chip, even if the driver is not installed and the device is displayed as "Unknown Device."
⚠️ Note: If the list displays multiple lines, use the first (topmost) one, as it contains the most specific identifier for your device revision. Lower lines may be common to an entire series of chips.
The obtained codes can be entered into a search engine or specialized PCI ID databases. For example, the code VEN_10EC belongs to Realtek, and DEV_8812 indicates a specific RTL8812AU controller model. This allows you to find a driver even for a device without a specific model number.
Using the Command Prompt and PowerShell
For those who prefer console utilities or need to automate the data collection process, the Windows command line offers powerful tools. Using commands, you can quickly export data to a text file or copy it for further analysis, bypassing the graphical interface.
Launch the command prompt (cmd) or PowerShell as administrator. Enter the command wmic path win32_pnpentity where "PNPClass='Net'" get name, deviceid /format:listThis command will list all network devices with their full IDs. Look for lines containing "Wireless" or "Wi-Fi."
More detailed information, including the driver version and chip manufacturer, can be obtained via PowerShell. Run the command:
Get-NetAdapter | Where-Object {$_.Status -eq "Up"} | Select-Object Name, InterfaceDescription, DriverVersion
Although this method does not always show the exact chipset ID, the field InterfaceDescription Often contains the internal model name, which is easier to Google than the marketing name. For example, instead of "TP-Link Archer T4U," you might see "Realtek 8812BU Wireless LAN 802.11ac USB NIC."
Diagnostic software: AIDA64 and HWiNFO
If Windows' built-in tools don't seem informative enough, specialized system diagnostic software will provide comprehensive data. Programs like AIDA64, HWiNFO or Speccy can read data directly from device registers, ignoring standard driver names.
In AIDA64, go to "Network" → "Windows Network." Here you'll see not only the adapter name, but also the bus type, connection speed, and, most importantly, detailed chip information. You can often find the exact controller model in "Devices" → "Windows Devices" → "Network Adapters."
The advantage of using such tools is that they aggregate data from different sources. If the driver is installed incorrectly, these programs may show the device as "Generic" or "Unknown" but still recognize its PCI/USB ID, which will be visible in the report.
Identification in a Linux environment
For Linux users and enthusiasts using network testing distributions (such as Kali or Parrot OS), identifying the chipset is especially challenging, as kernel driver support varies greatly depending on the specific model. In Linux, command-line tools provide perhaps the most transparent information.
The basic command to list USB devices (if you have a USB adapter) is lsusb. Run it in the terminal. The output will contain lines like Bus 001 Device 004: ID 2357:0120 TP-Link Technologies Co., LtdCodes after ID - these are the desired VEN and DEV.
For PCI/PCI-E adapters (internal cards) the command is used lspciTo filter network controllers directly, enter:
lspci -nn | grep -i network
Flag -nn is critical because it displays the numeric vendor and device IDs in square brackets, such as [8086:08b1]Knowing these numbers, you can use the command modinfo for the loaded kernel module to find out which driver it is (ath9k, rtl88xxau etc.) serves this chip.
⚠️ Note: Command line interfaces and package names in Linux distributions may change with kernel updates. Always check the command syntax in your distribution's official documentation if standard commands don't work.
Decoding Vendor ID and Device ID
Having received hexadecimal codes, users often wonder: what to do with them next? These codes are a unique device ID in the world of computer hardware. The first four digits after VEN_ or the first colon is the manufacturer code, and the next four after DEV_ — code of a specific device.
Global PCI ID databases exist that allow you to match these numbers with the actual chip name. Knowing the manufacturer (e.g., MediaTek, Ralink, Atheros) can help predict driver behavior. Below is a table of the most common Wi-Fi chip vendors.
| VEN Code (Hex) | Manufacturer (Vendor) | Popular chip series |
|---|---|---|
| 10EC | Realtek Semiconductor Corp. | RTL8812, RTL8821, RTL8188 |
| 168C | Atheros Communications (Qualcomm) | AR9271, QCA9377, QCA6174 |
| 14E4 | Broadcom Corporation | BCM43xx, BCM20702 |
| 8086 | Intel Corporation | Intel AC 7260, AX200, AX210 |
| 0E8D | MediaTek Inc. (Ralink) | MT7612, MT7921, RT5370 |
Using this data, you can accurately determine which driver to download from the manufacturer's website. It often happens that the same TP-Link or D-Link adapter was released in three different versions (V1, V2, V3) with completely different chips inside. The VEN/DEV code never lies, unlike the sticker on the case.
Physical inspection and opening of the device
In extreme cases, when the device isn't detected by the system at all (a burned-out USB port, a problem with the power controller) or software methods fail, a physical inspection is the only option. This method requires careful attention and typically voids the warranty, so only experienced users should attempt it.
You need to open the adapter case. On the board, you'll notice the largest chip with markings. This is usually a square black case with numerous pins. The manufacturer's logo and model number are laser-etched onto it, for example, RTL8812AU or MT7612UN.
Please note that signal amplifier chips (FEM - Front End Module) or EEPROM memory, which stores MAC addresses and calibration data, may be located near the main chip. Do not confuse these with the main controller. The main chip usually has more complex markings and more contacts.
Risks of opening
When opening monolithic USB adapter housings, there's a high risk of damaging antenna wires or tearing off SMD components. Use plastic cards to open the housings, avoiding metal tools.
Common compatibility issues and nuances
Even knowing the exact chipset, users may encounter problems. It's common for a driver to be compatible with a chip but fail to work due to a USB controller firmware version or a software version conflict. This is especially true for Realtek chips, which require separate installation of not only the driver but also a configuration utility.
Another nuance is standard support. The chip may physically support Wi-Fi 6 (802.11ax), but if you connect it to a USB 2.0 port or use an older driver, it will operate in 802.11ac mode. Always check that the driver you use matches not only the chip model but also the desired operating mode.
- 🔍 Version conflict: New driver versions can disable older features (such as monitor mode), so penetration testing often looks for older, "leaky" driver versions.
- 🔍 Counterfeit adapters: Adapters often appear on marketplaces to be a high-powered model (for example, AC1200), even though they contain a cheap N-class chip. Checking the hardware ID is the only way to identify a counterfeit.
- 🔍 Thermal throttling: Some powerful chipsets (such as those from MediaTek) are prone to overheating and throttling. Knowing the model allows you to consider installing a heatsink or active cooling in advance.
Understanding your Wi-Fi adapter's architecture gives you complete control over your network connection. You're no longer dependent on automatic Windows updates, which can break a working configuration, and can choose the optimal software yourself.
☑️ Checklist before buying a new adapter
Frequently Asked Questions (FAQ)
Is it possible to update the Wi-Fi adapter chipset using software?
No, the chipset is physical hardware. It cannot be changed through software. However, it can be updated. firmware (firmware) or driver, which can improve stability, speed, or add support for new features if they are included by the manufacturer.
Why does Device Manager show "Unknown Device"?
This means the operating system sees a bus connection (USB or PCI), but doesn't have a driver installed that can tell it how to work with this device. In this case, identifying the device by hardware ID (VEN/DEV) is the only way to find the required driver.
Does the chipset affect internet speed?
Yes, directly. Different chipsets have different processor performance, support for encryption standards (WPA3), number of MIMO streams, and receiver sensitivity. For example, Broadcom and Intel chips often demonstrate more stable speeds in noisy environments than budget solutions.
Where can I find a driver if the manufacturer's website is closed?
Knowing the exact chip model (for example, RTL8812BU), you can find the driver on the chip developer's website (Realtek), in GitHub repositories (enthusiasts often post improved versions), or on specialized forums. The key is to search by chip model, not adapter brand.