MA530 Bluetooth Adapter. No devices on scan and computer not visible

norysq · 2025-06-01 17:58:32

Hello fellow Arch users,

I have had a problem setting up my MA530 bluetooth dongle. The adapter is found as default controller and everything seems to behave as it should, except there are no devices no matter how long I scan for and my PC is not discoverable even when discoverable setting is set, e.g from my phone. I have tried a lot of things I found in the forum but none of them worked.

`btusb` is loaded. I tried changing the class to 0x100100, but that didn't seem to work (also doesn't show in `btmgmt info` unless I set it manually using `hciconfig`). Even though I didn't expect it to work, I also tried installing hid2hci (https://wiki.archlinux.org/title/Blueto … _not_found). As expected that did nothing. Here is some related info

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 2c4e:0115 Mercucys INC Mercusys MA530 Adapter    <----- THIS ONE
Bus 003 Device 003: ID 1532:02a1 Razer USA, Ltd Razer Ornata V3
Bus 003 Device 004: ID 1462:7c37 Micro Star International MYSTIC LIGHT 
Bus 003 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
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 005 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 005 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 005 Device 004: ID 1050:0402 Yubico.com Yubikey 4/5 U2F
Bus 005 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 005 Device 006: ID 1e7d:2e2c ROCCAT ROCCAT Kone Aimo 16K
Bus 005 Device 007: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 006 Device 003: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 006 Device 004: ID 05e3:0612 Genesys Logic, Inc. Hub

$ lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 480M
    |__ Port 003: Dev 007, If 0, Class=Wireless, Driver=btusb, 12M                                  <-----
    |__ Port 003: Dev 007, If 1, Class=Wireless, Driver=btusb, 12M                                  <-----
    |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 004: Dev 003, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 005: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 006: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/3p, 480M
        |__ Port 001: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/2p, 480M
    |__ Port 004: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 006, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 007, If 0, Class=Video, Driver=uvcvideo, 480M
        |__ Port 002: Dev 007, If 1, Class=Video, Driver=uvcvideo, 480M
        |__ Port 002: Dev 007, If 2, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 002: Dev 007, If 3, Class=Audio, Driver=snd-usb-audio, 480M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/2p, 5000M
    |__ Port 003: Dev 005, If 0, Class=Hub, Driver=hub/2p, 5000M
    |__ Port 004: Dev 004, If 0, Class=Hub, Driver=hub/4p, 5000M

$ btmgmt info
Index list with 1 item
hci0:	Primary controller
	addr 30:16:9D:6B:3D:4D version 10 manufacturer 93 class 0x6c0104
	supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy static-addr phy-configuration 
	current settings: powered ssp br/edr secure-conn 
	name pcmichi
	short name

What confuses me here is that it does not have `connectable` as current setting, but I have not found a way to change that. I figured that will show once I actually pair a device.

$ rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

$ uname -a
Linux pcmichi 6.14.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 29 May 2025 21:42:15 +0000 x86_64 GNU/Linux

$ paru -Qs bluez
local/bluez 5.82-1
    Daemons for the bluetooth protocol stack
local/bluez-deprecated-tools 5.82-1
    Deprecated tools that are no longer maintained
local/bluez-hid2hci 5.82-1
    Put HID proxying bluetooth HCI's into HCI mode
local/bluez-libs 5.82-1
    Deprecated libraries for the bluetooth protocol stack
local/bluez-obex 5.82-1
    Object Exchange daemon for sharing content
local/bluez-utils 5.82-1
    Development and debugging utilities for the bluetooth protocol stack

Unplugging and replugging yields the following journal output (which seems correct but is not what is listed on the wiki; I think the wiki is just quite old, but I might be wrong)

