Hello everyone,
I cannot get Bluetooth to even show up on Gigabyte X870E Aorus Elite Wifi 7 rev. 1.0 with MediaTek MT7925. I am no Linux guru, so was using Claude AI for most of the troubleshooting. These are the findings:
Symptom:
WiFi works perfectly (mt7925e driver loads, interface comes up fine). Bluetooth is completely absent — no adapter shown in any Bluetooth settings UI, and no Bluetooth entry in rfkill list at all (only WLAN is listed).
Confirmed working on Windows with the same hardware, same board, no changes — so this rules out any physical/hardware fault or BIOS-disabled radio.
Troubleshooting done so far:
lsusb shows the Gigabyte-side ITE USB hub (048d:5711) that the Bluetooth device should sit behind, but nothing enumerates downstream of it — no MediaTek/Foxconn (0489:xxxx) device appears anywhere on the bus.
dmesg only ever shows mt7925e (WiFi/PCIe) loading; zero mentions of btusb, btmtk, or hci0.
btusb module loads fine manually (modprobe btusb), and its driver table already has a generic wildcard match for MediaTek/Foxconn vendor ID 0489, so this isn't a missing-driver-ID problem — the device simply never appears on the bus for any driver to claim.
Manually registering the known MT7925 Bluetooth product ID (0489:e124, seen on the same chipset on other boards) via new_id had nothing to attach to, confirming the device isn't enumerating at all.
Already on kernel 7.0 (very recent), so this doesn't look like a "need a newer kernel" issue.
Conclusion (AI):
This looks like a board-specific power-on/init sequencing issue for the Bluetooth half of the MT7925 module — the WiFi PCIe function initializes fine, but whatever triggers the internal USB hub to power up and expose the Bluetooth function isn't happening under Linux. A Linuxlookup review of this exact board at launch flagged the same "MT7925 Bluetooth not detected" issue. I've found similar reports for other Gigabyte AM5 boards with this chip family, and while some sibling boards (Z790 AORUS MASTER X, Aorus Master X3D) have gotten specific USB-ID patches merged for their MT7927 variant, I haven't found one yet for this board's exact module.
Has anyone with this board (or a similar Gigabyte X870/X870E board with the MT7925) gotten Bluetooth working under Linux?
The BIOS is latest to the date, secure boot and fast boot are disabled.
I was checking out the solution in the link above, but the guy had BT at least showing up in rfkill, I can only see one wireless LAN adapter in its output.
I tried that script on Github - printed that "No matching HWDB entries found". With AI, I tried this:
#Check every USB device's vendor ID directly from sysfs
#(more reliable than lsusb, bypasses any USB ID database naming issues):
for d in /sys/bus/usb/devices/*/idVendor; do
dev=$(dirname "$d")
vendor=$(cat "$d" 2>/dev/null)
product=$(cat "$dev/idProduct" 2>/dev/null)
echo "$dev -> $vendor:$product"
done
I checked the forum post from linuxmint and one thing worked - I made a full poweroff, removed power cable, drained the capacitors by pushing the power button, powered it on - and I can see Bluetooth present in system UI as well as terminal. What the hell?
lsusb | grep -i 0489
Bus 001 Device 002: ID 0489:e124 Foxconn / Hon Hai Wireless_Device
rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
bluetoothctl show
Controller 44:FA:66:65:66:6E (public)
Manufacturer: 0x0046 (70)
Version: 0x0d (13)
Name: --------
Alias: --------
Class: 0x007c0104 (8126724)
Powered: yes
Discoverable: yes
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0548
Discovering: yes
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x10 (16)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded