[SOLVED] Bluetoothctl - No default controller available

pit_p_an-arch_y · 2024-05-19 00:09:06

Hello everybody!

I just use a mouse bluetooth 5.0 but from today I'm encountered this problem.

Everything has always worked well until today, when I tried to switch from ly display manager to CDM, failing miserably. So I then also tried to start bspwm directly without display manager but I failed too. I don't know what I did wrong but this is not the point now. I went back to ly and now I can execute bspwm as before. The problem is that, after these "experiments", the mouse no longer connected automatically as it did before and, in addition, it is no longer possible to connect at all because bluetoothctl always responds with "No default controller available".

I searched the web and found, also on Arch Forum, something about a firmware update that may causes this issue, but I think that is not my case because I didn't do any updates today. I have not yet tried a solution that I found that suggests to disconnect the computer's battery for a while because, before removing some screws from my laptop, I would like to ask to the community if there is other soultions.

I already tried

sudo rmmod btusb
sudo systemctl disable bluetooth.service
sudo systemctl stop bluetooth.service
sudo modprobe btusb
sudo systemctl enable bluetooth.service
sudo systemctl start bluetooth.service

lsusb                                                                                                                                                             
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04f2:b760 Chicony Electronics Co., Ltd HP Wide Vision HD Camera
Bus 001 Device 003: ID 13d3:3567 IMC Networks Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More&Better]
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 1235:801c Focusrite-Novation Scarlett Solo USB
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

lsusb -v -s 001:003

Bus 001 Device 003: ID 13d3:3567 IMC Networks Wireless_Device
Couldn't open device, some information will be missing

followiong Arch Forum but nothing changed.

Here my

sudo dmesg | grep Bluetooth
[    4.394003] Bluetooth: Core ver 2.22
[    4.394306] Bluetooth: HCI device and connection manager initialized
[    4.394312] Bluetooth: HCI socket layer initialized
[    4.394316] Bluetooth: L2CAP socket layer initialized
[    4.394323] Bluetooth: SCO socket layer initialized
[    4.472021] Bluetooth: hci0: Failed to load firmware file (-2)
[    4.472023] Bluetooth: hci0: Failed to set up firmware (-2)
[    4.472025] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[  107.563211] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  107.563219] Bluetooth: BNEP filters: protocol multicast
[  107.563226] Bluetooth: BNEP socket layer initialized

journalctl -b | grep Bluetooth
mag 18 21:14:41 archpeter kernel: Bluetooth: Core ver 2.22
mag 18 21:14:41 archpeter kernel: Bluetooth: HCI device and connection manager initialized
mag 18 21:14:41 archpeter kernel: Bluetooth: HCI socket layer initialized
mag 18 21:14:41 archpeter kernel: Bluetooth: L2CAP socket layer initialized
mag 18 21:14:41 archpeter kernel: Bluetooth: SCO socket layer initialized
mag 18 21:14:41 archpeter kernel: Bluetooth: hci0: Failed to load firmware file (-2)
mag 18 21:14:41 archpeter kernel: Bluetooth: hci0: Failed to set up firmware (-2)
mag 18 21:14:41 archpeter kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
mag 18 21:14:41 archpeter systemd[1]: Reached target Bluetooth Support.
mag 18 21:16:24 archpeter systemd[1]: Starting Bluetooth service...
mag 18 21:16:24 archpeter bluetoothd[2169]: Bluetooth daemon 5.76
mag 18 21:16:24 archpeter systemd[1]: Started Bluetooth service.
mag 18 21:16:24 archpeter kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
mag 18 21:16:24 archpeter kernel: Bluetooth: BNEP filters: protocol multicast
mag 18 21:16:24 archpeter kernel: Bluetooth: BNEP socket layer initialized
mag 18 21:16:24 archpeter bluetoothd[2169]: Bluetooth management interface 1.22 initialized
mag 18 21:38:40 archpeter systemd[1]: Stopped target Bluetooth Support.
mag 18 21:39:35 archpeter systemd[1]: Stopping Bluetooth service...
mag 18 21:39:35 archpeter systemd[1]: Stopped Bluetooth service.

