You are not logged in.

Pages: 1

#1 2024-02-24 17:25:52

andyturfer
Member
Registered: 2021-01-08
Posts: 106

[SOLVED] Bluetooth does not activated after startup

I bought a new mini PC, and bluetooth is not starting on startup in Arch (KDE Plasma).

I can enable bluetooth manually by going to System Settings -> Bluetooth and then click the Enable button.

Once I manually enable bluetooth, if I do a sudo systemctl restart bluetooth.service, then bluetooth stops working again.

From boot logs:

# journalctl -b b9c40cababfe4216851f3c89c5bb4c54 | grep -i blue
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: Core ver 2.22
Feb 24 16:23:44 trigkey-s5 kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: HCI device and connection manager initialized
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: HCI socket layer initialized
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: L2CAP socket layer initialized
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: SCO socket layer initialized
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: Firmware Version: 255-255.255
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: Reading supported features failed (-19)
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: Error reading debug features
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 24 16:23:44 trigkey-s5 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Device revision is 1
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Secure boot is enabled
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: OTP lock is enabled
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: API lock is enabled
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Debug lock is disabled
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 24 16:23:45 trigkey-s5 kernel: Bluetooth: hci0: Firmware Version: 255-255.255
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Firmware loaded in 1454656 usecs
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Waiting for device to boot
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Device booted in 14922 usecs
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: Firmware revision 0.3 build 249 week 27 2023
Feb 24 16:23:46 trigkey-s5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Feb 24 16:23:47 trigkey-s5 systemd[1]: Starting Bluetooth service...
Feb 24 16:23:47 trigkey-s5 bluetoothd[1507]: Bluetooth daemon 5.72
Feb 24 16:23:47 trigkey-s5 systemd[1]: Started Bluetooth service.
Feb 24 16:23:47 trigkey-s5 systemd[1]: Reached target Bluetooth Support.
Feb 24 16:23:47 trigkey-s5 bluetoothd[1507]: Starting SDP server
Feb 24 16:23:47 trigkey-s5 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 24 16:23:47 trigkey-s5 kernel: Bluetooth: BNEP filters: protocol multicast
Feb 24 16:23:47 trigkey-s5 kernel: Bluetooth: BNEP socket layer initialized
Feb 24 16:23:47 trigkey-s5 bluetoothd[1507]: Bluetooth management interface 1.22 initialized
Feb 24 16:23:47 trigkey-s5 bluetoothd[1507]: Battery Provider Manager created
Feb 24 16:23:47 trigkey-s5 kernel: Bluetooth: MGMT ver 1.22
Feb 24 16:23:47 trigkey-s5 kernel: Bluetooth: ISO socket layer initialized
Feb 24 16:23:47 trigkey-s5 bluetoothd[1507]: Adv Monitor Manager created with supported features:0x00000001, enabled features:0x00000001, max number of supported monitors:32, max number of supported patterns:16
Feb 24 16:23:47 trigkey-s5 NetworkManager[1506]: <info>  [1708791827.2926] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-1/libnm-device-plugin-bluetooth.so)
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/ldac
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aptx
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aac
Feb 24 16:24:03 trigkey-s5 kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 24 16:24:03 trigkey-s5 kernel: Bluetooth: RFCOMM socket layer initialized
Feb 24 16:24:03 trigkey-s5 kernel: Bluetooth: RFCOMM ver 1.11
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aac
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc_xq
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc_xq
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/faststream
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/opus_05
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/opus_05
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 24 16:24:03 trigkey-s5 bluetoothd[1507]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Feb 24 16:24:05 trigkey-s5 kded5[1905]: kf.bluezqt: PendingCall Error: "The name is not activatable"

Bluetooth service status:

$ sudo systemctl status bluetooth.service 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2024-02-24 17:22:44 GMT; 1min 4s ago
       Docs: man:bluetoothd(8)
   Main PID: 1471 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 73395)
     Memory: 3.3M (peak: 3.7M)
        CPU: 54ms
     CGroup: /system.slice/bluetooth.service
             └─1471 /usr/lib/bluetooth/bluetoothd

Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/faststream
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_05
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_05
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 24 17:23:01 trigkey-s5 bluetoothd[1471]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_05_duplex

