Lspci stands for list PCI devices. Lspci command is used to display information about PCI buses in the system and hardware devices that are connected to PCI and PCI bus. It will display information about model number/chip details for devices like PCI bridge, VGA controller, Ethernet controller, USB controller, Audio device, IDE interface, etc. Pciutils-3.5.5-win32.zip - 32-bit Windows version (runs on both x86 and x64 Windows) pciutils-3.5.5-win64.zip - 64-bit Windows version (only works on x64 Windows) lspci and setpci require Administrator privileges for certain operations - run them in an elevated command prompt on Windows Vista and newer.

• Mar 27, 2018 Windows 10’s Anniversary Update added support for Linux environments to Windows 10 back in 2016. But don’t be deceived: this is more than just a Bash shell. It’s a full compatibility layer for running Linux applications on Windows.
• I've made a batch file on a Windows machine, with the following command: rsh hdvg-1 -l root lspci The hdvg-1 is the name of the Linux machine on the network. But what I get in result is: command.

How to identify a device > PCI

How to 'identify' the PCI-like devices (AGP, PCI-Express, CardBus, Express Card, etc) that are connected to you computer.

Many people simply use lspci, which is available on every Debian system, to list the device on their computer. Gnome users can install and use the hardinfo method. KDE user can use kinfocenter.

Devices are mainly identified using a pair of hexadecimal numbers, like 1014:003E.

• The 4 first hexadecimal digits are the Vendor ID (1014 = IBM)
• The 4 last hexadecimal digits are the Device ID (003e = 16/4 Token ring)

Actually there is also some sub-vendor-id, sub-vendor-id (to identify the computer/vendor implementation), pci function and class... see references for more information.

Some of the devices (device-ids) handled by Debian are listed in the page : DeviceDatabase/PCI.

lspci

lspci [package:pciutils] is the standard tool to query the devices connected to any pci compatible bus.

Sample output ('-nn' option only works with newer Linux versions):

Notes regarding the example above :

• 104c:ac56 is the cardbus bridge ('controller')
• 1317:1985 is a PCCard (32-bit Cardbus) Ethernet Adapter.

• if your device description says 'Unknown device', you can update your local pci-id definition by running update-pciids as root.

man (8)lspci (8)update-pciids
/usr/share/misc/pci.ids - A text file mapping vendor IDs and device IDs to a text description.

You can use grep to shorten the above list:

Under Gnome : hardinfo

Gnomes's System Information (Hardinfo in Menu Applications/System Tools, from package:hardinfo) has an information page on the 'PCI' cards.

Under KDE : KInfocenter

KDE's KInfoCenter (in K Menu / System / KInfoCenter Info Center, from package:kcontrol) has an information page on the 'PCI' cards.

Note: KInfoCenter provides the PCI device names, not PCI IDs.

discover

The discover package has a nice command too:

man discover(1)
discover uses its own files: /lib/discover/pci-busclass.xml, /lib/discover/pci-device.xml, /lib/discover/pci-vendor.xml

/proc/bus/pci/devices

If lspci isn't available (!), you can display the content of /proc/bus/pci/devices to list vendor and device IDs.

/sys/bus/pci

If lspci isn't available (!), you can browse /sys/bus/pci (assuming sysfs is mounted on /sys).

/usr/share/doc/linux-doc-2.6.26/Documentation/filesystems/sysfs-pci.txt.gz - /sys/bus/pci overview

Lspci On Windows 7

• Wikipedia - PCI

• http://pci-ids.ucw.cz/ maintains a list of device-id and vendor-id to text mappings (used by lspci, xorg and more).