From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot
Date: Sat, 13 Nov 2021 09:19:41 +0000 [thread overview]
Message-ID: <bug-213829-62941-6k9eV0gnQR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213829-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213829
--- Comment #25 from Marco (rodomar705@protonmail.com) ---
(In reply to Josh Ellithorpe from comment #24)
> (In reply to Tedd An from comment #23)
> > Could you try with the latest firmware from linux-firmware.git?
> > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> >
> > Copy the intel/*.sfi to /lib/firmware/intel/ and cold boot.
> >
> > It will help to rule out if it is fw issue or not.
>
> I just tried. I installed the latest linux-firmware-git package that pulled
> latest.
>
> On cold boot I had `bluetoothctl list` hang after boot. Then after
> restarting the bluetooth service, it showed the device but still refused to
> even do a basic scan.
>
> `Failed to start discovery: org.bluez.Error.NotReady`
>
> Then after doing another quick cold boot (stayed off only a few seconds), no
> device was listed at all. =\
Same thing here, just tested with the latest 5.15 that supposedly should
contains the aforementioned fix above:
With the current firmware in linux-firmware, the issue is still the same after
a reboot. With the latest firmware (just downloaded ibt-0041-0041.ddc and sfi,
but if the wireless portion is needed, I can add that too) and that made things
even weirder and weirder. After a cold boot, the adapter was working as
standard. Rebooted and the device was disabled by default (my machine is
configured to auto enable the bluetooth at boot), but after disabling and
reenabling the radio from my DE, the bluetooth reconnected to my mouse for the
first time since I've got this adapter under Linux. After another reboot, the
radio completely disappeared (not even detected from my DE). I don't really
know where the problem resides, but I'm happy that someone is trying to see to
the bottom of this.
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:[~2021-11-13 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-213829-62941@https.bugzilla.kernel.org/>
2021-09-10 4:41 ` [Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot bugzilla-daemon
2021-10-17 18:05 ` bugzilla-daemon
2021-11-02 13:57 ` bugzilla-daemon
2021-11-02 20:02 ` bugzilla-daemon
2021-11-11 1:11 ` bugzilla-daemon
2021-11-11 3:12 ` bugzilla-daemon
2021-11-13 3:43 ` bugzilla-daemon
2021-11-13 9:19 ` bugzilla-daemon [this message]
2021-11-13 17:55 ` bugzilla-daemon
2021-11-14 8:07 ` bugzilla-daemon
2021-11-14 14:36 ` bugzilla-daemon
2021-11-25 12:19 ` bugzilla-daemon
2021-11-26 14:49 ` bugzilla-daemon
2022-01-02 20:37 ` bugzilla-daemon
2022-01-02 21:07 ` bugzilla-daemon
2022-01-06 12:58 ` bugzilla-daemon
2022-01-06 13:03 ` 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-213829-62941-6k9eV0gnQR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).