Answer: A PCI vendor/device pair identifies a registered controller or device family. In lspci -nn, [8086:10c9] means vendor 8086 and device 10c9. An optional subsystem pair narrows the OEM identity. Match all supplied IDs against the same pci.ids record; a name alone does not verify board revision, driver support or health.
Use hexadecimal IDs. Subsystem is a separate subvendor:subdevice pair; it never replaces the function’s vendor/device identity.
The example uses registered IDs; it is not a capture from your computer. First lookup loads about 1.7 MB of local reference text.
Read the original identity
lspci -nn
lspci -nnvv -s 01:00.0The vendor and device IDs belong to the PCI function. Read the separate Subsystem: line for an OEM pair. Linux can bind a driver even when its local naming database has no entry. To inspect the captured registers, use the PCI config decoder; for evidence and comparisons, open the Console.
Sources and snapshot
Updated . Database version 2026.10.19, saved 20 October 2026. Names come from the community-maintained PCI ID Repository, also used by pciutils. The snapshot can lag new or corrected registrations.
Questions
- Where do I find a PCI vendor and device ID?
- Run lspci -nn. A pair such as [8086:10c9] means vendor 8086 and device 10c9. Use lspci -nnvv -s 01:00.0 for the optional Subsystem pair; replace the example address with your function.
- Does a PCI ID identify the exact board or driver?
- A vendor/device pair usually identifies the controller or device family. OEM boards can share it. The optional subsystem pair can narrow the name, but the result does not establish board revision, driver compatibility, authenticity or hardware health.
- Why is my device unknown?
- This is a community-maintained snapshot, not a live hardware inventory. A new, custom or unregistered ID may be absent. Keep the raw IDs and check the hardware documentation; unknown does not mean invalid hardware.
- Are IDs sent to an external lookup service?
- No. The first lookup downloads the same public database file from Header7F for every user. Matching runs locally; vendor, device and subsystem queries are not included in requests.