bluetooth not working - No default controller available

LoB · 2025-10-14 20:15:55

I recently installed archlinux on my pc but I could not get bluetooth to work. I have a mercusys card (AX3000 Wi-Fi 6 Bluetooth 5.3 PCIe Adapter MA80XE) that provides both wifi and bluetooth functionality. The wifi is provided by a PCiE connection (it works) and the bluetooth by a connection in the slot used otherwise to make the case usb ports work. I dualboot windows, where both wifi and bluetooth work with no issue.

I followed the instructions on the wiki to setup bluetooth ( https://wiki.archlinux.org/title/Bluetooth#Installation ). The kde settings menu fails to enable bluetooth, while bluetoothctl displays "No default controller available" and doesn't list any controllers with the "list" command.

As per the instructions, I installed the bluez and bluez-utils packages, enabled btusb and bluetooth.service.

$ sudo lsmod | grep btusb
btusb                  81920  0
btrtl                  32768  1 btusb
btintel                73728  1 btusb
btbcm                  24576  1 btusb
btmtk                  32768  1 btusb
bluetooth            1114112  17 btrtl,btmtk,btintel,btbcm,bnep,btusb

$ sudo journalctl -b -u bluetooth.service
Oct 14 18:21:55 penguin systemd[1]: Starting Bluetooth service...
Oct 14 18:21:55 penguin bluetoothd[587]: Bluetooth daemon 5.84
Oct 14 18:21:55 penguin systemd[1]: Started Bluetooth service.
Oct 14 18:21:55 penguin bluetoothd[587]: Starting SDP server
Oct 14 18:21:55 penguin bluetoothd[587]: Bluetooth management interface 1.23 initialized

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 3434:0311 Keychron Keychron V1
Bus 001 Device 003: ID 3554:f58a Compx VXE NordicMouse 1K Dongle
Bus 001 Device 004: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 005: ID 1532:0531 Razer USA, Ltd Razer Seiren Mini
Bus 001 Device 006: ID 13d3:3625 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 8089:0009 SayoDevice SayoDevice O3C v1
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

$ sudo dmesg | egrep -i 'blue|firm'
egrep: warning: egrep is obsolescent; using grep -E
[    0.260107] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.439967] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.463843] acpi PNP0A08:00: [Firmware Info]: ECAM [mem 0xf0000000-0xf7ffffff] for domain 0000 [bus 00-7f] only partially covers this bridge
[    8.727292] amdgpu 0000:08:00.0: amdgpu: [drm] Loading DMUB firmware via PSP: version=0x02020021
[    8.727702] amdgpu 0000:08:00.0: amdgpu: Found VCN firmware Version ENC: 1.33 DEC: 4 VEP: 0 Revision: 13
[    9.681440] systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
[   10.130666] Bluetooth: Core ver 2.22
[   10.130684] NET: Registered PF_BLUETOOTH protocol family
[   10.130686] Bluetooth: HCI device and connection manager initialized
[   10.130691] Bluetooth: HCI socket layer initialized
[   10.130694] Bluetooth: L2CAP socket layer initialized
[   10.130700] Bluetooth: SCO socket layer initialized
[   10.135337] faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
[   10.336623] mt7921e 0000:04:00.0: WM Firmware Version: ____000000, Build Time: 20250523103234
[   11.056895] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.056896] Bluetooth: BNEP filters: protocol multicast
[   11.056899] Bluetooth: BNEP socket layer initialized
[   12.189226] Bluetooth: hci0: Opcode 0x0c03 failed: -110

$ sudo bluetoothctl
Agent registered
[bluetoothctl]> power on
No default controller available
[bluetoothctl]> list
[bluetoothctl]>

seth · 2025-10-15 07:40:31

I dualboot windows, where

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I have a mercusys card (AX3000 Wi-Fi 6 Bluetooth 5.3 PCIe Adapter MA80XE)

egrep: warning: egrep is obsolescent; using grep -E

Don't grep - there's an mt7921e chip?
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Because of the mediatek chip also try to completely cut power from the system (in doubt remove the battery for some minutes) after the voodoo dance.

LoB · 2025-10-15 13:04:58

seth wrote:

