[Solved] Odd bluetooth issue that started recently

Issues & Assistance Networking Support
1

I have a bluetooth speaker as well as a bluetooth mouse
this is the speaker I have Amazon.com
and this is the mouse I have if this information helps
Amazon.com

The issue is during boot up. if the speaker connects up first it is fine but if the mouse connects up first the bluetooth just dies and needs a reboot to get bluetooth working again

I know I could just use the 2.4 dongle that came with the mouse. I may end up going that route but wanted to report it just in case others have the problem or there is a solution. I know when I had this issue with fedora and any and all fedora based distros i was told to just get a different bluetooth adapter as they were thinking it was a faulty adapter. But up until now it worked with Garuda and even all debian based distros I tried on this pc. But guess I could look into getting a different adapter too.

 ╰─λ garuda-inxi
System:
  Kernel: 6.15.4-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=27f7c19c-bea9-4ffd-9917-bd5c85a754bc rw rootflags=subvol=@
    quiet rd.luks.uuid=ff2fc42e-a649-4547-b6c3-bcbc470252e3 loglevel=3
    ibt=off
  Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.15.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: Pro Q670M-C v: Rev 1.xx serial: <superuser required>
    part-nu: SKU uuid: <superuser required> UEFI: American Megatrends v: 1622
    date: 08/23/2022
