c/linux · by potentiallynotfelix@lemmy.fish · 1y

Bluetooth issues

Using latest fedora 41 with Plasma Mobile, I can't get Bluetooth to work. Nothing shows up running bluetoothctl list. It's an intel wireless 7265, which shows up as a network controller under lspci, but the bluetooth part doesnt. hciconfig returns nothing.

Steps I've taken:

sudo modprobe bluetooth

sudo dnf install bluez bluez-utils

sudo systemctl start bluetooth

I'm having deja vu where I followed all these steps before, but somehow I'm stuck here. Thank you for any help.

17 points · 11 comments · view on lemmy.world

11 Comments

Strit@lemmy.linuxuserspace.show · 4 pts · 1y (6 replies)

Make sure that the driver for the module is enabled in the kernel. dmesg | grep bluetooth should reveal something there.

Also, make sure the module is not blocked in rfkill.

potentiallynotfelix@lemmy.fish · 1 pts · 1y (5 replies)

dmesg | grep -i bluetooth says this after loading bluetooth with modprobe:

Bluetooth: Core ver 2.22

NET: Registered PF_BLUETOOTH protocol family

Bluetooth: HCI device and connection manager initialized

Bluetooth: HCI socket layer initialized

Bluetooth: L2CAP socket layer initialized

Bluetooth: SC0 socket later initialized

Rfkill only lists my wlan device which is unlocked.

Strit@lemmy.linuxuserspace.show · 2 pts · 1y (2 replies)

Does not look like the driver is enabled in the kernel you are running then. :(

potentiallynotfelix@lemmy.fish · 1 pts · 1y

question! do you think installing the fedora vanilla kernel would solve this? I've used different distros that supported this bluetooth driver, so I assume it's already in the kernel and ready.

link to wiki

potentiallynotfelix@lemmy.fish · 1 pts · 1y

anon5621@lemmy.ml · 1 pts · 1y (1 reply)

Usual plasma using bluedevil as frontend for Bluetooth does it installed? And what log saying in Bluetooth service sudo systemctl status bluetooth?

potentiallynotfelix@lemmy.fish · 1 pts · 1y

Plasma mobile is probably different, I only see bluetoothctl and bluemoon from bluez-utils. When I run bluetoothctl power on it says No default controller available. systemctl status bluetooth initially returns inactive (dead) with no logs, and when I start it it gives the log:

Jan 20 16:24:38 solstice systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

This error is fixed by running modprobe bluetooth as root. I can start bluetoothctl, and it runs successfully. The systemd logs return:

Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support bap plugin
Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support bass plugin
Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support mcp plugin
Jan 20 16:25:29 solstice bluetoothd[2481]: src/plugin.c:init_plugin() System does not support vcp plugin

Another lemmier suggested that my system just doesn't have the right kernel. This is unfortunate but may be true at this point.

shekau@lemmy.today · 1 pts · 1y (2 replies)

[ removed ]

potentiallynotfelix@lemmy.fish · 1 pts · 1y

By the check, I meant that I'd already had it enabled and checked that.

potentiallynotfelix@lemmy.fish · 1 pts · 1y

✅

el_psd@sh.itjust.works · 1 pts · 1y (1 reply)

I cannot into computers, but draining the capacitors before rebooting has fixed this issue for me in the past. Not sure if this is even possible on your device given you're running Plasma Mobile

potentiallynotfelix@lemmy.fish · 2 pts · 1y

No luck, I removed the batteries, held the power button down for ~1m30s, and let it sit for another two minutes.