Bluetooth device on garuda

Today, I installed Garuda for the first time, and after a LOT of tweaking I riced it pretty well for myself. problem is now my wireless earbuds, I connected them over bluetooth and Garuda recognizes them fine, even displays them as an "audio device", problem is that they don't play anything, and I don't have such device listed anywhere. All I have is family17h controller (?) and my HDMI output...
what do?

Post your inxi -Faz

and welcome.

2 Likes
System:    Kernel: 5.14.6-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=4fca18c1-0dd3-45f3-a311-eda326496099  
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux  
base: Arch Linux  
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: <filter>  
UEFI: American Megatrends v: 4011 date: 04/19/2018  
CPU:       Info: 6-Core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen family: 17 (23)  
model-id: 1 stepping: 1 microcode: 8001137 cache: L2: 3 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 83838  
Speed: 2797 MHz min/max: 1550/3500 MHz boost: disabled Core speeds (MHz): 1: 2797 2: 2877  
3: 2794 4: 2874 5: 2796 6: 2804 7: 2797 8: 2836 9: 2809 10: 2806 11: 3267 12: 2813  
Vulnerabilities: Type: itlb_multihit status: Not affected  
Type: l1tf status: Not affected  
Type: mds status: Not affected  
Type: meltdown status: Not affected  
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp  
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
Type: spectre_v2  
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling  
Type: srbds status: Not affected  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nvidia v: 470.74  
alternate: nouveau,nvidia_drm bus-ID: 07:00.0 chip-ID: 10de:2182 class-ID: 0300  
Device-2: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 6-1:2 chip-ID: 2833:0211  
class-ID: ef00 serial: <filter>  
Device-3: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 6-3:3 chip-ID: 2833:0211  
class-ID: ef00 serial: <filter>  
Device-4: Oculus VR Rift CV1 Sensor type: USB driver: uvcvideo bus-ID: 6-4:4 chip-ID: 2833:0211  
class-ID: ef00 serial: <filter>  
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: nvidia display-ID: :0  
screens: 1  
Screen-1: 0 s-res: 3200x1080 s-dpi: 92 s-size: 883x301mm (34.8x11.9") s-diag: 933mm (36.7")  
Monitor-1: DVI-D-0 res: 1280x1024 hz: 60 dpi: 86 size: 376x301mm (14.8x11.9") diag: 482mm (19")  
Monitor-2: HDMI-0 res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.9x11.8") diag: 609mm (24")  
OpenGL: renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 470.74  
direct render: Yes  
Audio:     Device-1: NVIDIA TU116 High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 07:00.1  
chip-ID: 10de:1aeb class-ID: 0403  
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel  
bus-ID: 09:00.3 chip-ID: 1022:1457 class-ID: 0403  
Sound Server-1: ALSA v: k5.14.6-zen1-1-zen running: yes  
Sound Server-2: JACK v: 1.9.19 running: no  
Sound Server-3: PulseAudio v: 15.0 running: no  
Sound Server-4: PipeWire v: 0.3.35 running: yes  
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A  
driver: r8169 v: kernel port: f000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200  
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>  
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8  
bus-ID: 1-3:2 chip-ID: 0a12:0001 class-ID: e001  
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>  
Drives:    Local Storage: total: 4.21 TiB used: 13.65 GiB (0.3%)  
SMART Message: Unable to run smartctl. Root privileges required.  
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SKC600512G size: 476.94 GiB block-size:  
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0102
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD40EZRZ-00WN9B0 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: 0A80 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: KingDian model: N480-120GB size: 111.79 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1A scheme: MBR
Partition: ID-1: / raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 13.65 GiB (2.9%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 13.65 GiB (2.9%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 13.65 GiB (2.9%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 13.65 GiB (2.9%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 23.41 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 47.9 C mobo: N/A gpu: nvidia temp: 43 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 39%
Info:      Processes: 307 Uptime: 1h 5m wakeups: 0 Memory: 23.41 GiB used: 3.9 GiB (16.6%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1159 lib: 279
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

The problem has been fixed by a reboot and nothing else

Next time, that first:

Then search online.
And then, if if you still need help, that:

2 Likes

Sounds like you updated your kernel but didn't reboot. Newly-connected devices won't be detected until the new kernel is loaded.

1 Like

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