You are not logged in.
Pages: 1
This is what I've done so far
1- installed bluez, bluez-utils
2- loaded the btusb module
$ lsmod | grep "btusb"
btusb 65536 0
btrtl 24576 1 btusb
btbcm 20480 1 btusb
btintel 32768 1 btusb
bluetooth 712704 16 btrtl,btintel,btbcm,bnep,btusb3-Start/enable bluetooth.service
$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabl>
Active: active (running) since Tue 2020-08-04 02:41:31 EET; 40mi>
Docs: man:bluetoothd(8)
Main PID: 343 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9413)
Memory: 2.9M
CGroup: /system.slice/bluetooth.service
└─343 /usr/lib/bluetooth/bluetoothd4.1- for bluetoothctl
$ bluetoothctl show
No default controller available4.2- for blueberry and slimier graphical front-ends
Could not retrieve the BT adapter name with 'bt-adapter -i': Command '['timeout', '2s', 'bt-adapter', '-i']' died with <Signals.SIGABRT: 6>or a slimier error.
Additional Information:
* lspci's output
➜ ~ 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:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
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: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.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (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)
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] (rev 83)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter* lspci -k -s 03:00.0
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
Subsystem: Hewlett-Packard Company Device 804c
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be* journalctl -b | grep -i Blue
Aug 04 02:41:23 x kernel: usb 1-4: Product: Bluetooth Radio
Aug 04 02:41:28 x kernel: Bluetooth: Core ver 2.22
Aug 04 02:41:28 x kernel: Bluetooth: HCI device and connection manager initialized
Aug 04 02:41:28 x kernel: Bluetooth: HCI socket layer initialized
Aug 04 02:41:28 x kernel: Bluetooth: L2CAP socket layer initialized
Aug 04 02:41:28 x kernel: Bluetooth: SCO socket layer initialized
Aug 04 02:41:29 x kernel: Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
Aug 04 02:41:29 x kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Aug 04 02:41:29 x kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_fw.bin
Aug 04 02:41:29 x kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8723b_config.bin
Aug 04 02:41:29 x kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin failed with error -2
Aug 04 02:41:29 x kernel: Bluetooth: hci0: RTL: cfg_sz -2, total sz 22496
Aug 04 02:41:29 x kernel: Bluetooth: hci0: RTL: fw version 0x0e2f9f73
Aug 04 02:41:30 x systemd[1]: Starting Bluetooth mesh service...
Aug 04 02:41:30 x systemd[1]: Starting Bluetooth service...
Aug 04 02:41:30 x bluetoothd[343]: Bluetooth daemon 5.54
Aug 04 02:41:31 x bluetooth-meshd[342]: D-Bus ready
Aug 04 02:41:32 x kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Aug 04 02:41:32 x kernel: Bluetooth: BNEP filters: protocol multicast
Aug 04 02:41:32 x kernel: Bluetooth: BNEP socket layer initialized
Aug 04 02:41:31 x audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth-mesh comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 04 02:41:31 x 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'
Aug 04 02:41:32 x bluetooth-meshd[342]: Request name success
Aug 04 02:41:32 x bluetooth-meshd[342]: Loading node configuration from /var/lib/bluetooth/mesh
Aug 04 02:41:32 x bluetooth-meshd[342]: Added Network Interface on /org/bluez/mesh
Aug 04 02:41:32 x bluetooth-meshd[342]: Hci dev 0000 removed
Aug 04 02:41:31 x systemd[1]: Started Bluetooth mesh service.
Aug 04 02:41:31 x bluetoothd[343]: Starting SDP server
Aug 04 02:41:31 x bluetoothd[343]: Bluetooth management interface 1.16 initialized
Aug 04 02:41:31 x systemd[1]: Started Bluetooth service.
Aug 04 02:41:31 x dbus-daemon[344]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=343 comm="/usr/lib/bluetooth/bluetoothd ")
Aug 04 02:41:31 x systemd[1]: Reached target Bluetooth.
Aug 04 02:41:33 x NetworkManager[345]: <info> [1596501693.4443] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-bluetooth.so)
Aug 04 02:52:04 x sudo[2261]: x : TTY=pts/0 ; PWD=/home/x ; USER=root ; COMMAND=/usr/bin/bluetoothctl show* Bluetooth works at Windows 10 as well as Ubuntu 20.04 installed on the same machine
Offline
Removing NetworkManager solved this issue for me i don't know if they somehow conflicts with each other, can anyone with better knowledge explain why this happened?
Update: it seems it solve the issue with bluetoothctl only but not with the other front-ends
Last edited by asio (2020-08-04 04:25:52)
Offline
I hit this same problem and posted about it here: https://bbs.archlinux.org/viewtopic.php?id=258052
The incredibly helpful folks on this forum told me to get another keyboard.
I'm noticing a lot of bluetooth brokenness recently...this post is another one: https://bbs.archlinux.org/viewtopic.php?id=258262
I wonder if there's been some churn in that area recently? In any case, you're not alone. I'll ping this thread if I find a fix.
Offline
I was having a similar problem, where my bluetooth controller would randomly not appear at times.
It turns out that bluetooth-mesh removes the hci device that should act as the controller, and instead adds a new network interface.
It's likely that NetworkManager automatically enables bluetooth-mesh.service, although in my case I had accidentally enabled it manually. Disabling this service solved the issue for me.
Offline
Pages: 1