This bug was fixed in the package linux - 6.14.0-15.15
---------------
linux (6.14.0-15.15) plucky; urgency=medium
* plucky/linux: 6.14.0-15.15 -proposed tracker (LP: #2106239)
* Enabling GENDWARFKSYMS breaks loading modules (LP: #2103771)
- [Packaging] Bump pahole build-dep
* BMG: support additional PCI ID (LP: #2105768)
- SAUCE: drm/xe/bmg: Add one additional PCI ID
* Missing bpftool binary on riscv64 (LP: #2106091)
- [Packaging] Build bpftool and linux-perf on riscv64
- [Packaging] Allow binary-debs target without enabling
do_flavour_image_package
- [Packaging] Fix bpftool, linux-perf packaging in binary-perarch
-- Paolo Pisati <paolo.pis...@canonical.com> Sun, 06 Apr 2025 14:36:36
+0200
** Changed in: linux (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2094969
Title:
bluetooth/detect-output failed due to the lack of USB device id in
btusb.c
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-oem-6.11 source package in Plucky:
Invalid
Bug description:
[Impact]
BT hardware is not available on certain machines:
1. Machine with MT7925 BT (USB VID/PID 13d3/3628)
2. Machine with MT7925 BT (USB VID/PID 0489/e14e)
[Fix]
Add USB device IDs into device table in btusb.c fixes the issue.
1. For VID/PID 13d3/3628, the patch has already been merged into
linux-next:
f597b8982d51 Bluetooth: btusb: Add new VID/PID 13d3/3628 for MT7925
2. For VID/PID 0489/e14e, the patch is still under review. Out of the
urgency, we're going to make a SAUCE patch first.
[Test Plan]
1. Install Ubuntu image and boot into the OS
2. Run $ sudo checkbox-cli run
com.canonical.certification::bluetooth/detect-output and see if the test is
passed
[Where problems could occur]
The two BT hardware may have not yet been matured, so there might be issues
in the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2094969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
