Can´t activate Bluetooth

Issues & Assistance
1

systemctl status bluetooth;

╭─b0tfukk3r@0111010101011 in ~ as 🧙 took 2m13s
[🔴] × systemctl status bluetooth
○ bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)

feb 11 12:31:01 0111010101011 systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
feb 11 12:31:43 0111010101011 systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

garuda-inxi;

╭─b0tfukk3r@0111010101011 in ~ as 🧙 took 4s
╰─λ sudo garuda-inxi --help
System:
Kernel: 6.1.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4cb2ec4b-dcc0-401a-9b17-00e2420e854e rw rootflags=subvol=@
quiet
cryptdevice=UUID=f60b5a45-88c2-4b96-a9fc-44b34879b241:luks-f60b5a45-88c2-4b96-a9fc-44b34879b241
root=/dev/mapper/luks-f60b5a45-88c2-4b96-a9fc-44b34879b241 quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0
resume=/dev/mapper/luks-54ea68d6-4688-4450-8538-97a886e39679 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock
wm: kwin_x11 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: LENOVO product: 90N9000BMW v: IdeaCentre G5 14IMB05
serial: <filter> Chassis: type: 3 serial: <filter>
Mobo: LENOVO model: 370A v: SDK0J40700 WIN 3258175487150 serial: N/A
UEFI: LENOVO v: O4HKT22A date: 06/08/2020
CPU:
Info: model: Intel Core i5-10400F socket: U3E1 bits: 64 type: MT MCP
arch: Comet Lake gen: core 10 level: v3 note: check built: 2020
process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 3
microcode: 0xF4
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 3895 high: 4001 min/max: 800/4300 base/boost: 2871/8300
scaling: driver: intel_pstate governor: performance volts: 0.8 V
ext-clock: 100 MHz cores: 1: 4000 2: 4000 3: 2838 4: 3901 5: 4001 6: 4000
7: 4000 8: 4000 9: 4000 10: 4000 11: 4000 12: 4000 bogomips: 69597
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: ZOTAC
driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
status: current (as of 2023-02) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.0 chip-ID: 10de:1f08 class-ID: 0300
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 4080x2160 s-dpi: 94 s-size: 1103x584mm (43.43x22.99")
s-diag: 1248mm (49.14")
Monitor-1: DP-0 pos: primary,bottom-c res: 1920x1080 hz: 60 dpi: 96
size: 509x286mm (20.04x11.26") diag: 584mm (22.99") modes: N/A
Monitor-2: DP-3 pos: middle-r res: 1080x1920 hz: 60 dpi: 96
size: 286x509mm (11.26x20.04") diag: 584mm (22.99") modes: N/A
Monitor-3: DP-4 pos: middle-l res: 1080x1920 hz: 60 dpi: 96
size: 286x509mm (11.26x20.04") diag: 584mm (22.99") modes: N/A
Monitor-4: HDMI-0 pos: top-center res: 1920x1080 hz: 60 dpi: 96
size: 509x286mm (20.04x11.26") diag: 584mm (22.99") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX
2060/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel Comet Lake PCH-V cAVS vendor: Lenovo driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a3f0 class-ID: 0403
Device-2: NVIDIA TU106 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
Sound API: ALSA v: k6.1.10-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.65 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 4000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Lenovo driver: rtw_8822ce v: N/A modules: rtw88_8822ce pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:c822
class-ID: 0280
IF: wlp4s0 state: down mac: <filter>
Drives:
Local Storage: total: 1.38 TiB used: 37.55 GiB (2.7%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB512HBJQ-000L7 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 5M2QEXF7 temp: 41.9 C scheme: GPT
SMART: yes health: PASSED on: 164d 22h cycles: 997
read-units: 94,770,593 [48.5 TB] written-units: 70,106,823 [35.8 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-08WN4A0 family: Blue size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD
rpm: 7200 serial: <filter> rev: 1A02 temp: 42 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 158d 5h cycles: 933
Partition:
ID-1: / raw-size: 459.65 GiB size: 459.65 GiB (100.00%)
used: 37.55 GiB (8.2%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-f60b5a45-88c2-4b96-a9fc-44b34879b241
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 752 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw-size: 459.65 GiB size: 459.65 GiB (100.00%)
used: 37.55 GiB (8.2%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-f60b5a45-88c2-4b96-a9fc-44b34879b241
ID-4: /var/log raw-size: 459.65 GiB size: 459.65 GiB (100.00%)
used: 37.55 GiB (8.2%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-f60b5a45-88c2-4b96-a9fc-44b34879b241
ID-5: /var/tmp raw-size: 459.65 GiB size: 459.65 GiB (100.00%)
used: 37.55 GiB (8.2%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 254:0 mapped: luks-f60b5a45-88c2-4b96-a9fc-44b34879b241
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.45 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 16.99 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-54ea68d6-4688-4450-8538-97a886e39679
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A gpu: nvidia temp: 46 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 31%
Info:
Processes: 362 Uptime: 53m wakeups: 0 Memory: 15.45 GiB
used: 7.01 GiB (45.4%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 2023 libs: 557 tools: gnome-software,octopi,pamac,paru
Shell: garuda-inxi (sudo) default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.25
Garuda (2.6.14-1):
System install date:     2023-01-16
Last full system update: 2023-02-11
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

In addition;

╭─b0tfukk3r@0111010101011 in ~ as 🧙 took 14s
╰─λ systemctl start bluetooth

╭─b0tfukk3r@0111010101011 in ~ as 🧙 took 1s
╰─λ systemctl status bluetooth
○ bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)

feb 11 12:31:01 0111010101011 systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
feb 11 12:31:43 0111010101011 systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
feb 11 13:30:47 0111010101011 systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
2

Try with a cold boot.
If it is an external USB adaper, try also unplugging and plugging it back.
Also, make sure fast boot is disabled in the BIOS.

4 Likes
3

I tried cold boot and the live usb, without success...
Bluetooth device is on the Motherboard, also tried all options in bios, weird thing is that the onboard WIFI works just fine.

4

Bluetooth "disappearing" isn't the first time it has been commentated on in this forum (multiple times). Suggest you do a thorough search here and the web. Oftentimes it originates in the BIOS hardware detection module..

I've had it happen to me.

3 Likes
5

Yeah Ive tried all solutions I found here before posting, nothing worked....
Okay will search further online =)

6

All solutions is a bit too much :wink:... And vague...
For example have you tried different kernels to rule out a regression in the latest one?
See

3 Likes
7

Yes Ive tried all options in Garuda bootmenu including LTS. Im pretty sure the issue occurred going to Zen 6.xx from 5.xx tho

8

I couldn´t figure it out...
So I installed Widows 10, did all the updates and got the Bluetooth working, only to install Garuda after that, now everything works great!
It is not the first time I´ve used a Win install to reset bios hehehe

9

May all those involved with M$ burn in hell!

This is not meant in a bad way, there is no hell :grin:

I mark it solved :slight_smile:

5 Likes
10

You may find a Windows update disables your bluetooth again at some point in the future. Sometimes it's difficult to keep BT working if Windows has infested your machine.

Be sure you have all bios settings in place for Linux compatibility.

Make sure all networking components are enabled in your bios.

Be sure secure boot and fast boot are disabled.

Disable all network adapter's power saving options in Windows device manager's advanced properties tabs.

If all else fails and Windows appropriates your network adapter and won't let go, try a full power down and remove all power sources for at least 5 minutes. If you continue having problems enabling BT/Wifi then try resetting your bios back to the factory defaults. After doing a factory reset you will again need to change the relevant bios settings for good Linux compatibility.

6 Likes
11

Check on all above! Not a trace left of mine unfaithful sidestep :wink:

1 Like
12

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