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.
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