Unable to use bluetooth [No default controller aviable]

Aryeth_ · 2021-10-18 07:41:26

Hello !

I tried today to use bluetoothctl to connect a device, however I am unable to use it, as it returns

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

I've checked lsusb, which returns me :

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device
Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
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

Also, by using lspci, I've determined that my network controller was :

00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi

I looked for answers online, sadly however no posts helped me, so I figured out I'd write one myself.

Also, as extra info : the machine is my laptop, and not a VM. I also used bluetooth before on another installation of arch with cinnamon, and it worked fine. The OS before that was Windows and it worked fine too.

Thanks a lot in advance for your help !
(P.S. as this being my first post on here, please tell me if I can write my post better / if there is any problem ^_^)

V1del · 2021-10-18 07:42:45

Check kernel logs on whether there are any issues initialising btusb. Is the bluetooth.service started/enabled?

Aryeth_ · 2021-10-18 07:52:44

Thanks for the quick answer,
I am not really sure what to look at in journalctl as there is nothing concerning btusb ^^'
Is there a command to search directly btusb in it ?
As for bluetooth.service, I enabled and started it, and the status is :

# systemctl status bluetooth.service 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Mon 2021-10-18 09:10:26 CEST; 41min ago
       Docs: man:bluetoothd(8)
   Main PID: 394 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18872)
     Memory: 2.1M
        CPU: 9ms
     CGroup: /system.slice/bluetooth.service
             └─394 /usr/lib/bluetooth/bluetoothd

Oct 18 09:10:26 ArcheBtw systemd[1]: Starting Bluetooth service...
Oct 18 09:10:26 ArcheBtw bluetoothd[394]: Bluetooth daemon 5.62
Oct 18 09:10:26 ArcheBtw systemd[1]: Started Bluetooth service.
Oct 18 09:10:26 ArcheBtw bluetoothd[394]: Starting SDP server
Oct 18 09:10:26 ArcheBtw bluetoothd[394]: Bluetooth management interface 1.21 initialized

little update, after searching in my journal, the only btusb related line was

-- Boot 0cfa741b0bdb4f078584b414b4bc1ba0 --
Oct 18 08:11:31 ArcheBtw kernel: usbcore: registered new interface driver btusb

Last edited by Aryeth_ (2021-10-18 11:18:12)

Ferdinand · 2021-10-18 16:45:31

bluetoothctl is an interactive application. Note the changed prompt. Try typing the command help; it will list available commands.
You can get more help on the commands by typing help after the command name.
Try the commands list and select.
More info in the wiki:
https://wiki.archlinux.org/title/Blueto … _available

Last edited by Ferdinand (2021-10-18 16:47:11)

Aryeth_ · 2021-10-19 14:05:49

Hello,
thanks for taking the time to help me ^_^
I tried the solutions listed on the wiki, and neither of the two solution proposed worked sadly.
I looked a bit on this forum, and found a post with a similar issue to me :
https://bbs.archlinux.org/viewtopic.php?id=171357

however, when trying to

sudo hciconfig hci0 down

I get :

Can't down device hci0: Device or resource busy (16)

I dont really know what to try anymore...
Anything else that could help ?

Last edited by Aryeth_ (2021-10-19 14:06:55)

Ferdinand · 2021-10-19 16:02:55

From what you've said so far it looks like it should work; it loads btusb fine and the bluetooth.service is running.

Try to start bluetoothctl again, and issue the command "list".
If you get anything then "select" that - and if it doesn't find any controllers try "power on" and list again.

If it still doesn't work try exiting bluetoothctl and type "rfkill list" to see if it's blocked somehow.

Also, depending on your DE there's a number of front-ends that can be worth checking out.
I use Xfce and think Blueman works well. I suspect things are all right with you, it's just that the device isn't turned on or is blocked.

Aryeth_ · 2021-10-20 09:19:09

Hi, thanks for the answer. I tried what you said, which gave me theses results :

$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# power on
No default controller available
[bluetooth]# exit

$ rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

As for a DE, since I'm using bspwm, I dont really have any native bluetooth gui.
I installed blueberry that said, since I was on cinnamon before and that it worked well, but it doesnt detect any devices and displays an error when I turn on and off the bluetooth.
I dont really understand either why it isnt working since it's said that the service runs but no agent appears in bluetoothctl...

Ferdinand · 2021-10-22 16:59:26

Hm. I'm a bit at a loss here.
The AX201 Bluetooth adapter is supported by the kernel since version 5.2, I read somewhere, so you should be good.
There's a long list of troubleshooting tips on the bluetooth wiki page, but I guess you've been through that already?
Also check out the talk page, there's a discussion there with a procedure that might be worth trying:
https://wiki.archlinux.org/title/Talk:B … nd_hcitool
Also also, do you have linux-firmware and microcode installed?
And, unless you solved it, share your journalctl -b - there must be something in there.

