Arch Linux

nodauf

Member

Registered: 2016-06-16

Posts: 9

Bluetooth Issue: "No default controller available"

Hello all,

I tried to add the bluetooth on my laptop. But I have several issue.
Here what I do;

Package installed:

extra/bluez 5.40-1
    Daemons for the bluetooth protocol stack
extra/bluez-firmware 1.2-8
    Firmwares for Broadcom BCM203x and STLC2300 Bluetooth chips
extra/bluez-hid2hci 5.40-1
    Put HID proxying bluetooth HCI's into HCI mode
extra/bluez-libs 5.40-1
    Deprecated libraries for the bluetooth protocol stack
extra/bluez-utils 5.40-1
    Development and debugging utilities for the bluetooth protocol stack
extra/gnome-bluetooth 3.20.0-1
    The GNOME Bluetooth Subsystem

Before evreything:

modprobe btusb
systemctl start bluetooth

With the command dmesg, I see the bluetooth:

[ 1435.113805] Bluetooth: Core ver 2.21
[ 1435.113824] Bluetooth: HCI device and connection manager initialized
[ 1435.113827] Bluetooth: HCI socket layer initialized
[ 1435.113829] Bluetooth: L2CAP socket layer initialized
[ 1435.113833] Bluetooth: SCO socket layer initialized
[ 1461.096170] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1461.096175] Bluetooth: BNEP filters: protocol multicast
[ 1461.096180] Bluetooth: BNEP socket layer initialized

And lsmod:

bluetooth             454656  11 bnep,btbcm,btrtl,btusb,btintel
rfkill                 20480  6 cfg80211,bluetooth
crc16                  16384  2 ext4,bluetooth

But nothing in lsub

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

When I start bluetoothctl:

# bluetoothctl 
[bluetooth]# agent KeyboardOnly 
Agent registered
[bluetooth]# default-agent 
Default agent request successful
[bluetooth]# scan on
No default controller available

And rfkill list return nothing.

I really need help, please. I don't know what can I do.

Thanks
Nodauf

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

Back up a few steps.   This is a USB adapter.  Is integral to the system, or can you plug and unplug it?
Assuming it is a plugable device,  what gets added to the journal when you connect the device.  I am not encouraged by the device not showing up in the output of lsusb

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

Thank you for your reply.
It's not a USB adapter. It's integral to the system.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

What is the output of lspci  ?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "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/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series 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/C210 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01)
03:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)

lspci | grep -i blu ==> nothing

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

Okay, your Bluetooth comes from the Centrino Wireless-N 2230.

What is the output of lspci -k -s 02:00.0

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

Here the output:

02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
	Subsystem: Intel Corporation Centrino Wireless-N 2230 BGN
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

That looks about right.  Working from memory, that is the driver on my HP Envy which uses the Intel 3160 system (also a combo Bluetooth/wifi).

Inside the bluetoothctl shell, what is the response to power on   ?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

The output is the same as scan on: "No default controller available"

