Bluetooth doesn't work on start

I have been having this issue for a while now my blutooth doesn’t work on wake up unless I run these commands first and I have to unpair and pair the headset again

sudo modprobe -r btusb
sudo modprobe btusb
sudo systemctl restart bluetooth

inxi -zv8

 Kernel: 6.18.26-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: hpet avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
    root=UUID=b395b351-d6f7-40f1-88ff-43ee89d7e608 rw usbcore.autosuspend=-1
    quiet acpi_osi=off apparmor=1 security=apparmor udev.log_priority=3
    acpi_backlight=native nowatchdog
  Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A info: frameworks v: 6.25.0
    wm: kwin_wayland with: docker vt: 1 dm: SDDM Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82B5 v: Lenovo Legion 5 15ARH05
    serial: <superuser required> Chassis: type: 10 v: Lenovo Legion 5 15ARH05
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN
    serial: <superuser required> part-nu: LENOVO_MT_82B5_BU_idea_FM_Legion 5
    15ARH05 uuid: <superuser required> Firmware: UEFI vendor: LENOVO
    v: EUCN41WW date: 09/20/2023
Battery:
  ID-1: BAT0 charge: 26.1 Wh (59%) condition: 44.2/60 Wh (73.7%) volts: 15.76
    min: 15.44 model: SMP L19M4PC0 type: Li-poly serial: <filter> charging:
    status: not charging type: long_life avail: long_life,standard
    cycles: 1407
