Dennis HilkLinux diagnosticsDE

Bluetooth

Intel USB Bluetooth family (8087:0032)

An Intel USB controller route using the combined Intel setup path. Its firmware naming depends on controller version fields, not only its USB product number.

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

8087:0032 is explicitly marked BTUSB_INTEL_COMBINED. The source table does not give this pair a unique marketed Wi-Fi card name.

Curated identifiers
usb 8087:0032

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 handles USB transport and btintel handles Intel initialization. Setup reads controller/bootloader information before choosing SFI firmware and DDC configuration.

  • btusb — kernel driver/module candidate
  • btintel — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

These source-backed filename families cover controller-specific firmware and configuration. Whether setup downloads them and which exact names apply must come from this controller’s log.

Checked examples or filename branches, not a complete installation list:

  • intel/ibt-*.sfi
  • intel/ibt-*.ddc

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 USB transport binding

lsusb -t

Find the controller’s port and interface in the USB tree. Driver=btusb is transport binding, not proof that firmware setup or audio profiles succeeded. This query normally needs no root privileges.

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

A corresponding Wi-Fi device need not be visible on the same bus. The generic ibt patterns cannot resolve a specific SFI/DDC pair without controller version information.

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.