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.
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
.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.
Does not look like the driver is enabled in the kernel you are running then. :(
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
Usual plasma using bluedevil as frontend for Bluetooth does it installed?
Plasma mobile is probably different, I only see
bluetoothctl
andbluemoon
frombluez-utils
. When I runbluetoothctl power on
it saysNo default controller available
.systemctl status bluetooth
initially returnsinactive (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:Another lemmier suggested that my system just doesn’t have the right kernel. This is unfortunate but may be true at this point.