Mediatek mt7922 - Bluetooth always disabled on startup

Issues & Assistance Networking Support
1

Hi there,

I can’t figured out why my bluetooth adapter won’t automatically enable on startup. I always have to manually enable bluetooth in the system tray first. After being manually enabled, it works fine until i reboot the computer.

I have checked that :

  • bluetooth.service is enabled in systemctl
  • AutoEnable=true in /etc/bluetooth/main.cf
  • The option “Enable bluettoth device on startup” is selected in Plasma system configuration

But nothing worked, my computer just boots with bluetooth disabled every time.

Thanks a lot for any help :wink:

System:
  Kernel: 6.13.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=81917e19-1ef7-4f5d-adb2-efa1f1cc34fe rw rootflags=subvol=@ quiet quiet
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=b5f5224c-7f0c-4f99-b519-7c88d92f1a1a loglevel=3 acpi_enforce_resources=lax splash
    ibt=off
  Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A info: frameworks v: 6.10.0 wm: kwin_wayland
    with: krunner vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2 v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: FC date: 03/24/2023
CPU:
  Info: model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+ gen: 3 level: v3 note: check
    built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
    microcode: 0xA201210
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 96 MiB desc: 1x96 MiB
  Speed (MHz): avg: 3486 min/max: 550/4550 boost: enabled scaling: driver: amd-pstate-epp
    governor: powersave cores: 1: 3486 2: 3486 3: 3486 4: 3486 5: 3486 6: 3486 7: 3486 8: 3486
    9: 3486 10: 3486 11: 3486 12: 3486 13: 3486 14: 3486 15: 3486 16: 3486 bogomips: 108599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
    vendor: XFX Speedster MERC 319 driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-2
    off: HDMI-A-1 empty: DP-1,DP-3,Writeback-1 bus-ID: 09:00.0 chip-ID: 1002:73bf class-ID: 0300
  Device-2: Huawei HiCamera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 3-2.2.1:5 chip-ID: 12d1:4321 class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5 compositor: kwin_wayland
    driver: X: loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: DP-2 model: Dell AW3423DWF serial: <filter> built: 2022 res: mode: 3440x1440 hz: 165
    scale: 100% (1) dpi: 109 gamma: 1.2 size: 800x337mm (31.5x13.27") diag: 868mm (34.2") modes:
    max: 3440x1440 min: 720x400
  Monitor-2: HDMI-A-1 model: Dell AW3423DWF serial: <filter> built: 2022 res: 3440x1440 dpi: 109
    gamma: 1.2 size: 800x337mm (31.5x13.27") diag: 868mm (34.2") modes: max: 3440x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 6900 XT (radeonsi navi21 LLVM 19.1.7 DRM 3.59
    6.13.2-zen1-1-zen) device-ID: 1002:73bf memory: 15.62 GiB unified: no display-ID: :0.0
  API: Vulkan v: 1.4.303 layers: 11 device: 0 type: discrete-gpu name: AMD Radeon RX 6900 XT
    (RADV NAVI21) driver: N/A device-ID: 1002:73bf surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 19.1.7 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: corectrl, lact, radeontop wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.4
    chip-ID: 1022:1487 class-ID: 0
