Public bug reported: SUMMARY The Bluetooth controller on my MediaTek MT7925 WiFi/BT combo card fails to initialise. The adapter is detected at the USB/kernel level but never completes firmware setup, so it never gets a MAC address and cannot be brought up. WiFi on the same combo card works normally — this is Bluetooth-specific. hciconfig hci0 always shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 bluetoothctl reports: "No default controller available" HARDWARE / SYSTEM - Motherboard/CPU: AMD Ryzen 9950X desktop - GPU: AMD Radeon RX 9070 XT - Bluetooth/WiFi adapter: MediaTek MT7925 combo card, USB (OEM USB ID 13d3:3602, IMC Networks) - BIOS: version 0227, dated 23/07/2024 (unchanged throughout testing) - Ubuntu release: 26.04 ("resolute") - Kernels tested: 7.0.0-28-generic and 7.0.0-29-generic (both installed via linux-generic-hwe-26.04, 27-generic was removed 2026-08-04 when 29 was installed) DMESG OUTPUT (identical signature on every failed attempt, across both kernels and both firmware versions tested) Bluetooth: Core ver 2.22 NET: Registered PF_BLUETOOTH protocol family Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized usbcore: registered new interface driver btusb Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20260106153314 mt7925e 0000:09:00.0: HW/SW Version: 0x8a108a10, Build Time: 20260106153007a mt7925e 0000:09:00.0: WM Firmware Version: ____000000, Build Time: 20260106153120 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: hci0: Execution of wmt command timed out Bluetooth: hci0: Failed to send wmt patch dwnld (-110) Bluetooth: hci0: Failed to set up firmware (-110) Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. (Also observed on a separate attempt after a manual USB unbind/rebind: Bluetooth: hci0: Failed to get device id (-110)) STEPS ALREADY TRIED (all failed to resolve, same error every time) 1. Booted and tested on both installed kernels: 7.0.0-28-generic and 7.0.0-29-generic. Identical failure on both. 2. Downgraded linux-firmware-mediatek from 20260319.git217ca6e4-0ubuntu1.2 (BT firmware build 2026-06-05) to 20260319.git217ca6e4-0ubuntu1 (BT firmware build 2026-01-06). Confirmed via dmesg Build Time strings and on-disk file timestamps that the older firmware genuinely loaded. Identical failure on both firmware versions. 3. Reloaded btusb module alone, and btusb + mt7925e together (modprobe -r / modprobe). No change. 4. Forced a hard USB device reset via /sys/bus/usb/devices/<path>/authorized (0 then 1). No change. 5. Disabled USB autosuspend for btusb via /etc/modprobe.d/btusb.conf ("options btusb enable_autosuspend=N"), rebuilt initramfs for all kernels, rebooted. No change. 6. Multiple consecutive plain reboots with no config changes, to rule out a timing/race condition. Failure is fully deterministic, not intermittent. 7. Confirmed BIOS version/date unchanged throughout testing, ruling out a firmware-level system change. 8. Checked for local interference: no custom udev rules for bluetooth/mtk/mediatek, bluetooth.service is completely stock/ unmodified, no systemd unit overrides. Only the autosuspend conf added during testing (step 5) is present, and removing it makes no difference. Note: this had previously been working; the exact date it stopped is unclear, but it coincides roughly with a kernel upgrade from 27→28→29 and/or a linux-firmware-mediatek point release, though testing shows neither variable alone explains the failure (see above — every kernel/firmware combination tested fails identically). ADDITIONAL INFO REQUESTED BY OTHERS INVESTIGATING SIMILAR ISSUES lsusb -v output for 13d3:3602: [attach separately, see below] WORKAROUND IN USE NONE ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 13 20:12:27 2026 InstallationDate: Installed on 2026-07-13 (32 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp9s0Link: Not connected. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=3a461c9a-9a90-4a3c-9f9f-3905092280d0 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2024 dmi.bios.release: 2.27 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0227 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0227:bd07/23/2024:br2.27:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "lsusb output" https://bugs.launchpad.net/bugs/2163428/+attachment/5991785/+files/sudo%20lsusb%20v%20d%2013d3%203602.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163428 Title: Bluetooth (MT7925, btusb) fails to initialise: "Execution of wmt command timed out" / "Failed to set up firmware (-110)" — reproducible across kernels 28/29 and two firmware versions Status in linux package in Ubuntu: New Bug description: SUMMARY The Bluetooth controller on my MediaTek MT7925 WiFi/BT combo card fails to initialise. The adapter is detected at the USB/kernel level but never completes firmware setup, so it never gets a MAC address and cannot be brought up. WiFi on the same combo card works normally — this is Bluetooth-specific. hciconfig hci0 always shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 bluetoothctl reports: "No default controller available" HARDWARE / SYSTEM - Motherboard/CPU: AMD Ryzen 9950X desktop - GPU: AMD Radeon RX 9070 XT - Bluetooth/WiFi adapter: MediaTek MT7925 combo card, USB (OEM USB ID 13d3:3602, IMC Networks) - BIOS: version 0227, dated 23/07/2024 (unchanged throughout testing) - Ubuntu release: 26.04 ("resolute") - Kernels tested: 7.0.0-28-generic and 7.0.0-29-generic (both installed via linux-generic-hwe-26.04, 27-generic was removed 2026-08-04 when 29 was installed) DMESG OUTPUT (identical signature on every failed attempt, across both kernels and both firmware versions tested) Bluetooth: Core ver 2.22 NET: Registered PF_BLUETOOTH protocol family Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized usbcore: registered new interface driver btusb Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20260106153314 mt7925e 0000:09:00.0: HW/SW Version: 0x8a108a10, Build Time: 20260106153007a mt7925e 0000:09:00.0: WM Firmware Version: ____000000, Build Time: 20260106153120 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: hci0: Execution of wmt command timed out Bluetooth: hci0: Failed to send wmt patch dwnld (-110) Bluetooth: hci0: Failed to set up firmware (-110) Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. (Also observed on a separate attempt after a manual USB unbind/rebind: Bluetooth: hci0: Failed to get device id (-110)) STEPS ALREADY TRIED (all failed to resolve, same error every time) 1. Booted and tested on both installed kernels: 7.0.0-28-generic and 7.0.0-29-generic. Identical failure on both. 2. Downgraded linux-firmware-mediatek from 20260319.git217ca6e4-0ubuntu1.2 (BT firmware build 2026-06-05) to 20260319.git217ca6e4-0ubuntu1 (BT firmware build 2026-01-06). Confirmed via dmesg Build Time strings and on-disk file timestamps that the older firmware genuinely loaded. Identical failure on both firmware versions. 3. Reloaded btusb module alone, and btusb + mt7925e together (modprobe -r / modprobe). No change. 4. Forced a hard USB device reset via /sys/bus/usb/devices/<path>/authorized (0 then 1). No change. 5. Disabled USB autosuspend for btusb via /etc/modprobe.d/btusb.conf ("options btusb enable_autosuspend=N"), rebuilt initramfs for all kernels, rebooted. No change. 6. Multiple consecutive plain reboots with no config changes, to rule out a timing/race condition. Failure is fully deterministic, not intermittent. 7. Confirmed BIOS version/date unchanged throughout testing, ruling out a firmware-level system change. 8. Checked for local interference: no custom udev rules for bluetooth/mtk/mediatek, bluetooth.service is completely stock/ unmodified, no systemd unit overrides. Only the autosuspend conf added during testing (step 5) is present, and removing it makes no difference. Note: this had previously been working; the exact date it stopped is unclear, but it coincides roughly with a kernel upgrade from 27→28→29 and/or a linux-firmware-mediatek point release, though testing shows neither variable alone explains the failure (see above — every kernel/firmware combination tested fails identically). ADDITIONAL INFO REQUESTED BY OTHERS INVESTIGATING SIMILAR ISSUES lsusb -v output for 13d3:3602: [attach separately, see below] WORKAROUND IN USE NONE ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 13 20:12:27 2026 InstallationDate: Installed on 2026-07-13 (32 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp9s0Link: Not connected. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=3a461c9a-9a90-4a3c-9f9f-3905092280d0 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2024 dmi.bios.release: 2.27 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0227 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0227:bd07/23/2024:br2.27:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163428/+subscriptions
Комментариев нет:
Отправить комментарий