rfkill
ID TYPE      DEVICE      SOFT      HARD
 1 wlan      phy0   unblocked unblocked
 2 bluetooth hci0   unblocked unblocked

 inxi -F
System:
  Host: archpeter Kernel: 6.9.1-zen1-1-zen arch: x86_64 bits: 64
  Desktop: bspwm v: 0.9.10 Distro: Arch Linux
Machine:
  Type: Laptop System: HP product: Victus by HP Laptop 16-e1xxx v: N/A
    serial: <superuser required>
  Mobo: HP model: 8A22 v: 19.75 serial: <superuser required> UEFI: AMI
    v: F.20 date: 11/17/2023
Battery:
  ID-1: BAT0 charge: 15.6 Wh (25.2%) condition: 62.0/62.0 Wh (100.0%)
    volts: 14.5 min: 15.4
CPU:
  Info: 8-core model: AMD Ryzen 7 6800H with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 524 min/max: 400/4785 cores: 1: 400 2: 400 3: 1397
    4: 400 5: 400 6: 400 7: 1397 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
    14: 400 15: 400 16: 400
Graphics:
  Device-1: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] driver: nouveau
    v: kernel
  Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel
  Device-3: Chicony HP Wide Vision HD Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0 driver: X:
    loaded: amdgpu,modesetting,nouveau unloaded: vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: nouveau,radeonsi,swrast
    platforms: x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: amd mesa v: 24.0.7-arch1.3
    renderer: AMD Radeon Graphics (radeonsi rembrandt LLVM 17.0.6 DRM 3.57
    6.9.1-zen1-1-zen)
Audio:
  Device-1: NVIDIA driver: snd_hda_intel
  Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
  Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x
  Device-4: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  Device-5: Focusrite-Novation Scarlett Solo USB driver: snd-usb-audio
    type: USB
  API: ALSA v: k6.9.1-zen1-1-zen status: kernel-api
  Server-1: PipeWire v: 1.0.6 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: eno1 state: down mac: 5c:60:ba:c0:95:aa
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
  IF: wlp4s0 state: up mac: 34:6f:24:c9:cd:89
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: N/A
Drives:
  Local Storage: total: 1.84 TiB used: 41.61 GiB (2.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 1000GB
    size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD PC SN810
    SDCPNRY-1T00-1006 size: 953.87 GiB
Partition:
  ID-1: / size: 937.33 GiB used: 41.39 GiB (4.4%) fs: ext4 dev: /dev/nvme1n1p2
  ID-2: /boot size: 511 MiB used: 219 MiB (42.9%) fs: vfat
    dev: /dev/nvme1n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 44.4 C mobo: 36.0 C gpu: amdgpu temp: 42.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Info:
  Memory: total: 16 GiB note: est. available: 14.83 GiB used: 1.99 GiB (13.4%)
  Processes: 299 Uptime: 4h 44m Shell: Zsh inxi: 3.3.34

  systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sun 2024-05-19 02:04:27 CEST; 16s ago
       Docs: man:bluetoothd(8)
   Main PID: 200863 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18119)
     Memory: 692.0K (peak: 976.0K)
        CPU: 32ms
     CGroup: /system.slice/bluetooth.service
             └─200863 /usr/lib/bluetooth/bluetoothd

mag 19 02:04:27 archpeter bluetoothd[200863]: Starting SDP server
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support bap plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support bass plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support mcp plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support vcp plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support micp plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support ccp plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: src/plugin.c:init_plugin() System does not support csip plugin
mag 19 02:04:27 archpeter bluetoothd[200863]: Bluetooth management interface 1.22 initialized

I do not know what to do. Any suggestions are so welcome.

Last edited by pit_p_an-arch_y (2024-05-26 14:14:05)

