[RESPONDED] USB Device (Antlion Wireless Dongle) not working properly

Framework Laptop 13 Linux
1

Hi there,
i got my new Framework 13 (Intel 13th Generation) last weekend, and I am quite happy. But I have an USB Device that makes Problems. It is an Antlion ModMic Wireless Dongle.

When I attach the Dongle into the USB-A Port of the Notebook, or to an USB-C Port with an adapter, it does not work under Linux (Arch, Kernel 6.5).

When attaching it to an USB Hub it works.

Here is the output of journal:

Okt 26 07:43:50 georgs-framework kernel: usb 3-2: new full-speed USB device number 25 using xhci_hcd
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: New USB device found, idVendor=2f96, idProduct=0100, bcdDevice= 1.00
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: Product: Antlion Wireless Microphone
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: Manufacturer: Antlion Audio
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: 1:1: cannot set freq 48000 to ep 0x82
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: 10:0: failed to get current value for ch 0 (-22)
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: 10:0: cannot get min/max values for control 2 (id 10)
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: 10:0: failed to get current value for ch 0 (-22)
Okt 26 07:43:51 georgs-framework kernel: usbhid 3-2:1.2: can't add hid device: -71
Okt 26 07:43:51 georgs-framework kernel: usbhid: probe of 3-2:1.2 failed with error -71
Okt 26 07:43:51 georgs-framework kernel: usb 3-2: USB disconnect, device number 25
Okt 26 07:43:51 georgs-framework (udev-worker)[20500]: controlC1: /usr/lib/udev/rules.d/78-sound-card.rules:5 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/sound/card1/controlC1/../uevent}, ignoring: No such file or directory

Here the Output of lsusb -t

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 20000M/x2
    |__ Port 004: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M
        |__ Port 001: Dev 003, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 004: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
        |__ Port 004: Dev 004, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 004: Dev 006, If 0, Class=Video, Driver=uvcvideo, 5000M
            |__ Port 004: Dev 006, If 1, Class=Video, Driver=uvcvideo, 5000M
            |__ Port 004: Dev 006, If 2, Class=Human Interface Device, Driver=usbhid, 5000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 003: Dev 014, If 0, Class=[unknown], Driver=[none], 12M
    |__ Port 005: Dev 008, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 001: Dev 009, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 004: Dev 010, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 001: Dev 012, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 003: Dev 015, If 0, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 003: Dev 015, If 1, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 003: Dev 015, If 2, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 004: Dev 013, If 0, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 004: Dev 013, If 1, Class=Human Interface Device, Driver=usbhid, 12M
                |__ Port 004: Dev 013, If 2, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 002: Dev 017, If 0, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 002: Dev 017, If 1, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 002: Dev 017, If 2, Class=Application Specific Interface, Driver=[none], 480M
        |__ Port 005: Dev 011, If 0, Class=[unknown], Driver=[none], 480M
    |__ Port 007: Dev 002, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 007: Dev 002, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 009: Dev 003, If 0, Class=Vendor Specific Class, Driver=[none], 12M
    |__ Port 010: Dev 004, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 010: Dev 004, If 1, Class=Wireless, Driver=btusb, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M

I am not sure, if this is a hardware Problem, or something else. This dongle worked in all other Notebooks I have and the Hubs as well.

2

Hi @Georg_Focsaneanu, welcome to the community.

On officially supported distros like Ubuntu 22.04.3 with the OEM C kernel or just with Fedora 38/39, it should just work.

As we don’t test against Arch, it would be worth testing it with Fedora 38 to see if you get it working from a Live USB.

3

Good morning.
I tested with Fedora 38 this morning. Exact the same behavior and Error Messages in the Logs. The Dongle works fine on all other systems I have here. And it works on an USB Hub (with Power).
But attached to the Framework it does not work. When it is attached while booting (also with Ferdora Live) I see this Message in the Terminal Boot Logs already:

usbhid 3-2:1.2: can't add hid device: -71
1 Like
4

Hmm, this may be an incompatibility issue. What does it show up as under lsusb?

5

I am currently on vacation until Sunday. And did not take the usb device with me. I posted lsusb in the first post. Or do you mean when it is attached through a hub?

I first asked in the arch forum, there are some more informations

https://bbs.archlinux.org/viewtopic.php?id=289841

My assumption is a problem with the firmware. Before my vacation I tested the disc in my Lenovo notebook and it worked.

6

Here the lsusb output when attached directly to the framework

