linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Firmware load fails in 3.18.0
@ 2014-12-10 13:19 Chris Clayton
  2014-12-10 13:23 ` Chris Clayton
  2014-12-11 12:55 ` Marcel Holtmann
  0 siblings, 2 replies; 3+ messages in thread
From: Chris Clayton @ 2014-12-10 13:19 UTC (permalink / raw)
  To: linux-bluetooth

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Firmware load fails in 3.18.0
  2014-12-10 13:19 Firmware load fails in 3.18.0 Chris Clayton
@ 2014-12-10 13:23 ` Chris Clayton
  2014-12-11 12:55 ` Marcel Holtmann
  1 sibling, 0 replies; 3+ messages in thread
From: Chris Clayton @ 2014-12-10 13:23 UTC (permalink / raw)
  To: linux-bluetooth

Sorry, I accidentally clicked the send button when I meant to save the mail as a draft when I had a moment of
inspiration about what the problem might be.

In 3.17.6, btusb is a module whereas it's built in in 3.18.0, so rootfs may not be mounted. Switching back to module.

On 12/10/14 13:19, Chris Clayton wrote:
> 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
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Firmware load fails in 3.18.0
  2014-12-10 13:19 Firmware load fails in 3.18.0 Chris Clayton
  2014-12-10 13:23 ` Chris Clayton
@ 2014-12-11 12:55 ` Marcel Holtmann
  1 sibling, 0 replies; 3+ messages in thread
From: Marcel Holtmann @ 2014-12-11 12:55 UTC (permalink / raw)
  To: Chris Clayton; +Cc: linux-bluetooth

Hi Chris,

> 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

this is pretty much clear. The filesystem where the firmware is located is not yet mounted. Build the btusb.ko driver has a module.

Regards

Marcel


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-12-11 12:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-10 13:19 Firmware load fails in 3.18.0 Chris Clayton
2014-12-10 13:23 ` Chris Clayton
2014-12-11 12:55 ` Marcel Holtmann

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).