No bluetooth adapters have been found

[nicko02338]

As I know I have a broadcom bluetooth built-in on my notebook. The problem is when I want to activate it, system says "No bluetooth adapters have been found". Is there anything I can do to kubuntu 14.04.2 recognise the bluetooth adapter?.
I know it is a broadcom bluetooth, because it was recognised as that by others linux distros in the past.

Thank you in advance.

[SteveRiley]

What's the output of lsusb and lspci -k?

[nicko02338]

What's the output of lsusb and lspci -k?

Here is the output of lsusb:
Bus 002 Device 003: ID 13d3:5162 IMC Networks
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here is the output of lspci -k:
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
Subsystem: Lenovo Device 3977
Kernel driver in use: ivb_uncore
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
Subsystem: Lenovo Device 3977
Kernel driver in use: i915
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: mei_me
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: lpc_ich
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
Subsystem: Lenovo Device 3977
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
Subsystem: Lenovo Device 3977
01:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
Subsystem: Lenovo Device 3979
Kernel driver in use: alx
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4)
Subsystem: Intel Corporation Centrino Wireless-N 2200 BGN
Kernel driver in use: iwlwifi
03:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30)
Subsystem: Lenovo Device 3976
Kernel driver in use: sdhci-pci
03:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30)
Subsystem: Lenovo Device 3976
03:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 30)
Subsystem: Lenovo Device 3976
Kernel driver in use: jmb38x_ms
03:00.4 System peripheral: JMicron Technology Corp. xD Host Controller (rev 30)
Subsystem: Lenovo Device 3976

What do you think?

[nicko02338]

HI!

Is there anything I could do to fix this issue?

thanks.

[SteveRiley]

So on most machines, Bluetooth interfaces are connected to the USB bus (not the PCI bus). What's the output of

sudo lshw -C communication

[nicko02338]

So on most machines, Bluetooth interfaces are connected to the USB bus (not the PCI bus). What's the output of

sudo lshw -C communication

here is the output of code that you requested
-communication
description: Communication controller
product: 7 Series/C210 Series Chipset Family MEI Controller #1
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=mei_me latency=0
resources: irq:43 memory:d0714000-d071400f

[SteveRiley]

Well, your Bluetooth hardware appears not to be detected. If it were, you'd also see something like the following in that output:

  *-usb:1                 
       description: Bluetooth wireless interface
       vendor: Intel Corp.
       physical id: 7
       bus info: usb@1:7
       version: 0.01
       capabilities: bluetooth usb-2.01
       configuration: driver=btusb maxpower=100mA speed=12Mbit/sp

What's the output of

grep -i blue /var/log/syslog

[nicko02338]

Here is the output requested:

bluetoothd[934]: Bluetooth daemon 4.101
May  8 19:16:50 Morocha1 kernel: [   23.523381] Bluetooth: Core ver 2.19
May  8 19:16:50 Morocha1 kernel: [   23.523392] Bluetooth: HCI device and connection manager initialized
May  8 19:16:50 Morocha1 kernel: [   23.523398] Bluetooth: HCI socket layer initialized
May  8 19:16:50 Morocha1 kernel: [   23.523399] Bluetooth: L2CAP socket layer initialized
May  8 19:16:50 Morocha1 kernel: [   23.523406] Bluetooth: SCO socket layer initialized
May  8 19:16:50 Morocha1 kernel: [   23.525852] Bluetooth: RFCOMM TTY layer initialized
May  8 19:16:50 Morocha1 kernel: [   23.525859] Bluetooth: RFCOMM socket layer initialized
May  8 19:16:50 Morocha1 kernel: [   23.525863] Bluetooth: RFCOMM ver 1.11
May  8 19:16:50 Morocha1 bluetoothd[934]: Starting SDP server
May  8 19:16:50 Morocha1 bluetoothd[934]: DIS cannot start: GATT is disabled
May  8 19:16:50 Morocha1 bluetoothd[934]: Failed to init deviceinfo plugin
May  8 19:16:50 Morocha1 bluetoothd[934]: Failed to init proximity plugin
May  8 19:16:50 Morocha1 bluetoothd[934]: Failed to init time plugin
May  8 19:16:50 Morocha1 bluetoothd[934]: Failed to init alert plugin
May  8 19:16:50 Morocha1 bluetoothd[934]: Failed to init thermometer plugin
May  8 19:16:50 Morocha1 bluetoothd[934]: Failed to init gatt_example plugin
May  8 19:16:50 Morocha1 bluetoothd[934]: Bluetooth Management interface initialized
May  8 19:16:50 Morocha1 kernel: [   23.686240] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May  8 19:16:50 Morocha1 kernel: [   23.686243] Bluetooth: BNEP filters: protocol multicast
May  8 19:16:50 Morocha1 kernel: [   23.686249] Bluetooth: BNEP socket layer initialized
May 10 09:08:42 Morocha1 kernel: [   23.512824] Bluetooth: Core ver 2.19
May 10 09:08:42 Morocha1 kernel: [   23.512835] Bluetooth: HCI device and connection manager initialized
May 10 09:08:42 Morocha1 kernel: [   23.512840] Bluetooth: HCI socket layer initialized
May 10 09:08:42 Morocha1 kernel: [   23.512842] Bluetooth: L2CAP socket layer initialized
May 10 09:08:42 Morocha1 kernel: [   23.512848] Bluetooth: SCO socket layer initialized
May 10 09:08:42 Morocha1 kernel: [   23.515168] Bluetooth: RFCOMM TTY layer initialized
May 10 09:08:42 Morocha1 kernel: [   23.515173] Bluetooth: RFCOMM socket layer initialized
May 10 09:08:42 Morocha1 kernel: [   23.515176] Bluetooth: RFCOMM ver 1.11
May 10 09:08:42 Morocha1 bluetoothd[914]: Starting SDP server
May 10 09:08:42 Morocha1 bluetoothd[914]: DIS cannot start: GATT is disabled
May 10 09:08:42 Morocha1 bluetoothd[914]: Failed to init deviceinfo plugin
May 10 09:08:42 Morocha1 bluetoothd[914]: Failed to init proximity plugin
May 10 09:08:42 Morocha1 bluetoothd[914]: Failed to init time plugin
May 10 09:08:42 Morocha1 bluetoothd[914]: Failed to init alert plugin
May 10 09:08:42 Morocha1 bluetoothd[914]: Failed to init thermometer plugin
May 10 09:08:42 Morocha1 kernel: [   23.832313] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 10 09:08:42 Morocha1 kernel: [   23.832316] Bluetooth: BNEP filters: protocol multicast
May 10 09:08:42 Morocha1 kernel: [   23.832322] Bluetooth: BNEP socket layer initialized
May 10 09:08:42 Morocha1 bluetoothd[914]: Failed to init gatt_example plugin
May 10 09:08:42 Morocha1 bluetoothd[914]: Bluetooth Management interface initialized