Memory:
  System RAM: total: 16 GiB available: 14.99 GiB used: 8.41 GiB (56.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 3200 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Kingston
    part-no: LV32D4S2S8HD-8 serial: <filter>
  Device-2: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 3200 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: Samsung
    part-no: M471A1G44AB0-CWE serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 2 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x860010D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1771 min/max: 1400/3000 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1771 2: 1771 3: 1771
    4: 1771 5: 1771 6: 1771 7: 1771 8: 1771 9: 1771 10: 1771 11: 1771 12: 1771
    bogomips: 71866
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibrs
    ibs irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor
    movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw
    overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core
    perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rapl rdpid
    rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni skinit smap smca
    smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock
    syscall tce topoext tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif
    vmcb_clean vme vmmcall wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr
    xsaveopt xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
    always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Lenovo
    driver: nvidia v: 595.71.05 alternate: nouveau,nova_core,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16 ports: active: none
    empty: DP-1,HDMI-A-1,eDP-2 bus-ID: 01:00.0 chip-ID: 10de:1f95
    class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series /
    Radeon Mobile Series] vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5
    code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: eDP-1 empty: none bus-ID: 05:00.0
    chip-ID: 1002:1636 class-ID: 0300 temp: 41.0 C
  Device-3: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:2 chip-ID: 5986:212b
    class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: AU Optronics 0xd1ed built: 2019 res:
    mode: 1920x1080 hz: 120 scale: 100% (1) dpi: 142 gamma: 1.2 chroma: red:
    x: 0.561 y: 0.341 green: x: 0.349 y: 0.573 blue: x: 0.161 y: 0.118 white:
    x: 0.314 y: 0.329 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x800,
    1280x720, 1024x768, 800x600, 640x480
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: radeonsi x11: drv: radeonsi
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 26.0.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    renoir ACO DRM 3.64 6.18.26-1-MANJARO) device-ID: 1002:1636
    memory: 500 MiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 8 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 26.0.6-arch1.1
    device-ID: 1002:1636 surfaces: N/A device: 1 type: discrete-gpu
    name: NVIDIA GeForce GTX 1650 Ti driver: nvidia v: 595.71.05
    device-ID: 10de:1f95 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10fa
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Lenovo
    driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.18.26-1-MANJARO status: kernel-api with: 1: aoss
    type: oss-emulator 2: apulse type: pulse-emulator
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.6.4 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: br-a29a26287470 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-4: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  Info: services: NetworkManager, systemd-networkd, systemd-timesyncd,
    wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:6 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 5 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.14 TiB used: 593.81 GiB (50.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLB256HBHQ-000L2 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 3L1QEXH7 temp: 43.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10SPSX-08A6W
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 51.29 GiB size: 50.31 GiB (98.08%) used: 46.3 GiB (92.0%)
    fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5 label: N/A
    uuid: b395b351-d6f7-40f1-88ff-43ee89d7e608
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 53.5 MiB (55.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: N/A uuid: 0C75-E2CB
  ID-3: /home raw-size: 68.07 GiB size: 66.45 GiB (97.62%)
    used: 58.06 GiB (87.4%) fs: ext4 dev: /dev/nvme0n1p7 maj-min: 259:7
    label: N/A uuid: 8688e415-56b2-481d-827b-210e7dfd1197
  ID-4: /run/media/yamo/9640794240792A5F raw-size: 97.58 GiB
    size: 97.58 GiB (100.00%) used: 69.15 GiB (70.9%) fs: ntfs
    dev: /dev/nvme0n1p3 maj-min: 259:3 label: N/A uuid: 4C924D4C924D3BA8
  ID-5: /run/media/yamo/dev raw-size: 150.39 GiB size: 146.97 GiB (97.73%)
    used: 22.08 GiB (15.0%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 label: dev
    uuid: 282ad770-afcf-4122-a65c-cc2ce3ae8ed4
  ID-6: /run/media/yamo/edu raw-size: 300 GiB size: 299.99 GiB (100.00%)
    used: 211.23 GiB (70.4%) fs: exfat dev: /dev/sda3 maj-min: 8:3 label: edu
    uuid: EFC6-65D4
  ID-7: /run/media/yamo/shared raw-size: 131.11 GiB
    size: 131.1 GiB (100.00%) used: 43.61 GiB (33.3%) fs: exfat dev: /dev/sda5
    maj-min: 8:5 label: shared uuid: F9C9-E5D6
  ID-8: /run/media/yamo/storage raw-size: 350 GiB size: 343.44 GiB (98.13%)
    used: 141.88 GiB (41.3%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: storage
    uuid: e5489775-d90c-4696-a864-e63bb4b4852f
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 20.48 GiB used: 1.46 GiB (7.1%)
    priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:6 label: N/A
    uuid: ae9bb7f8-1320-4d92-9e21-1ebd6e555f8a
Unmounted:
  ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-2: /dev/nvme0n1p4 maj-min: 259:4 size: 962 MiB fs: ntfs label: N/A
    uuid: A65C81855C81514B
  ID-3: /dev/sda1 maj-min: 8:1 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-3:2 info: Bison Integrated Camera type: video driver: uvcvideo
    interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 5986:212b class-ID: 0e02
  Hub-2: 2-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 3-1:2 info: Genesys Logic Hub ports: 2 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 3-1.1:4 info: Razer USA Cobra type: mouse,keyboard
    driver: razermouse,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1532:00a3 class-ID: 0300
  Device-2: 3-3:6 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Device-3: 3-4:5 info: Integrated Express ITE Device(8910) type: keyboard
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 048d:c100 class-ID: 0301
  Hub-5: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-6: 4-1:2 info: Genesys Logic GL3523 Hub ports: 2 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0620
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 54.1 C mobo: N/A gpu: amdgpu temp: 41.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: 2384 pm: dpkg pkgs: 0 pm: pacman pkgs: 2352 libs: 547
    tools: pamac,yay pm: flatpak pkgs: 17 pm: snap pkgs: 15
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    2: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    3: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
    4: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    5: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    6: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    7: https://mirror.23m.com/manjaro/stable/$repo/$arch
    8: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    9: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    10: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    11: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    12: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    13: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    14: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    15: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    16: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    17: https://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    18: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    19: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    20: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    21: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    22: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    23: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    24: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    25: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    26: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    27: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    28: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    29: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    30: https://manjaro.ynh.ovh/stable/$repo/$arch
    31: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    32: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    33: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    34: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    35: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    36: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    37: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    38: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    39: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    40: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    41: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    42: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
    43: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
    44: https://mirrors2.manjaro.org/stable/$repo/$arch
    45: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    46: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    47: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    48: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    49: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    50: https://manjaro.grena.ge/stable/$repo/$arch
    51: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    52: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    53: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    54: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    55: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    56: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    57: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    58: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    59: https://mirror.init7.net/manjaro/stable/$repo/$arch
    60: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    61: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    62: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    63: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    64: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    65: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    66: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    67: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    68: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    69: https://mirror.dimensiondata.com/mirrors/manjaro.org/stable/$repo/$arch
    70: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    71: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    72: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    73: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    74: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    75: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    76: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    77: https://manjaro.mirror-services.net/pub/stable/$repo/$arch
    78: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 464
  1: cpu: 81.1% command: code pid: 50451 mem: 291.1 MiB (1.8%)
  2: cpu: 62.4% command: exe pid: 50856 mem: 736.6 MiB (4.7%)
  3: cpu: 50.0% command: ps pid: 62369 mem: 4.41 MiB (0.0%)
  4: cpu: 31.4% command: vivaldi-bin pid: 54095 mem: 976.9 MiB (6.3%)
  5: cpu: 16.6% command: vivaldi-bin pid: 54815 mem: 364.3 MiB (2.3%)
  Memory top: 5 of 464
  1: mem: 976.9 MiB (6.3%) command: vivaldi-bin pid: 54095 cpu: 31.4%
  2: mem: 736.6 MiB (4.7%) command: exe pid: 50856 cpu: 62.4%
  3: mem: 539.4 MiB (3.5%) command: vivaldi-bin pid: 54209 cpu: 12.2%
  4: mem: 507.8 MiB (3.3%) command: exe pid: 50877 cpu: 2.6%
  5: mem: 488.7 MiB (3.1%) command: zen pid: 7620 cpu: 0.4%
Info:
  Processes: 464 Power: uptime: 6h 11m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 5.89 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 260 default: graphical tool: systemctl
  Compilers: clang: 22.1.3 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: kitty
    inxi: 3.3.40
1 Like

On XFCE, i solve this problem with bluetooth off at boot with TLP. Not sure if Plasma has something builtin, or maybe it can be done with Powerdevil rule.

1 Like

Sometimes the network manager locks the wireless devices, and when you boot the PC it shows as disabled and won’t let you turn it on. I ran this command and it never happened again.

rfkill unblock bluetooth
systemctl start bluetooth
3 Likes

Also, some BIOS have bluetooth off on boot settings.

1 Like

Thanks I will try your suggestions and let you know,

Appreciate you taking the time to answer!

@programmingManjar
I did rfkill list to check if there were any blocks but there weren’t

1: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
6: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

I did the commands and will try again after next boot

@Teo
I installed tlp it’s part of the extra repo so it’s already there, found the steps after some search, I’ll try it as well
the steps just to confirm were:

  1. go to /etc/tlp.conf
  2. uncomment these 2 lines:
DEVICES_TO_DISABLE_ON_STARTUP="bluetooth"
RESTORE_DEVICE_STATE_ON_STARTUP=0
  1. sudo tlp start

oh, btw plasma does have startup option in the settings, not sure about the disable bluetooth option tho.

edit: I found an option to disable it on start through editing /etc/bluetooth/main.conf apparently I had AutoEnable=true I set it to false now, and will update you.

Mod edit: Consecutive posts merged.

Are you sure you are up to date with merged .pacnew files? Cause this was one of the changes after the May update - remember state got deprecated. If you merged the pacnew you shouldn’t have it. And the other one is also not what you want.

The current working option is called something like “enabled devices on boot” (sorry can’t check now) and by default contains only “wifi”. Which you change to “wifi bluetooth”.
That worked in my case.

@Teo
I believe I am merged with the latest .pacnew as I haven’t made any manual changes.

Just checked my tlp.conf. The only uncommented line i have is

DEVICES_TO_ENABLE_ON_STARTUP="wifi bluetooth"
1 Like

thanks I went ahead and uncommented the same line, I am still experiencing the same issue though, it has not been fixed, not sure what the error is, I could post the fix that works for me but it’s annoying that I have to run this script on each login.

#!/usr/bin/env zsh

sudo modprobe -r btusb
sudo modprobe btusb
sudo systemctl restart bluetooth

So far these 3 commands in sequence are what makes the bluetooth work for me.

So it is a USB bluetooth stick? I thought it is a pci card? That makes a difference i guess. At least there are problems with this since at least 2016 in the internet forums.

If that workaround works for you, make a systemd service that starts on boot maybe? The alternative will probably be some udev rule but i do not know how to do it this way.

I feel a good part of the answer will be in your system log. After a reboot, wait a minute then login. Run your script to disable and re-enable bluetooth then run: journalctl -b | grep -iE "bluetooth|hci|btusb"

But I also found this thread. Its a little old but its the same device you have 8087:0029. You could check your firmware is up to date fwupdmgr, and try a different kernel, perhaps firstly a newer LTS and then an older LTS kernel if the newer one doesn’t work.

@Teo No, it’s an integrated card, no sticks.
Do I have the wrong thing?

lsusb | grep “Bluetooth”:

Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth

@bananamangodog

I just rebooted, ran the script, and got the logs.

journalctl -b | grep -iE “bluetooth|hci|btusb”

ay 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.0: version 3.0
May 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
May 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.0: 1/1 ports implemented (port mask 0x1)
May 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
May 31 11:10:53 Yamo-Legion5 kernel: scsi host0: ahci
May 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
May 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
May 31 11:10:53 Yamo-Legion5 kernel: ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part
May 31 11:10:53 Yamo-Legion5 kernel: scsi host1: ahci
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 1
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 2
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
May 31 11:10:53 Yamo-Legion5 kernel: usb usb1: Product: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: usb usb1: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb usb2: Product: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: usb usb2: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 3
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 4
May 31 11:10:53 Yamo-Legion5 kernel: xhci_hcd 0000:05:00.4: Host supports USB 3.1 Enhanced SuperSpeed
May 31 11:10:53 Yamo-Legion5 kernel: usb usb3: Product: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: usb usb3: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb usb4: Product: xHCI Host Controller
May 31 11:10:53 Yamo-Legion5 kernel: usb usb4: Manufacturer: Linux 6.12.91-1-MANJARO xhci-hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb 1-3: new high-speed USB device number 2 using xhci_hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb 3-3: new full-speed USB device number 3 using xhci_hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb 3-1.1: new full-speed USB device number 4 using xhci_hcd
May 31 11:10:53 Yamo-Legion5 kernel: usb 3-4: new full-speed USB device number 5 using xhci_hcd
May 31 11:10:57 Yamo-Legion5 NetworkManager[2541]: <info>  [1780215057.0442] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.56.1-1/libnm-device-plugin-bluetooth.so)
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: Core ver 2.22
May 31 11:10:57 Yamo-Legion5 kernel: NET: Registered PF_BLUETOOTH protocol family
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: HCI device and connection manager initialized
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: HCI socket layer initialized
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: L2CAP socket layer initialized
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: SCO socket layer initialized
May 31 11:10:57 Yamo-Legion5 kernel: usbcore: registered new interface driver btusb
May 31 11:10:57 Yamo-Legion5 systemd[1]: Starting Bluetooth service...
May 31 11:10:57 Yamo-Legion5 (bluetoothd)[3704]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 11:10:57 Yamo-Legion5 bluetoothd[3704]: Bluetooth daemon 5.86
May 31 11:10:57 Yamo-Legion5 systemd[1]: Started Bluetooth service.
May 31 11:10:57 Yamo-Legion5 bluetoothd[3704]: Starting SDP server
May 31 11:10:57 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: BNEP filters: protocol multicast
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: BNEP socket layer initialized
May 31 11:10:57 Yamo-Legion5 bluetoothd[3704]: Bluetooth management interface 1.23 initialized
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware already loaded
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 31 11:10:57 Yamo-Legion5 bluetoothd[3704]: Battery Provider Manager created
May 31 11:10:57 Yamo-Legion5 kernel: Bluetooth: MGMT ver 1.23
May 31 11:10:57 Yamo-Legion5 bluetoothd[3704]: Failed to set default system config for hci0
May 31 11:10:57 Yamo-Legion5 NetworkManager[2541]: <info>  [1780215057.7921] manager: (04:79:70:EC:9C:0B): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/6)
May 31 11:11:07 Yamo-Legion5 kernel: Bluetooth: RFCOMM TTY layer initialized
May 31 11:11:07 Yamo-Legion5 kernel: Bluetooth: RFCOMM socket layer initialized
May 31 11:11:07 Yamo-Legion5 kernel: Bluetooth: RFCOMM ver 1.11
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 11:11:07 Yamo-Legion5 bluetoothd[3704]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 31 11:11:54 Yamo-Legion5 sudo[21698]:     yamo : TTY=pts/22 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/modprobe -r btusb
May 31 11:11:54 Yamo-Legion5 kernel: usbcore: deregistering interface driver btusb
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Battery Provider Manager destroyed
May 31 11:11:54 Yamo-Legion5 systemd[1]: Stopped target Bluetooth Support.
May 31 11:11:54 Yamo-Legion5 sudo[21757]:     yamo : TTY=pts/22 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/modprobe btusb
May 31 11:11:54 Yamo-Legion5 kernel: usbcore: registered new interface driver btusb
May 31 11:11:54 Yamo-Legion5 systemd[7485]: Reached target Bluetooth.
May 31 11:11:54 Yamo-Legion5 systemd[1]: Reached target Bluetooth Support.
May 31 11:11:54 Yamo-Legion5 sudo[21762]:     yamo : TTY=pts/22 ; PWD=/home/yamo ; USER=root ; COMMAND=/usr/bin/systemctl restart bluetooth
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Terminating
May 31 11:11:54 Yamo-Legion5 systemd[1]: Stopping Bluetooth service...
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Stopping SDP server
May 31 11:11:54 Yamo-Legion5 bluetoothd[3704]: Exit
May 31 11:11:54 Yamo-Legion5 systemd[1]: bluetooth.service: Deactivated successfully.
May 31 11:11:54 Yamo-Legion5 systemd[1]: Stopped Bluetooth service.
May 31 11:11:54 Yamo-Legion5 systemd[1]: Starting Bluetooth service...
May 31 11:11:54 Yamo-Legion5 (bluetoothd)[21770]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
May 31 11:11:54 Yamo-Legion5 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 31 11:11:54 Yamo-Legion5 kernel: Bluetooth: hci0: Boot Address: 0x24800
May 31 11:11:54 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware Version: 193-33.24
May 31 11:11:54 Yamo-Legion5 kernel: Bluetooth: hci0: Firmware already loaded
May 31 11:11:54 Yamo-Legion5 kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Bluetooth daemon 5.86
May 31 11:11:54 Yamo-Legion5 systemd[1]: Started Bluetooth service.
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Starting SDP server
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Bluetooth management interface 1.23 initialized
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Battery Provider Manager created
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Failed to set default system config for hci0
May 31 11:11:54 Yamo-Legion5 kernel: Bluetooth: MGMT ver 1.23
May 31 11:11:54 Yamo-Legion5 NetworkManager[2541]: <info>  [1780215114.7620] manager: (04:79:70:EC:9C:0B): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/8)
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 31 11:11:54 Yamo-Legion5 bluetoothd[21770]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex

Mod edit: Consecutive posts merged.

Actually the AX200 is one of the best supported Bluetooth chipsets for Linux.

Is there a chance, that this could be the Problem “bluetooth.service: ConfigurationDirectory ‘bluetooth’ already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)”

