From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Salvatore Bonaccorso <carnil@debian.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Erik Brangs <erik.brangs@gmx.de>,
benh@debian.org, stable@vger.kernel.org,
regressions@lists.linux.dev, linux-bluetooth@vger.kernel.org,
1149377@bugs.debian.org, Christoph Zwerschke <cito@online.de>,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [regression 6.12.y] After backport of 980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") bluethooth not anymore working on 0b05:1bef ASUSTek Computer, Inc. Bluetooth Controller (requests firmware)
Date: Sun, 25 Oct 2026 07:16:47 +0100 [thread overview]
Message-ID: <2026102508-thicket-duration-c971@gregkh> (raw)
In-Reply-To: <2026-10-24-1-daily-reply-0001-bluetooth-asus-rtl8761cu-firmware@kernel.org>
On Sat, Oct 24, 2026 at 04:10:59PM -0400, Sasha Levin wrote:
> > I did meanwhile and agree, the backports of these should be reverted
> > from 6.18.y and 6.12.y:
> >
> > * 980084de4d9b25 ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek
> > 8761CU") [v7.3-rc1]
> > * 6f0624b4427e38 ("Bluetooth: btusb: Add ASUS USB-BT600 for Realtek
> > 8761CU") [v7.3-rc1]
> > * 4a23ce935f74d1 ("Bluetooth: btrtl: Add the support for RTL8761CUV")
> > [v6.19-rc1]
>
> The stable trees match mainline here, so nothing is going into stable for
> this. The fix has to come from the Bluetooth maintainers or Christoph: an
> upstream revert of the ID commits, or a fallback to the ROM firmware when
> rtl8761cu_fw.bin is missing. Stable will take either one for 7.2, 6.18 and
> 6.12 through the normal Cc: stable route once it is in mainline.
>
> The other way out is on the distro side. rtl_bt/rtl8761cu_fw.bin has been in
> linux-firmware since 20251111, so a newer firmware-realtek package fixes this
> without any kernel change.
That's the simplest solution, any users hitting this should also upgrade
that package as it's been out for almost a year now.
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-25 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 15:15 [regression 6.12.y] After backport of 980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") bluethooth not anymore working on 0b05:1bef ASUSTek Computer, Inc. Bluetooth Controller (requests firmware) Salvatore Bonaccorso
2026-10-04 16:29 ` Sasha Levin
2026-10-12 12:00 ` Thorsten Leemhuis
2026-10-12 17:28 ` Salvatore Bonaccorso
2026-10-13 9:03 ` Thorsten Leemhuis
2026-10-23 13:43 ` Thorsten Leemhuis
2026-10-24 14:32 ` Erik Brangs
2026-10-24 20:10 ` Sasha Levin
2026-10-25 6:16 ` Greg Kroah-Hartman [this message]
2026-10-25 6:27 ` Thorsten Leemhuis
2026-10-25 7:37 ` Christoph Zwerschke
2026-10-25 8:07 ` Thorsten Leemhuis
2026-10-25 23:29 ` Sasha Levin
2026-10-29 6:02 ` Salvatore Bonaccorso
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=2026102508-thicket-duration-c971@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=1149377@bugs.debian.org \
--cc=benh@debian.org \
--cc=carnil@debian.org \
--cc=cito@online.de \
--cc=erik.brangs@gmx.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox