[SOLVED] Bluetooth Stopped Working "Unknown Bluetooth Controller in /etc/bluetooth/main.conf"

PasBern · 06-13-2021, 03:13 PM

Hello all,

I am running on Hefftor Linux an Arch derivative on a Lenovo X250.

A few weeks ago I disabled bluetooth in XFCE, now I wanted to turn it on again for an external nouse.

Turns out, bluetooth is not working and I cannot get it working

My system is running on kernel version:

Code:

# uname -r
5.12.9-arch1-1

Kernel module is loaded

Code:

# lsmod | grep btusb
btusb                  69632  0
btrtl                  28672  1 btusb
btbcm                  16384  1 btusb
btintel                32768  1 btusb
bluetooth             724992  11 btrtl,btintel,btbcm,bnep,btusb

No bluetooth shows up here:

Code:

# lspci --nnk

00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: bdw_uncore
lspci: Unable to load libkmod resources: error -2
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: i915
00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) I218-LM [8086:15a2] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: e1000e
00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 [8086:9c9a] (rev e3)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 [8086:9c94] (rev e3)
        Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB EHCI Controller [8086:9ca6] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation Wildcat Point-LP LPC Controller [8086:9cc3] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] [8086:9c83] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation Wildcat Point-LP SMBus Controller [8086:9ca2] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: i801_smbus
00:1f.6 Signal processing controller [1180]: Intel Corporation Wildcat Point-LP Thermal Management Controller [8086:9ca4] (rev 03)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: intel_pch_thermal
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader [10ec:5227] (rev 01)
        Subsystem: Lenovo Device [17aa:2226]
        Kernel driver in use: rtsx_pci
03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095b] (rev 59)
        Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5210]
        Kernel driver in use: iwlwifi

None here:

Code:

# rkill list all

0: tpacpi_wwan_sw: Wireless WAN
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

I tried the approach in the Arch wiki

When issuing the command: /usr/lib/bluetooth/bluetoothd -n -d

I receive the following error:

Code:

bluetoothd[461399]: Bluetooth daemon 5.58
bluetoothd[461399]: src/main.c:check_config() Unknown group Controller in /etc/bluetooth/main.conf
bluetoothd[461399]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf

My main.conf looks like this: see Pastebin

Checking systemctl, it tells me a similar story

Code:

# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2021-06-10 19:14:46 CEST; 3 days ago
       Docs: man:bluetoothd(8)
   Main PID: 262658 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9370)
     Memory: 992.0K
        CPU: 22ms
     CGroup: /system.slice/bluetooth.service
             └─262658 /usr/lib/bluetooth/bluetoothd

Jun 10 19:14:46 ThinkLin systemd[1]: Starting Bluetooth service...
Jun 10 19:14:46 ThinkLin bluetoothd[262658]: Bluetooth daemon 5.58
Jun 10 19:14:46 ThinkLin bluetoothd[262658]: src/main.c:check_config() Unknown group Controller in /etc/bluetooth/main.conf
Jun 10 19:14:46 ThinkLin systemd[1]: Started Bluetooth service.
Jun 10 19:14:46 ThinkLin bluetoothd[262658]: Starting SDP server
Jun 10 19:14:46 ThinkLin bluetoothd[262658]: Bluetooth management interface 1.19 initialized

The command btmgmt also recognizes no bluetooth controller

Code:

[mgmt]# info
Index list with 0 items
[mgmt]# config
Unconfigured index list with 0 items
[mgmt]#

Searching for the error message about the unknown group controller, I haven't come upon a solution yet

I hope here somebody has an idea how I can further troubleshoot this.

Happy to provide additional information in case needed.

Many thanks in advance

business_kid · 06-14-2021, 05:00 AM

Many bluetooth chips are on the USB bus, not the PCIE bus.

Go about faultfinding the usual way - find the relevant module & firmware, and check you're loading them. Then we'll get to configuring.

PasBern · 06-14-2021, 07:10 AM

Hello business_kid

many thanks for your quick reply.

How exactly do I find out module and firmware?

Couldn't find any useful information here

Code:

# inxi -Faz | grep bluetooth

Code:

# lsusb | grep bluetooth

Code:

# dmesg | grep -i blue
[ 8107.025283] Bluetooth: Core ver 2.22
[ 8107.025315] Bluetooth: HCI device and connection manager initialized
[ 8107.025329] Bluetooth: HCI socket layer initialized
[ 8107.025332] Bluetooth: L2CAP socket layer initialized
[ 8107.025335] Bluetooth: SCO socket layer initialized
[ 8107.037569] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8107.037572] Bluetooth: BNEP filters: protocol multicast
[ 8107.037575] Bluetooth: BNEP socket layer initialized

Thanks for your further advice

business_kid · 06-14-2021, 12:07 PM

/Later

I managed to find some details about the bluetooth for you. I had to do a spec search for the Lenovo X250 (which you might have done. I got nothing under Bluetooth, but got this under WLAN

Code:

11b/g/n, Intel Wireless-N 7265, 2x2, Wi-Fi + Bluetooth combo adapter, M.2 card

That sounds to me like an add-on to the wifi, as bluetooth is usually a separate chip.

This search is not going well. The wifi is sorted with module & firmware. You don't know that your add-on has either. I suggest you get the finger out and do some serious searching. If you find the bluetooth chip itself, I may be able to identify it from my past in electronic hardware. You could try on linux-laptop.net or Lenovo, anywhere & everywhere; but we(which means YOU) need to stop hanging about and get some real information. We need a module, a usb id, the story with firmware, that sort of thing.

PasBern · 06-15-2021, 07:22 AM

Hey, I got your point.

After a Kernel update, bluetooth is running again.

Many thanks for your effort.

Will mark this thread as solved now.

business_kid · 06-15-2021, 10:39 AM

Quote:

Originally Posted by PasBern

Hey, I got your point.

After a Kernel update, bluetooth is running again.

Many thanks for your effort.

Will mark this thread as solved now.

Lucky you. I bet it shows now in the logs. The kernel module and/or firmware is probably there now.