You are not logged in.

#1 2024-01-31 12:13:37

inspectorEvan
Member
Registered: 2024-01-31
Posts: 3

WiFi adapter ALFA awus036axml - trouble initializing USB interface

Hi forum,

I have an ALFA awus036axml. It should be supported by the mt7921u driver since kernel 5.18.

cfa3405d-05bd-4659-8fd7-fec2e084866b.webp

Link to manufacturer page.

Mirror for those reading this in two years.

I'm connecting it to the front USB panel on a Lenovo ThinkCentre M720q. Then this happens:

[    0.000000] Linux version 6.7.2-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Fri, 26 Jan 2024 19:10:20 +0000
[...]
[   47.058294] usb 1-2: new high-speed USB device number 8 using xhci_hcd
[   47.201117] usb 1-2: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[   47.201131] usb 1-2: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[   47.201138] usb 1-2: Product: Wireless_Device
[   47.201143] usb 1-2: Manufacturer: MediaTek Inc.
[   47.201147] usb 1-2: SerialNumber: 000000000
[   47.312635] Bluetooth: Core ver 2.22
[   47.312655] NET: Registered PF_BLUETOOTH protocol family
[   47.312656] Bluetooth: HCI device and connection manager initialized
[   47.312660] Bluetooth: HCI socket layer initialized
[   47.312661] Bluetooth: L2CAP socket layer initialized
[   47.312665] Bluetooth: SCO socket layer initialized
[   47.382840] usbcore: registered new interface driver btusb
[   47.398008] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20231109191416
[   47.411111] Bluetooth: hci0: urb 00000000ef75083e failed to resubmit (2)
[   71.272318] Bluetooth: hci0: Device setup in 23329385 usecs
[   71.272331] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   73.389287] usb 1-2: USB disconnect, device number 8
[   73.411552] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[   75.545068] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[   77.681567] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[   77.682511] mt7921u: probe of 1-2:1.3 failed with error -5
[   77.682608] usbcore: registered new interface driver mt7921u
[   77.958155] usb 1-2: new low-speed USB device number 9 using xhci_hcd
[   78.084817] usb 1-2: device descriptor read/64, error -71
[   78.314885] usb 1-2: device descriptor read/64, error -71
[   78.545365] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[   83.774819] usb 1-2: device descriptor read/64, error -110
[   99.351428] usb 1-2: device descriptor read/64, error -110
[   99.458132] usb usb1-port2: attempt power cycle
[   99.864708] usb 1-2: new high-speed USB device number 11 using xhci_hcd
[  104.985085] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  110.317916] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  110.524579] usb 1-2: device not accepting address 11, error -62
[  110.651162] usb 1-2: new high-speed USB device number 12 using xhci_hcd
[  115.864615] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  121.197918] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  121.404587] usb 1-2: device not accepting address 12, error -62
[  121.404807] usb usb1-port2: unable to enumerate USB device

lsusb then show nothing connected to usb bus 1, port 2.

I'm a but stumped, to be honest. Any idea would be appreciated.

Last edited by inspectorEvan (2024-01-31 12:20:53)

Offline

#2 2024-01-31 12:40:05

inspectorEvan
Member
Registered: 2024-01-31
Posts: 3

Re: WiFi adapter ALFA awus036axml - trouble initializing USB interface

There is progress. As a hail mary, I have decided to blacklist the entire bluetooth stack:

[root@mybox ~]# cat /etc/modprobe.d/bluetooth.conf 
install bluetooth /bin/true
install btusb /bin/true

...and the thing starts working:

[  117.802493] usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd
[  117.821063] usb 2-2: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  117.821078] usb 2-2: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[  117.821084] usb 2-2: Product: Wireless_Device
[  117.821088] usb 2-2: Manufacturer: MediaTek Inc.
[  117.821092] usb 2-2: SerialNumber: 000000000
[  117.891920] btmtk: Unknown symbol hci_cmd_sync_queue (err -2)
[  117.891980] btmtk: Unknown symbol hci_devcd_init (err -2)
[  117.892025] btmtk: Unknown symbol hci_devcd_complete (err -2)
[  117.892082] btmtk: Unknown symbol __hci_cmd_send (err -2)
[  117.892122] btmtk: Unknown symbol hci_devcd_register (err -2)
[  117.892213] btmtk: Unknown symbol hci_devcd_append (err -2)
[  117.892261] btmtk: Unknown symbol bt_info (err -2)
[  117.892300] btmtk: Unknown symbol bt_err (err -2)
[  117.892346] btmtk: Unknown symbol __hci_cmd_sync (err -2)
[  118.203433] usb 2-2: reset SuperSpeed USB device number 5 using xhci_hcd
[  118.250711] usbcore: registered new interface driver mt7921u
[  118.258113] mt7921u 2-2:1.3: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  118.522436] mt7921u 2-2:1.3: WM Firmware Version: ____010000, Build Time: 20231109190959
[  120.154307] mt7921u 2-2:1.3 wlp0s20f0u2i3: renamed from wlan0

This isn't really a solution though. I don't need bluetooth on this machine, but in general, the initialization should "just work".

The whole thing, now that is at least partially talking to our USB host controller shows us the following interface structure:

/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 002: Dev 005, If 0, Class=Wireless, Driver=[none], 5000M
        ID 0e8d:7961 MediaTek Inc. 
    |__ Port 002: Dev 005, If 1, Class=Wireless, Driver=[none], 5000M
        ID 0e8d:7961 MediaTek Inc. 
    |__ Port 002: Dev 005, If 2, Class=Wireless, Driver=[none], 5000M
        ID 0e8d:7961 MediaTek Inc. 
    |__ Port 002: Dev 005, If 3, Class=Vendor Specific Class, Driver=mt7921u, 5000M
        ID 0e8d:7961 MediaTek Inc. 

So, three whatevers and one actual interface for the WiFi chip. Hm.

Where should I take this "problem" for maximum effect? Mailing list for the mediatek driver?

Offline

#3 2024-03-08 16:49:00

bluetail
Member
Registered: 2024-03-08
Posts: 1

Re: WiFi adapter ALFA awus036axml - trouble initializing USB interface

I could reproduce this.
What is the current status on this?
I am on Kernel 6.7.9-2 now and your fix to block the entire bluetooth stack helped!

Last edited by bluetail (2024-03-08 16:49:29)

Offline

#4 2024-03-11 11:49:40

inspectorEvan
Member
Registered: 2024-01-31
Posts: 3

Re: WiFi adapter ALFA awus036axml - trouble initializing USB interface

I posted the whole thing to the mailing-list of the linux-mediatek driver. The devs didn't bother to react in any way so I gave up and stopped caring as well.

Offline

#5 2024-03-13 12:28:53

control
Member
Registered: 2012-03-03
Posts: 2

Re: WiFi adapter ALFA awus036axml - trouble initializing USB interface

I found out that after disabling and removing bluetooth driver for this usb wifi card everything works well.

Drivers can be found on morrownr github.

Last edited by control (2024-03-13 12:30:14)

Offline

Board footer

Powered by FluxBB