Section: The PCI Utilities (8)Updated: 31 January 2010Local indexUp
lspci - list all PCI devices
is a utility for displaying information about PCI buses in the system and
devices connected to them.
By default, it shows a brief list of devices. Use the options described
below to request either a more verbose output or output intended for
parsing by other programs.
If you are going to report bugs in PCI device drivers or in
itself, please include output of "lspci -vvx" or even better "lspci -vvxxx"
(however, see below for possible caveats).
Some parts of the output, especially in the highly verbose modes, are probably
intelligible only to experienced PCI hackers. For exact definitions of
the fields, please consult either the PCI specifications or the
Access to some parts of the PCI configuration space is restricted to root
on many operating systems, so the features of
available to normal users are limited. However,
tries its best to display as much as available and mark all other
Basic display modes
Dump PCI device data in a backward-compatible machine readable form.
See below for details.
Dump PCI device data in a machine readable form for easy parsing by scripts.
See below for details.
Show a tree-like diagram containing all buses, bridges, devices and connections
Be verbose and display detailed information about all devices.
Be very verbose and display more details. This level includes everything deemed
Be even more verbose and display everything we are able to parse,
even if it doesn't look interesting at all (e.g., undefined memory regions).
Show kernel drivers handling each device and also kernel modules capable of handling it.
Turned on by default when
is given in the normal mode of output.
(Currently works only on Linux with kernel 2.6 or newer.)
Show hexadecimal dump of the standard part of the configuration space (the first
64 bytes or 128 bytes for CardBus bridges).
Show hexadecimal dump of the whole PCI configuration space. It is available only to root
as several PCI devices
when you try to read some parts of the config space (this behavior probably
doesn't violate the PCI standard, but it's at least very stupid). However, such
devices are rare, so you needn't worry much.
Show hexadecimal dump of the extended (4096-byte) PCI configuration space available
on PCI-X 2.0 and PCI Express buses.
Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the
PCI bus instead of as seen by the kernel.
Always show PCI domain numbers. By default, lspci suppresses them on machines which
have only domain 0.
Options to control resolving ID's to names
Show PCI vendor and device codes as numbers instead of looking them up in the
PCI ID list.
Show PCI vendor and device codes as both numbers and names.
Use DNS to query the central PCI ID database if a device is not found in the local
file. If the DNS query succeeds, the result is cached in
and it is recognized in subsequent runs even if
is not given any more. Please use this switch inside automated scripts only
with caution to avoid overloading the database servers.
but the local cache is reset.
Query the central database even for entries which are recognized locally.
Use this if you suspect that the displayed entry is wrong.
Options for selection of devices
Show only devices in the specified domain (in case your machine has several host bridges,
they can either share a common bus number space or each of them can address a PCI domain
of its own; domains are numbered from 0 to ffff), bus (0 to ff), slot (0 to 1f) and function (0 to 7).
Each component of the device address can be omitted or set to "*", both meaning "any value". All numbers are
hexadecimal. E.g., "0:" means all devices on bus 0, "0" means all functions of device 0
on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only
the fourth function of each device.
Show only devices with specified vendor and device ID. Both ID's are given in
hexadecimal and may be omitted or given as "*", both meaning "any value".
as the PCI ID list instead of /usr/share/misc/pci.ids.
as the map of PCI ID's handled by kernel modules. By default, lspci uses
Applies only to Linux systems with recent enough module tools.
Invoke bus mapping mode which performs a thorough scan of all PCI devices, including
those behind misconfigured bridges, etc. This option gives meaningful results only
with a direct hardware access mode, which usually requires root privileges.
Please note that the bus mapper only scans PCI domain 0.
version. This option should be used stand-alone.
PCI access options
The PCI utilities use the PCI library to talk to PCI devices (see
pcilib(7) for details). You can use the following options to
influence its behavior:
The library supports a variety of methods to access the PCI hardware.
By default, it uses the first access method available, but you can use
this option to override this decision. See -A help for a list of
available methods and their descriptions.
The behavior of the library is controlled by several named parameters.
This option allows to set the value of any of the parameters. Use -O help
for a list of known parameters and their default values.
Use direct hardware access via Intel configuration mechanism 1.
(This is a shorthand for -A intel-conf1.)
Use direct hardware access via Intel configuration mechanism 2.
(This is a shorthand for -A intel-conf2.)
Instead of accessing real hardware, read the list of devices and values of their
configuration registers from the given file produced by an earlier run of lspci -x.
This is very useful for analysis of user-supplied bug reports, because you can display
the hardware configuration in any way you want without disturbing the user with
requests for more dumps.
Increase debug level of the library.
MACHINE READABLE OUTPUT
If you intend to process the output of lspci automatically, please use one of the
machine-readable output formats
described in this section. All other formats are likely to change
between versions of lspci.
All numbers are always printed in hexadecimal. If you want to process numeric ID's instead of
names, please add the
Simple format (-m)
In the simple format, each device is described on a single line, which is
formatted as parameters suitable for passing to a shell script, i.e., values
separated by whitespaces, quoted and escaped if necessary.
Some of the arguments are positional: slot, class, vendor name, device name,
subsystem vendor name and subsystem name (the last two are empty if
the device has no subsystem); the remaining arguments are option-like:
The relative order of positional arguments and options is undefined.
New options can be added in future versions, but they will always
have a single argument not separated from the option by any spaces,
so they can be easily ignored if not recognized.
Verbose format (-vmm)
The verbose output is a sequence of records separated by blank lines.
Each record describes a single device by a sequence of lines, each line
containing a single
are separated by a single tab character.
Neither the records nor the lines within a record are in any particular order.
Tags are case-sensitive.
The following tags are defined:
The name of the slot where the device resides
This tag is always the first in a record.
Name of the class.
Name of the vendor.
Name of the device.
Name of the subsystem vendor (optional).
Name of the subsystem (optional).
The physical slot where the device resides (optional, Linux only).
Revision number (optional).
Programming interface (optional).
Kernel driver currently handling the device (optional, Linux only).
Kernel module reporting that it is capable of handling the device
(optional, Linux only).
New tags can be added in future versions, so you should silently ignore any tags you don't recognize.
Backward-compatible verbose format (-vm)
In this mode, lspci tries to be perfectly compatible with its old versions.
It's almost the same as the regular verbose format, but the
tag is used for both the slot and the device name, so it occurs twice
in a single record. Please avoid using this format in any new code.
A list of all known PCI ID's (vendors, devices, classes and subclasses). Maintained
at http://pciids.sourceforge.net/, use the
utility to download the most recent version.
If lspci is compiled with support for compression, this file is tried before pci.ids.
All ID's found in the DNS query mode are cached in this file.
Sometimes, lspci is not able to decode the configuration registers completely.
This usually happens when not enough documentation was available to the authors.
In such cases, it at least prints the
mark to signal that there is potentially something more to say. If you know
the details, patches will be of course welcome.
Access to the extended configuration space is currently supported only by the