Bluetooth Device Wizard can't find my devices

Hi! I am using an external CSR 4.0 adapter for bluetooth, and the bluetooth device wizard can't seem to find my bluetooth devices. I tried it with my bluetooth speaker and my dualshock 4 controller. It is just stuck at scanning. Any idea why this might be? Bluetooth works fine on windows but not on garuda linux. I couldn't seem to make it work on other linux distros too :frowning:

inxi -Fxxxza

System:    Kernel: 5.11.6-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.1 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=babfeca7-69ba-4aac-bc94-681f770f0c20 
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 
systemd.unified_cgroup_hierarchy=1 loglevel=3 sysrq_always_enabled=1 
Desktop: KDE Plasma 5.21.3 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM 
Distro: Garuda Linux 
Machine:   Type: Desktop Mobo: Micro-Star model: H310M PRO-VDH (MS-7B29) v: 1.0 serial: <filter> 
UEFI: American Megatrends v: 1.20 date: 03/30/2018 
CPU:       Info: Quad Core model: Intel Core i3-8100 bits: 64 type: MCP arch: Kaby Lake note: check 
family: 6 model-id: 9E (158) stepping: B (11) microcode: DE L2 cache: 6 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 
Speed: 3600 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 3600 2: 3600 3: 3600 4: 3600 
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
Type: mds mitigation: Clear CPU buffers; SMT disabled 
Type: meltdown mitigation: PTI 
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 generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling 
Type: srbds mitigation: Microcode 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 8th Gen Core Processor Gaussian Mixture Model vendor: Micro-Star MSI 
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e91 class ID: 0380 
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 460.56 
alternate: nouveau,nvidia_drm bus ID: 01:00.0 chip ID: 10de:1c82 class ID: 0300 
Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: modesetting,nvidia 
display ID: :0 screens: 1 
Screen-1: 0 s-res: 3286x1080 s-dpi: 96 s-size: 867x285mm (34.1x11.2") s-diag: 913mm (35.9") 
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") 
diag: 551mm (21.7") 
Monitor-2: DP-1-1 res: 1366x768 hz: 60 dpi: 85 size: 410x230mm (16.1x9.1") diag: 470mm (18.5") 
OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 460.56 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
alternate: snd_soc_skl,snd_sof_pci bus ID: 00:1f.3 chip ID: 8086:a348 class ID: 0403 
Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 
chip ID: 10de:0fb9 class ID: 0403 
Device-3: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-14:7 
chip ID: 046d:081b class ID: 0102 serial: <filter> 
Sound Server: ALSA v: k5.11.6-zen1-1-zen 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI 
driver: r8169 v: kernel port: 4000 bus ID: 02:00.0 chip ID: 10ec:8168 class ID: 0200 
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Device-2: Realtek RTL8188EE Wireless Network Adapter driver: rtl8188ee v: kernel port: 3000 
bus ID: 03:00.0 chip ID: 10ec:8179 class ID: 0280 
IF: wlp3s0 state: down mac: <filter> 
Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8 
bus ID: 1-1:2 chip ID: 0a12:0001 class ID: e001 
Message: Required tool hciconfig not installed. Check --recommends 
Drives:    Local Storage: total: 1.72 TiB used: 29.56 GiB (1.7%) 
SMART Message: Unable to run smartctl. Root privileges required. 
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DX001-1NS162-SSHD size: 931.51 GiB 
block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
rev: HP76 scheme: GPT 
ID-2: /dev/sdb maj-min: 8:16 vendor: Gigabyte model: GP-GSTFS31240GNTD size: 223.57 GiB 
block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> 
rev: 61.2 scheme: GPT 
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital model: WD6400BPVT-16HXZT1 
size: 596.17 GiB block size: physical: 512 B logical: 512 B rotation: 5400 rpm serial: <filter> 
rev: 2.12 scheme: GPT 
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: HP model: v221w size: 14.86 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition: ID-1: / raw size: 48.85 GiB size: 48.85 GiB (100.00%) used: 21.99 GiB (45.0%) fs: btrfs
dev: /dev/sdb5 maj-min: 8:21
ID-2: /boot/efi raw size: 953 MiB size: 951.1 MiB (99.80%) used: 576 KiB (0.1%) fs: vfat
dev: /dev/sdb6 maj-min: 8:22
ID-3: /home raw size: 587.07 GiB size: 587.07 GiB (100.00%) used: 7.57 GiB (1.3%) fs: btrfs
dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw size: 48.85 GiB size: 48.85 GiB (100.00%) used: 21.99 GiB (45.0%) fs: btrfs
dev: /dev/sdb5 maj-min: 8:21
ID-5: /var/tmp raw size: 48.85 GiB size: 48.85 GiB (100.00%) used: 21.99 GiB (45.0%) fs: btrfs
dev: /dev/sdb5 maj-min: 8:21
Swap:      Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 3.88 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 3.88 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 3.88 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 3.88 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: 1024 dev: /dev/sdc3
maj-min: 8:35
Sensors:   System Temperatures: cpu: 51.0 C mobo: N/A gpu: nvidia temp: 42 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 40%
Info:      Processes: 268 Uptime: 1h 40m wakeups: 0 Memory: 15.5 GiB used: 4.18 GiB (26.9%) Init: systemd
v: 247 Compilers: gcc: 10.2.0 clang: 11.1.0 Packages: 1517 pacman: 1511 lib: 443 flatpak: 6
Shell: fish v: 3.1.2 running in: konsole inxi: 3.3.01

I suspect this is the important part:

Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8 
bus ID: 1-1:2 chip ID: 0a12:0001 class ID: e001 
Message: Required tool hciconfig not installed. Check --recommends

Installed bluez-utils-compat. Still not working.
New Bluetooth info:

Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8 
bus ID: 1-1:2 chip ID: 0a12:0001 class ID: e001 
Report: ID: hci0 state: up running address: <filter> 
Info: acl-mtu: 640:4 sco-mtu: 64:8 link-policy: rswitch hold sniff park link-mode: slave accept

This could be the problem their are a lot of this make that do not work, not saying yours is one but there are a lot of threads on this particular chip.
THe arch wiki also mentions this chip search under bluetooth

5 Likes

When these adapter work they're great, but they're also some that are a real pain to get working. The post below on the forum is one of the few solutions that actually have worked for this adapter:

Good luck, getting it working and welcome to Garuda.

Tip:

A little extra time searching is usually the most productive way to find a solution. :wink:

5 Likes

It Worked! Thanks a lot!

Believe me, I put a lot of time in this and somehow didn't find a solution this simple, maybe it is just inexperience. Thanks for the help! Arch wiki is such a great resource, but I can't understand many things written there as I am new to linux :wink:

That's fine, I wasn't going to apply the
scarlet "V" (help vampire) to your forehead just yet. :rofl:

It's just that you never know how much effort some people put into searching before opening a help request. Some people, their automatic default is to open a help request first. We simply try to encourage users to exhaust their search capabilities before opening a help request on the forum.

So glad that old thread helped get your adapter working.

3 Likes

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