I dualboot windows, where
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
I have a mercusys card (AX3000 Wi-Fi 6 Bluetooth 5.3 PCIe Adapter MA80XE)
egrep: warning: egrep is obsolescent; using grep -E
Don't grep - there's an mt7921e chip?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Because of the mediatek chip also try to completely cut power from the system (in doubt remove the battery for some minutes) after the voodoo dance.

I have disabled fast boot and restarted the computer several times into windows and linux, including turning off power for a minute. Bluetooth was still not working on linux.

Here's the journal:
http://0x0.st/KSfq.txt

seth · 2025-10-15 13:22:26

WiFi: https://linux-hardware.org/?id=pci:14c3-0616-14c3-0616
Probably Bluetooth: https://linux-hardware.org/?id=usb:13d3-3625

Oct 15 14:54:00 penguin kernel: usb 1-7: new high-speed USB device number 6 using xhci_hcd
Oct 15 14:54:00 penguin kernel: usb 1-7: New USB device found, idVendor=13d3, idProduct=3625, bcdDevice= 1.00
Oct 15 14:54:00 penguin kernel: usb 1-7: New USB device strings: Mfr=5, Product=6, SerialNumber=7
Oct 15 14:54:00 penguin kernel: usb 1-7: Product: Wireless_Device
Oct 15 14:54:00 penguin kernel: usb 1-7: Manufacturer: MediaTek Inc.
Oct 15 14:54:00 penguin kernel: usb 1-7: SerialNumber: 000000000

There're no other radio chips.

mt7921e.disable_aspm=1 pcie_aspm=off

https://wiki.archlinux.org/title/Kernel_parameters

You could also try to reset the device after the boot, https://www.baeldung.com/linux/usb-devi … sing-sysfs
I assume it also doesn't show up in rfkill?

LoB · 2025-10-15 14:08:28

seth wrote:

WiFi: https://linux-hardware.org/?id=pci:14c3-0616-14c3-0616
Probably Bluetooth: https://linux-hardware.org/?id=usb:13d3-3625
There're no other radio chips.

What does this mean?

seth wrote:

mt7921e.disable_aspm=1 pcie_aspm=off
https://wiki.archlinux.org/title/Kernel_parameters

I booted into linux while providing these parameters to refind. Bluetooth still wasn't working, same as before. Here's the log: https://0x0.st/KSOX.txt

seth wrote:

You could also try to reset the device after the boot, https://www.baeldung.com/linux/usb-devi … sing-sysfs

That didn't fix it.

seth wrote:

I assume it also doesn't show up in rfkill?

$ sudo rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

seth · 2025-10-15 19:17:55

Do you manually load btusb to get the (unresponsive) device in rfkill?

usb-devices | grep -C20 btusb

Does it help to "rfkill block bluetooth; sleep 10; rfkill unblock bluetooth"?

LoB · 2025-10-15 20:02:14

seth wrote:

Do you manually load btusb to get the (unresponsive) device in rfkill?

No I get that output before doing anything

seth wrote:

usb-devices | grep -C20 btusb

$ sudo usb-devices | grep -C20 btusb
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number

T:  Bus=01 Lev=01 Prnt=04 Port=05 Cnt=01 Dev#=  5 Spd=12   MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs=  1
P:  Vendor=1532 ProdID=0531 Rev=01.00
/usr/bin/usb-devices: line 103: printf: : invalid number
S:  Manufacturer=Razer Inc
S:  Product=Razer Seiren Mini
S:  SerialNumber=UC2118L03305112
C:  #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I:  If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
I:  If#= 2 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=87(I) Atr=03(Int.) MxPS=  16 Ivl=1ms

T:  Bus=01 Lev=01 Prnt=05 Port=06 Cnt=01 Dev#=  6 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=13d3 ProdID=3625 Rev=01.00
S:  Manufacturer=MediaTek Inc.
S:  Product=Wireless_Device
S:  SerialNumber=000000000
C:  #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=125us
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
/usr/bin/usb-devices: line 103: printf: : invalid number
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 2 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
/usr/bin/usb-devices: line 103: printf: : invalid number
E:  Ad=0a(O) Atr=03(Int.) MxPS=  64 Ivl=125us
E:  Ad=8a(I) Atr=03(Int.) MxPS=  64 Ivl=125us

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=10000 MxCh= 4
D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=06.17
S:  Manufacturer=Linux 6.17.2-arch1-1 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:02:00.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
/usr/bin/usb-devices: line 103: printf: : invalid number
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=06.17
S:  Manufacturer=Linux 6.17.2-arch1-1 xhci-hcd
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number
/usr/bin/usb-devices: line 103: printf: : invalid number

