Overview & identity
The checked modern PCI rule maps 1af4:1052 to virtio type 18 (input). This is a virtual function identity, not the host hardware model. Transitional PCI IDs use a different subsystem-ID rule and are deliberately not inferred here.
- Curated identifiers
pci 1af4:1052
A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.
Driver & binding
virtio_input matches type 18 and constructs input capabilities from the device configuration. The same guest protocol can expose keyboard, pointer or absolute-coordinate input; the PCI pair does not choose one retail device. lspci can therefore correctly report virtio-pci while the child function is bound to virtio_input.
virtio_pci— kernel driver/module candidatevirtio_input— kernel driver/module candidate
Firmware
No host payload established here
No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.
Read-only diagnostics
Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.
Inspect the PCI function and binding
lspci -nnk -s BDFReplace BDF with the complete address, for example 0000:00:14.0. This read-only query needs pciutils and normally no sudo. “Kernel driver in use” is observed binding; “Kernel modules” lists candidates.
Inspect the virtio child function driver
ls -l /sys/bus/pci/devices/BDF/virtio*/driverReplace BDF with the full observed PCI address. Read the child driver link without sudo; virtio_pci is the PCI transport, while this link belongs to the function driver. A missing child or link means that this layer was not observed.
Inspect input handlers and capabilities
cat /proc/bus/input/devicesThis reads the input registry without sudo and does not capture keystrokes. Names, handlers and bus information help associate event nodes with hardware; a device entry alone does not prove desktop routing or correct calibration.
Limitations & related issues
A function match cannot prove key layout, screen coordinate mapping or host focus routing. The input registry is metadata; no keystrokes are captured as part of these checks.
These guides are linked for relevant observations, not as known defects of every device in this family.
Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab
References
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: drivers/virtio/virtio_pci_common.c
Reviewed upstream source
virtio_pci_id_table[] - Linux: drivers/virtio/virtio_pci_modern_dev.c
Reviewed upstream source
mdev->id.device = pci_dev->device - 0x1040; - Linux: include/uapi/linux/virtio_ids.h
Reviewed upstream source
#define VIRTIO_ID_INPUT - Linux: drivers/virtio/virtio_input.c
Reviewed upstream source
{ VIRTIO_ID_INPUT, - Linux: Documentation/driver-api/virtio/virtio.rst
Project or distribution documentation
Device discovery and probing