You are not logged in.

#1 2021-07-09 20:26:54

akshansh2000
Member
From: India
Registered: 2020-11-07
Posts: 8
Website

[SOLVED] bluetoothctl: No default controller available

I am getting a No default controller available error while using bluetoothctl:

[akshansh2000@akshansh-arch ~]$ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]#

uname -r: 5.12.14-arch1-1
linux-firmware: 20210511.7685cf4-1

  • I am already a part of the bluetooth group

  • rfkill list all shows hci0: Bluetooth as unblocked

  • sudo bluetoothctl fails to recognise the controller

  • both bluez and bluez-utils are installed

The bluetooth service is enabled. Here is the output of systemctl status bluetooth just after boot:

* bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Sat 2021-07-10 07:05:17 IST; 12min ago
       Docs: man:bluetoothd(8)
   Main PID: 558 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18466)
     Memory: 2.9M
        CPU: 12ms
     CGroup: /system.slice/bluetooth.service
             `-558 /usr/lib/bluetooth/bluetoothd

Jul 10 07:05:17 akshansh-arch systemd[1]: Starting Bluetooth service...
Jul 10 07:05:17 akshansh-arch bluetoothd[558]: Bluetooth daemon 5.60
Jul 10 07:05:17 akshansh-arch systemd[1]: Started Bluetooth service.
Jul 10 07:05:17 akshansh-arch bluetoothd[558]: Starting SDP server
Jul 10 07:05:17 akshansh-arch bluetoothd[558]: Bluetooth management interface 1.19 initialized

Output of lspci -k:

...
...
02:00.0 Network controller: MEDIATEK Corp. Device 7961
        Subsystem: AzureWave Device 4680
        Kernel driver in use: mt7921e
        Kernel modules: mt7921e
...
...

Output of dmesg | grep -e mt7921e -e btusb:

[    1.686408] mt7921e 0000:02:00.0: enabling device (0000 -> 0002)
[    1.687215] mt7921e 0000:02:00.0: disabling ASPM  L1
[    1.687281] mt7921e 0000:02:00.0: ASIC revision: 79610010
[    1.692061] mt7921e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20210122002654a
[    1.706371] mt7921e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20210122002730
[    1.906417] usbcore: registered new interface driver btusb
[    1.975430] mt7921e 0000:02:00.0: Firmware init done

Output of lsmod | grep -e mt7921e -e btusb:

btusb                  69632  0
btrtl                  28672  1 btusb
btbcm                  16384  1 btusb
btintel                32768  1 btusb
bluetooth             724992  12 btrtl,btintel,btbcm,bnep,btusb
mt7921e                73728  0
mt76_connac_lib        36864  1 mt7921e
mt76                   81920  2 mt7921e,mt76_connac_lib
mac80211             1167360  3 mt76,mt7921e,mt76_connac_lib
cfg80211             1040384  4 mt76,mt7921e,mac80211,mt76_connac_lib

What can I do to fix this?

Last edited by akshansh2000 (2021-09-23 04:26:11)

Offline

#2 2021-08-11 17:34:32

Ipsedo
Member
Registered: 2021-08-11
Posts: 3

Re: [SOLVED] bluetoothctl: No default controller available

Is your arch in dual boot with Windows 10 ?

I am facing the same problem with the same network device but on a more recent kernel (5.13.9-arch1-1)

Offline

#3 2021-08-13 23:02:18

velemas
Member
Registered: 2018-05-27
Posts: 3

Re: [SOLVED] bluetoothctl: No default controller available

I had the same problem. I fixed it with this patch for 5.13.10 https://pastebin.pl/view/raw/152ca559

Basically it adds missing Vendor/Device ids with corresponding flags.

Offline

#4 2021-09-05 01:48:19

akshansh2000
Member
From: India
Registered: 2020-11-07
Posts: 8
Website

Re: [SOLVED] bluetoothctl: No default controller available

velemas wrote:

I had the same problem. I fixed it with this patch for 5.13.10 https://pastebin.pl/view/raw/152ca559

Basically it adds missing Vendor/Device ids with corresponding flags.

Seems like it's being merged into master for the next kernel release (5.14.1): commit

Offline

#5 2021-09-16 17:16:56

Ipsedo
Member
Registered: 2021-08-11
Posts: 3

Re: [SOLVED] bluetoothctl: No default controller available

Is it fixed for you with the last kernel update (5.14.5-arch1-1) ?

The problem stills remain on my laptop.

Offline

#6 2021-09-16 17:32:53

akshansh2000
Member
From: India
Registered: 2020-11-07
Posts: 8
Website

Re: [SOLVED] bluetoothctl: No default controller available

Ipsedo wrote:

Is it fixed for you with the last kernel update (5.14.5-arch1-1) ?

The problem stills remain on my laptop.

Not yet. I checked the source code, and the patch which fixes the issue is present in torvalds/linux v5.15-rc1. For reference, archlinux/linux v5.14.5-arch1 still has a couple commits missing.

For now, we can either apply this patch manually, or wait for the next kernel release (v5.15).

I have opened a support request in the bug tracker, though: https://bugs.archlinux.org/task/72138?p … &sort=desc

I will update this thread when this issue gets resolved in the mainline.

Offline

#7 2021-09-23 04:25:31

akshansh2000
Member
From: India
Registered: 2020-11-07
Posts: 8
Website

Re: [SOLVED] bluetoothctl: No default controller available

Offline

#8 2021-10-03 17:48:05

Ipsedo
Member
Registered: 2021-08-11
Posts: 3

Re: [SOLVED] bluetoothctl: No default controller available

akshansh2000 wrote:

Fixed too.

But I have to run "rfkill unblock bluetooth" and then restart bluetooth service to make it work.
Is this the same for you ?

Offline

#9 2021-10-04 18:30:12

akshansh2000
Member
From: India
Registered: 2020-11-07
Posts: 8
Website

Re: [SOLVED] bluetoothctl: No default controller available

Ipsedo wrote:
akshansh2000 wrote:

Fixed too.

But I have to run "rfkill unblock bluetooth" and then restart bluetooth service to make it work.
Is this the same for you ?

Nope, works straight out of the box for me.

Offline

#10 2021-11-13 11:43:45

prijindal
Member
Registered: 2021-11-13
Posts: 1

Re: [SOLVED] bluetoothctl: No default controller available

Still facing the same issue with kernel 5.14.10.
Also hciconfig -a is giving this output (BD Address 00):

hci0:	Type: Primary  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:21 acl:0 sco:0 commands:7 errors:0
	Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
	Packet type: DM1 DH1 HV1 
	Link policy: 
	Link mode: PERIPHERAL ACCEPT 

Offline

Board footer

Powered by FluxBB