Using Garuda i3wm in dell intel i5 10th gen .linux zen.i have required bluetooth utils but my wireless airdopes never connect.same issue faced with endeavour i3wm too
Read
and post
inxi -zaF
as text.
2 Likes
inxi -Faz
is same and shorter 
5 Likes
As a matter of fact, I actually copied the letters of inxi from one of your previous posts because I wasn’t sure 
2 Likes
I never startet with -a ... and yes I learnd here in Forum that a include the three x.
Next time, don't use old posts from me 
4 Likes
Sorry for the OT, but I'd like to recall this one
https://forum.garudalinux.org/t/inxi-fxxxza-inxi-faz/8878
5 Likes
System: Kernel: 5.13.5-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f510ce18-e009-4b48-98cd-c183b5227f9d rw rootflags=subvol=@ quiet
splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: i3 4.19.1 info: i3bar vt: 7 dm: LightDM 1.30.0 Distro: Garuda Linux
base: Arch Linux
Machine: Type: Laptop System: Dell product: Inspiron 3593 v: N/A serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: Dell model: 04N9HV v: A00 serial: <filter> UEFI: Dell v: 1.15.0
date: 04/08/2021
Battery: ID-1: BAT0 charge: 16.6 Wh (49.8%) condition: 33.3/42.0 Wh (79.4%) volts: 12.1
min: 11.4 model: SMP DELL VM73297 type: Li-poly serial: <filter>
status: Charging
CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake
family: 6 model-id: 7E (126) stepping: 5 microcode: A6 cache: L2: 6 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046
Speed: 3187 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 3187 2: 3600 3: 3584
4: 3600 5: 3602 6: 3602 7: 3600 8: 3601
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
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: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:8a56 class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3
chip-ID: 0bda:5520 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.12 driver: loaded: intel unloaded: modesetting
alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 143 size: 340x190mm (13.4x7.5")
diag: 389mm (15.3")
OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.1.5
direct render: Yes
Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_icl bus-ID: 00:1f.3 chip-ID: 8086:34c8
class-ID: 0403
Sound Server-1: ALSA v: k5.13.5-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.32 running: yes
Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169
v: kernel port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: enp1s0 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
vendor: Dell driver: ath10k_pci v: kernel port: 3000 bus-ID: 02:00.0
chip-ID: 168c:0042 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4
chip-ID: 0cf3:e009 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter>
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
port: 4060 bus-ID: 00:17.0 chip-ID: 8086.282a rev: 30 class-ID: 0104
Drives: Local Storage: total: 1.14 TiB used: 264.71 GiB (22.6%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 5400 serial: <filter> rev: 1002 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 model: AAR256GM061320030 size: 238.47 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
serial: <filter> rev: 7A0 scheme: GPT
Partition: ID-1: / raw-size: 84.83 GiB size: 84.83 GiB (100.00%) used: 17.86 GiB (21.1%)
fs: btrfs dev: /dev/sdb8 maj-min: 8:24
ID-2: /boot/efi raw-size: 1000 MiB size: 998 MiB (99.80%) used: 576 KiB (0.1%)
fs: vfat dev: /dev/sdb7 maj-min: 8:23
ID-3: /home raw-size: 84.83 GiB size: 84.83 GiB (100.00%)
used: 17.86 GiB (21.1%) fs: btrfs dev: /dev/sdb8 maj-min: 8:24
ID-4: /var/log raw-size: 84.83 GiB size: 84.83 GiB (100.00%)
used: 17.86 GiB (21.1%) fs: btrfs dev: /dev/sdb8 maj-min: 8:24
ID-5: /var/tmp raw-size: 84.83 GiB size: 84.83 GiB (100.00%)
used: 17.86 GiB (21.1%) fs: btrfs dev: /dev/sdb8 maj-min: 8:24
Swap: Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.54 GiB used: 1.51 GiB (20.0%) priority: 100
dev: /dev/zram0
Sensors: System Temperatures: cpu: 71.0 C mobo: N/A
Fan Speeds (RPM): cpu: 4654
Info: Processes: 298 Uptime: 5h 41m wakeups: 5 Memory: 7.54 GiB used: 5.81 GiB (77.1%)
Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1
Packages: pacman: 1245 lib: 309 Shell: Bash v: 5.1.8 running-in: alacritty
inxi: 3.3.06
If you include terminal outputs in your post please use the proper output format in your post.
Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.
Have you tested other kernels yet?
Many times bluetooth failing to connect can be fixed by a change in kernel. I would suggest testing linix-lts, linux-mainline and perhaps a couple of others.
Have you tested other Garuda desktops from a live environment to see if they're working?
Have you checked dmesg for bluetooth related errors?
This was issue long ago,now due to arch update,pipewire updates,my Bluetooth wireless is working fine.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.