Cross-posting this from Bazzite because the issue appears to be specific to the
OGC kernel / shipped btusb module:
ublue-os/bazzite#5769
Hardware / environment:
- MediaTek MT7922 Bluetooth
- USB ID:
13d3:3625
- Bazzite Stable
44.20260908
- Kernel
7.2.3-ogc3.1.fc44.x86_64
With the shipped btusb module the USB device is detected, but no usable HCI
controller is created:
btmgmt info
Index list with 0 items
I then rebuilt only drivers/bluetooth/btusb.ko from the current
OpenGamingCollective/linux ogc-7.2.y source against the exact same running
kernel.
That source contains:
{ USB_DEVICE(0x13d3, 0x3625), .driver_info = BTUSB_MEDIATEK |
BTUSB_WIDEBAND_SPEECH },
After loading the rebuilt module, hci0 initializes successfully and Bluetooth
works normally.
I packaged the rebuilt module under:
/usr/lib/modules/7.2.3-ogc3.1.fc44.x86_64/updates/btusb.ko
and verified that the fix also survives a clean reboot. An Xbox Wireless
Controller connects and works normally afterwards.
There is also an upstream change for this exact USB ID:
849a3bf1489093996859ba0c3c1c0cd314d6ff96
Bluetooth: btusb: Add USB ID 13d3:3625 for MediaTek MT7922
Could you check whether the Fedora/OGC kernel package shipped to Bazzite was
built from a revision that actually includes this quirk, or whether there is
another difference between the packaged module and the current ogc-7.2.y
source?
Full logs and reproduction details are in the Bazzite issue above.
I have the affected hardware available and can test an OGC kernel build if
useful.
Cross-posting this from Bazzite because the issue appears to be specific to the
OGC kernel / shipped
btusbmodule:ublue-os/bazzite#5769
Hardware / environment:
13d3:362544.202609087.2.3-ogc3.1.fc44.x86_64With the shipped
btusbmodule the USB device is detected, but no usable HCIcontroller is created:
btmgmt info
Index list with 0 items
I then rebuilt only drivers/bluetooth/btusb.ko from the current
OpenGamingCollective/linux ogc-7.2.y source against the exact same running
kernel.
That source contains:
{ USB_DEVICE(0x13d3, 0x3625), .driver_info = BTUSB_MEDIATEK |
BTUSB_WIDEBAND_SPEECH },
After loading the rebuilt module, hci0 initializes successfully and Bluetooth
works normally.
I packaged the rebuilt module under:
/usr/lib/modules/7.2.3-ogc3.1.fc44.x86_64/updates/btusb.ko
and verified that the fix also survives a clean reboot. An Xbox Wireless
Controller connects and works normally afterwards.
There is also an upstream change for this exact USB ID:
849a3bf1489093996859ba0c3c1c0cd314d6ff96
Bluetooth: btusb: Add USB ID 13d3:3625 for MediaTek MT7922
Could you check whether the Fedora/OGC kernel package shipped to Bazzite was
built from a revision that actually includes this quirk, or whether there is
another difference between the packaged module and the current ogc-7.2.y
source?
Full logs and reproduction details are in the Bazzite issue above.
I have the affected hardware available and can test an OGC kernel build if
useful.