[SOLVED] bluetooth not working. No controller found.

lixsuk · 2021-03-28 09:50:34

 bluetoothctl

get stuck on "Waiting to connect to bluetoothd..." . Tried it with and without sudo, enabled and started bluetooth as well. Still no progress.

privileged@arched ~]$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Mar 26 01:25:17 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 01:26:03 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 01:36:55 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.

Bluetooth was working fine on the previous arch install on the same system from the same boot drive.
To get around this, I found using the following command workes but I have to use it after every boot.

modprobe btusb
systemctl start bluetooth

After this, I get "Agent registered" but power on outputs "No default controller available" and list doesn't output anything.

[privileged@arched ~]$ sudo bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
[bluetooth]# list
[bluetooth]#

Bluetooth status after this changes to;

[root@arched privileged]# systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2021-03-26 01:54:50 UTC; 2min 32s ago
       Docs: man:bluetoothd(8)
   Main PID: 1769 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 3396)
     Memory: 2.1M
     CGroup: /system.slice/bluetooth.service
             └─1769 /usr/lib/bluetooth/bluetoothd

Mar 26 01:54:50 arched systemd[1]: Starting Bluetooth service...
Mar 26 01:54:50 arched bluetoothd[1769]: Bluetooth daemon 5.56
Mar 26 01:54:50 arched systemd[1]: Started Bluetooth service.
Mar 26 01:54:50 arched bluetoothd[1769]: Starting SDP server
Mar 26 01:54:50 arched bluetoothd[1769]: Bluetooth management interface 1.19 initialized

From here I have no idea what to do. Most of the threads on the forums use hcitools and some other bash commands that have been decommissioned from what I have read on the arch wiki.

I am using Dell inspiron N4010 with arch linux and xfce 4.16 and my the latest linux kernal 5.11.10-arch1-1

Here's output to some scary looking stuff that people from other threads asked for.

[root@arched privileged]# rfkill list all
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

[root@arched privileged]# dmesg | grep -i bluetooth
[ 1781.942691] Bluetooth: Core ver 2.22
[ 1781.942748] Bluetooth: HCI device and connection manager initialized
[ 1781.942754] Bluetooth: HCI socket layer initialized
[ 1781.942757] Bluetooth: L2CAP socket layer initialized
[ 1781.942762] Bluetooth: SCO socket layer initialized
[ 1818.481560] audit: type=1130 audit(1616723690.494:107): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1818.502337] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1818.502345] Bluetooth: BNEP filters: protocol multicast
[ 1818.502353] Bluetooth: BNEP socket layer initialized

[root@arched privileged]# journalctl | grep -i bluetooth
Mar 26 01:16:42 arched systemd[1]: Stopping Bluetooth service...
Mar 26 01:16:42 arched bluetoothd[3762]: Terminating
Mar 26 01:16:42 arched bluetoothd[3762]: Stopping SDP server
Mar 26 01:16:42 arched bluetoothd[3762]: Exit
Mar 26 01:16:42 arched systemd[1]: bluetooth.service: Succeeded.
Mar 26 01:16:42 arched audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 01:16:42 arched systemd[1]: Stopped Bluetooth service.
Mar 26 01:16:42 arched kernel: audit: type=1131 audit(1616721402.310:318): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 01:16:42 arched systemd[410]: Stopping Bluetooth OBEX service...
Mar 26 01:16:42 arched systemd[410]: Stopped Bluetooth OBEX service.
Mar 26 01:24:42 arched NetworkManager[306]: <info>  [1616721882.6629] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.30.2-1/libnm-device-plugin-bluetooth.so)
Mar 26 01:25:17 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 01:26:03 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 01:36:55 arched polkitd[447]: Operator of unix-session:2 successfully authenticated as unix-user:privileged to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.45 [systemctl start bluetooth] (owned by unix-user:privileged)
Mar 26 01:36:55 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 01:48:13 arched dbus-daemon[305]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.55' (uid=0 pid=1637 comm="sudo bluetoothctl ")
Mar 26 01:48:20 arched sudo[1637]: privileged : TTY=pts/0 ; PWD=/home/privileged ; USER=root ; COMMAND=/usr/bin/bluetoothctl
Mar 26 01:49:23 arched dbus-daemon[305]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.58' (uid=0 pid=1661 comm="sudo systemctl status bluetoothctl ")
Mar 26 01:49:23 arched sudo[1661]: privileged : TTY=pts/0 ; PWD=/home/privileged ; USER=root ; COMMAND=/usr/bin/systemctl status bluetoothctl
Mar 26 01:49:26 arched dbus-daemon[305]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.59' (uid=0 pid=1664 comm="sudo systemctl status bluetooth ")
Mar 26 01:49:26 arched sudo[1664]: privileged : TTY=pts/0 ; PWD=/home/privileged ; USER=root ; COMMAND=/usr/bin/systemctl status bluetooth
Mar 26 01:53:47 arched polkitd[447]: Operator of unix-session:2 successfully authenticated as unix-user:privileged to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.63 [systemctl start bluetooth] (owned by unix-user:privileged)
Mar 26 01:53:47 arched systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 26 01:54:13 arched kernel: Bluetooth: Core ver 2.22
Mar 26 01:54:13 arched kernel: Bluetooth: HCI device and connection manager initialized
Mar 26 01:54:13 arched kernel: Bluetooth: HCI socket layer initialized
Mar 26 01:54:13 arched kernel: Bluetooth: L2CAP socket layer initialized
Mar 26 01:54:13 arched kernel: Bluetooth: SCO socket layer initialized
Mar 26 01:54:50 arched systemd[1]: Starting Bluetooth service...
Mar 26 01:54:50 arched bluetoothd[1769]: Bluetooth daemon 5.56
Mar 26 01:54:50 arched systemd[1]: Started Bluetooth service.
Mar 26 01:54:50 arched audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 01:54:50 arched kernel: audit: type=1130 audit(1616723690.494:107): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 01:54:50 arched bluetoothd[1769]: Starting SDP server
Mar 26 01:54:50 arched kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar 26 01:54:50 arched kernel: Bluetooth: BNEP filters: protocol multicast
Mar 26 01:54:50 arched kernel: Bluetooth: BNEP socket layer initialized
Mar 26 01:54:50 arched dbus-daemon[305]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.67' (uid=0 pid=1769 comm="/usr/lib/bluetooth/bluetoothd ")
Mar 26 01:54:50 arched bluetoothd[1769]: Bluetooth management interface 1.19 initialized