403
  Device-3: C-Media USB Audio Device driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8:5 chip-ID: 0d8c:0012 class-ID: 0300
  Device-4: Huawei HiCamera driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 3-2.2.1:5 chip-ID: 12d1:4321 class-ID: 0102 serial: <filter>
  API: ALSA v: k6.13.2-zen1-1-zen status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter vendor: AzureWave ASUS
    PCE-AXE59BT driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 04:00.0
    chip-ID: 14c3:7922 class-ID: 0280
  IF: wlp4s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-6.3:4 chip-ID: 13d3:3568 class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status:
    discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 1.83 TiB used: 1.01 TiB (55.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S500G size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: ELFK0S.6 temp: 49.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Crucial model: CT1000P3SSD8 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: P9CR30A temp: 44.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 6B0Q
  ID-4: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: MU02
Partition:
  ID-1: / raw-size: 431.07 GiB size: 431.07 GiB (100.00%) used: 141.14 GiB (32.7%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 248.3 MiB (82.9%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 431.07 GiB size: 431.07 GiB (100.00%) used: 141.14 GiB (32.7%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 431.07 GiB size: 431.07 GiB (100.00%) used: 141.14 GiB (32.7%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 431.07 GiB size: 431.07 GiB (100.00%) used: 141.14 GiB (32.7%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.39 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 53.9 C mobo: 31.0 C gpu: amdgpu temp: 53.0 C mem: 52.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 6.4 GiB (20.5%)
  Processes: 467 Power: uptime: 15m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.48 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd I
nit: systemd v: 257
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1605 libs: 415 tools: paru Compilers: clang: 19.1.7 gcc: 14.2.1
    Client: shell wrapper v: 5.2.37-release inxi: 3.3.37
Garuda (2.6.26-1.1):
  System install date:     2023-05-03
  Last full system update: 2025-02-12
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:
2

Please, try X11 from login screen.
Problem start after system update?

1 Like
3

Hi,

The problem stays the same with X11.

I’m not sure exactly when it started, i just didn’t use bluetooth before. I am now because i bought a new wireless game controller.

4

hello Azerist,

can you check your Bluetooth Settings again to watch for these Settings.

bluetooth1
bluetooth1990×739 102 KB

bluethooth
bluethooth1440×900 197 KB

ups overread it you did already.but just for sure.

1 Like
5

can you check this please ?
rfkill list in the Terminal and post your output please.thx

6

Yeah already checked that setting multiple times, it’s set on the first option “enable bluetooth”

7

rfkill list :

0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
8

ok so no issue here to see.

ive think you did try already this but no help after reboot sudo systemctl enable bluetooth.service

can you check to update your Bios? Because you have the AMD R7 5800X3D CPU?

with the newer from this if you have the version from this but watch for your right rev:x.x Number because we dont know which one.

1 Like
9

Yeah already enabled bluetooth.service in systemd…

Strange for the bios, i’ll check that tomorrow but i thought i upgraded it much more recently than 2023.

10

I have the same problem with BT since Kernel 6.0. Plasma uses bluedevil and powerdevil, and the combination of those just sucks ass and they didn’t fix a darn thing so far.

I have to open up the setting panel → bluetooth → try to conncet Sony XM4, and it disables the BT adaptor all together. I have to enable it again and wait about 30 seconds for the list of BT devices to show up again and it connects for the 2nd time.

I’m really tired of this routine, but I don’t know where I take it to.

Isao

11

You don’t have use bluedevil and powerdevil. there are alternatives:

https://wiki.archlinux.org/title/Power_management

https://wiki.archlinux.org/title/TLP

https://aur.archlinux.org/packages/tlpui

https://wiki.archlinux.org/title/Powertop

https://wiki.archlinux.org/title/Bluetooth

https://wiki.archlinux.org/title/Blueman

Before changing your Bluetooth or Power Manager, I would suggest testing alternate kernels such as:

linux-mainline

or

linux-lts

The kernel in use has a huge bearing on how well Bluetooth performs, as support for Bluetooth comes explicitly from the kernel in use.

The MediaTek mt7921 & mt7922 have been at the top of the list for the most problematic adapters requiring assistance on the forum for the last several years. Consider yourself extremely lucky if you can get WiFi and Bluetooth working properly with either of those sub-par adapters.

3 Likes
12

Oh ok.

Well so far bluetooth works well - once manually activated.
I don’t use wifi on this machine, it’s just that internal adapters usually come with both.

But thanks for the heads-up, i’ll consider buying another wireless card maybe.

13

I have ordered a new adapter from TP-link (former was Asus) which is specified to use an intel chip.

I’ll check back here in a week when i get it and say if it helped solving the issue.

2 Likes
14

Had the idea to go check journalctl -xeu bluetooth.service but i can’t see much there, except maybe the last line that shows a strange error :

févr. 14 09:18:21 PC-JEREM systemd[1]: Starting Bluetooth service...
░░ Subject: L'unité (unit) bluetooth.service a commencé à démarrer
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ L'unité (unit) bluetooth.service a commencé à démarrer.
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: Bluetooth daemon 5.79
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: Starting SDP server
févr. 14 09:18:21 PC-JEREM systemd[1]: Started Bluetooth service.
░░ Subject: L'unité (unit) bluetooth.service a terminé son démarrage
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ L'unité (unit) bluetooth.service a terminé son démarrage, avec le résultat done.
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support bap plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support bass plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support mcp plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support vcp plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support micp plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support ccp plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support csip plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: src/plugin.c:init_plugin() System does not support asha plugin
févr. 14 09:18:21 PC-JEREM bluetoothd[1001]: Bluetooth management interface 1.23 initialized
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Battery Provider Manager created
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/ldac
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aptx_hd
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_hd
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aptx
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aac
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aac
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_g
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_g
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_1
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_0
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/faststream
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/faststream_duplex
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_05
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_05
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_05_duplex
févr. 14 09:18:41 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_05_duplex
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/ldac
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aptx_hd
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_hd
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aptx
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/aac
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aac
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_g
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_g
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_1
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_0
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/faststream
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/faststream_duplex
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_05
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_05
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink/opus_05_duplex
févr. 14 09:24:43 PC-JEREM bluetoothd[1001]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource/opus_05_duplex
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/ldac
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/aptx_hd
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aptx_hd
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/aptx
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aptx
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/aac
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aac
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/opus_g
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/opus_g
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/sbc
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/sbc
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aptx_ll_1
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aptx_ll_0
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/faststream
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/faststream_duplex
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/opus_05
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/opus_05
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSink/opus_05_duplex
févr. 14 09:24:45 PC-JEREM bluetoothd[1001]: Endpoint registered: sender=:1.152 path=/MediaEndpoint/A2DPSource/opus_05_duplex
févr. 14 09:24:51 PC-JEREM bluetoothd[1001]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
lines 23-89/89 (END)
15

Well looks like your were right, it suddenly stopped working (not detected anymore, not showing up in lsusb either…).

I’ll wait to see if it works with the new one i ordered, and then ask for a refund for this one which is barely a month old :o

16

There are two things that can sometimes help when this occurs:

  • Switch to the linux-lts kernel.

  • Reset your bios back to the factory default.

1 Like
17

Bluetooth works again with the new adapter which has an intel chip as shown by lsusb:

Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth

But it still gets disabled on startup.

However i’ve noticed a bit more: it does seem enabled after startup for like 2 or 3 seconds, i can see it in the system tray and clicking on it shows ‘active’, but something seems to automatically turn it of after idk how much time but less than 5s.

Looking through my auto-startup application list, i finally found the culprit and it seems to be Steam.

Whenever i start Steam (automatically or manually) it seems to disable buetooth…

If I remove steam from automatic startup list then bluetooth stays enabled. But whenever i start steam manually later it gets disabled again.

1 Like
19

Please do not post here in the forum, like in chat forums.
As long as no one has responded to your post, you can edit your post.

1 Like
20

Yeah your’re right i’m getting bad habits.

I edited my posts.

2 Likes
21

did you try to turn off the internal bluetooth in the bios settings and use only the dongle for testing?

how your garuda-inxi look with it?