Linux drivers which wifi

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

Introduction

This page provides support information on Broadcom BCM43xx wireless network cards. The aim of Ubuntu is to ensure all card models work automatically with no, or minimal configuration. For example, via System > Administration > Hardware/Additional Drivers. If you are having a WiFi issue, please see below on getting this addressed.

Identifying Your Broadcom BCM43xx Chipset

With this information, you may assess what drivers are supported for your card, and how to switch to a different driver from the instructions below.

Internal cards

To identify a card that was installed inside your computer prior to purchase, please open a Terminal and execute:

This will display:

You now know:

• The Chip ID: BCM4331
• The PCI-ID: 14e4:4331
• Kernel driver in use: wl

USB cards

One will want to execute at a terminal:

Drivers available in Ubuntu

The following is an overview of the different drivers that are available for Broadcom wireless devices.

Broadcom STA Wireless driver (Proprietary)

The propietary Broadcom STA Wireless driver is maintained upstream by Broadcom. As this driver is closed source, fixes in the driver itself may only be provided by Broadcom. As a convenience, Ubuntu offers two versions of this driver:

The bcmwl-kernel-source package aims to offer a later version for a given release. Instructions for installation may be found later in this article.

The broadcom-sta package aims to offer an earlier version for a given release.

As per the Broadcom readme file for driver version 6.30.223.271, the following devices are compatible:

b43 driver (Open-source)

For Chip ID BCM 4306 (rev 03), 4311, 4312, 4318, 4322, 4331, 43224 and 43225.

The b43 infrastructure is composed of two parts. The first is the firmware-b43-installer package. This is simply a script to extract and install the b43 driver firmware, maintained by the Ubuntu community. The second is the b43 driver, maintained upstream by the Linux kernel community. Instructions to install the package may be found below.

b43legacy driver (Open-source)

For Chip ID BCM 4301, 4306 (rev 02), and 4309.

The b43legacy infrastructure is composed of two parts. The first is the firmware-b43legacy-installer package. This is simply a script to extract and install the b43legacy driver firmware, maintained by the Ubuntu community. The second is the b43 driver, maintained upstream by the Linux kernel community. Instructions to install the package may be found below.

brcmsmac driver (Open-source)

For Chip ID BCM 4313, 43224 and 43225.

The open-source brcmsmac driver for PCIe devices is available from the brcm80211 module of the linux kernel package, maintained upstream by the linux kernel community. For more granular support information, please see their wiki page here.

brcmfmac driver (Open-source)

SDIO: For Chip ID BCM 4329, 4330, 4334, 4335, 4354, 43143, 43241, and 43362.
USB: For Chip ID BCM 43143, 43242, 43566, and 43569.

The open-source brcmfmac driver is available from the brcm80211 module of the linux kernel package, maintained upstream by the linux kernel community. For more granular support information, please see their wiki page here.

rndis_wlan driver (Open-source)

For Chip ID BCM 4320.

The open-source rndis_wlan driver is available from the linux kernel package, maintained upstream by the linux kernel community. For more granular support information, please see their wiki page here.

ndiswrapper (Open-source)

For all chip IDs.

The ndiswrapper package utilizes the Windows closed source drivers to activate your WiFi card. It is maintained upstream here. For installation instructions, please see here.

Installing STA drivers

STA — Internet access

If you have some other kind of Internet access on your computer (e.g. via an ethernet cable) then use the instructions below.

12.04 (Precise Pangolin)

Open a Terminal and install the bcmwl-kernel-source package:

Note: If you see the message «Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed» then you are missing the appropriate generic linux-header package(s).

To test the driver (and remove the need for a computer restart) use:

Allow several seconds for the network manager to scan for available networks before attempting a connection.

The bcmwl-kernel-source package should automatically blacklist the open source drivers so that the STA driver is the only one in use.
Back to top

STA — No Internet access

If you do not have any other means of Internet access on your computer, you can install the bcmwl-kernel-source package from the restricted folder under ../pool/restricted/b/bcmwl on the Ubuntu install media.

Note: The bcmwl-kernel-source package depends on the linux-headers packages so you may need to first retrieve the appropriate package(s) from the online repositories. A running LiveCD/LiveUSB environment has these packages (allowing the wireless to work), but an installed system may not. Make sure you have the linux-headers package that matches your current kernel version, plus the appropriate generic header packages so that they are automatically updated on a kernel upgrade. To find out your current kernel use the command:

To find what linux-headers packages you have installed use the command:

Systems installed from CDROM can add the install CD as a package source and install bcmwl-kernel-source using apt-get as above. However, if you want to do it manually then the instructions are as follows:

Navigate the install media and install the packages listed below by double clicking OR install the packages consecutively from a Terminal (in the commands below the install media is mounted at /cdrom, but yours maybe different):

Upstream 802.11 Linux STA driver

Installing b43/b43legacy firmware

The Ubuntu kernel now provides the b43 driver, however due to copyright restrictions not the proprietary firmware which is required to run your card. The following instructions explain how to extract the required firmware.

b43 — Internet access

12.04 (Precise Pangolin) — 14.04 (Trusty Tahr)

Open a Terminal and if you haven’t already done so, update your package list:

