I have a USB Wi-FI adapter (ALFA AWUS036AXM) that I am testing with the GL-iNET PULI (XE300).
Openwrt version: 4.3.16
Driver installed: kmod-mt7921u
kmod-mt76-connac - 5.10.176+2022-09-06-d7054646-5
kmod-mt76-core - 5.10.176+2022-09-06-d7054646-5
kmod-mt76-usb - 5.10.176+2022-09-06-d7054646-5
kmod-mt7921-common - 5.10.176+2022-09-06-d7054646-5
kmod-mt7921-firmware - 5.10.176+2022-09-06-d7054646-5
kmod-mt7921u - 5.10.176+2022-09-06-d7054646-5
Successful case
When the PULI is fully powered on, THEN The USB adapter plugged in, it is detected fine and a PHY is created
lsusb output
Bus 001 Device 005: ID 2c7c:0125 Android Android
Bus 001 Device 004: ID 1a86:7523 USB Serial
Bus 001 Device 003: ID 05e3:0752 Generic USB Storage
Bus 001 Device 007: ID 0e8d:7961 MediaTek Inc. Wireless_Device
Bus 001 Device 002: ID 05e3:0618 USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.176 ehci_hcd EHCI Host Controller
Failure case
If the USB adapter is plugged in, then the PULI is powered on, the wifi adapter is NOT detected. Even unplugging and reinserting does NOT help.
lsusb output
Bus 001 Device 004: ID 2c7c:0125 Android Android
Bus 001 Device 003: ID 05e3:0752 Generic USB Storage
Bus 001 Device 002: ID 05e3:0618 USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.176 ehci_hcd EHCI Host Controller
As you can see both the MediaTek device AND USB serial device are missing from lsusb
dmesg | grep usb
8.797948] usbcore: registered new interface driver usbfs
[ 8.803731] usbcore: registered new interface driver hub
[ 8.809349] usbcore: registered new device driver usb
[ 8.921891] ehci-platform 1b000000.usb: EHCI Host Controller
[ 8.927827] ehci-platform 1b000000.usb: new USB bus registered, assigned bus number 1
[ 8.936051] ehci-platform 1b000000.usb: irq 3, io mem 0x1b000000
[ 8.967007] ehci-platform 1b000000.usb: USB 2.0 started, EHCI 1.00
[ 9.023278] usbcore: registered new interface driver usb-storage
[ 9.497101] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 10.097212] usb 1-1.1: new high-speed USB device number 3 using ehci-platform
[ 10.298698] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 10.314283] scsi host0: usb-storage 1-1.1:1.0
[ 13.846991] usb 1-1.2: new high-speed USB device number 4 using ehci-platform
[ 37.488315] usbcore: registered new interface driver cdc_acm
[ 37.529354] usbcore: registered new interface driver cdc_wdm
[ 37.585343] usbcore: registered new interface driver ipheth
[ 37.824515] usbcore: registered new interface driver usbserial_generic
[ 37.831432] usbserial: USB Serial support registered for generic
[ 38.060815] usbcore: registered new interface driver cdc_ether
[ 38.082602] usbcore: registered new interface driver cdc_ncm
[ 38.198822] usbcore: registered new interface driver ch341
[ 38.204576] usbserial: USB Serial support registered for ch341-uart
[ 38.243607] usbcore: registered new interface driver huawei_cdc_ncm
[ 39.059820] usbcore: registered new interface driver mt7921u
[ 39.158245] qmi_wwan 1-1.2:1.4 wwan0: register 'qmi_wwan' at usb-1b000000.usb-1.2, WWAN/QMI device, 5e:b1:9b:b7:c5:94
[ 39.169526] usbcore: registered new interface driver qmi_wwan
[ 39.200937] usbcore: registered new interface driver rndis_host
[ 39.310718] usbcore: registered new interface driver option
[ 39.316563] usbserial: USB Serial support registered for GSM modem (1-port)
[ 39.331060] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[ 39.345269] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 39.359563] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 39.373801] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
I tried power cycling the usb but it didn't help
uhubctl -l 1 -p 1 -a off
uhubctl -l 1 -p 1 -a on
The issue did not occur with USB storage.
Any ideas what the issue is and any workarounds (e.g. to reset usb, reload modules)?
Thanks