[Help]: Alfa AWUS036AXM device not recognized

laubblaeser commented 1 month ago

Checklist

[X] I acknowledge that support is provided on a best-effort basis.
[X] I acknowledge that the authors and contributors to this repository cannot be held responsible for the results of my use of any information contained in or linked from this repository.

uname

Linux ferdux 6.10.2-1-default #1 SMP PREEMPT_DYNAMIC Mon Jul 29 08:51:47 UTC 2024 (65a34e2) x86_64 x86_64 x86_64 GNU/Linux

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 1b1c:1b36 Corsair Corsair Gaming K70 LUX Keyboard  
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 
Bus 004 Device 010: ID 0fce:720d Sony Ericsson Mobile Communications AB XQ-CT54 
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
Bus 005 Device 002: ID 1b1c:1b2f Corsair Sabre RGB [CH-9303011-XX] 
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

rfkill

EMPTY OUTPUT

dkms

EMPTY OUTPUT

iw

EMPTY OUTPUT

What happened?

The OS doesn't recognize the USB WiFi dongle at all. After plugging it in, I can run lsusb, which takes about 60-90 seconds until it returns anything and then the listed USB ports are "empty".

There's no problem with the stick itself as I've tested it on the same machine with a Windows dualboot where it gets recognized and works fine after installing the drivers. The stick was recognized exactly once after letting it plugged in when shutting down the PC from Windows and letting it reboot into Linux. Once I removed the stick and put it in any USB port of my PC again, it is not recognized again.

So, I can imagine that this is a really weird issue but it's worth a shot: Has anyone had this problem or a similar one? What can I do to track down the root of this issue?

System info

Operating System: openSUSE Tumbleweed 20240801 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT

Edit@16:07: A bit of formatting.

Edit@21:54: Clarify that Windows is dual-booted on the same machine.

bjlockie commented 1 month ago

In a terminal type sudo dmesg after you plug in the Alfa.

morrownr commented 1 month ago

Hi @laubblaeser

My thoughts after looking over the info you posted:

This is not a driver or firmware issue as usb adapters will show with lsusb even if the driver and firmware are not there. In fact, a lot of things can be ruled out at this point. Until lsusb can see the adapter, nothing else matters.

Is there a problem with the usb port? Maybe you should try a different port if the system has multiple ports.

Do you have another Linux system to test?

Is it possible that some bios usb settings could be causing the problem?

Can you backup your kernel to an earlier version like say 6.6? We have been seeing a LOT of problems related to wifi lately with all of the modernization that is going on.

You can always burn a flash drive with a Ubuntu 24.04 image and boot to the desktop to test. That would allow you to test a different distro and kernel without installing anything.

Cheers

laubblaeser commented 1 month ago

In a terminal type sudo dmesg after you plug in the Alfa.

Sure, here's the output:

