Dennis HilkLinux diagnosticsDE

Bluetooth

MediaTek USB Bluetooth family (0e8d:0608)

A MediaTek USB Bluetooth route whose helper reads controller registers to choose a ROM-patch filename. It is not identified from a Wi-Fi PCI label.

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

0e8d:0608 selects the MediaTek setup path in btusb. The numeric table entry is not promoted to a unique marketed combo-card or chip revision name.

Curated identifiers
usb 0e8d:0608

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 supplies transport and btmtk performs controller-specific firmware setup. Firmware names include the detected device/version fields, so the exact request needs the initialization log.

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

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

The source constructs names from chip and firmware version fields. This is a checked pattern example; no exact filename can be established from 0e8d:0608 alone.

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

  • mediatek/BT_RAM_CODE_MT*_1_*_hdr.bin

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

The example pattern covers one 79xx naming route, not every MediaTek generation. Working Wi-Fi and a listed Bluetooth USB function do not demonstrate a ready Bluetooth controller.

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.