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.
this post was submitted on 20 Jan 2025
17 points (94.7% liked)
Linux
49393 readers
1675 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
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.
Usual plasma using bluedevil as frontend for Bluetooth does it installed? And what log saying in Bluetooth service sudo systemctl status bluetooth?
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.
Make sure you have Bluetooth enabled in your firmware
✅
By the check, I meant that I'd already had it enabled and checked that.
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
No luck, I removed the batteries, held the power button down for ~1m30s, and let it sit for another two minutes.