If I try to start the bluetooth service using sudo systemctl start bluetooth.service, nothing happens, and the logs show:

Feb 24 16:36:54 trigkey-s5 sudo[3222]:      andy : TTY=pts/1 ; PWD=/home/andy ; USER=root ; COMMAND=/usr/bin/systemctl start bluetooth.service
Feb 24 16:36:54 trigkey-s5 sudo[3222]: pam_unix(sudo:session): session opened for user root(uid=0) by andy(uid=1000)
Feb 24 16:36:54 trigkey-s5 sudo[3222]: pam_unix(sudo:session): session closed for user root

If I try to restart the bluetooth service using sudo systemctl restart bluetooth.service, then it activates for about a second, but then disappears again, and the logs show:

Feb 24 16:39:52 trigkey-s5 sudo[3244]:      andy : TTY=pts/1 ; PWD=/home/andy ; USER=root ; COMMAND=/usr/bin/systemctl restart bluetooth.service
Feb 24 16:39:52 trigkey-s5 sudo[3244]: pam_unix(sudo:session): session opened for user root(uid=0) by andy(uid=1000)
Feb 24 16:39:52 trigkey-s5 systemd[1]: Stopping Bluetooth service...
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Terminating
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/ldac
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aptx
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aac
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aac
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc_xq
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc_xq
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/faststream
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/opus_05
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/opus_05
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Endpoint unregistered: sender=:1.30 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Destroy Adv Monitor Manager
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Battery Provider Manager destroyed
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Stopping SDP server
Feb 24 16:39:52 trigkey-s5 bluetoothd[3167]: Exit
Feb 24 16:39:52 trigkey-s5 systemd[1]: bluetooth.service: Deactivated successfully.
Feb 24 16:39:52 trigkey-s5 systemd[1]: Stopped Bluetooth service.
Feb 24 16:39:52 trigkey-s5 systemd[1]: Starting Bluetooth service...
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Bluetooth daemon 5.72
Feb 24 16:39:52 trigkey-s5 systemd[1]: Started Bluetooth service.
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Starting SDP server
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Bluetooth management interface 1.22 initialized
Feb 24 16:39:52 trigkey-s5 sudo[3244]: pam_unix(sudo:session): session closed for user root
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Battery Provider Manager created
Feb 24 16:39:52 trigkey-s5 systemd[1]: Starting Hostname Service...
Feb 24 16:39:52 trigkey-s5 systemd[1]: Started Hostname Service.
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Failed to clear UUIDs: Failed (0x03)
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Failed to add UUID: Failed (0x03)
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Failed to add UUID: Failed (0x03)
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Failed to add UUID: Failed (0x03)
Feb 24 16:39:52 trigkey-s5 bluetoothd[3252]: Adv Monitor Manager created with supported features:0x00000001, enabled features:0x00000001, max number of supported monitors:32, max number of supported patterns:16
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/ldac
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aptx
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/aac
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aac
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/sbc_xq
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/sbc_xq
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/faststream
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/opus_05
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/opus_05
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 24 16:39:53 trigkey-s5 bluetoothd[3252]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource/opus_05_duplex

Bluetooth package versions installed:

$ pacman -Q | grep -i blue
bluedevil 1:5.27.10-3
bluez 5.72-2
bluez-libs 5.72-2
bluez-qt5 5.115.0-1
bluez-utils 5.72-2

btmgmt info when bluetooth is down:

# btmgmt info
Index list with 1 item
hci0:   Primary controller
        addr C8:5E:A9:C3:B5:FD version 11 manufacturer 2 class 0x000000
        supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration wide-band-speech 
        current settings: bondable ssp br/edr le secure-conn 
        name trigkey
        short name 
hci0:   Configuration options
        supported options: public-address 
        missing options:

Bluetooth info from bluetoothctl:

