Make sure that the driver for the module is built into the kernel. dmesg | grep bluetooth
should reveal something there.
Also, make sure the module is not blocked in rfkill
.
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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Make sure that the driver for the module is built into 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.
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
Make sure you have Bluetooth enabled in your firmware
✅
By the check, I meant that I'd already had it enabled and checked that.