$ sudo journalctl -f
Jun 01 19:38:48 pcmichi bluetoothd[46343]: Endpoint unregistered: sender=:1.21 path=/MediaEndpoint/A2DPSource/opus_05
Jun 01 19:38:48 pcmichi bluetoothd[46343]: Endpoint unregistered: sender=:1.21 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jun 01 19:38:48 pcmichi bluetoothd[46343]: Endpoint unregistered: sender=:1.21 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jun 01 19:38:48 pcmichi bluetoothd[46343]: Battery Provider Manager destroyed
Jun 01 19:38:48 pcmichi systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 01 19:38:48 pcmichi systemd[803]: Stopped target Bluetooth.
Jun 01 19:38:48 pcmichi systemd[1]: Stopped target Bluetooth Support.
Jun 01 19:38:48 pcmichi systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 01 19:38:50 pcmichi sudo[170078]:    michi : TTY=pts/3 ; PWD=/home/michi ; USER=root ; COMMAND=/usr/bin/journalctl -f
Jun 01 19:38:50 pcmichi sudo[170078]: pam_unix(sudo:session): session opened for user root(uid=0) by michi(uid=1000)
Jun 01 19:38:51 pcmichi kernel: usb 3-3: new full-speed USB device number 7 using xhci_hcd
Jun 01 19:38:52 pcmichi kernel: usb 3-3: New USB device found, idVendor=2c4e, idProduct=0115, bcdDevice= 2.00
Jun 01 19:38:52 pcmichi kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 01 19:38:52 pcmichi kernel: usb 3-3: Product: Mercusys MA530 Adapter
Jun 01 19:38:52 pcmichi kernel: usb 3-3: Manufacturer:  
Jun 01 19:38:52 pcmichi kernel: usb 3-3: SerialNumber: 30169D6B3D4D
Jun 01 19:38:52 pcmichi systemd[803]: Reached target Bluetooth.
Jun 01 19:38:52 pcmichi systemd[1]: Reached target Bluetooth Support.
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Battery Provider Manager created
Jun 01 19:38:52 pcmichi kernel: Bluetooth: MGMT ver 1.23
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/ldac
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/aptx_hd
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aptx_hd
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/aptx
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aptx
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/aac
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aac
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/opus_g
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/opus_g
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/sbc
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/sbc
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/faststream
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/opus_05
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/opus_05
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jun 01 19:38:52 pcmichi bluetoothd[46343]: Endpoint registered: sender=:1.21 path=/MediaEndpoint/A2DPSource/opus_05_duplex

I did also change the link mode from dual to BR/EDR, but that also did not help (https://wiki.archlinux.org/title/Blueto … ow_energy)).
Maybe relevant grub config lines

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=6 quiet module_blacklist=i915 nvidia_drm.modeset=1"
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

I hope someone can point me into the right direction to fix this. If there is some information missing feel free to ask

Thank you

Pranas · 2025-06-23 12:43:11

I'm having the exact same issue with the same device. Did you manage to fix it?

norysq · 2025-06-23 13:14:04

I have not yet managed to fix it. I have been trying to fix this for over a year. That is why I opened this issue.

Edit: Is your output also the same?

Last edited by norysq (2025-06-23 13:27:00)

Pranas · 2025-06-23 14:07:57

Yeah same output, except for this:

btmgmt info
Unable to send index_list cmd

Also, I have found this: https://forums.linuxmint.com/viewtopic. … 0#p2609110 where the op managed to get it to work, but didn´t for me, obviously. I don't know it this can be useful somehow.

norysq · 2025-06-23 14:33:43

Oh yea that happened a few days ago for me as well. Seems to be a regression on 5.83 (see https://github.com/bluez/bluez/issues/1319 ). Just downgrade `bluez-utils` like explained in the wiki. Then you should get a helpful output. Please let me know if you have the same output. If so this might be a deeper issue with the device.

Pranas · 2025-06-23 21:21:53

Sorry for the delayed answer, I tried to downgrade the package but nothing seems to change, same output.

Edit: I picked the wrong version, after downgrading to 5.82 now this is the output:

btmgmt info
Index list with 1 item
hci0:	Primary controller
	addr 30:16:9D:6B:50:07 version 10 manufacturer 93 class 0x6c0104
	supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy static-addr phy-configuration 
	current settings: powered connectable discoverable bondable ssp br/edr le secure-conn 
	name pranas
	short name

Last edited by Pranas (2025-06-23 21:31:39)

norysq · 2025-06-23 21:49:52

After some juggling with btmgmt commands I can manage to produce the exact output you have. I am also not an expert but I will try to see if I can get rtl8192eu to run somehow and see if that makes a difference. I read a few forum posts that mentioned this driver (including the one you provided). I will need some time to confirm if this is the solution though as I don't have much time right now, especially not enough to fix a broken system in case I mess up. Any insights would be greatly appreciated to narrow it down somehow

Pranas · 2025-06-23 22:16:13

I'm not an expert myself, I don't really need bluetooth right now, on my desktop I only use it to play with a controller wireless, I guess I'll just use a cable and call it a day. I know I could buy a new dongle but it bothers me, especially because it works on Windows. Hopefully it will be fixed in future kernel updates, but in my spare time I'll keep looking online and I'll write here if I find something.

Edit: From a ubuntu 24.04 LTS live usb by following this tutorial https://forums.linuxmint.com/viewtopic. … 0#p2609110 works. Just wanted to try myself..

Last edited by Pranas (2025-06-24 12:01:18)

Arch Linux

#1 2025-06-01 17:58:32

MA530 Bluetooth Adapter. No devices on scan and computer not visible

#2 2025-06-23 12:43:11

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

#3 2025-06-23 13:14:04

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

#4 2025-06-23 14:07:57

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

#5 2025-06-23 14:33:43

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

#6 2025-06-23 21:21:53

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

#7 2025-06-23 21:49:52

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

#8 2025-06-23 22:16:13

Re: MA530 Bluetooth Adapter. No devices on scan and computer not visible

Board footer