http://bugzilla.opensuse.org/show_bug.cgi?id=1095147 Bug ID: 1095147 Summary: Atheros AR3012 bluetooth fails on kernel 4.4.132-53-default with Configuration file not found ar3k/ramps_0x00000200_0.dfu Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: chevy.stroker@yahoo.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Installing the latest kernel on Leap 42.3, 4.4.132-53-default makes bluetooth fail in my MSI GS40 laptop. dmesg|grep -i blue [ 20.548957] Bluetooth: Core ver 2.21 [ 20.548971] Bluetooth: HCI device and connection manager initialized [ 20.548974] Bluetooth: HCI socket layer initialized [ 20.548975] Bluetooth: L2CAP socket layer initialized [ 20.548980] Bluetooth: SCO socket layer initialized [ 20.560174] Bluetooth: Configuration file not found ar3k/ramps_0x00000200_0.dfu [ 20.560174] Bluetooth: Loading sysconfig file failed [ 54.478616] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 54.478617] Bluetooth: BNEP filters: protocol multicast [ 54.478621] Bluetooth: BNEP socket layer initialized I checked to insure all these files are present: /lib/firmware/ath3k-1.fw /lib/firmware/ar3k/AthrBT_0x01020200.dfu /lib/firmware/ar3k/ramps_0x01020200_26.dfu /lib/firmware/ar3k/ramps_0x01020200_40.dfu I also checked to insure these files were on the system, since as you will see below these are the ones the previous kernel used: /lib/firmware/qca/rampatch_usb_00000200.bin /lib/firmware/qca/nvm_usb_00000200.bin According to this thread https://bbs.archlinux.org/viewtopic.php?id=201646 the _0.dfu part of the file means the clock value is being read incorrectly. There also seems to be some issues around Qualcomm and Rome using the same chip ID. Which seems to be the issue here. In 4.4.126-48-default bluetooth worked fine, and I hope this will help from the /var/log/boot.log file from when it worked: May 22 09:16:06 kvm kernel: Bluetooth: Core ver 2.21 May 22 09:16:06 kvm kernel: Bluetooth: HCI device and connection manager initialized May 22 09:16:06 kvm kernel: Bluetooth: HCI socket layer initialized May 22 09:16:06 kvm kernel: Bluetooth: L2CAP socket layer initialized May 22 09:16:06 kvm kernel: Bluetooth: SCO socket layer initialized May 22 09:16:06 kvm kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin May 22 09:16:06 kvm kernel: Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111 May 22 09:16:07 kvm kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin May 22 09:16:07 kvm systemd[1]: Starting Bluetooth service... May 22 09:16:07 kvm bluetoothd[1599]: Bluetooth daemon 5.41 May 22 09:16:07 kvm bluetoothd[1599]: Starting SDP server May 22 09:16:07 kvm systemd[1]: Started Bluetooth service. May 22 09:16:07 kvm systemd[1]: Reached target Bluetooth. May 22 09:16:07 kvm kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 May 22 09:16:07 kvm kernel: Bluetooth: BNEP filters: protocol multicast May 22 09:16:07 kvm kernel: Bluetooth: BNEP socket layer initialized May 22 09:16:07 kvm bluetoothd[1599]: Bluetooth management interface 1.10 initialized May 22 09:16:07 kvm bluetoothd[1599]: Failed to obtain handles for "Service Changed" characteristic May 22 09:16:07 kvm bluetoothd[1599]: Sap driver initialization failed. May 22 09:16:07 kvm bluetoothd[1599]: sap-server: Operation not permitted (1) May 22 09:16:41 kvm bluetoothd[1599]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource May 22 09:16:41 kvm bluetoothd[1599]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink May 22 09:16:41 kvm kernel: Bluetooth: RFCOMM TTY layer initialized May 22 09:16:41 kvm kernel: Bluetooth: RFCOMM socket layer initialized May 22 09:16:41 kvm kernel: Bluetooth: RFCOMM ver 1.11 I am happy to test as needed. -- You are receiving this mail because: You are on the CC list for the bug.