PCI aliases carry more than a vendor/device pair
A concrete PCI modalias includes vendor, device, subsystem and class fields. Subsystem qualifiers can matter for a particular board or platform. The Explorer keeps missing qualifiers uncertain and rejects contradictory ones. A source-table match is still conditional on the installed kernel and probe outcome.
cat /sys/bus/pci/devices/BDF/modaliasUSB interface context can matter
USB aliases distinguish the device descriptor from interface class, subclass and protocol. Composite hardware can bind one driver per interface. Matching only the first two hexadecimal numbers can overstate support for a different interface or revision. A generic class profile provides context and never becomes an exact marketed-model identification.
Module alias patterns are not device observations
modinfo aliases often contain wildcards describing a range of matches. They do not state that a particular device is present. Paste the concrete device modalias or a numeric lspci/lsusb report instead. This browser tool uses curated, inspectable rules and cannot reproduce every matching constraint of an arbitrary kernel module.
modinfo -F alias MODULEReferences
Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.
- Linux driver binding
Project or distribution documentation
- PCI resources through sysfs
Project or distribution documentation
- Linux USB driver API
Project or distribution documentation