5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fedora |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Committed
|
Undecided
|
Dimitri John Ledkov | ||
snapd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg:
[ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-
[ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56)
Here's the full dmesg with grep -i blue:
https:/
On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices:
[ 5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-
[ 7.059104] Bluetooth: hci0: Waiting for firmware download to complete
[ 7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs
[ 7.059903] Bluetooth: hci0: Waiting for device to boot
[ 7.073886] Bluetooth: hci0: Device booted in 13691 usecs
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
drivers/ bluetooth/ btintel. c only declares
MODULE_ AUTHOR( "Marcel Holtmann <email address hidden>"); DESCRIPTION( "Bluetooth support for Intel devices ver " VERSION); VERSION( VERSION) ; LICENSE( "GPL"); FIRMWARE( "intel/ ibt-11- 5.sfi") ; FIRMWARE( "intel/ ibt-11- 5.ddc") ; FIRMWARE( "intel/ ibt-12- 16.sfi" ); FIRMWARE( "intel/ ibt-12- 16.ddc" );
MODULE_
MODULE_
MODULE_
MODULE_
MODULE_
MODULE_
MODULE_
thus during snap build we strip it, and it doesn't get included in the snap.
i wonder if we should adjust the MODULE_FIRMWARE to mention more things, or mentioned them with regexp. Such that we don't strip it and include them.