[root@arched privileged]# lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation HM57 Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
04:00.0 Ethernet controller: Qualcomm Atheros AR8152 v1.1 Fast Ethernet (rev c1)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
ff:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 (rev 05)
ff:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 05)
ff:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 05)

[privileged@arched ~]$ blueman-adapters
blueman-adapters version 2.1.4 starting
blueman-adapters 02.07.18 ERROR    Adapter:53 __init__  : No adapter(s) found
[privileged@arched ~]$ blueman-manager
blueman-manager version 2.1.4 starting
blueman-manager 02.07.24 ERROR    Manager:118 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 02.07.24 ERROR    Manager:122 on_dbus_name_appeared: No adapter(s) found, exiting

[privileged@arched ~]$ lsmod | grep -i bluetooth
bluetooth             749568  11 btrtl,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 28672  7 bluetooth,dell_laptop,cfg80211
crc16                  16384  2 bluetooth,ext4

Last edited by lixsuk (2021-04-24 19:18:42)

nick_0189 · 2021-03-30 16:43:19

Have you tried this: https://wiki.archlinux.org/index.php/Bl … ng_skipped?

lixsuk · 2021-04-24 18:59:16

nick_0189 wrote:

Have you tried this: https://wiki.archlinux.org/index.php/Bl … ng_skipped?

Yeah I tried that. Didn't work. But what worked was the thing above it, "This might also be caused by power saving measures, in which case adding the kernel parameter btusb.enable_autosuspend=n is a potential solution". I didn't do it at first because I didn't get what a kernel parameter is or how to change it. But I saw someone on another thread add the

 btusb.enable_autosuspend=n

in the grub configurations. Which worked for me.

From what I can tell the grub configurations are not the same as kernal parameters. Or even if it is I think that they should add the detail about adding this in the grub.d in the arch wiki that you linked.

Do you know where I can check how or why this worked? Or why it was broken in the first place? This really conserns me.

Slithery · 2021-04-24 19:15:44

lixsuk wrote:

I didn't do it at first because I didn't get what a kernel parameter is or how to change it.

Did you not think to look at the wiki?
https://wiki.archlinux.org/index.php/Kernel_parameters

lixsuk wrote:

Or even if it is I think that they should add the detail about adding this in the grub.d in the arch wiki that you linked.

It already is...

lixsuk · 2021-04-24 19:38:02

Slithery wrote:

lixsuk wrote:
I didn't do it at first because I didn't get what a kernel parameter is or how to change it.
Did you not think to look at the wiki?
https://wiki.archlinux.org/index.php/Kernel_parameters

Like I said already, I read it. The entire thing. I know people don't read the wiki and it really frustrates you good helpful folks so I spent a lot of time reading a lot of wikis and tried making sense of everything I could. So I am sorry but I just don't really appreciate the condescending tone there.

It already is...

Again the same as before, maybe I missed something. It can totally happen and I apologise if that is the case. But the wiki stated "To make the change persistent after reboot, you could manually edit /boot/grub/grub.cfg with the exact line from above, but the best practice is to:
Edit /etc/default/grub and append your kernel options between the quotes in the GRUB_CMDLINE_LINUX_DEFAULT line:

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

”

Which did not solve the problem in my case. Mine was solved by adding the kernal parameter

 GRUB_CMDLINE_LINUX_DEFAULT=btusb.enable_autosuspend=n

But it doesn't matter. I got my bluetooth working. So thanks for your help and Have a good one. Cheers! (:

Arch Linux

#1 2021-03-28 09:50:34

[SOLVED] bluetooth not working. No controller found.

#2 2021-03-30 16:43:19

Re: [SOLVED] bluetooth not working. No controller found.

#3 2021-04-24 18:59:16

Re: [SOLVED] bluetooth not working. No controller found.

#4 2021-04-24 19:15:44

Re: [SOLVED] bluetooth not working. No controller found.

#5 2021-04-24 19:38:02

Re: [SOLVED] bluetooth not working. No controller found.

Board footer