[ 6554.969849] [   T7445] usb 3-5: new high-speed USB device number 4 using xhci_hcd
[ 6555.112994] [   T7445] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 6555.113002] [   T7445] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 6555.113007] [   T7445] usb 3-5: Product: Wireless_Device
[ 6555.113010] [   T7445] usb 3-5: Manufacturer: MediaTek Inc.
[ 6555.113013] [   T7445] usb 3-5: SerialNumber: 000000000
[ 6555.271753] [  T19523] Bluetooth: Core ver 2.22
[ 6555.271780] [  T19523] NET: Registered PF_BLUETOOTH protocol family
[ 6555.271782] [  T19523] Bluetooth: HCI device and connection manager initialized
[ 6555.271786] [  T19523] Bluetooth: HCI socket layer initialized
[ 6555.271788] [  T19523] Bluetooth: L2CAP socket layer initialized
[ 6555.271792] [  T19523] Bluetooth: SCO socket layer initialized
[ 6555.299105] [  T19525] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 6555.299248] [  T19525] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 6555.299403] [  T19525] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 6555.304767] [  T19520] usbcore: registered new interface driver btusb
[ 6555.338858] [    T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427
[ 6559.015966] [    T191] Bluetooth: hci0: Device setup in 3624245 usecs
[ 6559.015972] [    T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.

laubblaeser commented 1 month ago

This is not a driver or firmware issue as usb adapters will show with lsusb even if the driver and firmware are not there. In fact, a lot of things can be ruled out at this point. Until lsusb can see the adapter, nothing else matters.

Yeah, I figured as much but thought it's worth a shot asking here if anyone else ever experienced such a problem.

Do you have another Linux system to test?

Is it possible that some bios usb settings could be causing the problem?

Well, only other systems with Tumbleweed on them. 😄 Certainly worth a shot to try the USB dongle on another device just to rule out that the hardware isn't failing or BIOS settings aren't blocking anything. But to be honest that shouldn't be the case as it works on the same machine under Windows without any issues.

morrownr commented 1 month ago

New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00

Interesting that this line shows in the log but not with lsusb. That test with the Ubuntu 24.04 flash drive may give us an idea.

laubblaeser commented 1 month ago

Is there a problem with the usb port? Maybe you should try a different port if the system has multiple ports.

Forgot to answer this. I've tried 7 different ports on the machine so far. The dongle always lights up but doesn't show up in lsusb. :/

morrownr commented 1 month ago

The dongle always lights up...

That just means it is getting power.

I've tried 7 different ports on the machine so far.

Had to try it.

bjlockie commented 1 month ago

Type lsusb -t and lshw -c network

laubblaeser commented 1 month ago

So it just worked while I plugged it in and out multiple times in a row. Here's a bit more dmesg output showing the failed and successful attempts.

It seems as if sometimes the stack doesn't properly load and some probing fails? Does this help in any way?

``` [ 6554.969849] [ T7445] usb 3-5: new high-speed USB device number 4 using xhci_hcd [ 6555.112994] [ T7445] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 6555.113002] [ T7445] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 6555.113007] [ T7445] usb 3-5: Product: Wireless_Device [ 6555.113010] [ T7445] usb 3-5: Manufacturer: MediaTek Inc. [ 6555.113013] [ T7445] usb 3-5: SerialNumber: 000000000 [ 6555.271753] [ T19523] Bluetooth: Core ver 2.22 [ 6555.271780] [ T19523] NET: Registered PF_BLUETOOTH protocol family [ 6555.271782] [ T19523] Bluetooth: HCI device and connection manager initialized [ 6555.271786] [ T19523] Bluetooth: HCI socket layer initialized [ 6555.271788] [ T19523] Bluetooth: L2CAP socket layer initialized [ 6555.271792] [ T19523] Bluetooth: SCO socket layer initialized [ 6555.299105] [ T19525] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 6555.299248] [ T19525] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 6555.299403] [ T19525] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [ 6555.304767] [ T19520] usbcore: registered new interface driver btusb [ 6555.338858] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 6559.015966] [ T191] Bluetooth: hci0: Device setup in 3624245 usecs [ 6559.015972] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 6561.103107] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 6563.239755] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 6565.373058] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 6565.512710] [ T19525] usb 3-5: reset high-speed USB device number 4 using xhci_hcd [ 6570.829683] [ T19525] usb 3-5: device descriptor read/64, error -110 [ 6586.402851] [ T19525] usb 3-5: device descriptor read/64, error -110 [ 6586.639531] [ T19525] usb 3-5: reset high-speed USB device number 4 using xhci_hcd [ 6591.946128] [ T19525] usb 3-5: device descriptor read/64, error -110 [ 6607.522600] [ T19525] usb 3-5: device descriptor read/64, error -110 [ 6607.755978] [ T19525] usb 3-5: reset high-speed USB device number 4 using xhci_hcd [ 6612.945886] [ T19525] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6618.279129] [ T19525] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6618.489117] [ T19525] usb 3-5: device not accepting address 4, error -62 [ 6618.619150] [ T19525] usb 3-5: reset high-speed USB device number 4 using xhci_hcd [ 6623.825764] [ T19525] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6629.155746] [ T19525] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6629.365654] [ T19525] usb 3-5: device not accepting address 4, error -62 [ 6629.365726] [ T635] usb 3-5: USB disconnect, device number 4 [ 6629.365860] [ T19525] mt7921u 3-5:1.3: probe with driver mt7921u failed with error -5 [ 6629.365908] [ T19525] usbcore: registered new interface driver mt7921u [ 6629.367652] [ C1] retire_capture_urb: 147 callbacks suppressed [ 6629.488990] [ T635] usb 3-5: new high-speed USB device number 5 using xhci_hcd [ 6634.828948] [ T635] usb 3-5: device descriptor read/64, error -110 [ 6650.405454] [ T635] usb 3-5: device descriptor read/64, error -110 [ 6650.645407] [ T635] usb 3-5: new high-speed USB device number 6 using xhci_hcd [ 6655.955401] [ T635] usb 3-5: device descriptor read/64, error -110 [ 6671.528521] [ T635] usb 3-5: device descriptor read/64, error -110 [ 6671.638594] [ T635] usb usb3-port5: attempt power cycle [ 6672.058497] [ T635] usb 3-5: new high-speed USB device number 7 using xhci_hcd [ 6677.158604] [ T635] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6682.491773] [ T635] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6682.701704] [ T635] usb 3-5: device not accepting address 7, error -62 [ 6682.831703] [ T635] usb 3-5: new high-speed USB device number 8 using xhci_hcd [ 6688.034993] [ T635] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6693.371618] [ T635] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 6693.581580] [ T635] usb 3-5: device not accepting address 8, error -62 [ 6693.581644] [ T635] usb usb3-port5: unable to enumerate USB device [ 6693.690170] [ T19715] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6693.690175] [ T19715] Bluetooth: BNEP filters: protocol multicast [ 6693.690180] [ T19715] Bluetooth: BNEP socket layer initialized [ 7792.935879] [ T19519] usb 3-5: new high-speed USB device number 9 using xhci_hcd [ 7793.079498] [ T19519] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 7793.079507] [ T19519] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 7793.079511] [ T19519] usb 3-5: Product: Wireless_Device [ 7793.079515] [ T19519] usb 3-5: Manufacturer: MediaTek Inc. [ 7793.079518] [ T19519] usb 3-5: SerialNumber: 000000000 [ 7793.213856] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 7796.876838] [ T191] Bluetooth: hci0: Device setup in 3632044 usecs [ 7796.876846] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 7799.062472] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 7801.195785] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 7803.329108] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 7803.466494] [ T19519] usb 3-5: reset high-speed USB device number 9 using xhci_hcd [ 7803.645273] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 7803.661440] [ T19519] mt7921u 3-5:1.3: HW/SW Version: 0x8a108a10, Build Time: 20240219110958a [ 7803.766804] [ T191] Bluetooth: hci0: Device setup in 142317 usecs [ 7803.766812] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 7803.951335] [ T19519] mt7921u 3-5:1.3: WM Firmware Version: ____010000, Build Time: 20240219111038 [ 7803.997377] [ T191] Bluetooth: hci0: AOSP extensions version v1.00 [ 7803.997383] [ T191] Bluetooth: hci0: AOSP quality report is supported [ 7803.997493] [ T19697] Bluetooth: MGMT ver 1.22 [ 7804.001526] [ T20738] NET: Registered PF_ALG protocol family [ 7804.018961] [ T20747] Bluetooth: RFCOMM TTY layer initialized [ 7804.018969] [ T20747] Bluetooth: RFCOMM socket layer initialized [ 7804.018972] [ T20747] Bluetooth: RFCOMM ver 1.11 [ 7805.555873] [ T20734] mt7921u 3-5:1.3 wlp5s0f3u5i3: renamed from wlan0 [ 7808.715871] [ T2570] warning: `Qt bearer threa' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 [ 7972.490025] [ T19519] usb 3-5: USB disconnect, device number 9 [ 7976.420538] [ T19519] usb 3-5: new high-speed USB device number 10 using xhci_hcd [ 7976.564156] [ T19519] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 7976.564165] [ T19519] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 7976.564169] [ T19519] usb 3-5: Product: Wireless_Device [ 7976.564172] [ T19519] usb 3-5: Manufacturer: MediaTek Inc. [ 7976.564176] [ T19519] usb 3-5: SerialNumber: 000000000 [ 7976.699691] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 7976.707113] [ C1] Bluetooth: hci0: urb 0000000049d78c2e failed to resubmit (2) [ 7980.344626] [ T191] Bluetooth: hci0: Device setup in 3614442 usecs [ 7980.344632] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 7982.527127] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 7984.663764] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 7986.797075] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 7987.144483] [ T19519] usb 3-5: reset high-speed USB device number 10 using xhci_hcd [ 7992.463713] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8008.040206] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8008.270207] [ T19519] usb 3-5: reset high-speed USB device number 10 using xhci_hcd [ 8013.586841] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8029.163298] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8029.393300] [ T19519] usb 3-5: reset high-speed USB device number 10 using xhci_hcd [ 8034.579907] [ T19519] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 8039.913218] [ T19519] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 8040.119828] [ T19519] usb 3-5: device not accepting address 10, error -62 [ 8040.243183] [ T19519] usb 3-5: reset high-speed USB device number 10 using xhci_hcd [ 8045.246455] [ T19519] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 8050.579743] [ T19519] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 8050.786373] [ T19519] usb 3-5: device not accepting address 10, error -62 [ 8050.786567] [ T19519] mt7921u 3-5:1.3: probe with driver mt7921u failed with error -5 [ 8050.786885] [ T19519] usb 3-5: USB disconnect, device number 10 [ 8050.909712] [ T19519] usb 3-5: new high-speed USB device number 11 using xhci_hcd [ 8056.036339] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8071.609509] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8071.839485] [ T19519] usb 3-5: new high-speed USB device number 12 using xhci_hcd [ 8077.159445] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8092.729272] [ T19519] usb 3-5: device descriptor read/64, error -110 [ 8092.839318] [ T19519] usb usb3-port5: attempt power cycle [ 8093.242583] [ T19519] usb 3-5: new high-speed USB device number 13 using xhci_hcd [ 8098.365872] [ T19519] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command [ 8100.399935] [ T19519] usb 3-5: Device not responding to setup address. [ 8100.605825] [ T19519] usb 3-5: device not accepting address 13, error -71 [ 8103.945796] [ T19519] usb 3-5: new high-speed USB device number 15 using xhci_hcd [ 8104.089329] [ T19519] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 8104.089337] [ T19519] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 8104.089342] [ T19519] usb 3-5: Product: Wireless_Device [ 8104.089345] [ T19519] usb 3-5: Manufacturer: MediaTek Inc. [ 8104.089349] [ T19519] usb 3-5: SerialNumber: 000000000 [ 8104.202790] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 8107.848292] [ T191] Bluetooth: hci0: Device setup in 3584392 usecs [ 8107.848300] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 8109.885729] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 8112.019039] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 8114.155682] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 8119.809352] [ T19519] mt7921u 3-5:1.3: probe with driver mt7921u failed with error -5 [ 8119.809675] [ T19519] usb 3-5: USB disconnect, device number 15 [ 8120.172283] [ T19519] usb 3-5: new high-speed USB device number 16 using xhci_hcd [ 8120.315895] [ T19519] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 8120.315906] [ T19519] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 8120.315911] [ T19519] usb 3-5: Product: Wireless_Device [ 8120.315915] [ T19519] usb 3-5: Manufacturer: MediaTek Inc. [ 8120.315919] [ T19519] usb 3-5: SerialNumber: 000000000 [ 8120.457828] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 8124.098224] [ T191] Bluetooth: hci0: Device setup in 3609787 usecs [ 8124.098233] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 8126.098884] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 8128.232193] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 8130.365502] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 8130.710882] [ T19519] usb 3-5: reset high-speed USB device number 16 using xhci_hcd [ 8130.902510] [ T20721] mt7921u 3-5:1.3: HW/SW Version: 0x8a108a10, Build Time: 20240219110958a [ 8130.910996] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 8131.233189] [ T20721] mt7921u 3-5:1.3: WM Firmware Version: ____010000, Build Time: 20240219111038 [ 8132.843955] [ T21987] mt7921u 3-5:1.3 wlp5s0f3u5i3: renamed from wlan0 [ 8134.690320] [ T191] Bluetooth: hci0: Device setup in 3735411 usecs [ 8134.690329] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 8134.768485] [ T191] Bluetooth: hci0: AOSP extensions version v1.00 [ 8134.768494] [ T191] Bluetooth: hci0: AOSP quality report is supported [ 8134.768647] [ T19697] Bluetooth: MGMT ver 1.22 [ 8197.877199] [ T20721] usb 3-5: USB disconnect, device number 16 [ 8202.331375] [ T20721] usb 3-5: new high-speed USB device number 17 using xhci_hcd [ 8202.481582] [ T20721] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 8202.481591] [ T20721] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 8202.481596] [ T20721] usb 3-5: Product: Wireless_Device [ 8202.481599] [ T20721] usb 3-5: Manufacturer: MediaTek Inc. [ 8202.481602] [ T20721] usb 3-5: SerialNumber: 000000000 [ 8202.584369] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 8206.217909] [ T191] Bluetooth: hci0: Device setup in 3571340 usecs [ 8206.217916] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 8208.234644] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 8210.364617] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 8212.497932] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 8212.853915] [ T20721] usb 3-5: reset high-speed USB device number 17 using xhci_hcd [ 8216.264783] [ T20721] mt7921u 3-5:1.3: probe with driver mt7921u failed with error -5 [ 8216.265097] [ T20721] usb 3-5: USB disconnect, device number 17 [ 8216.591226] [ T20721] usb 3-5: new high-speed USB device number 18 using xhci_hcd [ 8216.734404] [ T20721] usb 3-5: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00 [ 8216.734413] [ T20721] usb 3-5: New USB device strings: Mfr=6, Product=7, SerialNumber=8 [ 8216.734418] [ T20721] usb 3-5: Product: Wireless_Device [ 8216.734421] [ T20721] usb 3-5: Manufacturer: MediaTek Inc. [ 8216.734425] [ T20721] usb 3-5: SerialNumber: 000000000 [ 8216.840690] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 8220.504281] [ T191] Bluetooth: hci0: Device setup in 3601245 usecs [ 8220.504290] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 8222.524492] [ T191] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 8224.657799] [ T191] Bluetooth: hci0: Failed to read MSFT supported features (-110) [ 8226.791117] [ T191] Bluetooth: hci0: AOSP get vendor capabilities (-110) [ 8227.141764] [ T20721] usb 3-5: reset high-speed USB device number 18 using xhci_hcd [ 8227.321065] [ T191] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 8227.358845] [ T19519] mt7921u 3-5:1.3: HW/SW Version: 0x8a108a10, Build Time: 20240219110958a [ 8227.689222] [ T19519] mt7921u 3-5:1.3: WM Firmware Version: ____010000, Build Time: 20240219111038 [ 8229.307362] [ T22240] mt7921u 3-5:1.3 wlp5s0f3u5i3: renamed from wlan0 [ 8231.093582] [ T191] Bluetooth: hci0: Device setup in 3708430 usecs [ 8231.093588] [ T191] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 8231.171385] [ T191] Bluetooth: hci0: AOSP extensions version v1.00 [ 8231.171393] [ T191] Bluetooth: hci0: AOSP quality report is supported [ 8231.171505] [ T19697] Bluetooth: MGMT ver 1.22 ```

So this means that

once the dongle is initialized properly, then there's no problem with running it in dual mode (BT and WiFi appear in the system tray, although so far I haven't tested using them both at the same time).
the issue I experience seems to be kind of the norm but replugging the dongle multiple times at the same USB port sporadically allows it to be recognized after all. (Previously I switched around the various ports and didn't repeatedly try the same port.)

bjlockie commented 1 month ago

So it just worked while I plugged it in and out multiple times in a row. Here's a bit more dmesg output showing the failed and successful attempts.

It seems as if sometimes the stack doesn't properly load and some probing fails? Does this help in any way?

So this means that
1. once the dongle is initialized properly, then there's no problem with running it in dual mode (BT and WiFi appear in the system tray, although so far I haven't tested using them both at the same time).

2. the issue I experience seems to be kind of the norm but replugging the dongle multiple times at the same USB port sporadically allows it to be recognized after all. (Previously I switched around the various ports and didn't repeatedly try the same port.)

I would try booting a different kernel via USB. My guess is there are kernel bugs. :-)

morrownr commented 1 month ago

Is your cpu amd or intel?

laubblaeser commented 1 month ago

I would try booting a different kernel via USB. My guess is there are kernel bugs. :-)

