From: Chris Clayton <chris2553@googlemail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Firmware load fails in 3.18.0
Date: Wed, 10 Dec 2014 13:19:53 +0000 [thread overview]
Message-ID: <54884879.8010903@googlemail.com> (raw)
Hi,
In trying to diagnose a problem with bluetooth-audio on my laptop, I've spotted that the firmware is failing to load.
The bluetooth related output from dmesg is:
[ 0.426890] Bluetooth: Core ver 2.19
[ 0.426986] Bluetooth: HCI device and connection manager initialized
[ 0.427038] Bluetooth: HCI socket layer initialized
[ 0.427087] Bluetooth: L2CAP socket layer initialized
[ 0.427137] Bluetooth: SCO socket layer initialized
[ 1.017575] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[ 1.017602] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq failed with error -2
[ 1.017604] Bluetooth: hci0 failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq(-2)
[ 1.017608] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.bseq failed with error -2
[ 1.017609] Bluetooth: hci0 failed to open default Intel fw file: intel/ibt-hw-37.7.bseq
[ 8.286733] Bluetooth: RFCOMM TTY layer initialized
[ 8.288739] Bluetooth: RFCOMM socket layer initialized
[ 8.290693] Bluetooth: RFCOMM ver 1.11
[ 63.965245] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 63.965257] Bluetooth: HIDP socket layer initialized
[ 63.966748] input: Bluetooth Laser Mouse as
/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:04B4:0033.0001/input/input10
[ 63.966891] hid-generic 0005:04B4:0033.0001: input: BLUETOOTH HID v6.11 Mouse [Bluetooth Laser Mouse] on
80:19:34:5a:67:51
The firmware two files mentioned are installed in /lib/firmware/intel and are successfully loaded by a 3.17.6 kernel:
[chris:~]$ dmesg | grep -i blue
[ 7.103619] Bluetooth: Core ver 2.19
[ 7.107523] Bluetooth: HCI device and connection manager initialized
[ 7.109453] Bluetooth: HCI socket layer initialized
[ 7.111373] Bluetooth: L2CAP socket layer initialized
[ 7.113301] Bluetooth: SCO socket layer initialized
[ 7.154252] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[ 7.298260] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[ 7.346464] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 8.475026] Bluetooth: RFCOMM TTY layer initialized
[ 8.476920] Bluetooth: RFCOMM socket layer initialized
[ 8.478797] Bluetooth: RFCOMM ver 1.11
[ 67.041180] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 67.041193] Bluetooth: HIDP socket layer initialized
[ 67.042339] input: Bluetooth Laser Mouse as
/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/bluetooth/hci0/hci0:256/0005:04B4:0033.0001/input/input10
[ 67.042478] hid-generic 0005:04B4:0033.0001: input: BLUETOOTH HID v6.11 Mouse [Bluetooth Laser Mouse] on
80:19:34:5a:67:51
next reply other threads:[~2014-12-10 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 13:19 Chris Clayton [this message]
2014-12-10 13:23 ` Firmware load fails in 3.18.0 Chris Clayton
2014-12-11 12:55 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54884879.8010903@googlemail.com \
--to=chris2553@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).