CPU:
  Info: model: 12th Gen Intel Core i7-12700 bits: 64 type: MST AMCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
    microcode: 0x3A
  Topology: cpus: 1x dies: 1 clusters: 9 cores: 12 threads: 20 mt: 8 tpc: 2
    st: 4 smt: enabled cache: L1: 1024 KiB desc: d-4x32 KiB, 8x48 KiB; i-8x32
    KiB, 4x64 KiB L2: 12 MiB desc: 8x1.2 MiB, 1x2 MiB L3: 25 MiB
    desc: 1x25 MiB
  Speed (MHz): avg: 800 min/max: 800/4800:4900:3600 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
    15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 bogomips: 84480
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
    470/480/570/570X/580/580X/590] vendor: XFX Pine driver: amdgpu v: kernel
    arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-2,HDMI-A-1
    empty: DP-1,DP-3,DVI-D-1 bus-ID: 01:00.0 chip-ID: 1002:67df class-ID: 0300
    temp: 56.0 C
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu d-rect: 3840x1080
    display-ID: 0
  Monitor-1: DP-2 pos: right model: MSI G24C serial: <filter> built: 2021
    res: mode: 1920x1080 hz: 144 scale: 100% (1) dpi: 94 gamma: 1.2
    size: 521x293mm (20.51x11.54") diag: 600mm (23.6") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-1 pos: primary,left model: Asus VS248 serial: <filter>
    built: 2018 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 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: 25.1.4-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi
    polaris10 ACO DRM 3.63 6.15.4-zen2-1-zen) device-ID: 1002:67df
    memory: 7.81 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.313 layers: 9 device: 0 type: discrete-gpu name: AMD
    Radeon RX 580 Series (RADV POLARIS10) driver: mesa radv v: 25.1.4-arch1.2
    device-ID: 1002:67df surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 20.1.6 256 bits) driver: mesa llvmpipe v: 25.1.4-arch1.2 (LLVM
    20.1.6) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon
    RX 470/480 / 570/580/590] vendor: XFX Pine driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aaf0
    class-ID: 0403
  API: ALSA v: k6.15.4-zen2-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.4.6 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: Intel Ethernet I219-LM vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:1a1c class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Fujitsu
    driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 05:00.0 chip-ID: 168c:0034 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Fujitsu driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-13.2:9 chip-ID: 04c5:1330 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
  Local Storage: total: 5.67 TiB used: 1.18 TiB (20.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Crucial model: CT4000P3PSSD8
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40D temp: 40.9 C
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: PNY model: CS1030 250GB SSD
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: CS103900 temp: 38.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Kodak model: SSD X100 480G
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3G30 scheme: MBR
  ID-4: /dev/sdb maj-min: 8:16 vendor: Kodak model: SSD X130 PRO 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: XKR scheme: GPT
  ID-5: /dev/sdg maj-min: 8:96 vendor: Kodak model: SSD X300 480G
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
    fw-rev: 1.00 scheme: MBR
Partition:
  ID-1: / raw-size: 232.59 GiB size: 232.59 GiB (100.00%)
    used: 208.53 GiB (89.7%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
    mapped: luks-ff2fc42e-a649-4547-b6c3-bcbc470252e3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 776 KiB (0.3%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
  ID-3: /home raw-size: 232.59 GiB size: 232.59 GiB (100.00%)
    used: 208.53 GiB (89.7%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
    mapped: luks-ff2fc42e-a649-4547-b6c3-bcbc470252e3
  ID-4: /var/log raw-size: 232.59 GiB size: 232.59 GiB (100.00%)
    used: 208.53 GiB (89.7%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
    mapped: luks-ff2fc42e-a649-4547-b6c3-bcbc470252e3
  ID-5: /var/tmp raw-size: 232.59 GiB size: 232.59 GiB (100.00%)
    used: 208.53 GiB (89.7%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
    mapped: luks-ff2fc42e-a649-4547-b6c3-bcbc470252e3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 70.28 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: amdgpu temp: 56.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 780
Info:
  Memory: total: 72 GiB available: 70.28 GiB used: 8.49 GiB (12.1%)
  Processes: 559 Power: uptime: 3m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 28.09 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 1682 pm: pacman pkgs: 1663 libs: 502
    tools: gnome-software,octopi,paru pm: flatpak pkgs: 19 Compilers:
    clang: 20.1.7 gcc: 15.1.1 Shell: garuda-inxi default: Bash v: 5.2.37
    running-in: gnome-terminal inxi: 3.3.38
Garuda (2.7.3-1):
  System install date:     2025-03-26
  Last full system update: 2025-07-04
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:
2

I totally forgot this is not just an issue during boot up it also happens if the computer goes into stand by/ hibernate / sleep mode.

3

I am replying again because the issue got worse. The bluetooth is dying every 10 minutes with out doing anything. Doing it all day, was trying to watch youtube and play a steam game but kept losing the sound and mouse would stop. So I am thinking maybe the guys at fedora were right in the card is junk. So looking at a new card.

4

Dying every 10 minutes tends to indicate a power saving issue. Check your Pacman log to see if bluedevil was updated during your last system upgrade. If it was, you could try installing the git version or downgrading bluedevil.

I assume your kernel was also likely updated when this issue began. I would suggest testing out at least 3 alternate kernels. I would for sure test at least these kernels:

linux-lts
linux-mainline
linux

Edit:

You could also try rolling back your system with a snapper backup created before your problems began.

3 Likes
5

Thank you, testing a snapshot form the 1st. I know it worked then. So far so good.

1 Like
6

I would increase your snapshot retention number, (if you have the spare space on your drive). I keep a rediculously large number (85), so that I don’t lose a working snapshot when testing many different packages. This will eventually consume a lot of space, so you need to carefully watch your drive’s capacity level.

4 Likes
7

This is working fine now. I did however buy a different bluetooth adapter which I mentioned in the chat. This new adapter is faster and I was able to connect every thing up with no issues. Before getting the new card I did need to keep restoring older snapshots so was not ideal.

8

This is for sure solved I just wanted to add a big thank you. Also last night I took the old buetooth adapter and put it in my 2014 lenovo, which already had a bluetooth adapter but I wanted to see what it would do in that computer. That computer was not running garuda it was running Aurora and it had no issue with a usb blue tooth adapter but this old blue tooth adapter that was having trouble in the new computer. It had way more issues in the lenovo. Nothing would connect at all but connected fine on the usb adapter I even tried taking the usb one out just in case there was some sort of conflict. Nope not working on the lenovo at all. So this old card is going in the recycle. The new card works great and if someone else wants a good bluetooth adapter here is the one I got that works great. Amazon.com

The old one looked a lot like that one but was a different brand and totally different model. Which I can not find any more.

9

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