Not able to enable Bluetooth

Hello.

I'm new to Arch and dual booted garuda with windows 10 on my Asus Tuf A15 system. Everything is working fine just i'm not able to enable bluetooth. Hovering over grayed-out bluetooth icon showing 'No Bluetooth adapter available.'

My bluetooth adapter present on machine is from Mediatek.
I've read almost all the threads about this issue.

  • Fast boot and secure boot is disabled.
  • turned off hibernation too in windows.
  • Turned of wifi powersave option in Garuda network Assistant
  • Tried various linux kernels -> lts, mainline, hardened

I thought it's kernel issue ( of 5.13.x ) but bluetooth was working in live install ( when i was installing garuda ) and also after install it was working. After that i rebooted my laptop and still it was working. After that i did pacman -Syy and rebooted my system and now it's not working.

╰─λ inxi -Faz
System:    Kernel: 5.13.9-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=c9b200e5-7dce-4444-a082-ab779f1022d8  
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 resume=UUID=ac02eee0-3cf0-4e16-9245-506de4be3952 loglevel=3
Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM  
Distro: Garuda Linux base: Arch Linux  
Machine:   Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A15 FA506QM_FA566QM v: 1.0  
serial: <filter>  
Mobo: ASUSTeK model: FA506QM v: 1.0 serial: <filter> UEFI: American Megatrends LLC.  
v: FA506QM.307 date: 06/02/2021  
Battery:   ID-1: BAT1 charge: 76.0 Wh (84.2%) condition: 90.3/90.2 Wh (100.1%) volts: 16.4 min: 15.9  
model: ASUS A32-K55 type: Li-ion serial: N/A status: Discharging  
CPU:       Info: 8-Core model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3  
family: 19 (25) model-id: 50 (80) stepping: 0 microcode: A50000C cache: L2: 4 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102206  
Speed: 1397 MHz min/max: 1200/3200 MHz boost: enabled Core speeds (MHz): 1: 1397 2: 2868  
3: 1397 4: 1397 5: 1397 6: 1397 7: 1397 8: 1397 9: 1397 10: 1397 11: 1731 12: 1396 13: 1397  
14: 1888 15: 1603 16: 1691  
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, IBRS_FW, STIBP: always-on, RSB filling  
Type: srbds status: Not affected  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK driver: nvidia  
v: 470.57.02 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:2520 class-ID: 0300  
Device-2: AMD Cezanne vendor: ASUSTeK driver: amdgpu v: kernel bus-ID: 05:00.0  
chip-ID: 1002:1638 class-ID: 0300  
Device-3: Sonix USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus-ID: 1-4:2  
chip-ID: 322e:202c class-ID: 0e02  
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: modesetting,nvidia  
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: eDP-1 res: 1920x1080 hz: 144 dpi: 142 size: 344x193mm (13.5x7.6")  
diag: 394mm (15.5")  
OpenGL: renderer: AMD RENOIR (DRM 3.41.0 5.13.9-zen1-1-zen LLVM 12.0.1) v: 4.6 Mesa 21.1.6  
direct render: Yes  
Audio:     Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 01:00.1  
chip-ID: 10de:228e class-ID: 0403  
Device-2: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 05:00.1  
chip-ID: 1002:1637 class-ID: 0403  
Device-3: AMD Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A  
alternate: snd_pci_acp3x, snd_rn_pci_acp3x bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480  
Device-4: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel  
bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403  
Sound Server-1: ALSA v: k5.13.9-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.33 running: yes  
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169  
v: kernel port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200  
IF: enp2s0 state: down mac: <filter>  
Device-2: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel port: e000 bus-ID: 03:00.0  
chip-ID: 14c3:7961 class-ID: 0280  
IF: wlp3s0 state: up mac: <filter>  
Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-3:2  
chip-ID: 13d3:3563 class-ID: e001 serial: <filter>  
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: N/A
Drives:    Local Storage: total: 476.94 GiB used: 8.87 GiB (1.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: HFM512GD3JX013N size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 41000C20 temp: 45.9 C scheme: GPT
Partition: ID-1: / raw-size: 44.92 GiB size: 44.92 GiB (100.00%) used: 8.68 GiB (19.3%) fs: btrfs
dev: /dev/nvme0n1p9 maj-min: 259:9
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 30.1 MiB (11.8%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 48.83 GiB size: 48.83 GiB (100.00%) used: 162.2 MiB (0.3%) fs: btrfs
dev: /dev/nvme0n1p8 maj-min: 259:8
ID-4: /var/log raw-size: 44.92 GiB size: 44.92 GiB (100.00%) used: 8.68 GiB (19.3%) fs: btrfs
dev: /dev/nvme0n1p9 maj-min: 259:9
ID-5: /var/tmp raw-size: 44.92 GiB size: 44.92 GiB (100.00%) used: 8.68 GiB (19.3%) fs: btrfs
dev: /dev/nvme0n1p9 maj-min: 259:9
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 3.91 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p10 maj-min: 259:10
ID-2: swap-2 type: zram size: 15.04 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 59.0 C mobo: N/A gpu: amdgpu temp: 52.0 C
Fan Speeds (RPM): cpu: 0
Info:      Processes: 386 Uptime: 11m wakeups: 1047 Memory: 15.04 GiB used: 3.49 GiB (23.2%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1180 lib: 296
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06
╰─λ sudo dmesg | grep -i bluetooth
[sudo] password for av:
[    4.124944] Bluetooth: Core ver 2.22
[    4.125012] Bluetooth: HCI device and connection manager initialized
[    4.125036] Bluetooth: HCI socket layer initialized
[    4.125039] Bluetooth: L2CAP socket layer initialized
[    4.125058] Bluetooth: SCO socket layer initialized
[    4.555971] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.555990] Bluetooth: BNEP filters: protocol multicast
[    4.556006] Bluetooth: BNEP socket layer initialized
╰─λ journalctl -b -1 | grep -i bluetooth
Aug 15 19:18:51 darkShadow kernel: Bluetooth: Core ver 2.22
Aug 15 19:18:51 darkShadow kernel: Bluetooth: HCI device and connection manager initialized
Aug 15 19:18:51 darkShadow kernel: Bluetooth: HCI socket layer initialized
Aug 15 19:18:51 darkShadow kernel: Bluetooth: L2CAP socket layer initialized
Aug 15 19:18:51 darkShadow kernel: Bluetooth: SCO socket layer initialized
Aug 15 19:18:51 darkShadow systemd[1]: Started Bluetooth autoconnect service.
Aug 15 19:18:51 darkShadow audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blueto
oth-autoconnect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 15 19:18:51 darkShadow systemd[1]: Starting Bluetooth service...
Aug 15 19:18:51 darkShadow bluetoothd[622]: Bluetooth daemon 5.60
Aug 15 19:18:51 darkShadow bluetoothd[622]: Starting SDP server
Aug 15 19:18:51 darkShadow systemd[1]: Started Bluetooth service.
Aug 15 19:18:51 darkShadow audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blueto
oth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 15 19:18:51 darkShadow systemd[1]: Reached target Bluetooth Support.
Aug 15 19:18:51 darkShadow kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Aug 15 19:18:51 darkShadow kernel: Bluetooth: BNEP filters: protocol multicast
Aug 15 19:18:51 darkShadow kernel: Bluetooth: BNEP socket layer initialized
Aug 15 19:18:51 darkShadow dbus-daemon[624]: [system] Activating via systemd: service name='org.freedesktop.ho
stname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0 pid=622 comm="/usr/lib/bluet
ooth/bluetoothd ")
Aug 15 19:18:51 darkShadow bluetoothd[622]: Bluetooth management interface 1.20 initialized
Aug 15 19:18:52 darkShadow NetworkManager[626]: <info>  [1629035332.0154] Loaded device plugin: NMBluezManager
(/usr/lib/NetworkManager/1.32.6-1/libnm-device-plugin-bluetooth.so)
Aug 15 19:18:59 darkShadow systemd[1816]: Starting Bluetooth OBEX service...
Aug 15 19:18:59 darkShadow systemd[1816]: Started Bluetooth OBEX service.
Aug 15 19:18:59 darkShadow kded5[2058]: bluedevil: Bluetooth operational changed true
Aug 15 19:21:54 darkShadow dbus-daemon[624]: [system] Activating via systemd: service name='org.freedesktop.ho
me1' unit='dbus-org.freedesktop.home1.service' requested by ':1.76' (uid=0 pid=7053 comm="sudo vim /etc/blueto
oth/main.conf ")
Aug 15 19:22:11 darkShadow dbus-daemon[624]: [system] Activating via systemd: service name='org.freedesktop.ho
me1' unit='dbus-org.freedesktop.home1.service' requested by ':1.78' (uid=0 pid=7530 comm="sudo vim /etc/blueto
oth/main.conf ")
Aug 15 19:22:11 darkShadow sudo[7530]:       av : TTY=pts/0 ; PWD=/home/av ; USER=root ; COMMAND=/usr/bin/vim
/etc/bluetooth/main.conf
Aug 15 19:24:16 darkShadow dbus-daemon[624]: [system] Activating via systemd: service name='org.freedesktop.ho
me1' unit='dbus-org.freedesktop.home1.service' requested by ':1.79' (uid=0 pid=9459 comm="sudo pacman -Ss garu
da-bluetooth ")
Aug 15 19:24:16 darkShadow sudo[9459]:       av : TTY=pts/0 ; PWD=/home/av ; USER=root ; COMMAND=/usr/bin/pacm
an -Ss garuda-bluetooth
Aug 15 19:26:49 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:26:50 darkShadow systemd[1816]: Starting Bluetooth management applet...
Aug 15 19:26:50 darkShadow systemd[1]: Starting Bluetooth management mechanism...
Aug 15 19:26:50 darkShadow systemd[1]: Started Bluetooth management mechanism.
Aug 15 19:26:50 darkShadow systemd[1816]: Started Bluetooth management applet.
Aug 15 19:27:01 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:27:14 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:27:34 darkShadow systemd[1816]: Starting Bluetooth Manager...
Aug 15 19:27:34 darkShadow systemd[1816]: Started Bluetooth Manager.
Found module libbluetoothplugin.so with build-id: e264bdb6
a0b41e1677bedba4127fbd917d75d282
Aug 15 19:28:18 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:29:01 darkShadow systemd[1]: Starting Bluetooth management mechanism...
Aug 15 19:29:01 darkShadow systemd[1]: Started Bluetooth management mechanism.
Aug 15 19:29:14 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:29:25 darkShadow systemd[1816]: Starting Bluetooth Manager...
Aug 15 19:29:25 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:29:33 darkShadow systemd[1816]: Starting Bluetooth Manager...
Aug 15 19:29:33 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:29:47 darkShadow systemd[1816]: Starting Bluetooth Manager...
Aug 15 19:29:47 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:31:11 darkShadow dbus-daemon[624]: [system] Activating via systemd: service name='org.freedesktop.ho
me1' unit='dbus-org.freedesktop.home1.service' requested by ':1.108' (uid=0 pid=15260 comm="sudo bluetoothctl
")
Aug 15 19:31:11 darkShadow sudo[15260]:       av : TTY=pts/0 ; PWD=/home/av ; USER=root ; COMMAND=/usr/bin/blu
etoothctl
Aug 15 19:35:37 darkShadow systemd[1]: Starting Bluetooth management mechanism...
Aug 15 19:35:38 darkShadow systemd[1]: Started Bluetooth management mechanism.
Aug 15 19:35:47 darkShadow systemd[1816]: Starting Bluetooth Manager...
Aug 15 19:35:47 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:35:51 darkShadow systemd[1816]: Starting Bluetooth Manager...
Aug 15 19:35:51 darkShadow systemd[1816]: Started Bluetooth Manager.
Aug 15 19:36:54 darkShadow systemd[1]: Stopped target Bluetooth Support.
Aug 15 19:36:54 darkShadow bluetoothd[622]: Terminating
Aug 15 19:36:54 darkShadow systemd[1]: Stopping Bluetooth service...
Aug 15 19:36:54 darkShadow dbus-daemon[624]: [system] Rejected send message, 0 matched rules; type="error", se
nder=":1.49" (uid=1000 pid=2443 comm="/usr/bin/pipewire-media-session ") interface="(unset)" member="(unset)"
error name="org.bluez.Profile1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=622 com
m="/usr/lib/bluetooth/bluetoothd ")
Aug 15 19:36:54 darkShadow dbus-daemon[624]: [system] Rejected send message, 0 matched rules; type="error", se
nder=":1.49" (uid=1000 pid=2443 comm="/usr/bin/pipewire-media-session ") interface="(unset)" member="(unset)"
error name="org.bluez.Profile1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=622 com
m="/usr/lib/bluetooth/bluetoothd ")
Aug 15 19:36:54 darkShadow bluetoothd[622]: Stopping SDP server
Aug 15 19:36:54 darkShadow bluetoothd[622]: Exit
Aug 15 19:36:54 darkShadow systemd[1]: bluetooth.service: Deactivated successfully.
Aug 15 19:36:54 darkShadow systemd[1]: Stopped Bluetooth service.
Aug 15 19:36:54 darkShadow audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetoo
th comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 15 19:36:54 darkShadow kernel: audit: type=1131 audit(1629036414.446:285): pid=1 uid=0 auid=4294967295 ses
=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res
=success'
Aug 15 19:36:54 darkShadow systemd[1]: Stopping Bluetooth autoconnect service...
Aug 15 19:36:54 darkShadow systemd[1816]: Stopping Bluetooth OBEX service...
Aug 15 19:36:54 darkShadow systemd[1816]: Stopped Bluetooth OBEX service.
Aug 15 19:36:54 darkShadow systemd[1]: bluetooth-autoconnect.service: Deactivated successfully.
Aug 15 19:36:54 darkShadow systemd[1]: Stopped Bluetooth autoconnect service.
Aug 15 19:36:54 darkShadow audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetoo
th-autoconnect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sudo systemctl status bluetooth


● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2021-08-15 19:37:35 IST; 25min ago
Docs: man:bluetoothd(8)
Main PID: 631 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 18428)
Memory: 3.0M
CPU: 22ms
CGroup: /system.slice/bluetooth.service
└─631 /usr/lib/bluetooth/bluetoothd

Aug 15 19:37:35 darkShadow systemd[1]: Starting Bluetooth service...
Aug 15 19:37:35 darkShadow bluetoothd[631]: Bluetooth daemon 5.60
Aug 15 19:37:35 darkShadow bluetoothd[631]: Starting SDP server
Aug 15 19:37:35 darkShadow systemd[1]: Started Bluetooth service.
Aug 15 19:37:35 darkShadow bluetoothd[631]: Bluetooth management interface 1.20 initialized
╰─λ sudo bluetoothctl power on
No default controller available

I can post any other command result.

sudo systemctl start bluetooth
sudo systemctl enable bluetooth
reboot if it works

1 Like

If nothing else works, maybe you could give a look also at this one.

It's not clear to me how this could be applied or if it is already in linux-next, but maybe someone can help you...

3 Likes

Can you post the output of

rfkill list

Not working

Yeah i also thought that it's a kernel issue but as i mentioned it was working for me ( for linux kernel 5.13.x )in live boot as well as in normal boot before i did pacman -Syy.

Yeah sure. Here's output

╰─λ rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

I still believe this is due to interference of windows, even if fast boot is disabled (also in BIOS possibly).
Why don't you try to disable bluetooth in windows and power down completely with the procedure below (although in that context for wifi issues)?

2 Likes

Okay. will try this too. But why i'm not doubting on windows is for 2 normal boot the bluetooth was working fine plus for 1 live boot. After i did pacman -Syy and rebooted, then it stopped working. maybe some upgrade in package conflicting with bluetooth ( random guess not sure ). Is there any command that can show whether this hypothesis is wrong or not ?

If you really want to get rid of this doubt, try to restore to a snapshot before that update.
Timeshift autosnap should be working by default.
If you need to know how to do it, there is an article in the Garuda wiki

You could try to give a look at
/var/log/pacman.log
If there was an update on a package like bluetooth. But theoretically this could be due to a package with a very different name...

1 Like

/var/log/pacman.log gives this output

╰─λ cat /var/log/pacman.log | grep 'bluetooth'
[2021-08-15T18:01:27+0530] [ALPM-SCRIPTLET] bluetooth-autoconnect 1.3-1
[2021-08-15T18:01:27+0530] [ALPM-SCRIPTLET] bluetooth-support 1-3
[2021-08-15T18:02:32+0530] [ALPM-SCRIPTLET] bluetooth-autoconnect 1.3-1
[2021-08-15T18:02:32+0530] [ALPM-SCRIPTLET] bluetooth-support 1-3
[2021-08-15T18:02:44+0530] [ALPM-SCRIPTLET] bluetooth-autoconnect 1.3-1
[2021-08-15T18:02:44+0530] [ALPM-SCRIPTLET] bluetooth-support 1-3

yeah i guess.

will try this too. Thanks @filo

Same issue Ankit. My bluetooth is fine and working before doing pacman -Syu & -Syy. But after the updates it doesn't work.

Please be mindful of the dates when you post to a thread. This one is coming up on a year old. This is called "necrobumping" and it is frowned upon because it pulls the thread off-topic; the chances your issue will be related to the old one are small.

For example: not only was this person running different hardware on a different release than you, but this was all the way back on 5.13 so basically their whole stack is different than yours.

All the same, welcome to the community @devianvisuals . :slightly_smiling_face:

3 Likes