seth wrote:

Does it help to "rfkill block bluetooth; sleep 10; rfkill unblock bluetooth"?

No.

By the way, I found a thread on reddit by someone with the same issues and card (USB ID 13d3:3625) on linux mint.
https://www.reddit.com/r/linuxmint/comm … w=original

seth · 2025-10-17 13:55:07

Also https://github.com/pop-os/pop/issues/3446 but

This should be fixed on 6.16. If I'm mistaken, let me know and I'll reopen this issue.

and also

I preferred to pass to ubuntu after this problem.

(implying the kernel version isn't necessarily relevant IFF the chip also worked on ubuntu - orall the information there is not entirely credible)

On a limb: add mt7921e to the initramfs (the MODULES array in your mkinitcpio.conf) so it loads early and ahead of btusb (w/ the theory being that it's requried to setup the device - but: rfkill'ing the device off/on should™ have achieved this)

LoB · 2025-10-27 10:35:41

seth wrote:

On a limb: add mt7921e to the initramfs (the MODULES array in your mkinitcpio.conf) so it loads early and ahead of btusb (w/ the theory being that it's requried to setup the device - but: rfkill'ing the device off/on should™ have achieved this)

I tried rfkilling off and on and also adding mt7921e to modules in mkinitcpio.conf, but it didn't work.

seth wrote:

Also https://github.com/pop-os/pop/issues/3446

The user that switched to ubuntu didn't mention whether bluetooth worked there and the developer didn't provide the reason for why it should be fixed, so I can't help but be skeptical.
Also, the hardware for linux link you found lists the device id (13d3:3625) as only "detected" across all the distros.

Is there a way to check the theory of the reddit Asleep_Average_2217 user? I mean, to find the btusb device table in the source for the arch linux package and see if the device id is there? Or is it not necessary for the id of a device to be there for it to work? Do devices have unique IDs that don't change? Unfortunately, I know very little about how linux drivers work.

Or should I simply ask about my device in some kernel development-related mailing list? Maybe the drivers aren't ready yet.

seth · 2025-10-27 14:41:24

Is there a way to check the theory of the reddit Asleep_Average_2217 user?

T:  Bus=01 Lev=01 Prnt=05 Port=06 Cnt=01 Dev#=  6 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=13d3 ProdID=3625 Rev=01.00
S:  Manufacturer=MediaTek Inc.
S:  Product=Wireless_Device
S:  SerialNumber=000000000
C:  #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=125us
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
===== this line ====> I:  If#= 2 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
E:  Ad=0a(O) Atr=03(Int.) MxPS=  64 Ivl=125us
E:  Ad=8a(I) Atr=03(Int.) MxPS=  64 Ivl=125us

but whether the assessment about the fw upload is correct idk.

Or should I simply ask about my device in some kernel development-related mailing list? Maybe the drivers aren't ready yet.

https://pkgbuild.com//~gromit/linux-bisection-kernels/ has builds of the 6.18 rc3 kernel, you could/should try that first

Last edited by seth (2025-10-27 14:41:45)

predacon · 2025-12-14 09:23:52

Try installing wireless-regdb package

Arch Linux

#1 2025-10-14 20:15:55

bluetooth not working - No default controller available

#2 2025-10-15 07:40:31

Re: bluetooth not working - No default controller available

#3 2025-10-15 13:04:58

Re: bluetooth not working - No default controller available

#4 2025-10-15 13:22:26

Re: bluetooth not working - No default controller available

#5 2025-10-15 14:08:28

Re: bluetooth not working - No default controller available

#6 2025-10-15 19:17:55

Re: bluetooth not working - No default controller available

#7 2025-10-15 20:02:14

Re: bluetooth not working - No default controller available

#8 2025-10-17 13:55:07

Re: bluetooth not working - No default controller available

#9 2025-10-27 10:35:41

Re: bluetooth not working - No default controller available

#10 2025-10-27 14:41:24

Re: bluetooth not working - No default controller available

#11 2025-12-14 09:23:52

Re: bluetooth not working - No default controller available

Board footer