USB bluetooth not recognized

tigerjack · 2025-09-24 09:56:35

I purchased a bluetooth USB adapter, but it's not working.
I installed the bluez package as per the wiki's instructions, and also the deprecated package.

rfkill list, and hciconfig -a returns nothing.

#>dmesg | grep -i blue
[  256.775144] Bluetooth: Core ver 2.22
[  256.775169] NET: Registered PF_BLUETOOTH protocol family
[  256.775171] Bluetooth: HCI device and connection manager initialized
[  256.775175] Bluetooth: HCI socket layer initialized
[  256.775177] Bluetooth: L2CAP socket layer initialized
[  256.775180] Bluetooth: SCO socket layer initialized
[  278.366191] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  278.366195] Bluetooth: BNEP filters: protocol multicast
[  278.366199] Bluetooth: BNEP socket layer initialized

On inserting the usb stick

 #>dmesg -w
[  190.992253] usb 1-3: new full-speed USB device number 8 using xhci_hcd
[  191.352068] usb 1-3: New USB device found, idVendor=0a12, idProduct=4010, bcdDevice=21.18
[  191.352074] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  191.358875] hub 1-3:1.0: USB hub found
[  191.361805] hub 1-3:1.0: 4 ports detected
[  191.672248] usb 1-3.1: new full-speed USB device number 9 using xhci_hcd
[  191.950747] usb 1-3.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=30.91
[  191.950754] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  191.950757] usb 1-3.1: Product: YET-LE10
[  191.950759] usb 1-3.1: Manufacturer: TaiYiLian
[  191.950762] usb 1-3.1: SerialNumber: 20250117V1.0.0
[  191.978983] input: TaiYiLian YET-LE10 Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:0A12:4007.0009/input/input23
[  192.029336] input: TaiYiLian YET-LE10 as /devices/pci0000:00/0000:00:02.1/0000:01:00.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:0A12:4007.0009/input/input24
[  192.040360] hid-generic 0003:0A12:4007.0009: input,hiddev97,hidraw3: USB HID v1.11 Device [TaiYiLian YET-LE10] on usb-0000:01:00.0-3.1/input0
[  192.051113] hid-generic 0003:0A12:4007.000A: hiddev98,hidraw4: USB HID v1.11 Device [TaiYiLian YET-LE10] on usb-0000:01:00.0-3.1/input1

$>lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 480M
    |__ Port 003: Dev 006, If 0, Class=Hub, Driver=hub/4p, 12M
        |__ Port 001: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 007, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 007, If 2, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 001: Dev 007, If 3, Class=Audio, Driver=snd-usb-audio, 12M

Lone_Wolf · 2025-09-24 10:41:44

Boot the system without the adapter present.
Once the system has fully booted, insert the adapter .

Then Rin as root (or with root rights)

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

and post the link it will output.

Moderator Note :
Moving to Kernel & Hardware

Last edited by Lone_Wolf (2025-09-24 10:42:37)

tigerjack · 2025-09-24 11:47:51

Lone_Wolf wrote:

...

Hey, thanks
Here is the link http://0x0.st/KmqC.txt.

Lone_Wolf · 2025-09-25 08:32:29

Notghing suspicious in the logs. Your device is a TaiYiLian YET-LE10 .

https://gist.github.com/Juul/bc3b9120c2 … aaed122000 is about a different device from that brand and the only somewhat relevant page I can find .

Please post the output of lsusb -tv with the adapter plugged in, it may be enough to determine the chipset it uses.

mmy8x · 2025-09-25 10:42:30

Can you install uhubctl (e.g. from AUR) and run it on this hub, i.e.

uhubctl -f -l 1-3

It looks the device contains a hub and the hub itself reports no connected devices besides some audio adapter.
In such case not sure what can be done about it, without taking things apart.

Does any bluetooth functionality show up with any other OS or host machine?

tigerjack · 2025-09-27 08:23:31

Lone_Wolf wrote:

