• bluetooth not loading after boot up


    Hello, I have reinstalled antergos on my shuttle pc and it works fine out of the box except I cannot get the bluetooth driver to start the service, I have done some research and in konsole queried the status of the bluetooth service with “lsmod | grep blue” and the following is the output: “3.629547] bluetooth hci0: Direct firmware load for rtl_bt/rtl8821a_config.bin failed with error -2”, so it seems the my bluetooth card is maybe not being recognised by the kernel? Any ideas how to fix this? thanks

  • Ok I have done some more reading on this and reinstalled the drivers and I get the below output from lsmod | grep blue:

    “bluetooth 475136 43 btrtl,hci_uart,btintel,btqca,bnep,btbcm,rfcomm,btusb
    ecdh_generic 24576 1 bluetooth
    rfkill 20480 8 bluetooth,cfg80211
    crc16 16384 2 bluetooth,ext4”

    what else should I be querying?

  • I’d also check the status of bluetooth service, in systemd terms. The service must be loaded, enabled, active and running:

    systemctl status bluetooth
    

    If it is not, it’s also possible to take a look at what was happening with bluetooth during boot:

    journalctl -b | grep blue
    

    If it doesn’t help, I’d try to monitor what happens with bluetooth service, while it is being started, in real time.

    Open two terminal windows. Start monitoring systemd’s journal in the first terminal:

    journalctl -ef
    

    Prepare the command to start bluetooth in the second terrminal, but don’t hit Enter yet:

    sudo systemctl start bluetooth
    

    While the 2nd terminal window remains focused, switch your attention to the 1st terminal, with the journal in real time, and hit Enter now - it will start bluetooth service in the 2nd terminal.

    Try to catch something relevant about bluetooth in the 1st terminal.

    journalctl -ef catches all systemd events, so other events may appear, mixed with bluetooth events.

    Just a shot in a dark.

  • Thanks, I did as you suggested and in the second terminal window I saw quite a few error messages in red - copied below. In the GUI for bluetooth in system settings, there is always an orange bar on the top with “your bluetooth adapter is powerred off” but when I click “fix it” close and reopen the window the same error message appears? any ideas?

    Aug 14 07:44:58 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:44:59 shuttle wpa_supplicant[419]: wlp1s0: Reject scan trigger since one is already pending
    Aug 14 07:45:13 shuttle konsole[1467]: Error loading text-to-speech plug-in "speechd"
    Aug 14 07:48:03 shuttle sudo[1527]: philip : TTY=pts/4 ; PWD=/home/philip ; USER=root ; COMMAND=/usr/bin/systemctl start bluetooth
    Aug 14 07:48:03 shuttle sudo[1527]: pam_unix(sudo:session): session opened for user root by philip(uid=0)
    Aug 14 07:48:03 shuttle sudo[1527]: pam_unix(sudo:session): session closed for user root
    Aug 14 07:49:02 shuttle plasmashell[777]: QXcbConnection: XCB error: 2 (BadValue), sequence: 14016, resource id: 60817426, major code: 142 (Unknown), minor code: 3
    Aug 14 07:49:20 shuttle kernel: Bluetooth: hci0 urb ffff8a7624de8c00 failed to resubmit (113)
    Aug 14 07:49:28 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:49:28 shuttle plasmashell[777]: BluezQt: PendingCall Error: "Failed"
    Aug 14 07:49:30 shuttle kernel: Bluetooth: hci0 urb ffff8a76a0f856c0 failed to resubmit (113)
    Aug 14 07:49:38 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:49:38 shuttle bluedevil-wizard[1479]: BluezQt: PendingCall Error: "Failed"
    Aug 14 07:49:50 shuttle kernel: Bluetooth: hci0 urb ffff8a7624de8e40 failed to resubmit (113)
    Aug 14 07:49:58 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:49:58 shuttle bluedevil-wizard[1479]: BluezQt: PendingCall Error: "Failed"
    Aug 14 07:50:00 shuttle kernel: Bluetooth: hci0 urb ffff8a76a0fcbe40 failed to resubmit (113)
    Aug 14 07:50:08 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:50:08 shuttle bluedevil-wizard[1479]: BluezQt: PendingCall Error: "Failed"
    Aug 14 07:50:29 shuttle kwin_x11[769]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 30303, resource id: 81788930, major code: 18 (ChangeProperty), minor code: 0
    Aug 14 07:50:29 shuttle dbus-daemon[673]: Activating service name='org.kde.kwalletd5’
    Aug 14 07:50:30 shuttle dbus-daemon[673]: Successfully activated service 'org.kde.kwalletd5’
    Aug 14 07:50:30 shuttle kwalletd5[1642]: old wallets were already migrated
    Aug 14 07:50:30 shuttle kwalletd5[1642]: kwalletd5 started
    Aug 14 07:50:30 shuttle kwalletd5[1642]: Setting useNewHash to true
    Aug 14 07:50:30 shuttle kwalletd5[1642]: Wallet new enough, using new hash
    Aug 14 07:50:30 shuttle kwalletd5[1642]: fsize: 448400536 encrypted.size(): 12824 blksz: 8
    Aug 14 07:50:30 shuttle kwalletd5[1642]: Application ’ “Opera” ’ using kwallet without parent window!
    Aug 14 07:50:35 shuttle kwalletd5[1642]: Setting useNewHash to true
    Aug 14 07:50:35 shuttle kwalletd5[1642]: Wallet new enough, using new hash
    Aug 14 07:50:59 shuttle wpa_supplicant[419]: wlp1s0: Reject scan trigger since one is already pending
    Aug 14 07:52:10 shuttle plasmashell[777]: QXcbConnection: XCB error: 2 (BadValue), sequence: 18550, resource id: 48234501, major code: 142 (Unknown), minor code: 3
    Aug 14 07:52:10 shuttle plasmashell[777]: QXcbConnection: XCB error: 2 (BadValue), sequence: 18563, resource id: 60817426, major code: 142 (Unknown), minor code: 3
    Aug 14 07:52:11 shuttle plasmashell[777]: QXcbConnection: XCB error: 2 (BadValue), sequence: 18582, resource id: 50331653, major code: 142 (Unknown), minor code: 3
    Aug 14 07:52:15 shuttle kwin_x11[769]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48551, resource id: 58720264, major code: 15 (QueryTree), minor code: 0
    Aug 14 07:52:16 shuttle plasmashell[777]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18884, resource id: 58720264, major code: 142 (Unknown), minor code: 3
    Aug 14 07:52:16 shuttle plasmashell[777]: QXcbConnection: XCB error: 2 (BadValue), sequence: 18958, resource id: 60817426, major code: 142 (Unknown), minor code: 3
    Aug 14 07:52:17 shuttle bluedevil-wizard[1479]: kf5.kwidgetsaddons: No frame loaded
    Aug 14 07:52:17 shuttle bluedevil-wizard[1479]: kf5.kwidgetsaddons: No frame loaded
    Aug 14 07:52:17 shuttle bluedevil-wizard[1479]: kf5.kwidgetsaddons: No frame loaded
    Aug 14 07:52:21 shuttle kernel: Bluetooth: hci0 urb ffff8a7662e92840 failed to resubmit (113)
    Aug 14 07:52:29 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:52:29 shuttle bluedevil-wizard[1479]: BluezQt: PendingCall Error: "Failed"
    Aug 14 07:54:34 shuttle plasmashell[777]: log_klipper: Checking clip data
    Aug 14 07:54:34 shuttle systemd[1]: Starting Cleanup of Temporary Directories…
    Aug 14 07:54:34 shuttle systemd-tmpfiles[1876]: [/usr/lib/tmpfiles.d/var.conf:17] Duplicate line for path “/var/log/lastlog”, ignoring.
    Aug 14 07:54:34 shuttle systemd[1]: Started Cleanup of Temporary Directories.
    Aug 14 07:54:35 shuttle plasmashell[777]: log_klipper: Synchronize? false

  • I have also queried “systemctl status bluetooth” and got the following output:

    bluetooth.service - Bluetooth service
    Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: di
    Active: active (running) since Mon 2017-08-14 07:39:25 BST; 20min ago
    Docs: man:bluetoothd(8)
    Main PID: 513 (bluetoothd)
    Status: "Running"
    Tasks: 1 (limit: 4915)
    CGroup: /system.slice/bluetooth.service
    └─513 /usr/lib/bluetooth/bluetoothd

    Aug 14 07:44:17 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:44:27 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:44:38 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:44:48 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:44:58 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:49:28 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:49:38 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:49:58 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:50:08 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    Aug 14 07:52:29 shuttle bluetoothd[513]: Failed to set mode: Failed (0x03)
    lines 1-20/20 (END)

  • I have seen the same problem on the Manjaro see “https://forum.manjaro.org/t/manjaro-bluetooth-doesnt-function/10815” I could try to roll back the drivers and kernel? Can that be done in Antergos? It worked on my previous Antergos installation from about 12 months ago so I’d like to roll back to that one, but I cannot find the ISO for that. So a manual rollback is required.

  • You need to find your drivers and manually compile them as a module. This should be possible as if “was” supported in an earlier kernel.

    I make things work…
    My humble wiki: https://anotherlinux.com/

  • @izznogooood thanks, that is something outside of my expertise, I will try anyway to see what drivers there are in arch linux for my bluetooth pci card - I have checked on info center and its a Realtek with Serial No.: 00e04c000001, so I will look for the drivers for this. AS a workaround I have connected my speakers to a cable and purchased a usb dongle, yet to arrive in the post, but I want to see if I can get the pci to work…

  • This problem is not confined to Arch linux, it has also surfaced on user groups using debian ubuntu 16.04 and it seems to me that the only solution short of recompiling the kernel is to switch mini pc cards so I have opted for an intel one (7260 wireless -ac) which should work properly - I’ll let you know when its installed and functioning. I believe Realtek chip is possibly badly designed and firmware is corrupted.

  • @philipmirabelli said in bluetooth not loading after boot up:

    Realtek chip is possibly badly designed

    This is a fact!

    also if you get it running, it may brake on the next kernel update, or without a reason…
    The best option is to replace it (if possible)

    But i was wondering if you can provide lsusb / lspci to get exact model e.t.c.

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • lsusb output is:

    Bus 002 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
    Bus 001 Device 003: ID 13d3:3458 IMC Networks
    Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
    Bus 001 Device 013: ID 0fce:0194 Sony Ericsson Mobile Communications AB
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    lspci output is:

    00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
    00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
    00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
    00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
    00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
    00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1)
    00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
    00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
    00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
    00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
    00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
    01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

    thanks, I’ll post outcome of replacement with intel mini pci card

  • @philipmirabelli said in bluetooth not loading after boot up:

    Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

    seems the drivers and firmware are inside kernels:

    rtl8821ae                                                                                                                                                                                                                      1 ↵
    /usr/lib/firmware/rtlwifi/rtl8821aefw.bin
    /usr/lib/firmware/rtlwifi/rtl8821aefw_29.bin
    /usr/lib/firmware/rtlwifi/rtl8821aefw_wowlan.bin
    /usr/lib/modules/4.12.8-1-ARCH/build/include/config/rtl8821ae.h
    /usr/lib/modules/4.12.8-1-ARCH/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae
    /usr/lib/modules/4.12.8-1-ARCH/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko.gz
    /usr/lib/modules/4.9.44-1-lts/build/include/config/rtl8821ae.h
    /usr/lib/modules/4.9.44-1-lts/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae
    /usr/lib/modules/4.9.44-1-lts/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko.gz
    

    But lwfinger is still provideing new ones for rtlwifi:

    https://github.com/lwfinger/rtlwifi_new/commit/a24cb561b4d23187ea103255336daa7ca88791a7

    https://aur.archlinux.org/packages/rtlwifi_new-dkms/

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • Thanks, yes I guessed that the kernel will need tweaking, something I have reservations about doing! I’ll see what the Intel chip is like first, thanks again anyway very helpful!

  • Just following up: installed intel chip and as I had anticipated it worked out of the box. Will now be closing this post. I’d be interested to know if the latest evolution of the kernel will have a working patch at some point.

  • @philipmirabelli i am shure you will be happy with your solution, caus also if the rtl-driver will be fixed, it can broke again on some changes later on…

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

loading18 bluetooth28 boot184 Posts 15Views 724
Log in to reply