New: 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
Bug ID: 221754
Summary: RTL8852BE Bluetooth (0bda:b853) fails to init: Opcode
0xfcf0 failed: -16, hci0 never registers with mgmt (BD
Address 00:00:00:00:00:00)
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: blocking
Priority: P3
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: NoFull bug report for Realtek RTL8852BE internal Bluetooth failing to initialize on
Lenovo IdeaPad Pro 5 14AGP11 (Ubuntu 26.04, kernel 7.0.0-27-generic). Includes dmesg output, hciconfig/btmgmt/rfkill output, and a list of all troubleshooting steps already attempted (driver reload, USB rebind, firmware replacement, DKMS rebuild, manual BD address assignment) — all reproducing the identical Opcode 0xfcf0 / -EBUSY failure.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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 #1 from [email protected] ---
Created attachment 310453
--> https://bugzilla.kernel.org/attachment.cgi?id=310453&action=edit
rtl8852be-bluetooth-bug-report.md
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
Adam ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #2 from Adam ([email protected]) --- I have very same problem on Lenovo IdeaPad Slim 5 14AHP11
Disribution & kernel: Ubuntu 26.04 LTS, kernel 7.0.0-27-generic
lsusb: 0bda:b853 Realtek Semiconductor Corp. Bluetooth Radio
My filtered dmseg trace:
``` [ 3.426562] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67 [ 4.034621] amdxdna 0000:05:00.1: [drm] Load firmware amdnpu/1502_00/npu_7.sbin [ 4.058678] kvm_amd: [Firmware Bug]: Cannot enable x2AVIC, AVIC is unsupported [ 4.081452] rtw89_8852be 0000:02:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 4.089206] rtw89_8852be 0000:02:00.0: Firmware version 0.29.29.15 (6fb3ec41), cmd version 0, type 5 [ 4.089213] rtw89_8852be 0000:02:00.0: Firmware version 0.29.29.15 (6fb3ec41), cmd version 0, type 3 [ 5.716983] amdgpu 0000:04:00.0: [drm] Loading DMUB firmware via PSP: version=0x08005700 [ 5.717220] amdgpu 0000:04:00.0: [VCN instance 0] Found VCN firmware Version ENC: 1.24 DEC: 9 VEP: 0 Revision: 16 [ 5.750181] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852 [ 5.753172] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 5.756172] Bluetooth: hci0: RTL: btrtl_initialize: key id 0 [ 5.756176] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin [ 5.757225] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin [ 5.766164] Bluetooth: hci0: AOSP extensions version v0.96 [ 5.766168] Bluetooth: hci0: AOSP quality report is not supported [ 131.458300] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852 [ 131.461055] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 131.464314] Bluetooth: hci0: RTL: btrtl_initialize: key id 0 [ 131.464331] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin [ 131.465152] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin [ 131.470914] Bluetooth: hci0: Opcode 0xfcf0 failed: -16 [ 131.475291] Bluetooth: hci0: AOSP extensions version v0.96 [ 131.475307] Bluetooth: hci0: AOSP quality report is not supported ```
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
jeremy ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #3 from jeremy ([email protected]) --- (In reply to serge.brun from comment #1)
Quoted 2 lines
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
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
--- Comment #4 from [email protected] ---
(In reply to jeremy from comment #3)
Quoted 6 lines
(In reply to serge.brun from comment #1)
Quoted 2 lines
Created attachment 310453 [details]
rtl8852be-bluetooth-bug-report.mdMy 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).
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
--- Comment #5 from jeremy ([email protected]) --- Might want to try
https://github.com/mihaits/rtl8852bd-bt-linux/blob/main/README.md
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |ANSWERED--- Comment #6 from [email protected] ---
Update: this is fixed, and Adam's case is very likely the same root cause.
mihaits' repo (https://github.com/mihaits/rtl8852bd-bt-linux) nailed it. The actual problem was never the Opcode 0xfcf0 failure we were all chasing — that turned out to be a red herring. The real issue: this specific silicon cut (rom_version=3, aka "RTL8852BD") needs a firmware patch at "eco 4", and linux-firmware's rtl8852bu_fw.bin only ships eco 1/2 for this chip. It's a missing-firmware-content problem, not a driver bug — no amount of driver reloading, address reassignment, or rebuilding btusb was ever going to fix it, since the firmware needed was never there to load in the first place.
The fix extracts the eco-4 firmware from the Windows Bluetooth driver package (proprietary Realtek code, not redistributable, so each user has to pull it from their own vendor's driver download) and feeds it to a patched btrtl that knows how to apply it correctly — apparently the tricky part is that a specific memory pointer (0x801200cc) has to be set before streaming the firmware fragments, or they silently land in the wrong place and the patch never launches even though every command still reports success.
What I did:
$ git clone https://github.com/mihaits/rtl8852bd-bt-linux $ cd rtl8852bd-bt-linux $ sudo ./install.sh ~/Downloads/<lenovo-bluetooth-driver>.exe
(Bluetooth driver .exe pulled from Lenovo's support site for my exact model — support.lenovo.com > IdeaPad Pro 5 14AGP11 > Drivers & Software > Bluetooth
[https://support.lenovo.com/ca/en/downloads/DS579027])
Result:
$ hciconfig hci0
hci0: Type: Primary Bus: USB
BD Address: 14:B5:CD:7D:92:86 ACL MTU: 1021:6 SCO MTU: 255:12
UP RUNNING$ sudo hcitool -i hci0 cmd 0x04 0x01 ... fw 0x3C91950E (patched), HCI 5.4
Bluetooth is fully working now — paired and streaming audio to headphones without issue, survives a reboot.
Jeremy — really appreciate you staying engaged on this even once it became clear the fix wasn't going to be a Makefile/id_table change. Given this turned out to be a firmware-content gap rather than something fixable in btusb.c, it might be worth linking mihaits' repo from bluetooth-7.0's README for anyone who lands there first with a rom_version=3 8852BE — could save the next person a lot of the loop we all just went through.
Adam (comment #2) — worth checking dmesg | grep -i "RTL: rom_version" on your machine; if I read your comment correctly it also reports version=3, so this should fix yours too.
Thanks all & Claude — closing this out as resolved on my end.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
--- Comment #7 from Adam ([email protected]) --- (In reply to jeremy from comment #5)
Quoted 2 lines
Might want to try
https://github.com/mihaits/rtl8852bd-bt-linux/blob/main/README.md
Thank you very much. It resolved my problem.
I had to additionally enroll DKMS key into firmware's Machine Owner Key as I use Secure Boot via
``` sudo mokutil --import /var/lib/shim-signed/mok/MOK.der ```
Thanks again to both of you.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
q234rty ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #8 from q234rty ([email protected]) ---
Please do not close this bug as resolved until a fix lands in the mainline kernel :)
In fact, support for the new firmware format has already been submitted to the kernel:
https://lore.kernel.org/linux-bluetooth/[email protected]/
One can verify this by pulling in the patch and simply replacing rtl8852bu_fw.bin with the rtl8852bd_mp_chip_new.dat file extracted from the windows driver .exe, without doing any additional processing to the .dat file.
I assume realtek intends to submit the new firmware to linux-fimware.git after the support code has been merged into the kernel.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|ANSWERED |------ Comment #9 from [email protected] ---
Agreed, reopening makes sense — thanks q234rty for flagging the upstream patch, and Adam for confirming that mihaits repo works with Secure Boot too (via mokutil --import, good tip for anyone else on Secure Boot).
To be clear about what's actually been verified so far: the DKMS workaround
(https://github.com/mihaits/rtl8852bd-bt-linux) is a real, working fix at the driver level. I've confirmed it myself (comment #6) and Adam has too. But it's a third-party out-of-tree module, not a mainline fix, and per the repo's own "Upstreaming" note, it was blocked specifically on Realtek needing to publish proper firmware support which sounds like exactly what's now happening via Hilda Wu's patch.
Given that, this should stay open until:
1. The btrtl firmware-format patch lands in mainline, and
2. The actual eco-4 firmware for this chip is published in linux-firmware.git
Will keep an eye on the patch thread and report back once I can test against a kernel that includes it. In the meantime, mihaits workaround remains a solid stopgap for anyone hitting this — for the sake of clarity it's a bridge, not the destination.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
FoxyLoon ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #10 from FoxyLoon ([email protected]) ---
I'm also having this exact problem on my computer. I have a Lenovo LOQ Essential 15ARP11. This card also reports “0bda:b853” and “rom_version=3” with the same symptoms described.
However, I tried to apply the fix by following the instructions, but unfortunately, I was unable to do so. I get the error “error:
rtl8852bd_mp_chip_new.dat not found...”. I downloaded the Windows Bluetooth driver from Lenovo’s support page for my computer model and followed the instructions as stated, but I don’t know why it doesn’t include the required .dat file.
I downloaded this one specifically from my computer’s model page (it was the only one available there as well):
- Name: Bluetooth Driver (Realtek, Mediatek)
- Version: 8852BE_18.4032.0.3008,MT7920_25.20.5.20
- Date: Aug 18, 2026
I also don’t know which other driver might have this necessary .dat file, since it was mentioned that it’s not something found in just one place or specific to a single brand, but I’d rather play it safe.
So, I’ll be waiting for them to fix this kernel bug.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
--- Comment #11 from Martino P. ([email protected]) --- I can confirm the issue is still present on Fedora 44 / kernel 7.2.8
Hardware: Lenovo IdeaPad Slim 3 15IWC11, system product 83RR, BIOS U2CN21WW (2026-05-13). Bluetooth USB 0bda:b853; Wi-Fi PCI 10ec:b852, driver rtw89_8852be. Fedora 44 x86_64, kernel 7.2.8-200.fc44.x86_64; linux-firmware/realtek-firmware 20260916-1.fc44; BlueZ 5.87+1.git8750129efca8-1.fc44.
With the stock Fedora modules:
- HCI version 0x0b, HCI revision 0x000b, LMP version 0x0b, LMP subversion 0x8852.
- rom_version status=0 version=3; key id 0.
- Requests rtl_bt/rtl8852bu_fw.bin and rtl_bt/rtl8852bu_config.bin.
- hci0 DOWN, zero BD_ADDR, no management adapter, no rfkill block.
- A single privileged HCIDEVUP returns ENODATA (errno 61).
- Opcode 0xfcf0 failed: -16 appears, but "didn't find patch for chip id 3" does not.
The installed rtl8852bu_fw.bin.xz decompresses to an RTBTCore (v2) container with two patch subsections: eco 1 (67133 bytes), eco 2 (62533 bytes), no eco 4.
I checked the exact Fedora source RPM kernel-7.2.8-200.fc44.src.rpm. Its btrtl.c/h and btusb.c are byte-identical to kernel-ark tag kernel-7.2.8-0, and the Fedora patch does not seem to change these files. Static analysis shows that the v2 parser selects eco == rom_version + 1 (4 here), finds no matching content, and returns -ENODATA before firmware download. The exact stock source has no BTNIC003 parser.
The user-provided Lenovo Windows installer for my laptop model (7ns3020flz7uw5k0.exe) contains Realtek_8852BE_18.4032.0.3008/rtl8852bd_mp_chip_new.dat. The INF explicitly associates USB\VID_0BDA&PID_B853 with 8852BD. INF DriverVer:
10/10/2025,18.4032.0.3008. The .dat is 68176 bytes, magic BTNIC003.
For a temporary test, I ported only the multi-record eco4 download path from mihaits/rtl8852bd-bt-linux onto the exact Fedora btrtl source, adding pre-download container validation and a check of the final commit response. The repack uses that project's extractor. I signed the module with an enrolled akmods MOK; Secure Boot remained enabled.
Three records loaded, hci0 UP with a nonzero address, one adapter visible to btmgmt/BlueZ. Read Local Version returns status 0, HCI/LMP 0x0d, HCI revision 0x3c91, manufacturer 93, LMP subversion 0x950e (combined version 0x3C91950E). A Bluetooth mouse connects and works.
Regarding comment #10: the installer named above does contain the required .dat, although its Realtek driver version is also 18.4032.0.3008. I cannot infer the content of a different Lenovo installer from the driver version alone, and I can't provide the binary directly. You can try downloading the same driver for my model, the firmware for the device should be the same.
Regarding comment #8: I found a v8 revision of Hilda Wu's firmware-v3 series dated 2026-09-23:
https://lore.kernel.org/linux-bluetooth/[email protected]/
Mirror: https://patchew.org/linux/[email protected]/
The submission uses RTL8922D as its example. Could Realtek confirm whether this older 8852BD cut / Windows BTNIC003 file is covered, and which official firmware should be used? I have not applied or tested that series.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[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)
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=221754
--- Comment #12 from FoxyLoon ([email protected]) --- Hey Martinho P. (in response to Comment #11)
A few days after posting my previous message, I went through the discussion history on this page again and noticed a link to a drive that another user had shared for their computer model. I tried it out of curiosity, but I forgot to come back to this discussion and report what happened afterwards.
I decided to give it a try because the GitHub repository containing the fix stated that, in theory, any drive related to the hardware in question should work.
After running the script again, it successfully detected the .dat file and installed the firmware. As a result, Bluetooth is now working on my system.
However, it is only partially functional. Bluetooth can now be enabled and disabled, and I can connect devices, but establishing a stable connection can sometimes take up to five minutes or more.
For example, when I try to connect my headphones, the following happens:
- I enable Bluetooth.
- I turn on my headphones.
- A connection is established, but no audio comes through the headphones yet...
- A few seconds later, the Bluetooth connection drops, even though Bluetooth itself is still enabled.
- I try to reconnect the headphones, but the same thing happens again.
- Sometimes in this process, the headphones volume slider appears in the KDE Plasma volume control, but audio still does not play through them, and if the Bluetooth disconnects again, the slider ends up disappearing as well.
- After a few seconds, the connection drops again.
- This cycle continues until the headphones finally connect successfully and start playing audio. Once that happens, the connection remains stable and everything works as expected until I manually disconnect the headphones or shut down / suspend the computer.
However, if I manually turn off the headphones, the same bug MAY occur the next time I try to turn them on, repeating what I described above.
The behaviour is quite inconsistent. Sometimes the headphones connect immediately and work without any problems. On other occasions, I have to wait several minutes for a successful connection because the connection repeatedly drops and reconnects. The number of failed attempts also varies: for example, the connection may drop and reconnect anywhere from 2 to ~10 times before it finally works.
So, this bug appears to be partially resolved for me with the drive provided above. Bluetooth is now functional, but establishing a connection can still be unreliable, and sometimes I have to be patient and try several times before everything works properly.
I'm not entirely sure what additional information would be useful to help diagnose this bug, but I've tried to describe the behaviour as accurately as possible.
Take care!
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.