$ bluetoothctl show
Controller C8:5E:A9:C3:B5:FD (public)
        Manufacturer: 0x0002 (2)
        Version: 0x0b (11)
        Name: trigkey-s5
        Alias: trigkey
        Class: 0x006c0104 (7078148)
        Powered: yes
        PowerState: on
        Discoverable: no
        DiscoverableTimeout: 0x000000b4 (180)
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Audio Stream Control      (0000184e-0000-1000-8000-00805f9b34fb)
        UUID: Volume Offset Control     (00001845-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Volume Control            (00001844-0000-1000-8000-00805f9b34fb)
        UUID: Microphone Control        (0000184d-0000-1000-8000-00805f9b34fb)
        UUID: Audio Input Control       (00001843-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Published Audio Capabil.. (00001850-0000-1000-8000-00805f9b34fb)
        UUID: Broadcast Audio Scan      (0000184f-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0548
        Discovering: no
        Roles: central
        Roles: peripheral
        Roles: central-peripheral
        ExperimentalFeatures: BlueZ Experimental Simu.. (671b10b5-42c0-4696-9227-eb28d1b049d6)
        ExperimentalFeatures: BlueZ Experimental Blue.. (330859bc-7506-492d-9370-9a6f0614037f)
        ExperimentalFeatures: BlueZ Experimental LL p.. (15c0a148-c273-11ea-b3de-0242ac130004)
        ExperimentalFeatures: BlueZ Experimental ISO... (6fbaf188-05e0-496a-9885-d6ddfdb4e03e)
Advertising Features:
        ActiveInstances: 0x00 (0)
        SupportedInstances: 0x0c (12)
        SupportedIncludes: tx-power
        SupportedIncludes: appearance
        SupportedIncludes: local-name
        SupportedSecondaryChannels: 1M
        SupportedSecondaryChannels: 2M
        SupportedCapabilities.MinTxPower: 0xffffffde (-34)
        SupportedCapabilities.MaxTxPower: 0x0007 (7)
        SupportedCapabilities.MaxAdvLen: 0xfb (251)
        SupportedCapabilities.MaxScnRspLen: 0xfb (251)
        SupportedFeatures: CanSetTxPower
        SupportedFeatures: HardwareOffload
Advertisement Monitor Features:
        SupportedMonitorTypes: or_patterns
        SupportedFeatures: controller-patterns

When I boot from a Live USB stick for other KDE distros, bluetooth works (i.e. it's enabled when the desktop starts, I don't have to manually enable it).

Is there anything I can do to start the bluetooth service automatically so I don't have to do it manually? A kernel param, perhaps?

Last edited by andyturfer (2024-02-25 12:47:56)

Offline

#2 2024-02-25 01:10:14

andyturfer
Member
Registered: 2021-01-08
Posts: 106

Re: [SOLVED] Bluetooth does not activated after startup

The following two methods work to turn on bluetooth after my computer boots:

$ sudo bluetoothctl power on

and:

$ sudo rfkill block bluetooth
$ sudo rfkill unblock bluetooth

I have created a bash script that runs on startup to turn on bluetooth:

#!/usr/bin/env bash

/usr/bin/rfkill block bluetooth
/usr/bin/rfkill unblock bluetooth
/usr/bin/sleep 3
/usr/bin/bluetoothctl connect 00:42:79:C4:CB:42

(the last line connects to my bluetooth speaker)

Not ideal, but works for now smile

Last edited by andyturfer (2024-02-25 10:59:20)

Offline

#3 2024-02-25 03:42:12

andyturfer
Member
Registered: 2021-01-08
Posts: 106

Re: [SOLVED] Bluetooth does not activated after startup

I swapped the m.2 wifi-BT card with one that was in my laptop. The laptop works fine with the wifi-bluetooth card (i.e. bluetooth automatically starts when the laptop boots), so it looks like the issue isn't with the m.2 bluetooth card. Also, the wifi-BT card that was in my laptop (and was working perfectly) also fails to enable bluetooth on boot. So it looks like it's something on my mini PC that is causing the issue. I'll try a clean install...

Offline

#4 2024-02-25 12:47:34

andyturfer
Member
Registered: 2021-01-08
Posts: 106

Re: [SOLVED] Bluetooth does not activated after startup

Clean install did the trick - bluetooth is now enabled when the computer boots.

Offline

Pages: 1

Board footer

Powered by FluxBB