Dennis HilkLinux diagnosticsDE

Input & other peripherals

Wacom USB tablet identity 056a:00b9

The checked tablet profile separates pen capabilities from application mapping and display geometry.

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

056a:00b9 is the checked Wacom HID table pair. Upstream labels its features “Intuos4 6x9”; that source label is evidence about the table, not a user-confirmed retail model or serial identity.

Curated identifiers
usb 056a:00b9

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

wacom is a specialized HID driver over USB transport and publishes pen, buttons and related input capabilities. The input registry helps distinguish the tablet from a normal pointer; userspace still maps it to screens and applications.

  • wacom — 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 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.

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.

Limitations & related issues

The checked ID does not prove calibration, button configuration or a particular desktop’s tablet support. Do not infer working pressure in every application solely from the kernel match.

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.