Bluetooth is not working anymore

noreset · 2020-09-23 15:36:30

Hello, I got some newbie issues going on with the bluetooth, it used to work properly until I merged the old config file with the .pacnew one. Now whatever I try to do it does not start anymore. I try to give you as many details as possible.

uname -r
5.4.65-1-lts

 lsmod
Module                  Size      Used by
bluetooth             679936  16 btrtl,btintel,btbcm,bnep,btusb

systool -v -m btusb
Module = "btusb"

  Attributes:
    coresize            = "65536"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    srcversion          = "3CD7BE023732358B4F20408"
    taint               = ""
    uevent              = <store method only>
    version             = "0.8"

  Parameters:
    disable_scofix      = "N"
    enable_autosuspend  = "Y"
    force_scofix        = "N"
    reset               = "Y"

  Sections:

modprobe -c | grep btusb
options btusb reset=1

modprobe --show-depends btusb
modprobe: FATAL: Module btusb not found in directory /lib/modules/5.4.65-1-lts

I tried to understand the problem looking into the bluetooth wiki page, although, I'm thinking that I cannot fully get if the problem lies under the 'module not loaded' side, if someone can give me an hint it would be much appreciated, thanks guys.

loqs · 2020-09-23 15:42:29

What is the output of

pacman -Qikk linux-lts

noreset · 2020-09-24 00:03:53

loqs wrote:

What is the output of
pacman -Qikk linux-lts

