Hi Chris, On Wed, Oct 16, 2024 at 2:51 PM Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > > Hi Grimoire, > > On Wed, Oct 16, 2024 at 3:28 AM Grimoire April <aprilgrimoire@xxxxxxxxx> wrote: > > > > Hi. I have a laptop with an integrated bluetooth adaptor recognized as > > a usb device. However, it fails to initialize properly. Searching for > > other instances on bugzilla, it seems others had success with > > 13d3:3585 adaptors. > > > > (base) ➜ ~ sudo dmesg | grep Bluetooth > > [ 0.422244] Bluetooth: Core ver 2.22 > > [ 0.422254] Bluetooth: HCI device and connection manager initialized > > [ 0.422257] Bluetooth: HCI socket layer initialized > > [ 0.422261] Bluetooth: L2CAP socket layer initialized > > [ 0.422265] Bluetooth: SCO socket layer initialized > > [ 0.530052] Bluetooth: HCI UART driver ver 2.3 > > [ 0.535346] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 > > [ 0.535355] Bluetooth: HIDP socket layer initialized > > [ 3.556068] Bluetooth: hci0: Opcode 0x0c03 failed: -110 > > > > https://bugzilla.kernel.org/show_bug.cgi?id=218472 > > > > I updated to 6.11.1 and the issue persists. > > Well it looks like the reset command is timing out, but the issue was > originally the PID:VID was not supported in btusb so perhaps something > else is happening, perhaps another manufacturer that don't support > short-transfer which was introduced by 7b05933340f4 ("Bluetooth: > btusb: Fix not handling ZPL/short-transfer") so try reverting that to > see if it helps. Seems this appears to be a Mediatek chip are you guys able to verify the above change doesn't break with your controllers? > > > Thank you. > > > > > -- > Luiz Augusto von Dentz -- Luiz Augusto von Dentz
