[Bug 219866] New: Bluetooth stops working on BE201 after linux-firmware 20250311

[Bug 219866] New: Bluetooth stops working on BE201 after linux-firmware 20250311

[bugzilla-daemon]

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

            Bug ID: 219866
           Summary: Bluetooth stops working on BE201 after linux-firmware
                    20250311
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: bhabeck34@outlook.com
        Regression: No

The linux-firmware 20250311 release appears to have shipped firmware for the
BE201 Wi-Fi chipset that has made Bluetooth unusable. 9971a5b6 appears to be
the commit that has updated firmware for this device.

Steps to reproduce:

1. Update to linux-firmware 20250311
2. Reboot
3. Notice that Bluetooth isn't working

There are some logs in the systemd journal:

Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0190-0291-pci.sfi
(-2)
Bluetooth: hci0: Failed to read MSFT supported features (-56)

Upon reverting to the linux-firmware 20250211 release, Bluetooth is functional
again.

System Info:
Distribution: Arch Linux
Kernel: 6.13.6
CPU: Intel(R) Core(TM) Ultra 7 258V
Network Controller: Intel Corporation BE201 320MHz (rev 10)
Bluetooth: Intel Corporation Device a876 (rev 10)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

[Bug 219866] Bluetooth stops working on BE201 after linux-firmware 20250311

[bugzilla-daemon]

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

Bryan H. (bhabeck34@outlook.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #1 from Bryan H. (bhabeck34@outlook.com) ---
There appears to be a merge request in the linux-firmware git repo that
addresses this issue, so I'm marking this as resolved.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.