All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219866] New: Bluetooth stops working on BE201 after linux-firmware 20250311
Date: Thu, 13 Mar 2025 18:43:40 +0000	[thread overview]
Message-ID: <bug-219866-62941@https.bugzilla.kernel.org/> (raw)

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.

             reply	other threads:[~2025-03-13 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 18:43 bugzilla-daemon [this message]
2025-03-14 17:53 ` [Bug 219866] Bluetooth stops working on BE201 after linux-firmware 20250311 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-219866-62941@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.