Hi all,
Ive been trying to get my Bluetooth working but seem to running into issues. I have tried following different guides online but have not be able to get it working. When I run bluetoothctl and attempt to scan I get an error saying “No default controller available”. Screenshot below:
Please let me know if anyone has any ideas or if I need to provide more info!
did you enable bluetooth?
sudo systemctl enable --now bluetooth
I believe so, after running the command it didnt seem to affect the Bluetooth tab in settings or blueman-manager. As another note, I when I try using the Enable in System Settings that doesn’t do anything either.
[ssolos@steven-b650gamingxax ~]$ sudo systemctl enable --now bluetooth
[ssolos@steven-b650gamingxax ~]$ bluetoothctl
[bluetooth]# Agent registered
[bluetooth]# scan on
No default controller available
[bluetooth]#
Maybe explain what it is your trying to get working?
My end goal is to connect my bluetooth controller, so I can use it for a couple games. Im struggling to figure out why the system wont enable/discover(?).
https://discovery.endeavouros.com/audio/bluetooth/2021/03/
Do you have either one of these installed?
blueman (gtk) recommended for GTK based [can be used in Desktop Environments independent]
bluedevil (qt) [Integrate the Bluetooth technology within KDE workspace and applications]
In a terminal, enter
pacman -Q | grep blue
and see if either blueman or buledevil is installed.
Also more info about your setup could be helpful. Such as Desktop Environment, maybe the bluetooth controller’s make and model number.
Pudge
So I installed both while trying to trouble shoot earlier (Unsure if thats a no no).
[ssolos@steven-b650gamingxax ~]$ pacman -Q | grep blue
bluedevil 1:6.2.5-1
blueman 2.4.3-2
bluez 5.79-1
bluez-libs 5.79-1
bluez-qt 6.10.0-1
bluez-utils 5.79-1
Here is a link to the Wifi Card I bought. https://www.amazon.com/gp/product/B09VCVTJV2
So AX210 I think would be the chipset? I’m outside of my realm of knowledge regarding that.
And For the Desktop Environment (Copied the the Settings)
Operating System: EndeavourOS
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 61.9 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 GRE
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 GAMING X AX
since your using kde then probably should use theirs bluedevil and in the first picture click the enable under where it says Bluetooth disabled and see what it does. I see the radio button is on but i dont use kde so not sure how they do things.
Sadly the Settings in the Bluetooth tab are unresponsive. Dont react to my clicks the button does a small flash to show I clicked but nothing happens after, and the toggle does not stay selected if I leave the page.
I wish I had more info to share, but I am not really sure whats wrong the only thing that throws a red flag in my head was the “No default controller available” from earlier
maybe run bluedevil from the command line and see what errors it may post in the background. Hopefully someone who uses KDE can chime in.
forgive question … what output of “show” via bluetoothctl . if any info you no happy share pls remove… pls no screenshot
After running systemsettings from the command line I had no warnings or errors show in the command line when clicking the bluetooth enable button.
I did not remove anything from the response this was all that was in the output.
[ssolos@steven-b650gamingxax ~]$ bluetoothctl show
No default controller available
[ssolos@steven-b650gamingxax ~]$
not sure if the results will be any different but maybe try blueman since you do have it installed. run it from the command line so any background errors may show
Same result sadly 
The only thing I found interesting if that when enabling a lot of functions stay grayed out and there is no options under adapter other than exit.
Also I do appreciate yall trying to help.
long shot… what get if " systemctl stop bluetooth-mesh.service " + you dual boot window? before you do this
[ssolos@steven-b650gamingxax ~]$ systemctl stop bluetooth-mesh.service
Failed to stop bluetooth-mesh.service: Unit bluetooth-mesh.service not loaded.
[ssolos@steven-b650gamingxax ~]$
I do still have Windows installed on a different hard drive so yes. I have not booted windows in a week or two. I am trying to transition to Linux fully.
any thing in dmesg ?
EDit… dmesg | grep Bluetooth ( worth try )
I don’t think your commands are exactly correct.
Table 1
bluetoothctl Commands
| Command | Description |
|---|---|
| 1. list | Generates a list of available controllers. You can pair a controller and a device while working from another controller, but on a home system you may have only one controller. However, you need the controller’s MAC address to run other commands. If it is no longer visible on screen, run list again. You might be able to simplify the process by turning off all controllers except the one to pair. |
| 2. show | Gathers information about available controllers, including their names and current state. This information can be useful for distinguishing one controller from the other. |
| 3. select | Selects the controller to pair. Once you select the controller, all controller-related commands will apply to it for three minutes or until you select a new controller. |
| 4. power on | Enables the selected controller. If you are pairing the controller on which bluetoothctl is running, this step is unnecessary. |
| 5. agent on | Turns on Bluetooth support. If you use a USB adapter, it is on as long as it is plugged in. |
| 6. default agent | Sets the current agent to the default. |
| 7. discoverable on | Makes the controller visible to other devices. As a security precaution, run discoverable off after pairing. |
| 8. scan on | Receives a list of detected devices (Figure 3). If a device you expect is not visible, check that it is turned on, ready to pair, and within range. Already paired devices will not be listed. |
| 9. pairable on | Readies the controller for pairing. Remember that you have three minutes after running this command to pair. |
| 10. devices | Lists available devices. You want the MAC address, not the name, to use with other commands. |
| 11. info | Displays information about a particular device (Figure 4). This command is most often useful in identifying the correct device. |
| 12. connect | Readies the device for pairing. |
| 13. pair | Pairs the device with the default controller. |
| 14. trust | Sets the device to re-pair automatically when it is turned on, which eliminates the need to pair all over again. |
| 15. discoverable off | Hides the controller from other Bluetooth devices. Otherwise, any device that can detect it has access to it, leaving a major security hole. In this respect, running bluetoothctl resembles logging in as root: you want to spend as little time running it as possible. |
Looks like there is something interesting in the output. I don’t really understand what it means though.
[ssolos@steven-b650gamingxax ~]$ sudo dmesg | grep Bluetooth
[ 5.246477] usb 1-9: Product: Bluetooth Radio
[ 6.988405] Bluetooth: Core ver 2.22
[ 6.988423] Bluetooth: HCI device and connection manager initialized
[ 6.988428] Bluetooth: HCI socket layer initialized
[ 6.988430] Bluetooth: L2CAP socket layer initialized
[ 6.988434] Bluetooth: SCO socket layer initialized
[ 8.449532] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.449535] Bluetooth: BNEP filters: protocol multicast
[ 8.449539] Bluetooth: BNEP socket layer initialized
[ 9.123725] Bluetooth: hci0: Reading Intel version command failed (-110)
[ 9.127291] Bluetooth: hci1: command 0xfc61 tx timeout
[ 9.127297] Bluetooth: hci1: RTL: Failed to generate devcoredump
[ 9.127313] Bluetooth: hci1: RTL: RTL: Read reg16 failed (-110)
[ssolos@steven-b650gamingxax ~]$