I don't no if it's important but I use the wifi (I've also tried to disconnect my wifi).

jeremy31

Member

Registered: 2015-11-01

Posts: 149

Re: Bluetooth Issue: "No default controller available"

Did bluetooth work before on a different OS?  No bluetooth is being found and with Intel wifi it should be listed in lsusb results.  Not all wifi cards have bluetooth.  This could be a timing issue with xhci being enabled for USB 3.0 support.

Is it is easy to access the wifi card, look at the sticker on it.  Does it have a WFM and BDM on the sticker?  WFM is the wifi MAC and BDM is the bluetooth MAC

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

...No bluetooth is being found and with Intel wifi it should be listed in lsusb results.  Not all wifi cards have bluetooth.  This could be a timing issue with xhci being enabled for USB 3.0 support..

http://www.intel.com/content/dam/www/pu … -brief.pdf

That card is a PCI-e (2 lane, I think) combo WiFi and Bluetooth 4.0 (including BLE)
USB is not in the picture.

Edit:
http://www.intel.com/content/www/us/en/ … 05511.html

Note that the correct driver is being pulled in.

Last edited by ewaller (2016-06-16 21:58:25)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

Yes, the bluetooth works on Windows.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

Okay, how about the output of journalctl -b | grep Bluetooth
?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

Very strange. I've start my laptop with "share connection" on USB of my smartphone and the bluetooth is enable without any action.
rfkill list see hci0,...

the output of the command journalctl -b | grep Bluetooth

Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
juin 17 00:02:47 flo-arch systemd[1003]: Starting Bluetooth OBEX service...
juin 17 00:02:48 flo-arch systemd[1003]: Started Bluetooth OBEX service.
juin 17 00:03:21 flo-arch org.gnome.Shell.desktop[1067]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000f (Bluetooth)
juin 17 00:03:21 flo-arch org.gnome.Shell.desktop[1067]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000f (Bluetooth)
juin 17 00:03:45 flo-arch org.gnome.Shell.desktop[1067]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x240000f (Bluetooth)

It's the output but it's works. Tomorrow, I will post the output without starting the laptop with "share connection" of my smartphone.

Do you have an idea of this issue?

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

Oh, wait.  Your user is not in the group wheel.  First, that means you see a truncated journal.  It might also mean you cannot get access to the Bluetooth stuff (not sure about that, though)
Try adding yourself to wheel, log out and back in and try it.  Also, do you not have sudo set up?  I highly recommend it.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

You are right. When I need to execute some debug commands, I execute in root with su. Here I forgot.

Here the entire output:

juin 17 07:52:03 flo-arch kernel: Bluetooth: Core ver 2.21
juin 17 07:52:03 flo-arch kernel: Bluetooth: HCI device and connection manager initialized
juin 17 07:52:03 flo-arch kernel: Bluetooth: HCI socket layer initialized
juin 17 07:52:03 flo-arch kernel: Bluetooth: L2CAP socket layer initialized
juin 17 07:52:03 flo-arch kernel: Bluetooth: SCO socket layer initialized
juin 17 07:52:14 flo-arch systemd[1]: Starting Bluetooth service...
juin 17 07:52:15 flo-arch bluetoothd[429]: Bluetooth daemon 5.40
juin 17 07:52:15 flo-arch systemd[1]: Started Bluetooth service.
juin 17 07:52:15 flo-arch systemd[1]: Reached target Bluetooth.
juin 17 07:52:15 flo-arch kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
juin 17 07:52:15 flo-arch kernel: Bluetooth: BNEP filters: protocol multicast
juin 17 07:52:15 flo-arch kernel: Bluetooth: BNEP socket layer initialized
juin 17 07:52:15 flo-arch bluetoothd[429]: Bluetooth management interface 1.12 initialized
juin 17 07:53:38 flo-arch kernel: Bluetooth: RFCOMM TTY layer initialized
juin 17 07:53:38 flo-arch kernel: Bluetooth: RFCOMM socket layer initialized
juin 17 07:53:38 flo-arch kernel: Bluetooth: RFCOMM ver 1.11
juin 17 07:53:32 flo-arch systemd[986]: Starting Bluetooth OBEX service...
juin 17 07:53:32 flo-arch systemd[986]: Started Bluetooth OBEX service.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,214

Re: Bluetooth Issue: "No default controller available"

Interesting, yours is very similar to mine, but yours never instantiates the /dev/hci0 device node

ewaller@turing/home/ewaller % journalctl -b | grep Bluetooth
Jun 15 19:21:56 turing kernel: Bluetooth: Core ver 2.21
Jun 15 19:21:56 turing kernel: Bluetooth: HCI device and connection manager initialized
Jun 15 19:21:56 turing kernel: Bluetooth: HCI socket layer initialized
Jun 15 19:21:56 turing kernel: Bluetooth: L2CAP socket layer initialized
Jun 15 19:21:56 turing kernel: Bluetooth: SCO socket layer initialized
Jun 15 19:21:56 turing kernel: Bluetooth: hci0: read Intel version: 3707100100012d0d00
Jun 15 19:21:56 turing systemd[1]: Reached target Bluetooth.
Jun 15 19:21:56 turing kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
Jun 15 19:21:56 turing kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Jun 16 13:11:49 turing systemd[1]: Starting Bluetooth service...
Jun 16 13:11:49 turing bluetoothd[10324]: Bluetooth daemon 5.40
Jun 16 13:11:49 turing systemd[1]: Started Bluetooth service.
Jun 16 13:11:49 turing kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jun 16 13:11:49 turing kernel: Bluetooth: BNEP filters: protocol multicast
Jun 16 13:11:49 turing kernel: Bluetooth: BNEP socket layer initialized
Jun 16 13:11:49 turing bluetoothd[10324]: Bluetooth management interface 1.12 initialized
Jun 16 13:11:50 turing kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 16 13:11:50 turing kernel: Bluetooth: RFCOMM socket layer initialized
Jun 16 13:11:50 turing kernel: Bluetooth: RFCOMM ver 1.11
ewaller@turing/home/ewaller %

Do you have core/linux-firmware installed?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

nodauf

Member

Registered: 2016-06-16

Posts: 9

Re: Bluetooth Issue: "No default controller available"

Yes, I have.
It's very strange. It's ok now. I've do nothing. At each reboot, the bluetooth is enable.

dcolceag

Member

Registered: 2017-06-22

Posts: 1

Re: Bluetooth Issue: "No default controller available"

This happens to me only after waking up. Put system to sleep/suspend, wake up -> No default controller found. I have AutoEnable=true.
Bluetooth can be found after restart.

I started the bluetooth service and searched for devices.

Output from bt-device --list

**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
Aborted

I've done rfkill block bluetooth , rfkill unblock bluetooh, started bluetooth service. Output from syslog:

Jun 22 16:35:45 T460 systemd[1]: Started Bluetooth service.
Jun 22 16:36:26 T460 kernel: [25393.390715] usb 1-7: USB disconnect, device number 5
Jun 22 16:36:26 T460 URfkill[858]: device_changed_cb: tpacpi_bluetooth_sw
Jun 22 16:36:26 T460 systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 22 16:36:26 T460 URfkill[858]: removing killswitch idx 3 hci0
Jun 22 16:36:26 T460 systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 22 16:36:26 T460 systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Jun 22 16:36:26 T460 systemd[1]: Stopped target Bluetooth.
Jun 22 16:36:33 T460 URfkill[858]: device_changed_cb: tpacpi_bluetooth_sw
Jun 22 16:36:33 T460 systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 22 16:36:33 T460 systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 22 16:36:33 T460 kernel: [25400.694282] usb 1-7: new full-speed USB device number 14 using xhci_hcd
Jun 22 16:36:33 T460 kernel: [25400.836142] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b
Jun 22 16:36:33 T460 kernel: [25400.836149] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 22 16:36:33 T460 URfkill[858]: adding killswitch type 2 idx 4 soft 0 hard 0
Jun 22 16:36:33 T460 URfkill[858]: Setting device 4 (BLUETOOTH) to unblocked
Jun 22 16:36:33 T460 URfkill[858]: set_soft: Setting BLUETOOTH to unblocked
Jun 22 16:36:33 T460 kernel: [25400.842351] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Jun 22 16:36:33 T460 kernel: [25400.849426] Bluetooth: hci0: Device revision is 5
Jun 22 16:36:33 T460 kernel: [25400.849432] Bluetooth: hci0: Secure boot is enabled
Jun 22 16:36:33 T460 kernel: [25400.849436] Bluetooth: hci0: OTP lock is enabled
Jun 22 16:36:33 T460 kernel: [25400.849439] Bluetooth: hci0: API lock is enabled
Jun 22 16:36:33 T460 kernel: [25400.849443] Bluetooth: hci0: Debug lock is disabled
Jun 22 16:36:33 T460 kernel: [25400.849449] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jun 22 16:36:33 T460 kernel: [25400.850685] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Jun 22 16:36:35 T460 kernel: [25402.532169] Bluetooth: hci0: Waiting for firmware download to complete
Jun 22 16:36:35 T460 kernel: [25402.532293] Bluetooth: hci0: Firmware loaded in 1652329 usecs
Jun 22 16:36:35 T460 kernel: [25402.532431] Bluetooth: hci0: Waiting for device to boot
Jun 22 16:36:35 T460 kernel: [25402.543301] Bluetooth: hci0: Device booted in 10649 usecs
Jun 22 16:36:35 T460 kernel: [25402.543359] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Jun 22 16:36:35 T460 kernel: [25402.547390] Bluetooth: hci0: Applying Intel DDC parameters completed
Jun 22 16:36:35 T460 bluetoothd[2482]: Failed to obtain handles for "Service Changed" characteristic
Jun 22 16:36:35 T460 bluetoothd[2482]: Not enough free handles to register service
Jun 22 16:36:35 T460 bluetoothd[2482]: Error adding Link Loss service
Jun 22 16:36:35 T460 bluetoothd[2482]: Not enough free handles to register service
Jun 22 16:36:35 T460 bluetoothd[2482]: message repeated 2 times: [ Not enough free handles to register service]
Jun 22 16:36:35 T460 bluetoothd[2482]: Current Time Service could not be registered
Jun 22 16:36:35 T460 bluetoothd[2482]: gatt-time-server: Input/output error (5)
Jun 22 16:36:35 T460 bluetoothd[2482]: Not enough free handles to register service
Jun 22 16:36:35 T460 systemd[1]: Reached target Bluetooth.
Jun 22 16:36:35 T460 bluetoothd[2482]: Not enough free handles to register service
Jun 22 16:36:35 T460 bluetoothd[2482]: Sap driver initialization failed.
Jun 22 16:36:35 T460 bluetoothd[2482]: sap-server: Operation not permitted (1)
Jun 22 16:36:35 T460 bluetoothd[2482]: Endpoint registered: sender=:1.91 path=/MediaEndpoint/A2DPSource
Jun 22 16:36:35 T460 bluetoothd[2482]: Endpoint registered: sender=:1.91 path=/MediaEndpoint/A2DPSink
Jun 22 16:36:41 T460 systemd[1]: Started Bluetooth service.

Okay, the

 
rfkill block bluetooh 
rfkill unblock bluetooth
sudo systemctl restart bluetooth

did the trick.

Last edited by dcolceag (2017-06-22 13:40:42)

sylv3r

Member

Registered: 2017-08-17

Posts: 3

Re: Bluetooth Issue: "No default controller available"

Same problem here on a Razer Blade Stealth Late 2016.

Unfortunately the rfkill trick doesn't work for me.

I noticed the bluetooth firmware couldn't be loaded randomly after some system suspends (see the last line)

Aug 16 22:47:29 saiph kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin
Aug 16 22:47:29 saiph kernel: Bluetooth: hci0: QCA: patch rome 0x302 build 0x138, firmware rome 0x302 build 0x111
Aug 16 22:47:29 saiph kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
Aug 17 10:50:12 saiph kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin
Aug 17 10:50:12 saiph kernel: Bluetooth: hci0: QCA: patch rome 0x302 build 0x138, firmware rome 0x302 build 0x111
Aug 17 10:50:12 saiph kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
Aug 17 11:09:10 saiph kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin
Aug 17 11:09:10 saiph kernel: Bluetooth: hci0: QCA: patch rome 0x302 build 0x138, firmware rome 0x302 build 0x111
Aug 17 11:09:10 saiph kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
Aug 17 11:21:11 saiph kernel: Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-11)

