No default controller available bluetooth ubuntu

I have problem with Bluetooth on my laptop, everything worked on windows but doesnt work on Linux. Here is outputs of a few commands:

# rfkill list all 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no

# bluetoothctl [bluetooth]# list [bluetooth]# show No default controller available [bluetooth]# agent on Agent registered [bluetooth]# list [bluetooth]# power on No default controller available [bluetooth]#

# lspci | grep -i blue (nothing)

If any other outputs required, I will add them here. Could someone help to solve this issue?

Last edited by brack11 (2017-11-17 16:39:18)

#2 2017-11-15 10:20:25

Re: [SOLVED] Bluetooth «No default controller available»

What does this command say?

systemctl status bluetooth

sudo systemctl start bluetooth

#3 2017-11-15 11:10:53

Re: [SOLVED] Bluetooth «No default controller available»

$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Wed 2017-11-15 11:28:20 CET; 35min ago Docs: man:bluetoothd(8) Main PID: 10073 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─10073 /usr/lib/bluetooth/bluetoothd

I have followed https://wiki.debian.org/BluetoothUser but nothing helped. When I try to power on bluetooth at bluetoothctl I get «No default controller available» and https://wiki.debian.org/BluetoothUser doesnt describe this error

#4 2017-11-15 11:58:41

iMBeCil WAAAT? From: Edrychwch o’ch cwmpas Registered: 2015-09-29 Posts: 767

Re: [SOLVED] Bluetooth «No default controller available»

Furthermore: what is the laptop model?

Finally: please chekc in BIOS (or UEFI) that the Bluetooth is enabled.

Postpone all your duties; if you die, you won’t have to do them ..

#5 2017-11-15 14:21:16

Re: [SOLVED] Bluetooth «No default controller available»

$ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 Ethernet controller: Qualcomm Atheros AR8162 Fast Ethernet (rev 10) 02:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)

As I understand Network controller also serves Bluetooth. It is laptop Lenovo g580

Bluetooth in bios is fine because I didnt change anything there since I install linux over windows, and bluetooth was working in windows

EDIT: I have checked the Bios and didn find any setting for Bluetooth

Last edited by brack11 (2017-11-15 14:31:50)

#6 2017-11-15 15:56:40

Re: [SOLVED] Bluetooth «No default controller available»

02:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)

Which kernel driver is in use for that device (`lspci -k` will show this information)?

I think it should be the wl driver so if it’s anything else then that may be your problem.

“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

#7 2017-11-15 21:03:25

iMBeCil WAAAT? From: Edrychwch o’ch cwmpas Registered: 2015-09-29 Posts: 767

Re: [SOLVED] Bluetooth «No default controller available»

Postpone all your duties; if you die, you won’t have to do them ..

#8 2017-11-16 09:33:50

Re: [SOLVED] Bluetooth «No default controller available»

02:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)

Which kernel driver is in use for that device (`lspci -k` will show this information)?

I think it should be the wl driver so if it’s anything else then that may be your problem.

That is correct, it is the wl driver and I have followed https://wiki.debian.org/wl and got the message

broadcom-sta-dkms is already the newest version.

so, I assume everything should work but it’s not

#9 2017-11-16 10:31:05

iMBeCil WAAAT? From: Edrychwch o’ch cwmpas Registered: 2015-09-29 Posts: 767

Re: [SOLVED] Bluetooth «No default controller available»

As I understand Network controller also serves Bluetooth. It is laptop Lenovo g580

Bluetooth in bios is fine because I didnt change anything there since I install linux over windows, and bluetooth was working in windows

1) Check if WiFi is enabled in BIOS/UEFI

Postpone all your duties; if you die, you won’t have to do them ..

#10 2017-11-16 13:33:08

Re: [SOLVED] Bluetooth «No default controller available»

1) Wifi is enabled in BIOS
2) UEFI is disabled Legacy mode Enabled
no bluetooth.

#11 2017-11-16 14:07:08

iMBeCil WAAAT? From: Edrychwch o’ch cwmpas Registered: 2015-09-29 Posts: 767

Re: [SOLVED] Bluetooth «No default controller available»

^I’m sorry, but i’m out of ideas, except to try to google it.

For exaple: I just checked on my laptop, the bluetooth is listed as usb, not pci. Please post output of:

Furthermore, check what kernel module you are using for bluetooth:

$ lsmod | grep blue $ lsmod | grep wl

(perhaps, wrong one must be blacklisted).

See if ‘hcitool’ can find your controller, after you have installed wl:

Postpone all your duties; if you die, you won’t have to do them ..

#12 2017-11-16 14:15:45

Re: [SOLVED] Bluetooth «No default controller available»

$ lsusb Bus 004 Device 003: ID 5986:0295 Acer, Inc Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 003 Device 004: ID 105b:e065 Bus 003 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ lsmod | grep blue bluetooth 374455 5 bnep 6lowpan_iphc 16588 1 bluetooth rfkill 18867 5 cfg80211,ideapad_laptop,bluetooth crc16 12343 2 ext4,bluetooth