Last edited by Ferdinand (2021-10-22 17:04:14)

Aryeth_ · 2021-10-29 06:42:25

Hello again,
sorry for the late answer, had a lot of work this week ^^'
I looked a bit further in your propositions and actually found something (I think);
While looking trough the bluetooth troubleshoot page, I tried to do

 hcitool lescan

(which needed sudo privileges too), and the scan actually worked. It is detecting some bluetooth devices yet blueberry is still bugged and bluetoothctl still doesnt work.
I wonder if maybe the problem is only a privilege problem..?
However Im not really sure how to fix it :-/
Thanks for your help !

Edit : This is my journalctl

Last edited by Aryeth_ (2021-10-29 06:48:27)

Kastakin · 2021-10-30 10:02:55

Hi, I'm encountering a similar issue on my new Lenovo P14s Gen2 AMD, the bluetooth behavior seems quite erratic: most of the time I get the same issue that Aryeth_ reported, other times bluetooth adapter is recognized but it goes inactive if not used for a while with the only way to have it working again being restarting the bluetooth service.

I've got bot linux-firmware and amd-ucode installed and properly configured with EFISTUB.

My

journalctl -b

doesn't seem particular informative. The only real issue that seem to pop-out is relative to

hci0

with the following lines appearing if bluetooth isn't recognized:

Oct 30 11:36:04 lorenzoP14s kernel: Bluetooth: hci0: Wrong op received 6 expected 1
Oct 30 11:36:04 lorenzoP14s kernel: Bluetooth: hci0: Failed to send wmt patch dwnld (-5)
Oct 30 11:36:04 lorenzoP14s kernel: Bluetooth: hci0: Wrong op received 1 expected 6
Oct 30 11:36:04 lorenzoP14s kernel: Bluetooth: hci0: Failed to send wmt func ctrl (-5)

If more info are needed I'm more then willing to source them!

EDIT: in my case the problem seems originating from having the WiFi + BT (Which in my case it's a Mediatek 7921e) card not loading correctly... I don't know if this is something that could be fixed by a new kernel update but I haven't found any particular info around

Last edited by Kastakin (2021-10-30 12:13:05)

Ferdinand · 2021-11-01 17:00:29

Well, it all looks good to me, so it's weird.

You've got a few log entries:

Oct 29 08:08:03 ArcheBtw kernel: Bluetooth: hci0: command 0xfc1e tx timeout
...
Oct 29 08:35:44 ArcheBtw kernel: Bluetooth: hci0: command 0x200b tx timeout
Oct 29 08:35:46 ArcheBtw kernel: Bluetooth: hci0: command 0x200c tx timeout
...
Oct 29 08:36:29 ArcheBtw kernel: Bluetooth: hci0: command 0x200c tx timeout

Searching, I found this issue, concerning power managers causing issues:
https://bbs.archlinux.org/viewtopic.php?id=226312

Might be worth checking out?

Last edited by Ferdinand (2021-11-01 17:00:50)

Aryeth_ · 2021-12-05 17:06:25

Hello everyone,

First off, sorry for coming back after such a long time.
Apparently the problem was caused by a problem in the network card (apparently a pretty frequent one on the Asus G17), and I sent back the laptop to repair.

Thanks a lot for your help,

Aryeth_

(P.S. how do I mark the subject resolved ?)

Last edited by Aryeth_ (2021-12-05 17:07:10)

Arch Linux

#1 2021-10-18 07:41:26

Unable to use bluetooth [No default controller aviable]

#2 2021-10-18 07:42:45

Re: Unable to use bluetooth [No default controller aviable]

#3 2021-10-18 07:52:44

Re: Unable to use bluetooth [No default controller aviable]

#4 2021-10-18 16:45:31

Re: Unable to use bluetooth [No default controller aviable]

#5 2021-10-19 14:05:49

Re: Unable to use bluetooth [No default controller aviable]

#6 2021-10-19 16:02:55

Re: Unable to use bluetooth [No default controller aviable]

#7 2021-10-20 09:19:09

Re: Unable to use bluetooth [No default controller aviable]

#8 2021-10-22 16:59:26

Re: Unable to use bluetooth [No default controller aviable]

#9 2021-10-29 06:42:25

Re: Unable to use bluetooth [No default controller aviable]

#10 2021-10-30 10:02:55

Re: Unable to use bluetooth [No default controller aviable]

#11 2021-11-01 17:00:29

Re: Unable to use bluetooth [No default controller aviable]

#12 2021-12-05 17:06:25

Re: Unable to use bluetooth [No default controller aviable]

Board footer