In this case, the only thing to do (else than restarting your whole system), is to hot remove and reload the kernel module

rmmod btusb

modprobe btusb

And here you are, back in the game :

Aug 17 14:33:16 saiph kernel: usbcore: registered new interface driver btusb
Aug 17 14:33:16 saiph kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin
Aug 17 14:33:16 saiph kernel: Bluetooth: hci0: QCA: patch rome 0x302 build 0x138, firmware rome 0x302 build 0x111
Aug 17 14:33:16 saiph systemd[1]: Starting Load/Save RF Kill Switch Status...
Aug 17 14:33:16 saiph systemd[1]: Started Load/Save RF Kill Switch Status.
Aug 17 14:33:16 saiph kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
Aug 17 14:33:17 saiph bluetoothd[30229]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSource
Aug 17 14:33:17 saiph bluetoothd[30229]: Endpoint registered: sender=:1.35 path=/MediaEndpoint/A2DPSink

antipovden

Member

Registered: 2019-04-10

Posts: 1

Re: Bluetooth Issue: "No default controller available"

I am sorry for resurrecting this dead topic, but I have just faced the same problem as TC. I did not see my hci0 device at all (neither in rfkill, nor in bleutoothctl). The root of the problem was that my bluetooth adapter was disabled in BIOS. In some sense this topic helped me discover this:
https://bbs.archlinux.org/viewtopic.php … 9#p1814689

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,287

Re: Bluetooth Issue: "No default controller available"

Thanks for sharing, however it is unlikely that the OP still runs into the same issue.

Closing.

Last edited by V1del (2019-04-10 15:51:22)