pacman -Qikk linux-lts
Name            : linux-lts
Version         : 5.4.66-1
Description     : The LTS Linux kernel and modules
Architecture    : x86_64
URL             : https://www.kernel.org/
Licenses        : GPL2
Groups          : None
Provides        : None
Depends On      : coreutils  kmod  initramfs
Optional Deps   : crda: to set the correct wireless channels of your country
                  linux-firmware: firmware images needed for some devices
                  [installed]
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 73.52 MiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : Thu 17 Sep 2020 08:00:06 PM CEST
Install Date    : Tue 22 Sep 2020 08:30:19 PM CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.alias (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.alias.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.builtin.alias.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.builtin.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.dep (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.dep.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.devname (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.softdep (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.symbols (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.66-1-lts/modules.symbols.bin (Modification time mismatch)
linux-lts: 6767 total files, 10 altered files

loqs · 2020-09-24 00:07:16

The package installed is linux-lts 5.4.66-1 while the running kernel is 5.4.65-1-lts. Was /boot not mounted when you updated the kernel package?
Edit:
Or did you not reboot after the kernel update?

Last edited by loqs (2020-09-24 00:08:21)

noreset · 2020-09-25 10:12:22

loqs wrote:

The package installed is linux-lts 5.4.66-1 while the running kernel is 5.4.65-1-lts. Was /boot not mounted when you updated the kernel package?
Edit:
Or did you not reboot after the kernel update?

Probably the last assumption is correct, it could be that I forgot to reboot the system after updating. Please tell me that it's possible to be fixed

EDIT: With the daily update it seems that the installed package and the running kernel are the same version now

 uname -r
5.4.67-1-lts

pacman -Qikk linux-lts
Name            : linux-lts
Version         : 5.4.67-1
Description     : The LTS Linux kernel and modules
Architecture    : x86_64
URL             : https://www.kernel.org/
Licenses        : GPL2
Groups          : None
Provides        : None
Depends On      : coreutils  kmod  initramfs
Optional Deps   : crda: to set the correct wireless channels of your country
                  linux-firmware: firmware images needed for some devices
                  [installed]
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 73.53 MiB
Packager        : Andreas Radke <andyrtr@archlinux.org>
Build Date      : Thu 24 Sep 2020 01:35:25 PM CEST
Install Date    : Fri 25 Sep 2020 12:25:11 PM CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.alias (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.alias.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.builtin.alias.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.builtin.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.dep (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.dep.bin (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.devname (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.softdep (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.symbols (Modification time mismatch)
warning: linux-lts: /usr/lib/modules/5.4.67-1-lts/modules.symbols.bin (Modification time mismatch)
linux-lts: 6767 total files, 10 altered files

Still, the bluetooth isn't working, are maybe these warnings about time mismatch related with the issue?

Last edited by noreset (2020-09-25 11:19:08)

loqs · 2020-09-25 12:25:01

Can you load the btusb module now the versions match? Exactly which config file did you merge?

noreset · 2020-09-28 13:28:42

loqs wrote:

Can you load the btusb module now the versions match? Exactly which config file did you merge?

First of all I tried to check if it was already loaded with modinfo, this is the output

modinfo btusb
filename:       /lib/modules/5.4.68-1-lts/kernel/drivers/bluetooth/btusb.ko.xz
license:        GPL
version:        0.8
description:    Generic Bluetooth USB driver ver 0.8
author:         Marcel Holtmann <marcel@holtmann.org>
firmware:       mediatek/mt7668pr2h.bin
firmware:       mediatek/mt7663pr2h.bin
srcversion:     3CD7BE023732358B4F20408
alias:          usb:v8087p0A5Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0930p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v413Cp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v13D3p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v050Dp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0B05p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0A5Cp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v04CAp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0489p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0BB4p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v105Bp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v19FFp0239d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v413Cp8197d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0C10p0000d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDBp1002d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v044Ep3002d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v044Ep3001d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v04BFp030Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v057Cp3800d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8281d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp821Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp821Fd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp821Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8218d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8215d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8213d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0A5Cp21E1d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp763Fd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v*p*d*dc*dsc*dp*icE0isc01ip01in*
alias:          usb:v*p*d*dcE0dsc01dp04ic*isc*ip*in*
alias:          usb:v*p*d*dcE0dsc01dp01ic*isc*ip*in*
alias:          of:N*T*Cusb4ca,301aC*
alias:          of:N*T*Cusb4ca,301a
alias:          of:N*T*Cusbcf3,e300C*
alias:          of:N*T*Cusbcf3,e300
alias:          of:N*T*Cusb1286,204eC*
alias:          of:N*T*Cusb1286,204e
depends:        bluetooth,btbcm,btintel,btrtl
retpoline:      Y
intree:         Y
name:           btusb
vermagic:       5.4.68-1-lts SMP mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        3E:EE:A5:8F:A4:1C:31:76:17:4A:8B:05:AC:BD:C2:E5:C3:E8:72:9B
sig_hashalgo:   sha512
signature:      16:4E:0C:A4:F7:52:B3:E0:19:D0:7D:8F:E4:A7:DC:A9:FA:DC:04:76:
		5A:9F:67:3D:07:99:63:3E:59:E0:7E:68:9A:10:C8:9E:54:AC:C8:B9:
		79:C9:A8:BF:FB:C7:58:DB:21:2F:30:90:A6:B5:F8:8D:E5:F7:C9:34:
		92:F0:1F:9B:F0:05:60:D7:B3:02:B1:4D:79:83:49:CA:F1:B6:73:2D:
		C6:13:6A:9F:94:D4:72:2D:4C:C9:99:51:1E:13:75:82:27:4E:D2:33:
		8D:56:1E:67:57:F1:2D:EA:2E:77:F4:75:25:59:81:AB:4F:EF:74:CA:
		9B:F1:52:A9:79:D0:69:A3:A1:50:C3:53:9A:E8:BD:4D:2C:89:DF:2E:
		B6:B1:B4:E8:FF:8D:0A:BF:D4:89:0F:CA:B3:F5:1F:AD:67:99:84:7C:
		67:94:69:0F:DB:66:84:37:05:DA:8B:77:77:03:45:40:2E:0A:EE:96:
		BA:3D:B0:32:7C:4F:B2:80:59:9E:C6:D3:85:3F:C9:28:AF:CF:7E:1F:
		7A:9B:FF:B9:22:9B:5B:E0:7A:04:CD:39:AB:3A:66:C7:30:49:E8:3D:
		9E:87:40:64:2D:8C:5C:9E:81:DF:76:81:A0:CE:E8:2D:E0:55:E5:48:
		E6:F7:8C:67:E4:3B:D7:54:AE:C1:69:98:EF:2C:75:D7:F6:D3:3B:A8:
		73:BE:37:E4:3B:AF:82:E7:0B:48:98:EB:AB:C5:8F:1B:E7:A6:DF:5B:
		FB:8C:1C:1D:7C:53:64:83:15:5E:1D:31:B9:4D:9A:94:8D:6C:8C:7A:
		B3:81:1F:5E:01:EC:B5:98:EF:78:68:6C:75:B3:BD:0D:79:01:1B:A9:
		DC:5D:D8:4E:70:29:F5:ED:8A:52:D2:11:F0:5F:67:06:B7:62:2B:FF:
		35:95:8F:29:B0:E9:DE:87:5F:45:2B:FA:C9:6B:FC:2D:F2:06:A6:39:
		BA:8A:F2:B4:F2:6F:5D:A8:CD:5B:F8:E6:8E:A8:04:F2:50:C0:3F:AC:
		D9:F0:8E:FF:9F:C4:23:42:53:38:23:97:E2:79:A8:90:43:8A:B3:6B:
		43:56:CA:47:48:1F:81:52:48:48:37:9F:0C:DD:79:C4:DF:29:2B:60:
		A0:80:89:B3:D2:90:C0:6E:7E:F3:EB:94:8F:14:C6:AA:4F:65:49:F7:
		DD:05:A8:DB:DA:46:1B:D3:5A:FC:49:AD:89:98:50:64:50:D0:8A:87:
		C1:C8:4B:1E:5E:66:4C:57:6B:A5:B9:2B:92:7D:17:E5:D1:43:4F:31:
		A1:64:FE:5F:9F:C5:3A:2E:54:56:1A:C2:9A:A7:03:64:8F:03:F2:CA:
		59:A6:CA:9F:9C:BC:13:A3:67:C8:21:A6
parm:           disable_scofix:Disable fixup of wrong SCO buffer size (bool)
parm:           force_scofix:Force fixup of wrong SCO buffers size (bool)
parm:           enable_autosuspend:Enable USB autosuspend by default (bool)
parm:           reset:Send HCI reset command on initialization (bool)

As long as I understand, under vermagic it says mod_unload, which makes me think it is not loaded, then I tried to load the module with #modprobe btusb, but the output of modinfo is always the same.

The file I merged some weeks ago was /etc/bluetooth/main.conf, basically I held the .pacnew version which now is this

cat main.conf 
[General]

# Default adapter name
# Defaults to 'BlueZ X.YZ'
#Name = BlueZ

# Default device class. Only the major and minor device class bits are
# considered. Defaults to '0x000000'.
#Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
#DiscoverableTimeout = 0

# Always allow pairing even if there are no agent registered
# Possible values: true, false
# Default: false
#AlwaysPairable = false

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
#PairableTimeout = 0

# Use vendor id source (assigner), vendor, product and version information for
# DID profile support. The values are separated by ":" and assigner, VID, PID
# and version.
# Possible vendor id source values: bluetooth, usb (defaults to usb)
#DeviceID = bluetooth:1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. For BR/EDR this option is really only needed for qualification since the
# BITE tester doesn't like us doing reverse SDP for some test cases, for LE
# this disables the GATT client functionally so it can be used in system which
# can only operate as peripheral.
# Defaults to 'true'.
#ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
#NameResolving = true

# Enable runtime persistency of debug link keys. Default is false which
# makes debug link keys valid only for the duration of the connection
# that they were created for.
#DebugKeys = false

# Restricts all controllers to the specified transport. Default value
# is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW).
# Possible values: "dual", "bredr", "le"
#ControllerMode = dual

# Enables Multi Profile Specification support. This allows to specify if
# system supports only Multiple Profiles Single Device (MPSD) configuration
# or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple
# Devices (MPMD) configurations.
# Possible values: "off", "single", "multiple"
#MultiProfile = off

# Permanently enables the Fast Connectable setting for adapters that
# support it. When enabled other devices can connect faster to us,
# however the tradeoff is increased power consumptions. This feature
# will fully work only on kernel version 4.1 and newer. Defaults to
# 'false'.
#FastConnectable = false

# Default privacy setting.
# Enables use of private address.
# Possible values: "off", "device", "network"
# "network" option not supported currently
# Defaults to "off"
# Privacy = off

# Specify the policy to the JUST-WORKS repairing initiated by peer
# Possible values: "never", "confirm", "always"
# Defaults to "never"
#JustWorksRepairing = never

# How long to keep temporary devices around
# The value is in seconds. Default is 30.
# 0 = disable timer, i.e. never keep temporary devices
#TemporaryTimeout = 30

# Enables the device to issue an SDP request to update known services when
# profile is connected. Defaults to true.
#RefreshDiscovery = true

[Controller]
# The following values are used to load default adapter parameters.  BlueZ loads
# the values into the kernel before the adapter is powered if the kernel
# supports the MGMT_LOAD_DEFAULT_PARAMETERS command. If a value isn't provided,
# the kernel will be initialized to it's default value.  The actual value will
# vary based on the kernel version and thus aren't provided here.
# The Bluetooth Core Specification should be consulted for the meaning and valid
# domain of each of these values.

# BR/EDR Page scan activity configuration
#BRPageScanType=
#BRPageScanInterval=
#BRPageScanWindow=

# BR/EDR Inquiry scan activity configuration
#BRInquiryScanType=
#BRInquiryScanInterval=
#BRInquiryScanWindow=

# BR/EDR Link supervision timeout
#BRLinkSupervisionTimeout=

# BR/EDR Page Timeout
#BRPageTimeout=

# BR/EDR Sniff Intervals
#BRMinSniffInterval=
#BRMaxSniffInterval=

# LE advertisement interval (used for legacy advertisement interface only)
#LEMinAdvertisementInterval=
#LEMaxAdvertisementInterval=
#LEMultiAdvertisementRotationInterval=

# LE scanning parameters used for passive scanning supporting auto connect
# scenarios
#LEScanIntervalAutoConnect=
#LEScanWindowAutoConnect=

# LE scanning parameters used for passive scanning supporting wake from suspend
# scenarios
#LEScanIntervalSuspend=
#LEScanWindowSuspend=

# LE scanning parameters used for active scanning supporting discovery
# proceedure
#LEScanIntervalDiscovery=
#LEScanWindowDiscovery=

# LE scanning parameters used for passive scanning supporting the advertisement
# monitor Apis
#LEScanIntervalAdvMonitor=
#LEScanWindowAdvMonitor=

# LE scanning parameters used for connection establishment.
#LEScanIntervalConnect=
#LEScanWindowConnect=

# LE default connection parameters.  These values are superceeded by any
# specific values provided via the Load Connection Parameters interface
#LEMinConnectionInterval=
#LEMaxConnectionInterval=
#LEConnectionLatency=
#LEConnectionSupervisionTimeout=
#LEAutoconnecttimeout=

[GATT]
# GATT attribute cache.
# Possible values:
# always: Always cache attributes even for devices not paired, this is
# recommended as it is best for interoperability, with more consistent
# reconnection times and enables proper tracking of notifications for all
# devices.
# yes: Only cache attributes of paired devices.
# no: Never cache attributes
# Default: always
#Cache = always

# Minimum required Encryption Key Size for accessing secured characteristics.
# Possible values: 0 and 7-16. 0 means don't care.
# Defaults to 0
#KeySize = 0

# Exchange MTU size.
# Possible values: 23-517
# Defaults to 517
#ExchangeMTU = 517

# Number of ATT channels
# Possible values: 1-5 (1 disables EATT)
# Default to 3
#Channels = 3

[Policy]
#
# The ReconnectUUIDs defines the set of remote services that should try
# to be reconnected to in case of a link loss (link supervision
# timeout). The policy plugin should contain a sane set of values by
# default, but this list can be overridden here. By setting the list to
# empty the reconnection feature gets disabled.
#ReconnectUUIDs=00001112-0000-1000-8000-00805f9b34fb,0000111f-0000-1000-8000-00805f9b34fb,0000110a-0000-1000-8000-00805f9b34fb

# ReconnectAttempts define the number of attempts to reconnect after a link
# lost. Setting the value to 0 disables reconnecting feature.
#ReconnectAttempts=7

# ReconnectIntervals define the set of intervals in seconds to use in between
# attempts.
# If the number of attempts defined in ReconnectAttempts is bigger than the
# set of intervals the last interval is repeated until the last attempt.
#ReconnectIntervals=1,2,4,8,16,32,64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'false'.
#AutoEnable=false

Last edited by noreset (2020-09-28 13:32:37)

loqs · 2020-09-28 14:24:02

Use lsmod to check if a module is loaded. modinfo examines the module on disk.

noreset · 2020-09-28 16:20:44

loqs wrote:

Use lsmod to check if a module is loaded. modinfo examines the module on disk.

Ok. it seems to be loaded according to lsmod

lsmod

btusb                  65536  0

noreset · 2020-10-01 22:30:47

I really don't understand why it doesn't work, checked again all the steps from the wiki page, moreover, today there was an update of gnome bluetooth, yet the situation it's not changed.

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2020-10-01 17:56:22 CEST; 7min ago
       Docs: man:bluetoothd(8)
   Main PID: 434 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 23824)
     Memory: 3.4M
     CGroup: /system.slice/bluetooth.service
             └─434 /usr/lib/bluetooth/bluetoothd

Oct 01 17:56:22 argon bluetoothd[434]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller”
Oct 01 17:56:22 argon bluetoothd[434]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Oct 01 17:56:22 argon bluetoothd[434]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Oct 01 17:56:22 argon bluetoothd[434]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Oct 01 17:56:22 argon bluetoothd[434]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Oct 01 17:56:22 argon bluetoothd[434]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Oct 01 17:56:22 argon systemd[1]: Started Bluetooth service.
Oct 01 17:56:22 argon bluetoothd[434]: Starting SDP server
Oct 01 17:56:22 argon bluetoothd[434]: Bluetooth management interface 1.14 initialized
Oct 01 17:57:09 argon bluetoothd[434]: src/adapter.c:index_removed() Ignoring index removal for a non-existent adapter

qinohe · 2020-10-02 02:16:26

This may be an unnecessary question, but, even though your BT service is active, is your controller powered on?

noreset · 2020-10-05 22:14:36

qinohe wrote:

This may be an unnecessary question, but, even though your BT service is active, is your controller powered on?

I tried with bluetoothctl and when I send the 'show' command this is the output

[bluetooth]# show
No default controller available

Is this the problem?

Edit: Maybe this can help

 journalctl -b |grep Bluetooth
Oct 02 00:55:08 argon kernel: Bluetooth: Core ver 2.22
Oct 02 00:55:08 argon kernel: Bluetooth: HCI device and connection manager initialized
Oct 02 00:55:08 argon kernel: Bluetooth: HCI socket layer initialized
Oct 02 00:55:08 argon kernel: Bluetooth: L2CAP socket layer initialized
Oct 02 00:55:08 argon kernel: Bluetooth: SCO socket layer initialized
Oct 02 00:55:08 argon kernel: Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
Oct 02 00:55:08 argon systemd[1]: Starting Bluetooth mesh service...
Oct 02 00:55:08 argon systemd[1]: Starting Bluetooth service...
Oct 02 00:55:08 argon bluetoothd[434]: Bluetooth daemon 5.55
Oct 02 00:55:08 argon systemd[1]: Started Bluetooth service.
Oct 02 00:55:09 argon kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 02 00:55:09 argon kernel: Bluetooth: BNEP filters: protocol multicast
Oct 02 00:55:09 argon kernel: Bluetooth: BNEP socket layer initialized
Oct 02 00:55:09 argon bluetoothd[434]: Bluetooth management interface 1.14 initialized
Oct 02 00:55:09 argon systemd[1]: Started Bluetooth mesh service.
Oct 02 00:55:09 argon systemd[1]: Reached target Bluetooth.
Oct 02 00:55:44 argon systemd[1]: Stopped target Bluetooth.
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Oct 02 00:55:47 argon systemd[863]: Reached target Bluetooth.
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: Device revision is 5
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: Secure boot is enabled
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: OTP lock is enabled
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: API lock is enabled
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: Debug lock is disabled
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 02 00:55:47 argon systemd[1]: Reached target Bluetooth.
Oct 02 00:55:47 argon kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Oct 02 00:55:49 argon kernel: Bluetooth: hci0: Waiting for firmware download to complete
Oct 02 00:55:49 argon kernel: Bluetooth: hci0: Firmware loaded in 1872176 usecs
Oct 02 00:55:49 argon kernel: Bluetooth: hci0: Waiting for device to boot
Oct 02 00:55:49 argon kernel: Bluetooth: hci0: Device booted in 11914 usecs
Oct 02 00:55:49 argon kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Oct 02 00:55:49 argon kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Oct 02 00:55:56 argon systemd[863]: Starting Bluetooth OBEX service...
Oct 02 00:55:56 argon systemd[863]: Started Bluetooth OBEX service.
Oct 02 10:08:47 argon systemd[863]: Stopped target Bluetooth.
Oct 02 10:08:47 argon systemd[1]: Stopped target Bluetooth.
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: Device revision is 5
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: Secure boot is enabled
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: OTP lock is enabled
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: API lock is enabled
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: Debug lock is disabled
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 02 10:08:47 argon kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Oct 02 10:08:47 argon systemd[1]: Reached target Bluetooth.
Oct 02 10:08:47 argon systemd[863]: Reached target Bluetooth.
Oct 02 10:08:49 argon kernel: Bluetooth: hci0: Waiting for firmware download to complete
Oct 02 10:08:49 argon kernel: Bluetooth: hci0: Firmware loaded in 1590692 usecs
Oct 02 10:08:49 argon kernel: Bluetooth: hci0: Waiting for device to boot
Oct 02 10:08:49 argon kernel: Bluetooth: hci0: Device booted in 10827 usecs
Oct 02 10:08:49 argon kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Oct 02 10:08:49 argon kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Oct 02 10:08:49 argon kernel: Bluetooth: RFCOMM TTY layer initialized
Oct 02 10:08:49 argon kernel: Bluetooth: RFCOMM socket layer initialized
Oct 02 10:08:49 argon kernel: Bluetooth: RFCOMM ver 1.11
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: Device revision is 5
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: Secure boot is enabled
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: OTP lock is enabled
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: API lock is enabled
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: Debug lock is disabled
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 04 02:35:42 argon kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Oct 04 02:35:42 argon systemd[863]: Stopped target Bluetooth.
Oct 04 02:35:42 argon systemd[1]: Stopped target Bluetooth.
Oct 04 02:35:42 argon systemd[1]: Reached target Bluetooth.
Oct 04 02:35:42 argon systemd[863]: Reached target Bluetooth.
Oct 04 02:35:44 argon kernel: Bluetooth: hci0: Waiting for firmware download to complete
Oct 04 02:35:44 argon kernel: Bluetooth: hci0: Firmware loaded in 1545093 usecs
Oct 04 02:35:44 argon kernel: Bluetooth: hci0: Waiting for device to boot
Oct 04 02:35:44 argon kernel: Bluetooth: hci0: Device booted in 10735 usecs
Oct 04 02:35:44 argon kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Oct 04 02:35:44 argon kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Oct 05 01:09:41 argon systemd[863]: Stopped target Bluetooth.
Oct 05 01:09:41 argon systemd[1]: Stopped target Bluetooth.
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: Device revision is 5
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: Secure boot is enabled
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: OTP lock is enabled
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: API lock is enabled
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: Debug lock is disabled
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 05 01:09:41 argon kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Oct 05 01:09:41 argon systemd[863]: Reached target Bluetooth.
Oct 05 01:09:41 argon systemd[1]: Reached target Bluetooth.
Oct 05 01:09:43 argon kernel: Bluetooth: hci0: Waiting for firmware download to complete
Oct 05 01:09:43 argon kernel: Bluetooth: hci0: Firmware loaded in 1613084 usecs
Oct 05 01:09:43 argon kernel: Bluetooth: hci0: Waiting for device to boot
Oct 05 01:09:43 argon kernel: Bluetooth: hci0: Device booted in 10681 usecs
Oct 05 01:09:43 argon kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Oct 05 01:09:43 argon kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Oct 05 22:40:58 argon systemd[863]: Stopped target Bluetooth.
Oct 05 22:40:58 argon systemd[1]: Stopped target Bluetooth.
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: Device revision is 5
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: Secure boot is enabled
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: OTP lock is enabled
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: API lock is enabled
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: Debug lock is disabled
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 05 22:40:58 argon kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Oct 05 22:40:58 argon systemd[863]: Reached target Bluetooth.
Oct 05 22:40:58 argon systemd[1]: Reached target Bluetooth.
Oct 05 22:41:00 argon kernel: Bluetooth: hci0: Waiting for firmware download to complete
Oct 05 22:41:00 argon kernel: Bluetooth: hci0: Firmware loaded in 1618538 usecs
Oct 05 22:41:00 argon kernel: Bluetooth: hci0: Waiting for device to boot
Oct 05 22:41:00 argon kernel: Bluetooth: hci0: Device booted in 10709 usecs
Oct 05 22:41:00 argon kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
Oct 05 22:41:00 argon kernel: Bluetooth: hci0: Applying Intel DDC parameters completed

Last edited by noreset (2020-10-05 22:29:59)

qinohe · 2020-10-05 22:49:44

noreset wrote:

qinohe wrote:
This may be an unnecessary question, but, even though your BT service is active, is your controller powered on?
I tried with bluetoothctl and when I send the 'show' command this is the output
[bluetooth]# show
No default controller available
Is this the problem?

Yes, it is, you need a controller to send/receive without it 'no Bluetooth'

Please show 'lsusb' or/and 'lspci'
and
'rfkill list all'

noreset · 2020-10-06 13:31:35

qinohe wrote:

noreset wrote:
qinohe wrote:
This may be an unnecessary question, but, even though your BT service is active, is your controller powered on?
I tried with bluetoothctl and when I send the 'show' command this is the output
[bluetooth]# show
No default controller available
Is this the problem?
Yes, it is, you need a controller to send/receive without it 'no Bluetooth'
Please show 'lsusb' or/and 'lspci'
and
'rfkill list all'

Here the outputs

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch Fingerprint Sensor
Bus 001 Device 004: ID 5986:0706 Acer, Inc ThinkPad P50 Integrated Camera
Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module
Bus 001 Device 009: ID 1fd2:6007 Melfas LGDisplay Incell Touch
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:16.3 Serial controller: Intel Corporation Sunrise Point-LP Active Management Technology - SOL (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-LM (rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

$ rfkill list all
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

qinohe · 2020-10-06 17:09:39

Looks like this is a 2 in one(WIFI+BT) device.
Have you installed the 'linux-firmware'?

edit: also have a look at https://wiki.archlinux.org/index.php/Ne … oexistence

Last edited by qinohe (2020-10-06 17:13:03)

noreset · 2020-10-07 11:18:55

qinohe wrote:

Looks like this is a 2 in one(WIFI+BT) device.
Have you installed the 'linux-firmware'?
edit: also have a look at https://wiki.archlinux.org/index.php/Ne … oexistence

It used to work properly once. BTW, yes I have the 'linux-firmware' installed. Furthermore, I had a look at the page you suggested and even with the creation of iwlwifi.conf with its option nothing has changed.

As we understood before I'm missing a default controller, can you give me an hand trying to get one?

Last edited by noreset (2020-10-07 12:03:13)

qinohe · 2020-10-07 21:28:43

Could be it's a problematic device, could you try and use 'btmgmt - /usr/bin/btmgmt' to check the device?

/usr/bin/btmgmt
info
config

'Info' probably shows nothing, 'config' hopefully shows a non configured BT device;)

edit: 'btmgmt' is part of 'bluez-utils' - which should be installed anyway...

Last edited by qinohe (2020-10-07 21:31:15)

aRcHaTe · 2020-10-07 21:53:09

Im having the same issue. It was working fine for very long time, but something with the lastest update broke something. I still havent figured out whats causing this issue. My headset connects and 1 second later disconnects.

qinohe · 2020-10-07 22:03:04

@aRcHaTe, that's a completely different issue, OP is missing his controller and cannot connect at all...
You better create a new thread for your issue

noreset · 2020-10-08 00:18:08

qinohe wrote:

Could be it's a problematic device, could you try and use 'btmgmt - /usr/bin/btmgmt' to check the device?
/usr/bin/btmgmt
info
config
'Info' probably shows nothing, 'config' hopefully shows a non configured BT device;)
edit: 'btmgmt' is part of 'bluez-utils' - which should be installed anyway...

As your suspects pointed out... it seems to be unconfigured

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

qinohe · 2020-10-08 01:20:24

Well no, not exactly, what I was 'hoping' for would be 'Unconfigured index list with 1 items'.
But, the device seems completely invisible, almost that is because your 'lsusb' clearly shows one...

You can still try a different port or try a different kernel.
If you have no positive result with that too , than I'm out of ideas ATM...

noreset · 2020-10-08 23:15:47

qinohe wrote:

Well no, not exactly, what I was 'hoping' for would be 'Unconfigured index list with 1 items'.
But, the device seems completely invisible, almost that is because your 'lsusb' clearly shows one...
You can still try a different port or try a different kernel.
If you have no positive result with that too , than I'm out of ideas ATM...

Ok, I'll try your suggestions and I'll update the thread later, thanks for your patience!

noreset · 2020-10-22 13:33:53

I tried all the available kernels, although the result was always the same, just as if nothing had changed

I have a question though, what did you mean with 'try a different port'?

Last edited by noreset (2020-10-22 13:36:33)

qinohe · 2020-10-22 17:35:00

...lsusb
Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
...

A different USB port, but, in case of a combined device this would may not be possible at all, even though it's showing itself as USB device...

Last edited by qinohe (2020-10-22 17:42:45)

noreset · 2020-10-22 18:50:06

qinohe wrote:

...lsusb
Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
...
A different USB port, but, in case of a combined device this would may not be possible at all, even though it's showing itself as USB device...

Yeah, unfortunately it's the integrated card of the laptop, not a usb device. I'm done, I'll try to boot from a live distro and if the bluetooth works fine there I probably will reinstall everything. I just have to figure out how to make a proper backup in order to reduce this pain in the ass.

Last edited by noreset (2020-10-22 18:50:40)

Arch Linux

#1 2020-09-23 15:36:30

Bluetooth is not working anymore

#2 2020-09-23 15:42:29

Re: Bluetooth is not working anymore

#3 2020-09-24 00:03:53

Re: Bluetooth is not working anymore

#4 2020-09-24 00:07:16

Re: Bluetooth is not working anymore

#5 2020-09-25 10:12:22

Re: Bluetooth is not working anymore

#6 2020-09-25 12:25:01

Re: Bluetooth is not working anymore

#7 2020-09-28 13:28:42

Re: Bluetooth is not working anymore

#8 2020-09-28 14:24:02

Re: Bluetooth is not working anymore

#9 2020-09-28 16:20:44

Re: Bluetooth is not working anymore

#10 2020-10-01 22:30:47

Re: Bluetooth is not working anymore

#11 2020-10-02 02:16:26

Re: Bluetooth is not working anymore

#12 2020-10-05 22:14:36

Re: Bluetooth is not working anymore

#13 2020-10-05 22:49:44

Re: Bluetooth is not working anymore

#14 2020-10-06 13:31:35

Re: Bluetooth is not working anymore

#15 2020-10-06 17:09:39

Re: Bluetooth is not working anymore

#16 2020-10-07 11:18:55

Re: Bluetooth is not working anymore

#17 2020-10-07 21:28:43

Re: Bluetooth is not working anymore

#18 2020-10-07 21:53:09

Re: Bluetooth is not working anymore

#19 2020-10-07 22:03:04

Re: Bluetooth is not working anymore

#20 2020-10-08 00:18:08

Re: Bluetooth is not working anymore

#21 2020-10-08 01:20:24

Re: Bluetooth is not working anymore

#22 2020-10-08 23:15:47

Re: Bluetooth is not working anymore

#23 2020-10-22 13:33:53

Re: Bluetooth is not working anymore

#24 2020-10-22 17:35:00

Re: Bluetooth is not working anymore

#25 2020-10-22 18:50:06

Re: Bluetooth is not working anymore

Board footer