Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1017977: Fails to load intel/ibt-20-1-3.sfi
560 views
Skip to first unread message
Olaf Meeuwissen
Oct 29, 2022, 10:10:03 PM10/29/22
to
> Package: linux-image-5.18.0-4-amd64
> Severity: important
>
> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
> Used that to report this bug as the failure to load leaves me without a
> working keyboard. It's a bluetooth-only keyboard and it not working at
> all is why I've marked this important.
I just want to add that this is still an issue with 6.0.0-2. Exact same
symptoms. Keyboard is useless when booting after a poweroff. Booting
into 5.18.0-3 restores keyboard usability. A subsequent *reboot* to the
latest linux-image version, as opposed to a poweroff+boot, leaves the
keyboard in a usable state.
Hope this helps,
--
Olaf Meeuwissen
> Severity: important
>
> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
> Used that to report this bug as the failure to load leaves me without a
> working keyboard. It's a bluetooth-only keyboard and it not working at
> all is why I've marked this important.
I just want to add that this is still an issue with 6.0.0-2. Exact same
symptoms. Keyboard is useless when booting after a poweroff. Booting
into 5.18.0-3 restores keyboard usability. A subsequent *reboot* to the
latest linux-image version, as opposed to a poweroff+boot, leaves the
keyboard in a usable state.
Hope this helps,
--
Olaf Meeuwissen
Olaf Meeuwissen
Nov 7, 2022, 6:10:03 AM11/7/22
to
Hi again,
Just upgraded 6.0.0-2 from 6.0.3-1 to 6.0.5-1 and firmware-iwlwifi, which
provides the intel/ibt-20-1-3.sfi file, from 20210818-1 to 20221012-1.
Still no working keyboard after booting following a poweroff.
I'm back to booting 5.18.0-3 which loads the file just fine and gives me
back my keyboard.
--
Olaf Meeuwissen
provides the intel/ibt-20-1-3.sfi file, from 20210818-1 to 20221012-1.
Still no working keyboard after booting following a poweroff.
I'm back to booting 5.18.0-3 which loads the file just fine and gives me
back my keyboard.
--
Olaf Meeuwissen
Olaf Meeuwissen
Nov 19, 2022, 10:10:05 PM11/19/22
to
I just want to add that there has been no improvement in the situation
with 6.0.0-3 as well as 6.0.0-4.
After a poweroff, I boot 5.18.0-3 (after I connect my PS2 keyboard via
a USB dongle so I can navigate the GRUB menu) and then *reboot* to the
latest kernel. This way, the firmware file is loaded by 5.18.0-3 and
stays in the hardware's memory during the reboot so I get to use that
latest kernel with my Bluetooth-only keyboard. Cumbersome, at best.
with 6.0.0-3 as well as 6.0.0-4.
After a poweroff, I boot 5.18.0-3 (after I connect my PS2 keyboard via
a USB dongle so I can navigate the GRUB menu) and then *reboot* to the
latest kernel. This way, the firmware file is loaded by 5.18.0-3 and
stays in the hardware's memory during the reboot so I get to use that
latest kernel with my Bluetooth-only keyboard. Cumbersome, at best.
Olaf Meeuwissen
Dec 3, 2022, 10:00:04 PM12/3/22
to
Upgrading the firmware-iwlwifi package last week (2022-11-27) from
20221012-1 to 20221109-2 fixed the issue for linux-image-6.0.0-4-amd64
6.0.8-1. The changelog for 20221109-1 mentioned
* iwlwifi: update firmware files for Intel Bluetooth AX2*
* iwlwifi: Add Intel Wireless AX211 Bluethooth firmware and
configuration (Closes: #1023245)
which may be related to fixing it for my
Intel Corporation Wi-Fi 6 AX200 (rev 1a)
However, upgrading today (2022-12-04) to linux-image-6.0.0-5-amd64
6.0.10-1 reintroduced it.
Cold booting into 6.0.0-4 I have a working Bluetooth-only keyboard.
Rebooting from that into 6.0.0-5 my keyboard remains functional.
Cold booting into 6.0.0-5 my Bluetooth-only keyboard is unresponsive.
For both 6.0.0-5 boot scenarios, dmesg --level=err includes
bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
Twice, actually, about 10 microseconds apart.
For 6.0.0-4 there is no such error message.
20221012-1 to 20221109-2 fixed the issue for linux-image-6.0.0-4-amd64
6.0.8-1. The changelog for 20221109-1 mentioned
* iwlwifi: update firmware files for Intel Bluetooth AX2*
* iwlwifi: Add Intel Wireless AX211 Bluethooth firmware and
configuration (Closes: #1023245)
which may be related to fixing it for my
Intel Corporation Wi-Fi 6 AX200 (rev 1a)
However, upgrading today (2022-12-04) to linux-image-6.0.0-5-amd64
6.0.10-1 reintroduced it.
Cold booting into 6.0.0-4 I have a working Bluetooth-only keyboard.
Rebooting from that into 6.0.0-5 my keyboard remains functional.
Cold booting into 6.0.0-5 my Bluetooth-only keyboard is unresponsive.
For both 6.0.0-5 boot scenarios, dmesg --level=err includes
bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
Twice, actually, about 10 microseconds apart.
For 6.0.0-4 there is no such error message.
Olaf Meeuwissen
Dec 10, 2022, 10:40:03 PM12/10/22
to
- firmware-iwlwifi from 20221109-2 to 20221109-4
- linux-image-6.0.0-5-amd64 from 6.0.10-1 to 6.0.10-2
- linux-image-amd64 from 6.0.10-1 to 6.0.10-2
Olaf Meeuwissen
Jan 21, 2023, 9:40:04 PM1/21/23
to
Olaf Meeuwissen <paddy...@member.fsf.org> writes:
> FYI, the situation is unchanged after upgrading
>
> - firmware-iwlwifi from 20221109-2 to 20221109-4
> - linux-image-6.0.0-5-amd64 from 6.0.10-1 to 6.0.10-2
> - linux-image-amd64 from 6.0.10-1 to 6.0.10-2
firmware-iwlwifi/testing,now 20221214-3 all [installed]
linux-image-6.0.0-4-amd64/now 6.0.8-1 amd64 [installed,local]
linux-image-6.0.0-6-amd64/now 6.0.12-1 amd64 [installed,local]
linux-image-6.1.0-1-amd64/testing,now 6.1.4-1 amd64 [installed,automatic]
linux-image-amd64/testing,now 6.1.4-1 amd64 [installed,automatic]
and still experience this issue when "cold" booting (i.e. after
`poweroff`) linux-image-6.1.0.1.
In order to use my Bluetooth-only keyboard, I cold boot with 6.0.0-4 so
that loading the intel/ibt-20-1-3.sfi firmware file succeeds and then
"warm" boot (i.e. `reboot`) into 6.1.0-1 to use the latest kernel. That
way I can use that Bluetooth-only keyboard.
BTW, in order to select a kernel in the GRUB menu I use an old PS/2
keyboard connected via a PS/2 to USB adapter.
P.S.: I have no info on cold booting with 6.0.0-6.
Olaf Meeuwissen
Feb 4, 2023, 9:30:05 PM2/4/23
to
Olaf Meeuwissen <paddy...@member.fsf.org> writes:
> I am currently on
>
> firmware-iwlwifi/testing,now 20221214-3 all [installed]
> linux-image-6.0.0-4-amd64/now 6.0.8-1 amd64 [installed,local]
> linux-image-6.0.0-6-amd64/now 6.0.12-1 amd64 [installed,local]
> linux-image-6.1.0-1-amd64/testing,now 6.1.4-1 amd64 [installed,automatic]
> linux-image-amd64/testing,now 6.1.4-1 amd64 [installed,automatic]
>
> and still experience this issue when "cold" booting (i.e. after
> `poweroff`) linux-image-6.1.0.1.
--
Olaf Meeuwissen
Olaf Meeuwissen
Feb 11, 2023, 10:00:04 PM2/11/23
to
Olaf Meeuwissen <paddy...@member.fsf.org> writes:
> Just checked again with 6.1.7-1 and still no joy :-(
Glad to report joy cold-booting linux-image-6.1.0-3-amd64.
> Just checked again with 6.1.7-1 and still no joy :-(
Currrently have the following installed
$ dpkg-query -W | grep -E '(linux-image|firmware-iwlwifi)'
firmware-iwlwifi 20221214-3
linux-image-6.1.0-2-amd64 6.1.7-1
linux-image-6.1.0-3-amd64 6.1.8-1
linux-image-amd64 6.1.8-1
Cold-booting with linux-image-6.1.0-2-amd64 didn't give me a working
keyboard.
I checked the changelog but did not find anything obviously related, but
maybe one of these upstream stable updates
- wifi: iwlwifi: fw: skip PPAG for JF
- Bluetooth: hci_sync: Fix use HCI_OP_LE_READ_BUFFER_SIZE_V2
fixed it?
Diederik de Haas
Feb 12, 2023, 10:30:04 AM2/12/23
to
On Sunday, 12 February 2023 03:29:14 CET Olaf Meeuwissen wrote:
> Olaf Meeuwissen <paddy...@member.fsf.org> writes:
> > Just checked again with 6.1.7-1 and still no joy :-(
>
> Glad to report joy cold-booting linux-image-6.1.0-3-amd64.
> Currrently have the following installed
That's great!
> Olaf Meeuwissen <paddy...@member.fsf.org> writes:
> > Just checked again with 6.1.7-1 and still no joy :-(
>
> Glad to report joy cold-booting linux-image-6.1.0-3-amd64.
> Currrently have the following installed
> I checked the changelog but did not find anything obviously related, but
> maybe one of these upstream stable updates
>
> - wifi: iwlwifi: fw: skip PPAG for JF
> - Bluetooth: hci_sync: Fix use HCI_OP_LE_READ_BUFFER_SIZE_V2
>
> fixed it?
fixed now.
If the issue does come back, then I'd suggest doing a `git bisect` between
v5.18.14 and v5.18.16 as that's where the initial problem surfaced and it also
has the benefit of being a reasonably small range.
https://wiki.debian.org/DebianKernel/GitBisect has instructions for it.
Olaf Meeuwissen
Mar 12, 2023, 1:50:04 AM3/12/23
to
Hi,
Again, unfortunately :-(
Diederik de Haas <didi....@cknow.org> writes:
> On Sunday, 12 February 2023 03:29:14 CET Olaf Meeuwissen wrote:
>> Olaf Meeuwissen <paddy...@member.fsf.org> writes:
>> > Just checked again with 6.1.7-1 and still no joy :-(
>>
>> Glad to report joy cold-booting linux-image-6.1.0-3-amd64.
>> Currrently have the following installed
>
> That's great!
Cold booting with 6.1.0-5, I was left without a working keyboard again.
Warm booting back to 6.1.0-3 did NOT give me a working keyboard either.
Repeated cold booting 6.1.0-3 did NOT give me my keyboard back. I don't
know what happened when I was able to report success.
Plugged in my PS/2 keyboard via USB dongle, added
deb [check-valid-until=no] https://snapshot.debian.org/archive/debian/20221112T151812Z/ sid main
to my APT sources and reinstalled 6.0.0-4. Cold booting that got my
Bluetooth-only keyboard back. Subsequent warm booting 6.1.0-5 left
that keyboard functional.
FTR, this is all using firmware-iwlwifi 20221214-3.
Earlier, in message #34, I reported that upgrading that package fixed
the issue for 6.0.0-4. Checking on packages.debian.org, I see that a
newer version is available for bookworm but that the section has been
renamed. Added that and upgraded which also bumped my other firmware
packages and pulled in the 6.1.0-6 kernel.
The 6.1.0-6 kernel also fails to load the firmware file, leaves me
without a working Bluetooth-only keyboard but warm booting to it (from a
6.0.0-4 cold boot) I can use said keyboard.
>> I checked the changelog but did not find anything obviously related, but
>> maybe one of these upstream stable updates
>>
>> - wifi: iwlwifi: fw: skip PPAG for JF
>> - Bluetooth: hci_sync: Fix use HCI_OP_LE_READ_BUFFER_SIZE_V2
>>
>> fixed it?
>
> I looked into them, but didn't find a direct link. But hopefully the issue is
> fixed now.
>
> If the issue does come back, then I'd suggest doing a `git bisect` between
> v5.18.14 and v5.18.16 as that's where the initial problem surfaced and it also
> has the benefit of being a reasonably small range.
Please note that 6.0.0-4 (package version 6.0.8-1) fixed it but 6.0.0-5
(package v6.0.10-1) broke it again. FTR,
diff -u /boot/config-6.0.0-{4,5}-amd64
--- /boot/config-6.0.0-4-amd64 2022-11-11 17:36:29.000000000 +0900
+++ /boot/config-6.0.0-5-amd64 2022-11-27 00:06:48.000000000 +0900
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# Linux/x86 6.0.8 Kernel Configuration
+# Linux/x86 6.0.10 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc-12 (Debian 12.2.0-9) 12.2.0"
CONFIG_CC_IS_GCC=y
so we can rule out a configuration change causing the breakage.
Thanks for the pointer but that is a bit more work than I currently care
to chew into.
--
Olaf Meeuwissen
Again, unfortunately :-(
Diederik de Haas <didi....@cknow.org> writes:
> On Sunday, 12 February 2023 03:29:14 CET Olaf Meeuwissen wrote:
>> Olaf Meeuwissen <paddy...@member.fsf.org> writes:
>> > Just checked again with 6.1.7-1 and still no joy :-(
>>
>> Glad to report joy cold-booting linux-image-6.1.0-3-amd64.
>> Currrently have the following installed
>
> That's great!
Warm booting back to 6.1.0-3 did NOT give me a working keyboard either.
Repeated cold booting 6.1.0-3 did NOT give me my keyboard back. I don't
know what happened when I was able to report success.
Plugged in my PS/2 keyboard via USB dongle, added
deb [check-valid-until=no] https://snapshot.debian.org/archive/debian/20221112T151812Z/ sid main
to my APT sources and reinstalled 6.0.0-4. Cold booting that got my
Bluetooth-only keyboard back. Subsequent warm booting 6.1.0-5 left
that keyboard functional.
FTR, this is all using firmware-iwlwifi 20221214-3.
Earlier, in message #34, I reported that upgrading that package fixed
the issue for 6.0.0-4. Checking on packages.debian.org, I see that a
newer version is available for bookworm but that the section has been
renamed. Added that and upgraded which also bumped my other firmware
packages and pulled in the 6.1.0-6 kernel.
The 6.1.0-6 kernel also fails to load the firmware file, leaves me
without a working Bluetooth-only keyboard but warm booting to it (from a
6.0.0-4 cold boot) I can use said keyboard.
>> I checked the changelog but did not find anything obviously related, but
>> maybe one of these upstream stable updates
>>
>> - wifi: iwlwifi: fw: skip PPAG for JF
>> - Bluetooth: hci_sync: Fix use HCI_OP_LE_READ_BUFFER_SIZE_V2
>>
>> fixed it?
>
> I looked into them, but didn't find a direct link. But hopefully the issue is
> fixed now.
>
> If the issue does come back, then I'd suggest doing a `git bisect` between
> v5.18.14 and v5.18.16 as that's where the initial problem surfaced and it also
> has the benefit of being a reasonably small range.
(package v6.0.10-1) broke it again. FTR,
diff -u /boot/config-6.0.0-{4,5}-amd64
--- /boot/config-6.0.0-4-amd64 2022-11-11 17:36:29.000000000 +0900
+++ /boot/config-6.0.0-5-amd64 2022-11-27 00:06:48.000000000 +0900
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# Linux/x86 6.0.8 Kernel Configuration
+# Linux/x86 6.0.10 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc-12 (Debian 12.2.0-9) 12.2.0"
CONFIG_CC_IS_GCC=y
so we can rule out a configuration change causing the breakage.
Thanks for the pointer but that is a bit more work than I currently care
to chew into.
--
Olaf Meeuwissen
Olaf Meeuwissen
May 12, 2023, 10:50:04 PM5/12/23
to
Hi,
I just upgraded linux-image-amd64 and that pulled in 6.1.0-9 and now
intel/ibt-20-1-3.sfi loads without issues and my Bluetooth keyboard
works, even when cold booting!
Cold booting 6.1.0-7 it fails and my keyboard is unresponsive.
For reference,
# grep -E '(version 6\.1\.0-|ibt-20-1-3\.sfi)' /var/log/kern.log | sed 's/.* kernel: //'
[ 0.000000] Linux version 6.1.0-7-amd64 (debian...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2 (2023-04-08)
[ 1.590712] bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
[ 1.590724] bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
[ 1.590726] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-20-1-3.sfi (-2)
[ 0.000000] Linux version 6.1.0-9-amd64 (debian...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)
[ 3.635292] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 3.635294] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
I don't know if it is related but when I boot 6.1.0-7, I also see a call
trace that starts with
[ 1.554110] alg: self-tests for ecdh-nist-p256 using ecdh-nist-p256-generic failed (rc=-14)
[ 1.554111] ------------[ cut here ]------------
This happens before 6.1.0-7 tries to load intel/ibt-20-1-3.sfi.
With 6.1.0-9, that call trace is gone too and loading the firmware file
appears to have been moved to a later phase based upon the time stamps.
I don't know what fixed it but I'm happy to report this fixed. At least
in 6.1.0-9, but I'm slightly worried a later version might reintroduce
it as that has happened before.
Oh, FYI, I have the following firmware packages installed at the moment
# apt list --installed 2>/dev/null | grep firmware
firmware-amd-graphics/testing,now 20230210-5 all [installed]
firmware-iwlwifi/testing,now 20230210-5 all [installed]
firmware-linux-free/unstable,unstable,testing,now 20200122-1 all [installed,automatic]
firmware-realtek/testing,now 20230210-5 all [installed]
I just upgraded linux-image-amd64 and that pulled in 6.1.0-9 and now
intel/ibt-20-1-3.sfi loads without issues and my Bluetooth keyboard
works, even when cold booting!
Cold booting 6.1.0-7 it fails and my keyboard is unresponsive.
For reference,
# grep -E '(version 6\.1\.0-|ibt-20-1-3\.sfi)' /var/log/kern.log | sed 's/.* kernel: //'
[ 0.000000] Linux version 6.1.0-7-amd64 (debian...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2 (2023-04-08)
[ 1.590712] bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
[ 1.590724] bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
[ 1.590726] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-20-1-3.sfi (-2)
[ 0.000000] Linux version 6.1.0-9-amd64 (debian...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)
[ 3.635292] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 3.635294] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
I don't know if it is related but when I boot 6.1.0-7, I also see a call
trace that starts with
[ 1.554110] alg: self-tests for ecdh-nist-p256 using ecdh-nist-p256-generic failed (rc=-14)
[ 1.554111] ------------[ cut here ]------------
This happens before 6.1.0-7 tries to load intel/ibt-20-1-3.sfi.
With 6.1.0-9, that call trace is gone too and loading the firmware file
appears to have been moved to a later phase based upon the time stamps.
I don't know what fixed it but I'm happy to report this fixed. At least
in 6.1.0-9, but I'm slightly worried a later version might reintroduce
it as that has happened before.
Oh, FYI, I have the following firmware packages installed at the moment
# apt list --installed 2>/dev/null | grep firmware
firmware-amd-graphics/testing,now 20230210-5 all [installed]
firmware-iwlwifi/testing,now 20230210-5 all [installed]
firmware-linux-free/unstable,unstable,testing,now 20200122-1 all [installed,automatic]
firmware-realtek/testing,now 20230210-5 all [installed]
0 new messages