Dennis HilkLinux diagnosticsDE

Input & other peripherals

USB HID keyboard and pointer transport

USB HID is a transport and report-description family shared by many input devices.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

USB interface class 03 points to HID, not an exact keyboard or mouse. Composite devices can expose several HID interfaces or use a specialized HID driver for one function.

This is an explicit class, transport or driver-context profile. It is not an exact numeric product match.

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

usbhid binds the USB interface and hands reports to the HID bus, where hid_generic or a device-specific driver interprets them. Those two bindings can both be correct; an input event handler is a further layer.

  • usbhid — kernel driver/module candidate
  • hid_generic — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.

Inspect firmware packaging on your distribution

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 interfaces and negotiated speed

lsusb -t

This read-only usbutils query normally needs no sudo. Driver belongs to the displayed interface, while speed is the negotiated connection. Other interfaces of the same physical device may use other drivers.

Inspect HID-layer bindings

ls -l /sys/bus/hid/devices/*/driver

Read HID driver symlinks without sudo. Correlate the HID path with its parent USB/I2C device before assigning a driver; a generic HID driver and a transport driver describe different layers.

Inspect input handlers and capabilities

cat /proc/bus/input/devices

This 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

HID class matching does not establish layout, media-key mapping or application behavior. Avoid recording raw keyboard events when a registry and driver link already answer the identity question.

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.