❯ sudo 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 002 Device 002: ID 291a:8383 Generic 4-Port USB 3.0 Hub
Bus 002 Device 003: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 002 Device 004: ID 058f:8468 Alcor Micro Corp. Mass Storage Device
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 005: ID 291a:5423 Generic 4-Port USB 2.0 Hub
Bus 003 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 007: ID 0bda:5450 Realtek Semiconductor Corp. BillBoard Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Here when it is attached to an USB Powered HUB:

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 002 Device 002: ID 291a:8383 Generic 4-Port USB 3.0 Hub
Bus 002 Device 003: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 002 Device 004: ID 058f:8468 Alcor Micro Corp. Mass Storage Device
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 005: ID 291a:5423 Generic 4-Port USB 2.0 Hub
Bus 003 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 007: ID 0bda:5450 Realtek Semiconductor Corp. BillBoard Device
Bus 003 Device 063: ID 2f96:0100 Antlion Audio Antlion Wireless Microphone
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

This is the device

Bus 003 Device 063: ID 2f96:0100 Antlion Audio Antlion Wireless Microphone
7

This is helpful, thank you. Feels like a powering issue for the device when not connected to the hub. Like, their device firmware isn’t playing nicely with ours. Thinking perhaps the hub sidesteps this by acting as a go-between.

And to confirm, when not connecting to a hub, no adapters are in use here? Just the expansion card.

Additionally, doe the hub connect to the same expansion card on your framework?

8

Yes. When connecting to my notebook I tried the USB-A Port and the USB-C Port with an adapter. The Hub was connected to the USB-C Port. I don’t have an USB-A Hub here.

I could get an USB-A Hub if needed, or if this could help. If I can support with some debug Logs, or something else, to help to improve the firmware, let me know.

9

This is tough as we don’t have access to this device here. We know it works with a hub on Arch, does it present similar behavior on something like a Fedora Live USB? I highly doubt it will matter as this feels like a firmware conflict, but it would be an interesting comparable at this stage.

10

I tested it with Fedora 38 Live CD already. Same behavior. As posted, there is also an error while booting and the device is attached.

Usbhid 3-2:1.2: can’t add hid device: -71

I don’t have a Windows License here, so I cannot test it with windows right now.

11

Appreciate the continued testing. It would surely behave differently on Windows. But it would rule out BIOS/firmware related issues in a test. You can install Windows (legally) without a license. It just shows as non-activated and has limited features. Easiest to do from another Windows machine, not impossible however on Linux, just more involved.

Either way, this is appears to be a conflict with how it is interacting with the laptop.

12

I will do this this weekend. Need the notebook for work now.

13

I tried to start Windows from an LiveUSB Stick. But this ends in a blue screen. So I now ordered a small second NVMe, so that I can install Windows properly and test it with windows.
But in the meantime, I organized an ANKER USB-C Hub (8-1). When I attach this Hub (without external Power) the Antlion USB Device also workes. So it seems not be an issue with Powered Hubs.

I will try Windows next weekend. Under the week I need the notebook for Work. And with the ANKER Hub I have an working Workaround for now.

1 Like
14

So I did it. Installed Windows 11 (what a horrible experiance…). After installing all the updates and drivers, I attached the Antlion to the USB Port. Than you hear the USB Attached Detached Programm several times, but it did not work. On an USB Hub, it worked like under Linux.

15

Darn it. It is possible the issue falls with the Antlion ModMic Wireless Dongle itself not playing nicely with the direction connection. If you’re able to use the hub as a workaround, this may be your best bet.

16

fwiw … i have the same issue on a Ubunut 23.10 …

dmesg shows:

[1055890.133629] usb 3-4: new full-speed USB device number 63 using xhci_hcd
[1055890.361820] usb 3-4: New USB device found, idVendor=2f96, idProduct=0100, bcdDevice= 1.00
[1055890.361824] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1055890.361825] usb 3-4: Product: Antlion Wireless Microphone
[1055890.361826] usb 3-4: Manufacturer: Antlion Audio
[1055890.365727] usb 3-4: 1:1: cannot set freq 48000 to ep 0x82
[1055890.367068] usb 3-4: 10:0: failed to get current value for ch 0 (-22)
[1055890.369550] usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
[1055890.370825] usb 3-4: 10:0: failed to get current value for ch 0 (-22)
[1055890.373140] usbhid 3-4:1.2: can't add hid device: -71
[1055890.429669] usbhid: probe of 3-4:1.2 failed with error -71
[1055890.429902] usb 3-4: USB disconnect, device number 63

when inserting the device … i’ll try a USB HUb later, but would prefer this directly connected to the laptop

17

also… after initial connect the USB-A port does not recognize devices anymore, i need to disconnect and reconnect the USB-A port for it to work again

18

… and it also works on a USB-C attached Hub