Dennis HilkLinux diagnosticsDE

Bluetooth

USB Bluetooth HCI transport class

A generic USB interface context for Bluetooth HCI. It can explain why btusb is a candidate without pretending to identify a chipset.

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

The source class match is e0/01/01: Wireless Controller, RF Controller, Bluetooth programming interface. This is a class profile, not an exact vendor/device match.

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

btusb provides USB transport. Vendor-specific helpers may add firmware or quirks after the class match; the transport name alone does not identify Intel, Realtek or another vendor.

  • btusb — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

No chipset or firmware file can be chosen from the HCI class alone. Read the vendor path and controller initialization log.

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.

Read the controller parent path

readlink -f /sys/class/bluetooth/CONTROLLER/device

Replace CONTROLLER with the local hci name, such as hci0, found in /sys/class/bluetooth. The path helps distinguish USB, serial and SDIO parents. It does not prove which UART protocol is active. No root privileges are needed.

Read controllers visible to BlueZ

bluetoothctl list

This asks the BlueZ daemon for known controllers without discovery or pairing. An empty response can mean daemon or D-Bus access problems as well as absent controllers; compare kernel enumeration. Normally no root privileges are needed.

Read controller initialization

journalctl -k -b --no-pager

Read the current boot’s kernel messages for the controller, requested firmware and setup result. Journal visibility depends on local permissions; an unreadable log is not evidence of no errors. This command does not change the device.

Limitations & related issues

USB transport binding, an hci controller, BlueZ visibility and an audio profile are four separate observations. Not every Bluetooth interface uses this standard class descriptor.

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.