Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53121 - [linux-firmware] intel 8260AC'bluetooth cannot work in archlinux

Attached to Project: Arch Linux
Opened by Hongyu.Du (dongfengweixiao) - Wednesday, 01 March 2017, 03:50 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 03 May 2017, 15:42 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

intel 8260AC's bluetooth cannot work in archlinux,but in ubuntu it works well.

kernel wanna intel/ibt-11-4.sfi,but only ibt-11-5.sfi & ibt-11-16.sfi in linux-firmware package.

$ lsmod |grep btusb
btusb 40960 0
btrtl 16384 1 btusb
btbcm 16384 1 btusb
btintel 16384 1 btusb
bluetooth 487424 12 btrtl,btintel,bnep,btbcm,btusb
usbcore 208896 8 usbhid,usb_storage,ehci_hcd,xhci_pci,btusb,uas,xhci_hcd,ehci_pci
$ lsusb; dmesg | egrep -i 'blue|firm'
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 8087:0a2b Intel Corp.
Bus 003 Device 007: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
Bus 003 Device 006: ID 046d:082b Logitech, Inc. Webcam C170
Bus 003 Device 005: ID 0483:5022 STMicroelectronics
Bus 003 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 0.954450] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 2.998785] Bluetooth: Core ver 2.22
[ 2.998799] Bluetooth: HCI device and connection manager initialized
[ 2.998801] Bluetooth: HCI socket layer initialized
[ 2.998803] Bluetooth: L2CAP socket layer initialized
[ 2.998807] Bluetooth: SCO socket layer initialized
[ 3.041430] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 3.043435] Bluetooth: hci0: Device revision is 4
[ 3.043436] Bluetooth: hci0: Secure boot is enabled
[ 3.043436] Bluetooth: hci0: OTP lock is disabled
[ 3.043437] Bluetooth: hci0: API lock is disabled
[ 3.043437] Bluetooth: hci0: Debug lock is disabled
[ 3.043438] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 3.097171] bluetooth hci0: Direct firmware load for intel/ibt-11-4.sfi failed with error -2
[ 3.097173] Bluetooth: hci0: Failed to load Intel firmware file (-2)
[ 3.532831] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-26.ucode failed with error -2
[ 3.532860] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-25.ucode failed with error -2
[ 3.533596] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-24.ucode failed with error -2
[ 3.533609] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with error -2
[ 3.540351] iwlwifi 0000:04:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
[ 4.421390] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.421391] Bluetooth: BNEP filters: protocol multicast
[ 4.421394] Bluetooth: BNEP socket layer initialized=

$ hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:43 acl:0 sco:0 events:2 errors:0
TX bytes:6 acl:0 sco:0 commands:2 errors:0
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 03 May 2017, 15:42 GMT
Reason for closing:  No response
Comment by Doug Newgard (Scimmia) - Wednesday, 26 April 2017, 16:17 GMT
I see no problems at all there

Edit: oh, I missed the "Failed to load Intel firmware file"; I'm guessing this has been fixed in newer kernels?

Loading...