Bluetooth not working on my new install

Issues & Assistance
,
1

Hello, the bluetooth on my pc has not been working since i installed the os yesterday. I do not know which exact bluetooth chipset my motherboard has as Asus does not list it on their website. I have tried looking for similar issues online but found no solutions that worked for me.

Motherboard: Asus Tuf Gaming B650M Plus Wifi
Kernel: 6.11.3-zen1-1-zen
CPU: Ryzen 5 7600x
GPU: Integrated
No bluetooth adapter.

System:
Kernel: 6.11.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=a21fa28d-e527-47ac-b7f7-0a4d685b6d7e rw rootflags=subvol=@
quiet loglevel=3 hush ibt=off
Desktop: KDE Plasma v: 6.2.0 tk: Qt v: N/A info: frameworks v: 6.6.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: TUF GAMING B650M-PLUS WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 1811 date: 10/07/2023
CPU:
Info: model: AMD Ryzen 5 7600X bits: 64 type: MT MCP arch: Zen 4 gen: 4
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 6 MiB
desc: 6x1024 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2988 min/max: 400/5453 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 2988 2: 2988 3: 2988
4: 2988 5: 2988 6: 2988 7: 2988 8: 2988 9: 2988 10: 2988 11: 2988 12: 2988
bogomips: 112599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Raphael vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: HDMI-A-1 empty: DP-1,Writeback-1 bus-ID: 0b:00.0
chip-ID: 1002:164e class-ID: 0300 temp: 49.0 C
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
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: 24.2.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
raphael_mendocino LLVM 18.1.8 DRM 3.59 6.11.3-zen1-1-zen)
device-ID: 1002:164e memory: 500 MiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 9 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv
v: 24.2.4-arch1.1 device-ID: 1002:164e surfaces: xcb,xlib,wayland
device: 1 type: cpu name: llvmpipe (LLVM 18.1.8 256 bits)
driver: mesa llvmpipe v: 24.2.4-arch1.1 (LLVM 18.1.8)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High Definition
Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0b:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.11.3-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.5 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: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
vendor: AzureWave driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 08:00.0 chip-ID: 14c3:7961 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:3
chip-ID: 13d3:3563 class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
Local Storage: total: 465.76 GiB used: 17.5 GiB (3.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD Blue SN570 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234110WD temp: 39.9 C scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 17.49 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 17.49 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 17.49 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 17.49 GiB (3.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.57 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.0 C mobo: 46.0 C gpu: amdgpu temp: 49.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.57 GiB used: 5.15 GiB (16.9%)
Processes: 339 Power: uptime: 57m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.22 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1865 libs: 545 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-10-12
Last full system update: 2024-10-12
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:
2

You can also know this by using the command lsusb

While I might not know enough to assist you fully, I can at least try to help you troubleshoot your problem.

→ is bluetooth soft/hard blocked on sudo rfkill list, can you unblock if blocked.
→ what if you restart your network manager sudo systemctl restart NetworkManager
→ Try your bluetooth-manager after restart.
→ what does jctl, have to say.

1 Like
3

This is what lsusb returns

Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

this is what sudo rfkill list returns

1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

Nothing happens after doing sudo systemctl restart NetworkManager.

This is the output from jctl

Oct 13 11:37:30 kiwi-pc 30-systemd-environment-d-generator[3085]: /home/kiwi/.config/environment.d/firefox.conf:2: invalid variable name "env MOZ_USE_XINPUT2", ignoring.
Oct 13 11:37:31 kiwi-pc 30-systemd-environment-d-generator[3287]: /home/kiwi/.config/environment.d/firefox.conf:2: invalid variable name "env MOZ_USE_XINPUT2", ignoring.
Oct 13 11:37:31 kiwi-pc kwin_wayland[3362]: kwin_xkbcommon: XKB: couldn't find a Compose file for locale "en_IN" (mapped to "en_IN.ISO8859-1")
Oct 13 11:37:32 kiwi-pc org_kde_powerdevil[3682]: busno=4, sleep-multiplier =  1.30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Oct 13 11:37:32 kiwi-pc sudo[4365]:     kiwi : a password is required ; TTY=pts/0 ; PWD=/home/kiwi ; USER=root ; COMMAND=/usr/bin/true
Oct 13 11:37:32 kiwi-pc plasmashell[3630]: aurorae: Couldn't find QML Decoration  ""
Oct 13 11:37:32 kiwi-pc plasmashell[3630]: qml: ENABLED CHANGEDD: true
Oct 13 11:37:33 kiwi-pc plasmashell[3630]: qml: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Oct 13 11:37:33 kiwi-pc plasmashell[3630]: qml: Error colorizing rect 0 E: TypeError: Cannot read property 'r' of null
Oct 13 11:37:33 kiwi-pc plasmashell[3630]: qml: Error colorizing rect 1 E: TypeError: Cannot read property 'r' of null
Oct 13 11:37:33 kiwi-pc plasmashell[3630]: qml: Error colorizing rect 2 E: TypeError: Cannot read property 'r' of null
4

Try installing the linux-lts kernel, and the linux-lts-headers .

Boot into the linux-lts kernel using the grub “Advanced” menu.

If that doesn’t help, try replacing bluedevil with an alternate power manager such as TLP:

https://wiki.archlinux.org/title/TLP

1 Like
5

Not the OP, but FWIW I have been using bluetooth speakers now for a few years. At one point a regression was introduced to the bluez packages so I had to roll back while upstream worked out a patch. That was a while back.

Now (as in today) I upgraded and bluetooth stopped working. I rolled back to yesterdays snapshot and it works. The bluetooth userspace isn’t changing, but the kernel is. when I upgrade from linux-zen 6.11.2 to 6.11.3, bluetooth stops finding my speakers. I’ll dig in more later, but I suspect it’s the kernel upgrade.

6

i tried switching to linux-lts but no luck, i will try using an alternative power manager tomorrow.

7

@kiwi

This shows that your Bluetooth device is not being detected. I would have suggested you change your kernel but apparently you already did.

Did some digging and found that maybe

sudo systemctl enable bluetooth

might work
But, I am not certain about it.

However, you will notice from

That your chip IMC Networks Wireless_Device, might have some problems working on various systems.
Hopefully you will get a solution., maybe try to create a probe and see if you can get drivers that can work.

8

I noticed this as well, usually testing other kernels is the most likely thing that will fix that.

Test the linux , linux-mainline , and linux-hardened kernels as well.

You could also try replacing the Bluetooth management utility bluez with blueman. To install the blueman package, issue the following command:

sudo pacman -S blueman

If none of the above suggestions helped then try the procedure below:

A network adapter not being detected properly can sometimes be corrected by power cycling and resetting the BIOS back to the factory default. Firstly, disconnect any other network devices that do not require troubleshooting. This includes LAN cables, USB WiFi or Ethernet adapters, and USB phone tethering.

Power down the computer, and the remove the PSU power plug. Let the computer sit without power for a few minutes. Then, hold down the power button for approximately 30 seconds. Pressing the power button will help drain all residual power from the unit’s circuit board. Then reattach the AC power cord, and restart. After booting into Garuda check if your adapter is now properly detected.

If your adapter is still not properly detected, then resetting your bios may help. Boot into your bios, then reset the bios to the factory defaults, then save the default settings. After doing this you will need to change some BIOS settings for best Linux compatibility. Some settings that you will need to disable include secure boot. fastboot, and RAID or RST (change to AHCI).

After resetting the bios to the factory defaults hopefully your adapter will be properly detected and initialized. Sometimes a BIOS update can also help to fix a device that is not detected or initialized properly.

Good luck finding your fix.

2 Likes
9

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