[Bug 221754] RTL8852BE Bluetooth (0bda:b853) fails to init: Opcode 0xfcf0 failed: -16, hci0 never registers with mgmt (BD Address 00:00:00:00:00:00)

https://bugzilla.kernel.org/show_bug.cgi?id=221754

--- Comment #4 from [email protected] ---
(In reply to jeremy from comment #3)
> (In reply to serge.brun from comment #1)
> > Created attachment 310453 [details]
> > rtl8852be-bluetooth-bug-report.md
> 
> My Bluetooth-7.0 repo only recently included the ID of your bluetooth
> device, you may want to try it again


Thanks for getting back. I saw the newer commit (61e58e8) adds an explicit
id_table entry for 0x0bda:0xb853 with BTUSB_WIDEBAND_SPEECH. 
Pulled it, rebuilt via DKMS, confirmed the rebuilt module loaded (checked via
modinfo), and reloaded.

Result:

$ sudo dmesg | grep -i hci0 | tail -15
[    4.309610] Bluetooth: hci0: RTL: rom_version status=0 version=3
[    4.311125] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[    4.311129] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[    4.311965] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[    4.315931] Bluetooth: hci0: Opcode 0xfcf0 failed: -16
[    4.317327] Bluetooth: hci0: AOSP extensions version v0.96
[    4.317331] Bluetooth: hci0: AOSP quality report is not supported
[ 1524.160747] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b
lmp_ver=0b lmp_subver=8852
[ 1524.162741] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 1524.164738] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ 1524.164744] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[ 1524.165315] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[ 1524.168747] Bluetooth: hci0: Opcode 0xfcf0 failed: -16
[ 1524.170741] Bluetooth: hci0: AOSP extensions version v0.96
[ 1524.170745] Bluetooth: hci0: AOSP quality report is not supported

$ sudo btmgmt info
Index list with 0 items

In case it's useful: my device was already binding to the stock in-kernel btusb
driver before testing any of your patches (the original bug report shows the
same RTL: examining/loading sequence without this repo installed at all), so
0x0bda:0xb853 seems to already be present in mainline's id_table. 
That would mean BTUSB_WIDEBAND_SPEECH is the main functional change here, and
since that quirk affects SCO/audio codec negotiation rather than the initial
power-on handshake, it may not be positioned to affect the Opcode 0xfcf0
failure specifically. Could be wrong about that though. 
Let me know if you want me to check anything else (e.g. instrument btrtl.c
around the vendor command send/response for opcode 0xfcf0, or test a specific
rom_version=3 code path).

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.