From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [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)
Date: Mon, 19 Oct 2026 08:45:10 +0000 [thread overview]
Message-ID: <bug-221754-62941-GxHZ9iytS2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221754-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221754
--- Comment #12 from FoxyLoon (virtualfoxyloon@gmail.com) ---
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!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-10-19 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 12:10 [Bug 221754] 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) bugzilla-daemon
2026-07-15 12:12 ` [Bug 221754] " bugzilla-daemon
2026-07-17 11:07 ` bugzilla-daemon
2026-08-02 13:01 ` bugzilla-daemon
2026-08-04 8:12 ` bugzilla-daemon
2026-08-04 11:33 ` bugzilla-daemon
2026-08-04 15:23 ` bugzilla-daemon
2026-08-04 19:35 ` bugzilla-daemon
2026-08-06 5:01 ` bugzilla-daemon
2026-08-07 16:12 ` bugzilla-daemon
2026-09-26 20:55 ` bugzilla-daemon
2026-10-06 12:45 ` bugzilla-daemon
2026-10-19 8:45 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221754-62941-GxHZ9iytS2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.