Bluetooth in Fedora with Asus Zenith Extreme X399

Hi all,

Any tips on getting bluetooth to work on the Zenith Extreme X399 board, I’m running a 1950X threadripper. Never had much luck getting this to work, doesn’t show up in lspci output. Hmm?

[15:11] mike-fedora:opt | sudo dmesg |grep -i bluetooth                                                      15:11:45
[    6.325513] Bluetooth: Core ver 2.22
[    6.325531] Bluetooth: HCI device and connection manager initialized
[    6.325534] Bluetooth: HCI socket layer initialized
[    6.325537] Bluetooth: L2CAP socket layer initialized
[    6.325541] Bluetooth: SCO socket layer initialized
[    7.855276] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.855277] Bluetooth: BNEP filters: protocol multicast
[    7.855281] Bluetooth: BNEP socket layer initialized
[   22.070836] Bluetooth: RFCOMM TTY layer initialized
[   22.070841] Bluetooth: RFCOMM socket layer initialized
[   22.070897] Bluetooth: RFCOMM ver 1.11
-- Logs begin at Sat 2019-09-14 15:54:43 +0530, end at Fri 2021-09-03 15:20:31 +0530. --
Sep 03 13:41:07 mike-fedora kernel: Bluetooth: Core ver 2.22
Sep 03 13:41:07 mike-fedora kernel: Bluetooth: HCI device and connection manager initialized
Sep 03 13:41:07 mike-fedora kernel: Bluetooth: HCI socket layer initialized
Sep 03 13:41:07 mike-fedora kernel: Bluetooth: L2CAP socket layer initialized
Sep 03 13:41:07 mike-fedora kernel: Bluetooth: SCO socket layer initialized
Sep 03 13:41:08 mike-fedora systemd[1]: Starting Bluetooth service...
Sep 03 13:41:08 mike-fedora bluetoothd[1222]: Bluetooth daemon 5.52
Sep 03 13:41:08 mike-fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_>
Sep 03 13:41:08 mike-fedora systemd[1]: Started Bluetooth service.
Sep 03 13:41:08 mike-fedora systemd[1]: Reached target Bluetooth.
Sep 03 13:41:08 mike-fedora kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 03 13:41:08 mike-fedora kernel: Bluetooth: BNEP filters: protocol multicast
Sep 03 13:41:08 mike-fedora kernel: Bluetooth: BNEP socket layer initialized
Sep 03 13:41:08 mike-fedora bluetoothd[1222]: Bluetooth management interface 1.15 initialized
Sep 03 13:41:08 mike-fedora NetworkManager[1340]: <info>  [1630656668.8221] Loaded device plugin: NMBluezManager (/u>
Sep 03 13:41:22 mike-fedora kernel: Bluetooth: RFCOMM TTY layer initialized
Sep 03 13:41:22 mike-fedora kernel: Bluetooth: RFCOMM socket layer initialized
Sep 03 13:41:22 mike-fedora kernel: Bluetooth: RFCOMM ver 1.11
Sep 03 13:41:30 mike-fedora systemd[2265]: Starting Bluetooth OBEX service...
Sep 03 13:41:30 mike-fedora systemd[2265]: Started Bluetooth OBEX service.
[15:21] mike-fedora:opt | systemctl status bluetooth                                                         15:21:22
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-09-03 13:41:08 +0530; 1h 40min ago
     Docs: man:bluetoothd(8)
 Main PID: 1222 (bluetoothd)
    Tasks: 1 (limit: 19660)
   Memory: 3.3M
   CGroup: /system.slice/bluetooth.service
           └─1222 /usr/libexec/bluetooth/bluetoothd

Sep 03 13:41:08 mike-fedora systemd[1]: Starting Bluetooth service...
Sep 03 13:41:08 mike-fedora bluetoothd[1222]: Bluetooth daemon 5.52
Sep 03 13:41:08 mike-fedora systemd[1]: Started Bluetooth service.
Sep 03 13:41:08 mike-fedora bluetoothd[1222]: Starting SDP server
Sep 03 13:41:08 mike-fedora bluetoothd[1222]: Bluetooth management interface 1.15 initialized
Sep 03 13:41:22 mike-fedora bluetoothd[1222]: Endpoint registered: sender=:1.379 path=/MediaEndpoint/A2DPSource
Sep 03 13:41:22 mike-fedora bluetoothd[1222]: Endpoint registered: sender=:1.379 path=/MediaEndpoint/A2DPSink

It seems to be running hmm.

You may need to use rfkill to wake it up. I have this issue with some dongles, they are there, bluez sees them, but the device is not responding. rfkill usually will restart the device which it then starts working as normal.

1 Like

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.