All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 07 Aug 2026 16:12:36 +0000	[thread overview]
Message-ID: <bug-221754-62941-F16xdqrXVJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221754-62941@https.bugzilla.kernel.org/>

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

serge.brun@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|ANSWERED                    |---

--- Comment #9 from serge.brun@gmail.com ---
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.

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

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

      parent reply	other threads:[~2026-08-07 16:12 UTC|newest]

Thread overview: 10+ 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 [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-F16xdqrXVJ@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.