Muxed0 · 2024-05-19 14:43:00

I am having the exact same issue. Booted into windows once to fetch an ebook and then boom, no more bluetooth on Arch. Exact same

sudo dmesg | grep Bluetooth

output, exact same

systemctl status bluetooth

output.

rfkill

is clean too, one more thing which, you may find the exact same issue I did OP, any

bluetoothctl

command yields

No default controller available

Now I am on a very different machine. Instead of a laptop I have a desktop with an Aorus B550i PRO AX motherboard on which the bluetooth adapter is integrated. That board has been terrible when it comes to wifi/bluetooth sometimes just disappearing for no reason, then reappearing after a full system reboot as was suggested to you OP. In my case, this involves simply taking the power cord out and pressing the power button to make sure everything in the machine is flat, then waiting for a bit before plugging everything back, which I did. Several times. The result: nothing. This supposedly forces the firmware to restart, but that doesn't seem to be the issue because nothing has changed.

Another difference is that I installed all updates that came my way. Although, the bluetooth stopped working before the whole bluez and bluez-utils were updated, leaving them out as the possible culprits. Best I've seen is that the most recent kernel doesn't play nice with some bluetooth adapters. If that's really all there is to it (which it might not be), then the solutions I've come across so far is to downgrade the kernel until it is fixed or just live without until the next update. I'm really hoping it doesn't come to this but at the end of the day, this is arch. Stuff like this is bound to happen from time to time. I guess we've just been very lucky for a while there.

Last edited by Muxed0 (2024-05-19 14:43:47)

pit_p_an-arch_y · 2024-05-19 16:23:10

Thank you @Muxed0 for the answer.

It works fine for like 6 months or more. It just stop to works after that damned and failed attempt to run bspwm, first with CDM and then without any DM, wich caused a black screen. Damn me.

Here also my

  sudo dmesg | grep firmware
[sudo] password di arch_peter: 
[    0.082820] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    2.223010] [drm] Loading DMUB firmware via PSP: version=0x04000044
[    2.223506] [drm] Found VCN firmware Version ENC: 1.30 DEC: 3 VEP: 0 Revision: 9
[    2.223511] amdgpu 0000:07:00.0: amdgpu: Will use PSP to load VCN firmware
[    5.103341] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    5.119910] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin failed with error -2
[    5.119914] Bluetooth: hci0: Failed to load firmware file (-2)
[    5.119916] Bluetooth: hci0: Failed to set up firmware (-2)

Hope can help to find a solution.

So is a problem related to missing firmware? There is not a way to re-load these firmwares or something like this? Sorry if this is a noob question...

I also find this discussion: https://www.linuxquestions.org/question … ost6435453 in which an answer containing the following link: https://cateee.net/lkddb/web-lkddb/MT7921E.html is indicated as a "solution" but I don't understand what I should possibly do.

Muxed0 · 2024-05-19 17:06:21

Well, to be fair I too am quite the noob when it comes to this. Both of our devices are indeed Mediatek wireless devices, so the thread you linked feels relevant. Unfortunately, it also looks like this is purely a firmware issue. I'll try just reinstalling arch completely to see if that fixes it, somehow. My bet is on not which means that arch won't be good until they do something about it. Weird that not many have had this issue yet though.

Muxed0 · 2024-05-19 17:32:34

Fresh arch install with linux-zen, same issues. Guess there really isn't much we can do about it.

pit_p_an-arch_y · 2024-05-19 18:15:29

.

What I still don't understand is why it happened randomly after the bspwm execution failure and not after a firmware update. The problem did not start after a firmware update. I mean: one moment everything works, no firmware problems -> bspwm execution failed -> firmware lost... Where is the connection?

mccord · 2024-05-19 19:16:46

It's a bug with the 6.9 kernel: https://bugzilla.kernel.org/show_bug.cgi?id=218757