Followed by: “Failed to set default system config for hci0”

Low probability. The permissions are known “opinion” of the bluetooth developers and this pops up on every update.
The error - maybe but i have a similar one and it works… :man_shrugging:

Nothing else is jumping out as an issue in this output. I’m sure there was a post about this recently, but I can’t find it. However I doubt this actually causes any harm or the issue here but one could always change systemd bluetooth.service ConfigurationDirectoryMode value from 0555 to 0755. But remember that it will likely get overwritten each time bluez is updated (unless they’ve change it).

Modifying systemd’s bluetooth.service unit, i.e. changing the ConfigurationDirectoryMode value from 0555 to 0755, reconciles the /etc/bluetooth directory created by bluez with mode 0755 with the service unit’s key-value setting of 0555.

@Yamo does it work fine out of the box - i.e. from a USB boot image?

I’m leaning toward it being the order in which something is getting loaded. Perhaps NetorkManager is now allowing bluetooth to activate correctly or it’s taking over. Might need to interrogate your logs further without the grep mask I suggested. Make sure there aren’t any further warnings or errors and make note of what order things are activating.

Could it be something in the way bluez directory is set up?
I mean I followed this wiki Bluetooth - ArchWiki trying to troubleshoot before but nothing in it seemed to work.
Not sure if this is relevant but this all happened after I made the mistake of trying pipewire, it had some issues that I didn’t like, so I switched back to pulse again and it has been happening ever since.

The permissions are not the problem, this warning is there since years. And root can write everywhere anyway.

I also thought exactly that about the loading order. In fact, this is the only logical explanation, because it works after restart of the module and service. But i don’t see anything in the log (except hci error, not sure about those).

Worst case scenario, as said, if you cannot find the real cause, a workaround will be a small script restarting it a minute after boot, launched from a systemwide systed service (because this needs root).

Hmmm, changing from pulse to pipewire and back might have something to do with it. Not sure.

You can use something like

For such long logs, otherwise you’ll probably hit some forum limit.

You’re a savior, this was so much pain, :joy:

Here is the logs from boot until the issue is resolved, I’ll go ahead and delete previous messages of logs

Mod edit: Merged consecutive posts.

It’s always nice when the actual fix gets documented, since Bluetooth startup issues can be frustrating to track down. This will probably help quite a few people who run into the same behavior after an update.

1 Like