Dennis HilkLinux diagnosticsDE

Input & other peripherals

Xbox 360 wired USB identity 045e:028e

A wired Xbox-compatible controller identity with a vendor-specific USB protocol rather than generic keyboard HID.

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

045e:028e is in the checked xpad device-information table with an Xbox 360 controller type. This describes the source identity, not verified authenticity or support for unrelated wireless receivers and Xbox One protocols.

Curated identifiers
usb 045e:028e

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

xpad’s USB binding table matches vendor/interface protocol combinations, then the device-information table selects type and mappings. The exact PID is therefore family evidence, while the actual interface and input binding still need observation.

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

Limitations & related issues

A kernel match does not configure a game’s controller selection, axes or force feedback. The diagnostic listings do not transmit rumble commands or demonstrate application compatibility.

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.