Notghing suspicious in the logs. Your device is a TaiYiLian YET-LE10 .
https://gist.github.com/Juul/bc3b9120c2 … aaed122000 is about a different device from that brand and the only somewhat relevant page I can find .
Please post the output of lsusb -tv with the adapter plugged in, it may be enough to determine the chipset it uses.

Sorry for the delay, I did not receive a notification.
Here is the output.

❯ sudo lsusb -tv
[sudo] password for simone: 
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/4p, 12M
        ID 0a12:4010 Cambridge Silicon Radio, Ltd Mpow HC5 Headset in charging mode - USB Hub
        |__ Port 001: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 0a12:4007 Cambridge Silicon Radio, Ltd Mpow HC5 Headset in charging mode - HID / Mass Storage
        |__ Port 001: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 0a12:4007 Cambridge Silicon Radio, Ltd Mpow HC5 Headset in charging mode - HID / Mass Storage
        |__ Port 001: Dev 005, If 2, Class=Audio, Driver=snd-usb-audio, 12M
            ID 0a12:4007 Cambridge Silicon Radio, Ltd Mpow HC5 Headset in charging mode - HID / Mass Storage
        |__ Port 001: Dev 005, If 3, Class=Audio, Driver=snd-usb-audio, 12M
            ID 0a12:4007 Cambridge Silicon Radio, Ltd Mpow HC5 Headset in charging mode - HID / Mass Storage
        |__ Port 001: Dev 005, If 4, Class=Audio, Driver=snd-usb-audio, 12M
            ID 0a12:4007 Cambridge Silicon Radio, Ltd Mpow HC5 Headset in charging mode - HID / Mass Storage
    |__ Port 007: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0610 Genesys Logic, Inc. Hub
    |__ Port 008: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 26ce:01a2  
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
        |__ Port 003: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
        |__ Port 004: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c336 Logitech, Inc. G213 Prodigy Gaming Keyboard
        |__ Port 004: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 046d:c336 Logitech, Inc. G213 Prodigy Gaming Keyboard
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M
        ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub

tigerjack · 2025-09-27 08:25:53

mmy8x wrote:

Can you install uhubctl (e.g. from AUR) and run it on this hub, i.e.
uhubctl -f -l 1-3
It looks the device contains a hub and the hub itself reports no connected devices besides some audio adapter.
In such case not sure what can be done about it, without taking things apart.
Does any bluetooth functionality show up with any other OS or host machine?

I did not try with any other machine; honestly at this point I am just thinking of returning it, especially if, as suggested before, it works only with one specific headset.

Anyway, here is the output.

❯ sudo uhubctl -f -l 1-3
Current status for hub 1-3 [0a12:4010, USB 2.00, 4 ports, ganged]
  Port 1: 0103 power enable connect [0a12:4007 TaiYiLian YET-LE10 20250117V1.0.0]
  Port 2: 0100 power
  Port 3: 0100 power
  Port 4: 0100 power

Lone_Wolf · 2025-09-27 10:22:32

The lsusb -yv output matches almost exactly with the devices in the gist.
The hub output also matches with search results for 0a12:4010 : a hub that doesn't show any connected devices.

Atleast one windows 11 user couldn't get it to work with their blutooth headset.

Returning it seems the best option.

Last edited by Lone_Wolf (2025-09-27 10:23:19)

Arch Linux

#1 2025-09-24 09:56:35

USB bluetooth not recognized

#2 2025-09-24 10:41:44

Re: USB bluetooth not recognized

#3 2025-09-24 11:47:51

Re: USB bluetooth not recognized

#4 2025-09-25 08:32:29

Re: USB bluetooth not recognized

#5 2025-09-25 10:42:30

Re: USB bluetooth not recognized

#6 2025-09-27 08:23:31

Re: USB bluetooth not recognized

#7 2025-09-27 08:25:53

Re: USB bluetooth not recognized

#8 2025-09-27 10:22:32

Re: USB bluetooth not recognized

Board footer