New: btintel lacks firmware dependencies for several versions
https://bugzilla.kernel.org/show_bug.cgi?id=221952
Bug ID: 221952
Summary: btintel lacks firmware dependencies for several
versions
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: NoI have a system with an Intel bluetooth card that requires the intel/ibt-17-16-1.sfi firmware to properly initialize.
lsusb: Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak
(JfP)
The firmware is available in the kernel tree and loads fine if it is present on module load, however, it is not declared as a dependency of btintel in btintel.c.
This appears to be the case for several other firmware versions as well, with the only ones listed at time of writing being
MODULE_FIRMWARE("intel/ibt-11-5.sfi");MODULE_FIRMWARE("intel/ibt-11-5.ddc");MODULE_FIRMWARE("intel/ibt-12-16.sfi");MODULE_FIRMWARE("intel/ibt-12-16.ddc");
Ordinarily, this would not be an issue, but I am using mkosi-initrd which utilizes the embedded firmware metadata for the kernel module to identify which files it needs to copy into (or retain) in the initrd. Because the firmware version required by this card is not listed, mkosi-initrd does not include it in the final initrd. This causes the card to not load properly on boot, requiring an rmmod/modprobe after the system has fully booted which lets it load the firmware file from main storage instead of the initrd.
dmesg in the initrd:
[ 5.765232] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 [ 5.766307] Bluetooth: hci0: Device revision is 2 [ 5.766315] Bluetooth: hci0: Secure boot is enabled [ 5.766320] Bluetooth: hci0: OTP lock is enabled [ 5.766324] Bluetooth: hci0: API lock is enabled [ 5.766327] Bluetooth: hci0: Debug lock is disabled [ 5.766331] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 5.766367] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2) [ 5.766385] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2) [ 5.766404] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2) [ 5.766411] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 5.767287] Bluetooth: hci0: Reading supported features failed (-56) [ 5.767296] Bluetooth: hci0: Error reading debug features [ 5.767303] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its
usage is not supported.
dmesg on the host after boot and rmmod/modprobe:
[ 3825.660321] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 [ 3825.661260] Bluetooth: hci0: Device revision is 2 [ 3825.661276] Bluetooth: hci0: Secure boot is enabled [ 3825.661284] Bluetooth: hci0: OTP lock is enabled [ 3825.661290] Bluetooth: hci0: API lock is enabled [ 3825.661295] Bluetooth: hci0: Debug lock is disabled [ 3825.661300] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 3825.665645] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [ 3825.665743] Bluetooth: hci0: Boot Address: 0x40800 [ 3825.665745] Bluetooth: hci0: Firmware Version: 201-12.24 [ 3827.420681] Bluetooth: hci0: Waiting for firmware download to complete [ 3827.421351] Bluetooth: hci0: Firmware loaded in 1714560 usecs [ 3827.421559] Bluetooth: hci0: Waiting for device to boot [ 3827.435417] Bluetooth: hci0: Device booted in 13654 usecs [ 3827.435607] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc [ 3827.437363] Bluetooth: hci0: Applying Intel DDC parameters completed [ 3827.438337] Bluetooth: hci0: Firmware revision 0.1 build 201 week 12 2024 [ 3827.440365] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its
usage is not supported.
I am not entirely familiar with how the module firmware metadata is used, but I assume that the lack of entries for this (and other) firmware is not intentional. In total, there are over 40 versions of the ibt firmware not listed in btintel.c.
This behaviour was observed on kernel version 6.12.107, but the latest commit on the kernel is still missing the applicable MODULE_FIRMWARE entries.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.