Currently have to deal with data limits from a metered connection. Maybe it's really worth a shot at some point but maybe this regression (?) will be fixed at some point in the near future.

Is your cpu amd or intel?

Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor

morrownr commented 1 month ago

AMD Ryzen 7 3700X 8-Core Processor

I have emailed a person that can provide a workaround for us to try. Standby.

FYI: This seems to only happen on AMD cpus. No idea why at this point... and it is only with the Alfa adapters... the AXM and ACML. This is the first time, if this is the issue i think it is, that I have seen a report from an AXM owner.

ZerBea commented 1 month ago

@laubblaeser Issue reports on ALFA AWUS036AXM and AWUS036AXML rise and all are similar to your report: https://www.reddit.com/r/openSUSE/comments/18tn3ev/alfa_awus036axm_not_working/ https://www.reddit.com/r/Kalilinux/comments/14h198n/awus036axml_network_card_inaccessible_in_kali_via/ https://bbs.archlinux.org/viewtopic.php?id=292420 https://forum.openwrt.org/t/alfa-awus036axml-has-anyone-got-it-to-work/184381 https://forum.garudalinux.org/t/problem-with-alfa-mediatek-wifi-awus036axml-mt7961/34098 This list is long and every day it grows.

I don't expect any fix in the next time: https://bugzilla.kernel.org/show_bug.cgi?id=219040

You can try to bisect the Linux kernel to identify the patch that caused this issue. I gave it up, because this device has never worked out of the box on my systems. Even with a workaround (disable BT, remove BT firmware), the driver sooner or later dies. In the worst case, the entire system becomes unresponsive.

morrownr commented 1 month ago

@laubblaeser

The quick way to test and see if we are the right track is to delete the bluetooth firmware:

$ sudo rm /usr/lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin*

Thanks for @ZerBea for helping out. Evidently this only shows up on AMD systems. Until very recently I only had Intel and ARM64 systems and had not ran into this issue. I have an AMD mini pc now but am not configured to test yet. This is really a mystery.

We really could use feedback at to where deleting the firmware as shown above is a good workaround.

morrownr / USB-WiFi