$ lsmod | grep wl wl 6299053 0 cfg80211 413828 1 wl

#13 2017-11-16 15:00:10

iMBeCil WAAAT? From: Edrychwch o’ch cwmpas Registered: 2015-09-29 Posts: 767

Re: [SOLVED] Bluetooth «No default controller available»

^This is your bluetooth device:

$ lsusb . Bus 003 Device 004: ID 105b:e065 .

Try to google ‘linux 105b:e065’ and you will see lots of problems.

The solution seems to be to get newer kernel. I’m not in position to check it, but if you are running stock BunsenLabs then you can backport the newer (4.9) kernel with apt-get (HoaS, somebody, help with this!, or see this post), and probably get the bluetooth working.

As a check, you may try to get, for example, some live distro with newer kernel (e.g. based on debian stretch), and see if bluetooth works on it.

Postpone all your duties; if you die, you won’t have to do them ..

#14 2017-11-16 20:16:13

Re: [SOLVED] Bluetooth «No default controller available»

Yes, this guide can be used to install a 4.9-series kernel:

some live distro with newer kernel (e.g. based on debian stretch), and see if bluetooth works on it.

I have a «SharpBang» live ISO image that is based on Debian stretch:

@OP, perhaps see if your bluetooth device works with that image?

“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

#15 2017-11-17 11:30:35

Re: [SOLVED] Bluetooth «No default controller available»

Ok, I used this manual to get to 4.9 kernel: https://forums.bunsenlabs.org/viewtopic.php?id=2445 now böuetooth is kinda recognizable

# hcitool dev Devices: hci0 B8:76:3F:A1:8E:48

# dmesg | grep tooth [ 16.535782] Bluetooth: Core ver 2.22 [ 16.535797] Bluetooth: HCI device and connection manager initialized [ 16.535800] Bluetooth: HCI socket layer initialized [ 16.535802] Bluetooth: L2CAP socket layer initialized [ 16.535811] Bluetooth: SCO socket layer initialized [ 18.667548] Bluetooth: hci0 command 0x1001 tx timeout [ 25.228241] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 25.228246] Bluetooth: BNEP filters: protocol multicast [ 25.228253] Bluetooth: BNEP socket layer initialized [ 26.859854] Bluetooth: hci0: BCM: Reading local version info failed (-110) [ 540.511028] Bluetooth: RFCOMM TTY layer initialized [ 540.511035] Bluetooth: RFCOMM socket layer initialized [ 540.511044] Bluetooth: RFCOMM ver 1.11 [ 720.594183] Bluetooth: hci0 command 0x1001 tx timeout [ 728.690408] Bluetooth: hci0: BCM: Reading local version info failed (-110) [ 867.332140] Bluetooth: hci0: BCM: chip id 70 [ 867.348132] Bluetooth: hci0: Yury-PC [ 867.348136] Bluetooth: hci0: BCM (001.001.011) build 0000 [ 867.381619] bluetooth hci0: firmware: failed to load brcm/BCM.hcd (-2) [ 867.381628] bluetooth hci0: Direct firmware load for brcm/BCM.hcd failed with error -2 [ 867.381633] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found [ 869.398913] Bluetooth: hci0 command 0x1003 tx timeout

# lsusb Bus 002 Device 003: ID 5986:0295 Acer, Inc 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 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 105b:e065 Foxconn International, Inc. BCM43142A0 Bluetooth module Bus 001 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical 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

# rfkill list all 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no

Last edited by brack11 (2017-11-17 11:35:52)

Источник

Bluetoothctl: No default controller available, despite being unblocked

I’m having issues connecting my Logitech K810 Bluetooth keyboard in Debian Jessie with BlueZ version 5.23-1, kernel 3.16.0-4. The keyboard works fine most of the time but sometimes it doesn’t work at all and bluetoothctl gives me the error that the controller is unavailable. When this occurs, hciconfig still recognizes the device and I get this output:

# hciconfig hci0 up # hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 40:2C:F4:68:02:CA ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21820 acl:1132 sco:0 events:68 errors:0 TX bytes:1182 acl:11 sco:0 commands:53 errors:0

[bluetooth]# power on No default controller available [bluetooth]# scan on No default controller available

Rebooting or sometimes suspending/resuming fixes the issue: bluetoothctl will again recognize both the controller and the keyboard which works again. Bluetooth is consistently hard and soft unblocked according to rfkill . The relevant output from lspci -v , I guess would be this:

03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at f0400000 (64-bit, non-prefetchable) [size=8K] Capabilities: Kernel driver in use: iwlwifi

I didn’t have this problem with the same hardware in Debian Wheezy. What could it be the bluetooth controller to be unavailable at times?

Источник