[claydoh]

Is there a keyboard combo (or physical switch) that turns Bluetooth off and on? It might be worth checking that out.

My laptop has a switch, and bt/wifi all completely disappear from lsu sb etc when switched off.

[nicko02338]

Is there a keyboard combo (or physical switch) that turns Bluetooth off and on? It might be worth checking that out.

My laptop has a switch, and bt/wifi all completely disappear from lsu sb etc when switched off.

Yes, there is a keyboard combo that turns bluetooth off, but it deoesn't work on Kubuntu as it works in Windows. It is quite rarely for me this situation,

After receive message from Claydoh, I did this:

1. Turn off the laptop and verified bluetooth and wireless PCB (both are together on the same PCB) in order to confirm if they are connect fine. It was OK.
2. I have dual boot on my computer with Windows 7 Home Premium. I booted with Windows and Bluetooth wasn't enabled, but It was easily fixed enabling it with "Enable/disable wireless" key. Now bluetooth is OK and ready to use on Windows.
3. Finally I back to Kubuntu. As soon as it booted up, bluetooth system were enabled and working fine as it should be from the beginning.

Conclusions:

• It seems windows have the priority over bluetooth driver, because if it is not enable on Windows it is not recognised on Kubuntu.
• On Windows, "Enable/Disable wireless" key, shows a windows where I can switch off/on wi-fi and bluetooth system. But on kubuntu, same key just switch on/off wifi, bluetooth is always enable (from now) unless I disable from right click menu over bluetooth icon near the clock.

Questions:

1. Do you think is there any way to change this situation?
2. Could it be possible Windows has priority over determined drivers?

[claydoh]

I think it is the lack of the key combo functioning properly in Linux, perhaps? What model is your laptop?

[nicko02338]

I think it is the lack of the key combo functioning properly in Linux, perhaps? What model is your laptop?

I have a Lenovo Y480.
Have you ever seen that Windows have the priority on some drivers over other OSs?

[claydoh]

No, but I have heard of people needing to be in Windows to at least initially turn on wifi before it would be used in Linux

[SteveRiley]

This isn't a "priority over drivers" issue. The key combination that enables/disables the hardware is not being recognized by the kernel or by Udev. You might want post a question on the Lenovo forum to see if anyone there has some ideas.

[nicko02338]

This isn't a "priority over drivers" issue. The key combination that enables/disables the hardware is not being recognized by the kernel or by Udev. You might want post a question on the Lenovo forum to see if anyone there has some ideas.

Thank you. That answer my next question that would be, what is the next step?.

I know you have a lot of experience on OS, then I would like to know your opinion about this:
What could happen if there I wouldn't have dual boot on my laptop?. I mean, this time I could went to Windows to enable bluetooth driver and the issue was fixed, but if I hadn't Windows installed, do you think could be any way to turn the driver on?.

(Sorry if I am asking too much, but this is my manner to contribute to Kubuntu been a better OS.)