If you have a b43 card use the command

or, if you need the b43legacy driver, use:

or, (12.04) if you need a LP-PHY version (e.g BCM4312), use:

Restart the computer or reload the b43/b43legacy module as outlined in the Switching between drivers section below (replace b43 with b43legacy where appropriate).

b43 — No Internet access

If you do not have any other means of Internet access from Ubuntu, then you will have to download the firmware from another computer with Internet access, from an existing OS on another partition, or before you install Ubuntu. You will also need the b43-fwcutter package which is usually included on the install media or can be downloaded from the official online repositories.

Install the b43-fwcutter package. This is usually located on the Ubuntu install media under /cdrom/pool/main/b/b43-fwcutter/ or you can download the binary ‘.deb’ package by following the links on launchpad.

Double click on the package to install or in a Terminal issue the following commands:

On a computer with Internet access, download the required firmware file:

Copy the downloaded file to your home folder. Open a new Terminal and use b43-fwcutter to extract and install the firmware:

b43legacy

b43 (12.04 Precise Pangolin)

b43 (14.04 Trusty Tahr)

Restart the computer or reload the b43/b43legacy module as outlined in the Switching between drivers section below (replace b43 with b43legacy where appropriate).

Switching between drivers

If you card is supported by more than one driver then use the modprobe command to test the drivers. First unload all conflicting drivers (this includes removing the driver you’re trying to install):

To load a specific driver use one of the following commands:

Allow several seconds for the network manager to scan for available networks before attempting a connection.

After a reboot the system may auto-load a different driver to the one you wanted to use. Consequently, for permanent use, you may find it necessary to blacklist the driver/module you are not using. In the command below replace drivername with the driver you want to blacklist:

Update the initramfs after any changes to the blacklist files:

Note: The bcmwl-kernel-source package will automatically blacklist the open source drivers/modules in /etc/modprobe.d/blacklist-bcm43.conf.

If you wish to permanently use the open source drivers then remove the bcmwl-kernel-source package:

Ensure that the driver/modules you wish to use are not blacklisted in any of the other files in /etc/modprobe.d .

Unsupported devices

If your wifi card/chipset and/or various modes are not supported by the STA driver or the open source kernel drivers, then you will need to go for ndiswrapper — this will allow you to use the Windows closed source drivers to activate your wifi card.

Known Issues

* LP#1010931 14e4:4727 [Dell Vostro 3555] Broadcom BCM4313 5GHz doesn’t work but 2.4GHz does

• The root cause is the card only transmits/receives on the single-band 2.4GHz only, so it would never broadcast at 5GHz.

Filing bug reports

Broadcom STA Wireless driver

While using either the bcmwl-kernel-source or broadcom-sta-source package from the Ubuntu repositories (not a recompiled/custom version) execute one of the following via a terminal:

This will file a new report. In it, please ensure all of the below is provided if missing:

Please include only one (not both) of the following corresponding to which driver series you are filing a report against:

Please execute the following via a terminal and post the results in your report:

The full manufacturer and model of your computer as noted on the sticker of the computer itself.

Did this problem not occur in a previous release? If so, which one(s) specifically?

Does this problem occur with the latest version of Ubuntu?

If available, please comment to how testing the relevant open source driver for your card type provides a WORKAROUND. If your chipset is supported as per above, but doesn’t work, please file a bug following the b43 driver procedure below.

Please provide the router manufacturer, model, and firmware version.

Please comment to how testing ndiswrapper for your card type provides a WORKAROUND. If it doesn’t work, please file a bug report as per the support article.

If the version of the driver you are using in the repository is the latest version available as per Broadcom, Broadcom wants you to send them an email about this to linux-wlan-client-support-list@broadcom.com. Please post their response to your report.

If the version of the driver you are using in the repository is an older version than that available from Broadcom, then contacting them would not apply. Instead, an investigation would need to occur to see if the version available for your release should be updated.

b43/b43legacy firmware utility

Before filing a bug report about b43 or b43legacy, it’s important to distinguish this as a issue with the firmware extraction script, or the driver itself. If it’s an issue with the script, one will need to install the version from the Ubuntu repositories (not a recompiled/custom version) and then execute via a terminal either:

b43/b43legacy driver

For bugs regarding the b43 or b43legacy driver, please execute the following via a terminal:

Also, please provide the following:

1. The full manufacturer and model of your computer as noted on the sticker of the computer itself.
2. Did this problem not occur in a previous release? If so, which one(s) specifically?
3. Does this problem occur with the latest version of Ubuntu?
4. If available, please comment to how testing test the relevant Broadcom STA Wireless driver for your card type provides a WORKAROUND. If it doesn’t, please file a report as per the procedure above.
5. Please provide the router manufacturer, model, and firmware version.

Please comment to how testing ndiswrapper for your card type provides a WORKAROUND. If it doesn’t work, please file a bug report as per the support article.

Once all of the required information is present, if the version of the driver you are using is the latest version available from the Ubuntu repositories, then one would want to e-mail the b43-dev mailing list following this procedure.

See Also

Installing Windows drivers with NdisWrapper.

Источник

Читайте также:  Темы значков рабочего стола windows