.TH lspci 8 "@TODAY@" "@VERSION@" "The PCI Utilities".IX lspci.SH NAMElspci \- list all PCI devices.SH SYNOPSIS.B lspci.RB [ options ].SH DESCRIPTION.B lspciis a utility for displaying information about all PCI buses in the system andall devices connected to them.By default, it shows a brief list of devices. Use the options describedbelow to request either a more verbose output or output intended forparsing by other programs.If you are going to report bugs in PCI device drivers or in.I lspciitself, 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, is probablyintelligible only to experienced PCI hackers. For the exact definitions ofthe fields, please consult either the PCI specifications or the.B header.hand.B /usr/include/linux/pci.hinclude files.Access to some parts of the PCI configuration space is restricted to rooton many operating systems, so the features of.I lspciavailable to normal users are limited. However,.I lspcitries its best to display as much as available and mark all otherinformation with.I <access denied>text..SH OPTIONS.TP.B -vBe verbose and display detailed information about all devices..TP.B -vvBe very verbose and display more details. This level includes everything deemeduseful..TP.B -vvvBe 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)..TP.B -nShow PCI vendor and device codes as numbers instead of looking them up in thePCI ID list..TP.B -nnShow PCI vendor and device codes as both numbers and names..TP.B -xShow hexadecimal dump of the standard part of the configuration space (the first64 bytes or 128 bytes for CardBus bridges)..TP.B -xxxShow hexadecimal dump of the whole PCI configuration space. It is available only to rootas several PCI devices.B crashwhen you try to read some parts of the config space (this behavior probablydoesn't violate the PCI standard, but it's at least very stupid). However, suchdevices are rare, so you needn't worry much..TP.B -xxxxShow hexadecimal dump of the extended (4096-byte) PCI configuration space availableon PCI-X 2.0 and PCI Express buses..TP.B -bBus-centric view. Show all IRQ numbers and addresses as seen by the cards on thePCI bus instead of as seen by the kernel..TP.B -tShow a tree-like diagram containing all buses, bridges, devices and connectionsbetween them..TP.B -s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]]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 domainof 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 arehexadecimal.  E.g., "0:" means all devices on bus 0, "0" means all functions of device 0on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows onlythe fourth function of each device..TP.B -d [<vendor>]:[<device>]Show only devices with specified vendor and device ID. Both ID's are given inhexadecimal and may be omitted or given as "*", both meaning "any value"..TP.B -i <file>Use.B<file>as the PCI ID list instead of @IDSDIR@/pci.ids..TP.B -mDump PCI device data in a backward-compatible machine readable form.See below for details..TP.B -mmDump PCI device data in a machine readable form for easy parsing by scripts.See below for details..TP.B -DAlways show PCI domain numbers. By default, lspci suppresses them on machines whichhave only domain 0..TP.B -MInvoke bus mapping mode which performs a thorough scan of all PCI devices, includingthose behind misconfigured bridges etc. This option is available only to root and itgives meaningful results only if combined with direct hardware access mode (otherwisethe results are identical to normal listing modes, modulo bugs in lspci). Please notethat the bus mapper doesn't support PCI domains and scans only domain 0..TP.B --versionShows.I lspciversion. This option should be used stand-alone..SH PCILIB AND ITS OPTIONSThe PCI utilities use PCILIB (a portable library providing platform-independentfunctions for PCI configuration space access) to talk to the PCI cards. It supportsthe following access methods:.TP.B linux_sysfsThe.B /sysfilesystem on Linux 2.6 and newer. The standard header of the config space is availableto all users, the rest only to root. Supports extended configuration space and PCI domains..TP.B linux_procThe.B /proc/bus/pciinterface supported by Linux 2.1 and newer. The standard header of the config space is availableto all users, the rest only to root..TP.B intel_conf1Direct hardware access via Intel configuration mechanism 1. Available on i386 and compatibleson Linux, Solaris/x86, GNU Hurd and Windows. Requires root privileges..TP.B intel_conf2Direct hardware access via Intel configuration mechanism 2. Available on i386 and compatibleson Linux, Solaris/x86 and GNU Hurd. Requires root privileges. Warning: This methodis able to address only first 16 devices on any bus and it seems to be veryunreliable in many cases..TP.B fbsd_deviceThe.B /dev/pcidevice on FreeBSD. Requires root privileges..TP.B obsd_deviceThe.B /dev/pcidevice on OpenBSD. Requires root privileges..TP.B nbsd_libpciThe.B /dev/pci0device on NetBSD accessed using the local libpci library..TP.B aix_deviceAccess method used on AIX. Requires root privileges..PBy default, PCILIB uses the first available access method and displays no debuggingmessages, but you can use the following switches to control its behavior:.TP.B -P <dir>Force use of the linux_proc access method, using.B <dir>instead of /proc/bus/pci..TP.B -H1Use direct hardware access via Intel configuration mechanism 1..TP.B -H2Use direct hardware access via Intel configuration mechanism 2..TP.B -F <file>Extract all information from given file containing output of lspci -x. This is veryuseful for analysis of user-supplied bug reports, because you can display thehardware configuration in any way you want without disturbing the user withrequests for more dumps..TP.B -GIncrease debug level of the library..SH MACHINE READABLE OUTPUTIf you intend to process the output of lspci automatically, please use one of themachine-readable output formats.RB ( -m ,.BR -vm ,.BR -vmm )described in this section. All other formats are likely to changebetween versions of lspci..PAll numbers are always printed in hexadecimal. If you want to process numeric ID's instead ofnames, please add the.B -nswitch..SS Simple format (-m)In the simple format, each device is described on a single line, which isformatted as parameters suitable for passing to a shell script, i.e., valuesseparated 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 ifthe device has no subsystem); the remaining arguments are option-like:.TP.BI -r revRevision number..TP.BI -p progifProgramming interface..PThe relative order of positional arguments and options is undefined.New options can be added in future versions, but they will alwayshave a single argument not separated from the option by any spaces,so they can be easily ignored if not recognized..SS 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 linecontaining a single.RI ` tag :.IR value 'pair. The.I tagand the.I valueare separated by a single tab character.Neither the records nor the lines within a record are in any particular order.Tags are case-sensitive..PThe following tags are defined:.TP.B SlotThe name of the slot where the device resides.RI ([ domain :] bus : device . function ).This tag is always the first in a record..TP.B ClassName of the class..TP.B VendorName of the vendor..TP.B DeviceName of the device..TP.B SVendorName of the subsystem vendor (optional)..TP.B SDeviceName of the subsystem (optional)..TP.B RevRevision number (optional)..TP.B ProgIfProgramming interface (optional)..PNew tags can be added in future versions, so you should silently ignore any tags you don't recognize..SS 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.BDevicetag is used for both the slot and the device name, so it occurs twicein a single record. Please avoid using this format in any new code..SH FILES.TP.B @IDSDIR@/pci.idsA list of all known PCI ID's (vendors, devices, classes and subclasses). Maintainedat http://pciids.sourceforge.net/, use the.B update-pciidsutility to download the most recent version..TP.B @IDSDIR@/pci.ids.gzIf lspci is compiled with support for compression, this file is tried before pci.ids..TP.B /proc/bus/pciAn interface to PCI bus configuration space provided by the post-2.1.82 Linuxkernels. Contains per-bus subdirectories with per-card config space files and a.I devicesfile containing a list of all PCI devices..SH BUGSSometimes, 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.B <?>mark to signal that there is potentially something more to say. If you knowthe details, patches will be of course welcome.Access to the extended configuration space is currently supported only by the.B linux_sysfsback-end..SH SEE ALSO.BR setpci (8),.BR update-pciids (8).SH AUTHORThe PCI Utilities are maintained by Martin Mares <mj@ucw.cz>.