All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221837] Bluetooth (RTL8852BU, 0bda:b853) never initializes.  Opcode 0xfcf0
Date: Thu, 06 Aug 2026 09:27:24 +0000	[thread overview]
Message-ID: <bug-221837-62941-Zk2rkAmsJt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221837-62941@https.bugzilla.kernel.org/>

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

--- Comment #2 from Rohan (rohanasrani3@gmail.com) ---
Sorry, I forgot to mention that I originally faced this issue in kernel
7.0.0-28 with the the latest firmware. I then tried to jump onto different old
kernel versions to see if that might fix the issue. No help. I'm not sure if
Mint supports 7.1.6 yet as I cannot see it in Update Manager. I get the same
dmesg on the new updated kernel as well:
```
[    1.457364] usb 1-5: Product: Bluetooth Radio
[    2.820216] Bluetooth: Core ver 2.22
[    2.834484] NET: Registered PF_BLUETOOTH protocol family
[    2.834492] Bluetooth: HCI device and connection manager initialized
[    2.834506] Bluetooth: HCI socket layer initialized
[    2.834511] Bluetooth: L2CAP socket layer initialized
[    2.834525] Bluetooth: SCO socket layer initialized
[    2.943691] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b
lmp_ver=0b lmp_subver=8852
[    2.946667] Bluetooth: hci0: RTL: rom_version status=0 version=3
[    2.949812] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[    2.949823] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[    2.950664] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[    2.959682] Bluetooth: hci0: AOSP extensions version v0.96
[    2.959687] Bluetooth: hci0: AOSP quality report is not supported
[    4.661628] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.661634] Bluetooth: BNEP filters: protocol multicast
[    4.661639] Bluetooth: BNEP socket layer initialized
```
Is there anything else I can do?

-- 
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-06  9:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 17:02 [Bug 221837] New: Bluetooth (RTL8852BU, 0bda:b853) never initializes. Opcode 0xfcf0 bugzilla-daemon
2026-08-06  9:15 ` [Bug 221837] " bugzilla-daemon
2026-08-06  9:27 ` bugzilla-daemon [this message]
2026-08-07 10:39 ` bugzilla-daemon
2026-08-07 12:49 ` bugzilla-daemon
2026-08-08 18:10 ` bugzilla-daemon
2026-08-09  8:27 ` bugzilla-daemon
2026-08-12  7:58 ` bugzilla-daemon
2026-08-12  8:04 ` bugzilla-daemon
2026-08-12  8:10 ` bugzilla-daemon
2026-08-12 10:20 ` bugzilla-daemon
2026-08-31 11:37 ` bugzilla-daemon

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-221837-62941-Zk2rkAmsJt@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.