All drivers wifi linux

Linux Find Wireless Wifi Driver Chipset Information

H ow do I find out Wireless driver chipset information under a Linux operating system? How do I get wireless card chipeset information without opening my systems or laptop using a Linux? How can I find out which Wi-Fi driver is installed on my Linux laptop? How do I see the information of currently installed WiFi drivers on my Ubuntu or Debian Linux laptop?

The simplest command to get this information is to use the lspci command. This utility show information about PCI buses in the system and devices connected to them. The PCI configuration space is restricted to root user. [donotprint]

Tutorial details
Difficulty level	Easy
Root privileges	Yes
Requirements	lspci
Est. reading time	1m

[/donotprint]So you need to run the following commands as root user to get all possible information about your wifi card chipset and Linux driver.

You may need to run update-pciids command to get the current version of the pci.ids file from the Internet and install it to get accurate results.

Linux Find Wireless Wifi Driver Chipset Information

The syntax is as follows for the lspci command and grep command:

Note down 0c:00.0 and enter the following command:
lspci -vv -s 0c:00.0
Sample outputs:

So I am using iwlagn driver. To get driver information type the following modinfo command:
$ modinfo iwlagn
Sample outputs:

Finally, you can run the following to get info about vendor & product code:
lspci -n -s 0c:00.0
Sample outputs:

• 0280 – Network controller:
• 8086:4235 – Intel Corporation Ultimate N WiFi Link 5300

Or the all in one following option:
$ lspci -nn -s 0c:00.0
Sample outputs:

Tip: Update pci database on Linux to get accurate infomation about the wireless / wifi chipset

Type the following update-pciids command to download new version of the PCI ID list to get accurate info from lspci:

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

Fig.01: Running update-pciids and lspci commands on a Linux

Using lshw command

One can use the lshw command as follows
$ lshw -C network
$ lshw -C network | more
Look for “Wireless interface”. Here is a sample outputs:

Fig.02: Finding WiFi chipset and driver information on Linux

A note about USB WiFi device

You need to use the lsusb command:
$ lsusb
Try to look a wireless or network device in the list.

A note about lsmod command

To see the status or list of all drivers (modules) loaded in the Linux Kernel, run the lsmod command:
$ lsmod
$ lsmod | more
OR use the grep command/egrep command to filter outputs:
$ lsmod | grep -i wifi
Sample outputs:

Look like I am using iwlwifi. Verify it with the following modinfo command:
$ modinfo iwlwifi
See the following tutorials for more info on Linux wifi drivers and commands:

Conclusion

You just learned how to find Wifi driver and chipset information on Linux based systems. I suggest you visit the main source of Documentation for the Linux wireless (IEEE-802.11) subsystem here. It features information for end-users, developers and vendors. Also read the man pages for the following command using the man command:
$ man lspci

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Category	List of Unix and Linux commands
Documentation	help • mandb • man • pinfo
Disk space analyzers	df • duf • ncdu • pydf
File Management	cat • cp • less • mkdir • more • tree
Firewall	Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04
Linux Desktop Apps	Skype • Spotify • VLC 3
Modern utilities	bat • exa
Network Utilities	NetHogs • dig • host • ip • nmap
OpenVPN	CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04
Package Manager	apk • apt
Processes Management	bg • chroot • cron • disown • fg • glances • gtop • jobs • killall • kill • pidof • pstree • pwdx • time • vtop
Searching	ag • grep • whereis • which
Shell builtins	compgen • echo • printf
Text processing	cut • rev
User Information	groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w
WireGuard VPN	Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04

Comments on this entry are closed.

Neat, useful, clear.
Thanks Vivek.

May the last item should have been [-nn] instead of [-n]

lspci -nn -s 0c:00.0

which gives both PCI IDs and description.

Ah, yes it take out all guess work. Thanks for pointing it out 🙂

Amazing help, I really appreciate it.

Amazing!
very detailed approach, helped alot
very usefull for new/beginers
Thanks!

the output is below,can anyone tell me my chipset information,

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)

when I ran the command ” lspci | grep -i wireless ” I got nothing. what exactly that means? What shall I do?

And what about the same information for wireless USB interfaces??

Источник

Ubuntu Documentation