Your options are:
Live without bluetooth and wait for the fix that'll probably arrive with 6.9.2
Patch and compile the kernel yourself with this patch
Downgrade to the latest 6.8 kernel
Create symbolic link to the old firmware in /lib/firmware/mediatek like the newest in the bug tracker comment mentioned, should probably be BT_RAM_CODE_MT7961_1_2_hdr.bin.zst -> BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst

I had the same problem and used the patch, but symbolic linking or downgrading should be the easier options.

pit_p_an-arch_y · 2024-05-19 20:46:46

mccord wrote:

It's a bug with the 6.9 kernel: https://bugzilla.kernel.org/show_bug.cgi?id=218757
Your options are:
Live without bluetooth and wait for the fix that'll probably arrive with 6.9.2
Patch and compile the kernel yourself with this patch
Downgrade to the latest 6.8 kernel
Create symbolic link to the old firmware in /lib/firmware/mediatek like the newest in the bug tracker comment mentioned, should probably be BT_RAM_CODE_MT7961_1_2_hdr.bin.zst -> BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst
I had the same problem and used the patch, but symbolic linking or downgrading should be the easier options.

Thank you mccord! You gave me some hope again!

I would like to try the option of creating a symbolic link to the old firmware but in my

/lib/firmware/mediatek

I have just:

ls -a /lib/firmware/mediatek | grep BT_RAM_CODE
BT_RAM_CODE_MT7922_1_1_hdr.bin.zst
BT_RAM_CODE_MT7961_1_2_hdr.bin.zst

Should I download BT_RAM_CODE_MT7961_1a_2_hdr.bin from the first link you mentioned in your comment?

About the downgrade option I'm scared about this

Tip: If you are unable to boot after a kernel update, you can downgrade the kernel chrooting into the system. Boot using an Arch Linux USB flash installation media and mount the partition where your system is installed to /mnt. If you have /boot or /var on separate partitions, also mount them to /mnt (e.g. mount /dev/sdc3 /mnt/boot). Then chroot into the system using:
# arch-chroot /mnt
Now you can go into the pacman cache directory and downgrade the Linux packages using the command indicated above. Once done, exit the chroot (with exit) and reboot.

From https://wiki.archlinux.org/title/Downgrading_packages because now I don't have any USB-key at hand.

Lastly I'm tempted by the patch option but unfortunately I don't understand what I should do because I'm basically a noob, but eager to learn so I will start to search how to do it and if understand something I will try.

In any case, thank you very much!

mccord · 2024-05-19 21:22:36

For symlinking this should theoretically work
sudo ln -s /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.zst /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst
You could also extract BT_RAM_CODE_MT7961_1_2_hdr.bin.zst and rename the resulting bin file to BT_RAM_CODE_MT7961_1a_2_hdr.bin like someone in the other thread mentioned.
There's also someone that has compiled the 6.9.1 kernel with the patch in that thread.

For downgrading the kernel you'd have to grab both linux and linux-headers from Arch Linux Archive https://archive.archlinux.org/
https://archive.archlinux.org/packages/ … kg.tar.zst
https://archive.archlinux.org/packages/ … kg.tar.zst
then installing with pacman -U linux-6.8.9.arch1-2-x86_64.pkg.tar.zst linux-headers-6.8.9.arch1-2-x86_64.pkg.tar.zst
edit: I'm not sure if this works cleanly if you are using nvidia drivers! Better to avoid or use nvidia-dkms drivers.

There's also the 'downgrade' package on the AUR that automates downloading from archive, installing and listing the package in IgnorePkg /etc/pacman.conf so it'll not get updated on the next pacman -Syu.

Last edited by mccord (2024-05-19 21:32:36)

Muxed0 · 2024-05-19 23:07:03

mccord wrote:

You could also extract BT_RAM_CODE_MT7961_1_2_hdr.bin.zst and rename the resulting bin file to BT_RAM_CODE_MT7961_1a_2_hdr.bin like someone in the other thread mentioned.

