From: Mark Gerlach <fedora-bugs@mailbox.org>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com
Subject: [BUG] btintel_pcie: Intel BE211 8086:a876 requests unavailable ibt-0190-01a1 firmware
Date: Sat, 5 Sep 2026 22:56:16 +0200 [thread overview]
Message-ID: <72098331-fa7c-443c-8b56-7671f9d711f2@mailbox.org> (raw)
Hello,
i am seeing a Bluetooth initialization failure with an Intel BE211
on a Lenovo ThinkPad E14 Gen 7 with Intel Lunar Lake
(Core Ultra 7 258V).
The PCI device is detected and btintel_pcie binds to it:
00:14.7 Bluetooth [0d11]: Intel Corporation Device [8086] (rev 10)
Subsystem: Intel Corporation Device [8086:0011]
Kernel driver in use: btintel_pcie
Kernel modules: btintel_pcie
During initialization, the driver requests:
intel/ibt-0190-01a1-iml.sfi
Loading the firmware then fails with ENOENT (-2):
Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-0190-01a1-iml.sfi (-2)
As a result, the controller does not complete initialization and
bluetoothctl list
shows no controller.
The issue is reproducible with:
Fedora 44 x86_64
kernel 7.1.9-200.fc44.x86_64
kernel 7.1.12-200.fc44.x86_64
linux-firmware-20260810-1.fc44.noarch
Hardware details:
Laptop: Lenovo ThinkPad E14 Gen 7
CPU: Intel Core Ultra 7 258V (Lunar Lake)
WLAN/BT: Intel BE211
PCI ID: 8086rev 10
Subsystem ID: 8086:0011
Wi-Fi on the same BE211 works correctly.
The installed linux-firmware package contains related Intel Bluetooth
firmware variants, including:
ibt-0190-0291-*
ibt-1190-01a1-*
ibt-00a0-01a1-*
but no:
ibt-0190-01a1-*
For diagnostic purposes, I temporarily created aliases from the
existing ibt-0190-0291 firmware files to the requested 0190-01a1
filenames.
With these aliases, the firmware files were found and downloaded, but
initialization then failed later with:
Bluetooth: hci0: Timeout (3000 ms) on alive interrupt,
alive context: intel_reset1
Bluetooth: hci0: Failed to send Intel Reset command
Bluetooth: hci0: Intel Soft Reset failed (-62)
I removed the aliases afterwards.
This suggests that the existing 0190-0291 firmware cannot simply be
used for this controller.
The same BE211 hardware works correctly under Windows using the HP OEM
driver package rather than Intel's generic driver package.
I initially reported this to Fedora to determine whether this might be
a Fedora packaging issue or an incorrect firmware selection by
btintel_pcie.
The Fedora developer has now confirmed that the issue is missing
firmware upstream and replied:
"The issue is missing firmware, we consume what ever the vendor pushes
upstream, it's not yet upstream, there's not much we can do about that
until the vendor bothers to send it upstream."
This therefore appears to require the corresponding Intel firmware to
be published upstream.
Could you please confirm that ibt-0190-01a1 is the expected firmware
variant for this BE211 / 8086/ subsystem 8086:0011 controller?
If so, could this be forwarded to the appropriate Intel firmware
maintainer, or is there an Intel contact or issue tracker where the
missing ibt-0190-01a1 firmware should be requested?
The Fedora bug report contains the full journal and lspci output:
https://bugzilla.redhat.com/show_bug.cgi?id=2527721
<https://bugzilla.redhat.com/show_bug.cgi?id=2527721>
There is also kernel Bug 221481 concerning btintel_pcie on Lunar Lake.
That report concerns a separate suspend issue. I previously added
information there about this controller's firmware loading failure.
Thanks,
Mark
next reply other threads:[~2026-09-05 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 20:56 Mark Gerlach [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 18:04 [BUG] btintel_pcie: Intel BE211 8086:a876 requests unavailable ibt-0190-01a1 firmware Sergey Lebedev
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=72098331-fa7c-443c-8b56-7671f9d711f2@mailbox.org \
--to=fedora-bugs@mailbox.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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