[Bug 213829] Intel AX210 Bluetooth controller doesn't start from warm boot

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)

quoted

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.