From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214111] rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
Date: Mon, 21 Mar 2022 16:46:06 +0000 [thread overview]
Message-ID: <bug-214111-62941-qShrkzM544@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214111-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214111
--- Comment #9 from Marco (rodomar705@protonmail.com) ---
(In reply to bryanhoop from comment #7)
> Unfortunately after the update to linux-firmware-20210919-125.fc34.noarch,
> it appears that the workaround is no longer working. Even with the updated
> firmware I still have to unplug/replug the dongle after startup to get
> bluetooth working.
Just realized right now, if you are using Arch, the firmware seems to be packed
in a xz archive on my system. It was still working here because for some reason
the .bin probably is getting loaded before the .bin.xz file from the
distribution.
By the way, I've seen that a Realtek engineer has updated the firmware file at
the end of last year, as of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtl_bt/rtl8761bu_fw.bin?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80,
but the bug with that firmware still remains. I need to force disable and
enable the device.
I'll probably just get an adapter for a mPCIEx or M2 laptop to PCIEx and
install an already available Intel module that I got flotaing around at this
point, I doubt that this will ever be fixed on this hardware, unfortunately.
Marco.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-03-21 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 20:35 [Bug 214111] New: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug bugzilla-daemon
2021-08-26 12:11 ` [Bug 214111] " bugzilla-daemon
2021-08-26 12:25 ` bugzilla-daemon
2021-08-30 16:01 ` bugzilla-daemon
2021-08-31 19:26 ` bugzilla-daemon
2021-11-01 12:58 ` bugzilla-daemon
2021-11-01 13:21 ` bugzilla-daemon
2022-03-21 16:46 ` bugzilla-daemon [this message]
2022-03-28 16:03 ` bugzilla-daemon
2023-10-11 15:09 ` bugzilla-daemon
2023-10-11 15:35 ` 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-214111-62941-qShrkzM544@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).