Wireless Troubleshooting Guide

This part of the guide is designed to help you troubleshoot your wireless adpater’s driver issues. This page is part of the WirelessTroubleShootingGuide. You should have correctly identified your device as detailed in the Devices page of this guide. See also the comprehensive explanations of commands for troubleshooting your wireless.

1. Check for Loaded Device Drivers

First you should check if a driver automatically loaded. (Your device may be supported in Ubuntu with a native driver.) Use the lshw command. As explained under lshw, if there is a line saying configuration: . driver=. in the description of the wireless card, this indicates the driver is installed.

If you are not running the most recent kernel, update your system (System > Administration > Update Manager). Drivers, especially wireless, are constantly being added and modified.

2. Choosing, Finding and Installing Drivers

2.1. Using Native Linux Drivers

Check in System > Administration > Hardware Drivers for a binary driver. For instance, many Broadcom cards will work with the Broadcom STA driver. Unfortunately, the driver is proprietary (the source code is not freely available), and so cannot be installed automatically as part of Ubuntu. If you are willing to accept this limitation, activate the driver.

Search your card manufacturer’s website for a Linux driver.

2.2. Using ndiswrapper for Cards Without a Linux Driver

If you find your card does not have a Linux driver you will have to look at an app called ndiswrapper.

full information on ndiswrapper kept on this page including troubleshooting help specific to ndiswrapper.

There may be a native driver that comes with Ubuntu which is conflicting with ndiswrapper. In such cases, if you want to use ndiswrapper, you can blacklist the native driver. See below for details.

3. Check Driver

If you ran lshw -C network and saw a driver bound to the device then let’s test to make sure it’s communicating with the kernel.

Run the command lsmod to see if driver is loaded. (look for the driver name that was listed in the output of lshw, «configuration» line).

If you did not see the driver module in the list then use the modprobe command to load it.

If you see two modules (usually ndiswrapper and a native Linux driver) blacklist one of them (see below).

run the command sudo iwconfig. If you see output like in the example in the command section then the driver is at least identifying the device as a wireless device to the kernel.

Opening networking in system>administration> and seeing the device in the list is how to identify through a gui if the driver is at least communicating with the kernel.

run the command sudo iwlist scan to scan for a router. If an access point is identified this shows that the card is probably working properly as it can complete a wireless interface task. (note not all cards support scanning)

3.1. Multiple drivers loaded

For some cards (e.g., SMC2632W v1.02), an additional set of drivers is incorrectly loaded, effectively disabling wireless networking by generating two apparent wifi cards where there should only be one. Typically, you’ll see entries for both eth1 and wlan0_rename after running the iwconfig command, with your communication speed divided evenly between them. One of those drivers should not be loaded, and should be blacklisted. To do so, edit /etc/modprobe.d/blacklist and add the following lines:

where is, for example, «hostap» (the «hostap» driver apparently causes problems for several cards). Then save, reboot, and check your connection with iwconfig.

3.2. Driver looks ok, device disabled

Newer laptops come with battery saving features to disable the wireless radio. Usually this is switched by a FN+Fx key combo or a specific button for the purpose. It is possible the driver and connection is ok but the wireless device is disabled and can’t be used. Using the designated key(s) in linux sometimes does not work.

Options for identifying this:

rfkill list will show if there is a hardware or software block.

lshw command you see *-network:1 DISABLED or wireless=radio off

If you run the iwconfig command you see eth1 NOT READY!.

So how do you rectify this? It varies so much the exact solution can’t be put here in this document for all the different models. So.

Look at the LaptopTestingTeam page on the team wiki to see if your laptop is listed with any information.
Do a google search using terms such as manufacture, model, linux, wireless, enable, button, radio. etc. When searching and finding similar pages that don’t help, use words that are used in those pages to help you search.

Go to the ubuntu forums and ask, maybe someone else has the same laptop and knows the work around.

Some laptops have a controller chip on the motherboard that is only accessible through a different OS. If you have turned off your wireless adapter in a different operating system, you may have to boot back into that OS and enable the card before it is accessible to Linux.

WifiDocs/WirelessTroubleShootingGuide/Drivers (последним исправлял пользователь knome 2013-12-13 18:55:41)

The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details

Источник