That'll do it. Just extract the file anywhere and

 sudo mv BT_RAM_CODE_MT7961_1a_2_hdr.bin /lib/firmware/mediatek

Now my bluetooth works again. Wonderful!

Edit: well, after another restart it seems like my adapter bit the dust entirely. Maybe this was not such a good idea after all?

Last edited by Muxed0 (2024-05-20 00:01:07)

pit_p_an-arch_y · 2024-05-20 11:28:04

mcord wrote:

For symlinking this should theoretically work
sudo ln -s /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.zst /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst

I confirm that the "symlink option" with

sudo ln -s /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.zst /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst

does the trick and fix the problem "No default controller available". Thank you so much!

To be honest, after creating the symlink and reboot the system, the first mouse pairing attempts were unsuccessful. bluetoothctl gave me errors like "Failed to pair: org.bluez.Error.Authentication" or something like this (I tried yesterday night and I didn't copy the exact output). However, following this forum https://askubuntu.com/questions/1240045 … or-authent I ran this command in #bluetoothctl:

disconnect <device>
untrust <device>
remove <device>

Then

scan on
pair <device>
trust <device>

And I was finally able to pair my mouse to my PC via bluetooth again.
Unfortunately however, after a few minutes of inactivity the mouse went into stand-by or something and disconnected and I was no longer able to connect it, even by repeating the steps above.
Finally, today I turned on the PC, checked that the bluetooth service was running, turned on the mouse, paired with bluetoothctl and everything is working. I do not know what to say. However, I notice that the mouse connection no longer behaves as it did before the firmware bug: even before going into stand-by like yesterday (now it doesn't go there also because I'm using it) the notification often pops up telling me that the mouse is connected , which didn't happen before, but that would be a topic for another discussion . THANK YOU SO MUCH!

Anyway I have a question about the symlink: if BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst will be added in future updates, will I have to disable the symlink? Otherwise the search for the BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst firmware will always be sent back to BT_RAM_CODE_MT7961_1_2_hdr.bin.zst even if this new firmware (if it still has that name) is present in the firmware/mediatek folder, or am I wrong?

THANK YOU SO MUCH ANOTHER TIME!

loqs · 2024-05-21 17:10:47

pit_p_an-arch_y wrote:

Anyway I have a question about the symlink: if BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst will be added in future updates, will I have to disable the symlink? Otherwise the search for the BT_RAM_CODE_MT7961_1a_2_hdr.bin.zst firmware will always be sent back to BT_RAM_CODE_MT7961_1_2_hdr.bin.zst even if this new firmware (if it still has that name) is present in the firmware/mediatek folder, or am I wrong?

Yes. The symlink will also prevent the installation of any linux-firmware package containing that file.

pit_p_an-arch_y · 2024-05-22 13:26:27

loqs wrote:

Yes. The symlink will also prevent the installation of any linux-firmware package containing that file.

Ok, thank you!

I'm going to mark this post as [SOLVED] since @mccord provided directions to resolve the "No default controller available" issue.

Just one last thing to make sure this isn't also related to the bug.

As I said in a previous comment, Bluetooth now always works when the PC starts, but it doesn't automatically reconnect to the mouse like it did before. Furthermore, when the system starts, running bluetoothctl and then info <device> I can see that the device is already paired and trusted but not connected. By pressing the mouse button to start the "pair mode" the device connects and disconnects after less than a second and automatically exits the "pair mode". In order to make the connection, each time, I have to untrust and remove the device and then repeat the process "scan on, pair <device>, connect <device>, trust <device>". I have to repeat this procedure at every startup to be able to connect.

This is my

 $ journalctl -b | grep blue
mag 22 10:40:46 archpeter bluetoothd[4991]: Bluetooth daemon 5.76
mag 22 10:40:46 archpeter bluetoothd[4991]: Starting SDP server
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support bap plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support bass plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support mcp plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support vcp plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support micp plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support ccp plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: src/plugin.c:init_plugin() System does not support csip plugin
mag 22 10:40:46 archpeter bluetoothd[4991]: Bluetooth management interface 1.22 initialized
mag 22 10:40:46 archpeter bluetoothd[4991]: Battery Provider Manager created
mag 22 10:40:46 archpeter bluetoothd[4991]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
mag 22 10:40:46 archpeter wireplumber[823]: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Invalid method call
mag 22 10:40:46 archpeter wireplumber[823]: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Invalid method call
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/ldac
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/aptx_hd
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_hd
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/aptx
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/aac
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aac
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/sbc
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/sbc
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/sbc_xq
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/sbc_xq
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_1
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_0
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/faststream
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/faststream_duplex
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/opus_05
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/opus_05
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSink/opus_05_duplex
mag 22 10:40:46 archpeter bluetoothd[4991]: Endpoint registered: sender=:1.18 path=/MediaEndpoint/A2DPSource/opus_05_duplex
mag 22 10:40:46 archpeter bluetoothd[4991]: Failed to load LTKs for hci0: Invalid Parameters (0x0d)
mag 22 10:40:46 archpeter bluetoothd[4991]: Failed to load IRKs for hci0: Invalid Parameters (0x0d)
mag 22 10:40:50 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
mag 22 10:40:50 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:report_read_cb() Error reading Report value: Request attribute has encountered an unlikely error
mag 22 10:40:50 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
mag 22 10:40:50 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error
mag 22 10:40:50 archpeter bluetoothd[4991]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
mag 22 10:41:17 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
mag 22 10:41:17 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
mag 22 10:41:17 archpeter bluetoothd[4991]: profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error
mag 22 10:41:17 archpeter bluetoothd[4991]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
mag 22 11:03:03 archpeter sudo[21686]: arch_peter : TTY=pts/0 ; PWD=/home/arch_peter ; USER=root ; COMMAND=/sbin/systemctl restart bluetooth.service
mag 22 11:03:03 archpeter bluetoothd[4991]: Terminating
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/ldac
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/aptx_hd
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_hd
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/aptx
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/aac
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aac
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/sbc
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/sbc
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/sbc_xq
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/sbc_xq
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_1
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_0
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/faststream
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/faststream_duplex
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/opus_05
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/opus_05
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSink/opus_05_duplex
mag 22 11:03:03 archpeter bluetoothd[4991]: Endpoint unregistered: sender=:1.18 path=/MediaEndpoint/A2DPSource/opus_05_duplex
mag 22 11:03:03 archpeter dbus-broker[527]: A security policy denied :1.30 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.19.
mag 22 11:03:03 archpeter bluetoothd[4991]: Battery Provider Manager destroyed
mag 22 11:03:03 archpeter bluetoothd[4991]: Stopping SDP server
mag 22 11:03:03 archpeter bluetoothd[4991]: Exit
mag 22 11:03:03 archpeter systemd[1]: bluetooth.service: Deactivated successfully.
mag 22 11:03:03 archpeter bluetoothd[21762]: Bluetooth daemon 5.76
mag 22 11:03:03 archpeter bluetoothd[21762]: Starting SDP server
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support bap plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support bass plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support mcp plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support vcp plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support micp plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support ccp plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: src/plugin.c:init_plugin() System does not support csip plugin
mag 22 11:03:03 archpeter bluetoothd[21762]: Bluetooth management interface 1.22 initialized
mag 22 11:03:03 archpeter bluetoothd[21762]: Battery Provider Manager created
mag 22 11:03:03 archpeter bluetoothd[21762]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
mag 22 11:03:04 archpeter bluetoothd[21762]: Failed to load LTKs for hci0: Invalid Parameters (0x0d)
mag 22 11:03:04 archpeter bluetoothd[21762]: Failed to load IRKs for hci0: Invalid Parameters (0x0d)
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/ldac
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/aptx_hd
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aptx_hd
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/aptx
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aptx
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/aac
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aac
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/sbc
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/sbc
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/sbc_xq
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/sbc_xq
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aptx_ll_1
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aptx_ll_0
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/faststream
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/faststream_duplex
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/opus_05
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/opus_05
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSink/opus_05_duplex
mag 22 11:03:06 archpeter bluetoothd[21762]: Endpoint registered: sender=:1.78 path=/MediaEndpoint/A2DPSource/opus_05_duplex

I also set

/etc/bluetooth/main.conf

[General]
DiscoverableTime = 0
[Policy]
AutoEnable=true

 /etc/udev/rules.d/50-usb_power_save.rules

   1 ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="13d3", ATTR{idProduct}=="3567", ATTR{power/autosuspend}="-1"

 /etc/udev/rules.d/91-wake-on-device.rules

   1 ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="13d3", ATTRS{idProduct}=="3567", ATTR{power/wakeup}="enabled", ATTR{driver/1-4/power/wakeup}="enabled"

And this is my

 /etc/systemd/system/bluetooth.target.wants/bluetooth.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth
 
[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
 
# Filesystem lockdown
ProtectHome=true
ProtectSystem=strict
PrivateTmp=true
ProtectKernelTunables=true
ProtectControlGroups=true
StateDirectory=bluetooth
StateDirectoryMode=0700
ConfigurationDirectory=bluetooth
ConfigurationDirectoryMode=0555

# Execute Mappings
MemoryDenyWriteExecute=true

# Privilege escalation
NoNewPrivileges=true
 
# Real-time
RestrictRealtime=true

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

Tell me if it's offtopic and I'll remove it immediately and open a new topic if necessary.
Thanks in advance for any help.

Last edited by pit_p_an-arch_y (2024-05-22 13:27:23)

Smoerrebroed · 2024-05-26 11:09:52

6.9.2.arch1-1 is available in testing and fixes this issue as well.

pit_p_an-arch_y · 2024-05-26 14:11:52

Smoerrebroed wrote:

6.9.2.arch1-1 is available in testing and fixes this issue as well.

Thank you @Smoerrebroed!
Also the last problem that I reported is fixed but unfortunately I really don't know what I did to reach this situation. Sorry if this question is also a noob question but: is possible that the last kernel update fix it?
Anyway I marked this as Solved.
Thank you all for the tips!

Last edited by pit_p_an-arch_y (2024-05-26 14:12:44)

Arch Linux

#1 2024-05-19 00:09:06

[SOLVED] Bluetoothctl - No default controller available

#2 2024-05-19 14:43:00

Re: [SOLVED] Bluetoothctl - No default controller available

#3 2024-05-19 16:23:10

Re: [SOLVED] Bluetoothctl - No default controller available

#4 2024-05-19 17:06:21

Re: [SOLVED] Bluetoothctl - No default controller available

#5 2024-05-19 17:32:34

Re: [SOLVED] Bluetoothctl - No default controller available

#6 2024-05-19 18:15:29

Re: [SOLVED] Bluetoothctl - No default controller available

#7 2024-05-19 19:16:46

Re: [SOLVED] Bluetoothctl - No default controller available

#8 2024-05-19 20:46:46

Re: [SOLVED] Bluetoothctl - No default controller available

#9 2024-05-19 21:22:36

Re: [SOLVED] Bluetoothctl - No default controller available

#10 2024-05-19 23:07:03

Re: [SOLVED] Bluetoothctl - No default controller available

#11 2024-05-20 11:28:04

Re: [SOLVED] Bluetoothctl - No default controller available

#12 2024-05-21 17:10:47

Re: [SOLVED] Bluetoothctl - No default controller available

#13 2024-05-22 13:26:27

Re: [SOLVED] Bluetoothctl - No default controller available

#14 2024-05-26 11:09:52

Re: [SOLVED] Bluetoothctl - No default controller available

#15 2024-05-26 14:11:52

Re: [SOLVED] Bluetoothctl - No default controller available

Board footer