Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of Bug Reports for the mt7921au chipset / mt7921u driver... #107

Open
morrownr opened this issue Sep 6, 2022 · 334 comments
Open

List of Bug Reports for the mt7921au chipset / mt7921u driver... #107

morrownr opened this issue Sep 6, 2022 · 334 comments

Comments

@morrownr
Copy link
Owner

morrownr commented Sep 6, 2022

This issue is for maintaining a list of problematic issues that need work. This list will be maintained and updated in this first post by @morrownr . Please add posts to this issue as you have updated information for the existing BUGs in the list or if you have information about a new BUG. Thank you.

Dear Mediatek devs... help is appreciated.


Bug: (2024-04-18) See: #392 . WDS/4addr not supported in AP mode. First reported with Alfa AXML adapter that uses the mt7921au chipset and mt7921u driver). The OP is unable to use WDS/4addr in AP mode.

Status: Open

Info: It was reported that this capability does work with an adapter that uses the mt7612u chipset/driver.


Bug: (2024-03-26) See: #378 Wifi adapter not showing up. First reported with Alfa AXML adapter that uses the mt7921au chipset and mt7921u driver). The adapter is non-functional until using the workaround below.

Status: Open

Workaround: the workaround is to run modprobe -r btusb first, then plug in the usb wifi adapter.

More input is needed. Is this a problem with btusb?

Update: When testing the Alfa AXML with Ubuntu 24.10, the system locks up. Things seem to be getting worse instead of better.


Bug: (2023-12-22) Linux distros are detecting Bluetooth capability in Alfa AXML. Alfa AXM and Confast 953 mt7921au based adapters but none of the adapters on the market have Bluetooth turned on so it won't work. Linux should not be detecting Bluetooth capability when it is actually not available.

Update: Evidently some Alfa AXML and AXM adapter do have bluetooth support turned on. I wish they would not do that but it is what it is. This problem is getting worse.

Status: Open and ongoing

Here is a link to a location where you can get a copy of the Intel White Paper that explains the details of why USB3 capable WiFi adapters should not have Bluetooth capability turned on:

https://www.usb.org/document-library/usb-30-radio-frequency-interference-impact-24-ghz-wireless-devices

USB3 WiFi adapters should not have Bluetooth turned on as the USB3 will cause interference with Bluetooth. If makers decide they really want Bluetooth capability in an adapter then they need to limit wifi to USB2 capability. All adapters with the mt7921au chipset that I am aware of have Bluetooth turned off so WiFi can operate in USB3 mode. However, there is a bug in that Bluetooth capability is still being detected by Linux distros and the driver/firmware is loading. Systems act like Bluetooth is available but when you try to use the Bluetooth, it won't work. It is not clear to me how this can be fixed but it really does need to be fixed.

This is not a problem with PCIe cards. I have a mt7922 based PCIe card. Wifi and Bluetooth work well together because wifi uses the PCIe bus and not USB. Please understand that issue in this bug is not exclusive to this chipset. This is an issue will all USB WiFi adapters. The adapters that have USB wifi capability and BT capabilities over the years have limited USB to USB2 to avoid the problem of interference.


Bug: (2023-12-07) Active monitor mode seems to be broken.

Status: open

Reporter: @ZerBea
Link: openwrt/mt76#839
Problem: Using Active Monitor mode breaks the driver

Driver reports that active monitor mode is possible:

$ iw list | grep active
Device supports active monitor (which will ACK incoming frames)

But if hcxdumptool set active monitor mode, it stops working.

If active monitor mode is disabled, everything's fine

0 ERROR(s) during runtime
638 Packet(s) captured by kernel
0 Packet(s) dropped by kernel
1 SHB written to pcapng dumpfile
1 IDB written to pcapng dumpfile
1 ECB written to pcapng dumpfile
83 EPB written to pcapng dumpfile

exit on sigterm
I don't think the problem is related to hcxdumptool, because it can be reproduced with iw, ip link and tshark, too:

$ sudo ip link set wlp22s0f0u4i3 down
$ sudo iw dev wlp22s0f0u4i3 set type monitor
$ sudo ip link set wlp22s0f0u4i3 up
$ tsahrk -i wlp22s0f0u4i3
22 packets captured

$ sudo ip link set wlp22s0f0u4i3 down
$ sudo iw dev wlp22s0f0u4i3 set monitor active
$ sudo ip link set wlp22s0f0u4i3 up
$ tshark -i wlp22s0f0u4i3
Capturing on 'wlp22s0f0u4i3'
^C
0 packets captured

Background:
Running active monitor mode, the device ACK incoming frames addressed to the virtual MAC of the device.
This feature is really useful to perform PMKID attacks.
At the moment, active monitor mode is working on:

mt76x0u
mt76x2u

It is not working on:

mt7601u
mt7921u

I see two options:
active monitor mode should be fixed, or
active monitor mode capability should not be reported by the driver

mt7601u
$ iw list | grep active
Device supports active monitor (which will ACK incoming frames)

mt7921u
$ iw list | grep active
Device supports active monitor (which will ACK incoming frames)


Bug: LED does not function in several of the usb wifi adapters that use the mt7921au chipset.

Status: open, it appears that LED support was never added to the driver.

Reported by @morrownr
Confirmed by numerous users.


Bug: AP Mode DFS (5 GHz) support is non-functional
Status: open

Reported by @morrownr
Confirmed by numerous users.

This is really a serious omission in that in many places in the world there are limited non-DFS channels available leading to high levels of congestion.

Dear Mediatek, does your usb chipset competitor support DFS channels in AP Mode? Yes they do. See: out-of-kernel drivers for rtl8852cu, rtl8812au, rtl8811au, rtl8812bu and rtl8811cu. You need to think about this. Sincerely.


Bug: txpower reading is showing as unusually low as in 3 dBm using iw.
Status: open

Reported by several individuals.

This reading is wrong. This really needs to be fixed. It is better to output nothing as opposed to something that wrong.


Bug: (feature request) mt7921u driver does not support 2 interfaces of AP mode on one adapter
Status: open

Reported by @whitslack

mt7921u driver does not support 2 instances of AP mode whereas this was common on some drivers for older adapters.

Now:

valid interface combinations:

	 * #{ managed, P2P-client } <= 2, #{ AP, P2P-GO } <= 1,
	   total <= 2, #channels <= 2

What we want:

valid interface combinations:

	 * #{ managed, P2P-client } <= 2, #{ AP, P2P-GO } <= 2,
	   total <= 2, #channels <= 2

Bug: connection is dropped and the only way to correct the situation is to reboot (AP mode)
Status: open

Testing to see if SG helps performance:

scatter-gather test with mt7921au based adapter

Issue: connection drops and the only resolution is to reboot the system.

Raspberry Pi 4B
RasPiOS 2023-05-03

I changed the modulate parameter and rebooted between each test so as to alternate on and off.

iperf3 -c 192.168.1.1 -t 300

scatter-gather off (disable_usb_sg=1)

1:
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.00 sec  19.9 GBytes   569 Mbits/sec    4             sender
[  5]   0.00-300.01 sec  19.9 GBytes   569 Mbits/sec                  receiver

2: 
[  5]   0.00-300.00 sec  19.9 GBytes   570 Mbits/sec    5             sender
[  5]   0.00-300.01 sec  19.9 GBytes   570 Mbits/sec                  receiver

3:
[  5]   0.00-300.00 sec  20.0 GBytes   573 Mbits/sec    2             sender
[  5]   0.00-300.01 sec  20.0 GBytes   573 Mbits/sec                  receiver

scatter-gather on (disable_usb_sg=0)

1:
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.00 sec  19.9 GBytes   570 Mbits/sec    1             sender
[  5]   0.00-300.01 sec  19.9 GBytes   570 Mbits/sec                  receiver

2:
[  5]   0.00-300.00 sec  20.0 GBytes   572 Mbits/sec   48             sender
[  5]   0.00-300.01 sec  20.0 GBytes   572 Mbits/sec                  receiver


3.
[  5]   0.00-300.00 sec  19.9 GBytes   571 Mbits/sec    0             sender
[  5]   0.00-300.02 sec  19.9 GBytes   571 Mbits/sec                  receiver

Observation: So much for needing to average the results. I was careful
to check that sg was on or off. I have no explanation for how the results
could be so close. I see no evidence that sg is providing any performance
increase.

Previous to this testing session, I have been able to see the issue of
the connection being dropped and only a reboot will connect the
situation. It happened twice a few days ago while testing with sg on.
There is a history of this with mt7612u adapters. I have yet to duplicate
the issue with sg off.

Conclusion: Further testing on different platforms is needed. I will test
x86_64 next. Given the history of sg causing problems such as connections
dropping that can only be corrected with a reboot, it may be better for the
default to be disable_usb_sg=1 with a follow up to determine what the
problem is.


@deren
Copy link

deren commented Sep 15, 2022

Hi @morrownr

I cannot reproduce the mess system log in in 6.0-rc3. Can you please show me full log & reproduce steps(if any special)?

Thanks,
Deren

@morrownr
Copy link
Owner Author

Hi @deren

I will retest on the original system plus two additional systems and report as soon as I can.

Regards,

Nick

@morrownr
Copy link
Owner Author

Hi @deren

I have numbered the bugs so as to make it easier to reference them. The bug in question is now called Bug 2.

I have withdrawn Bug 2. After additional testing on different hardware, it appears this bug may be unique to that system so I need to back up and see if I can isolate the cause.

Have you been able to duplicate Bug 1?

Regards,

Nick

@deren
Copy link

deren commented Sep 16, 2022

Hi @morrownr

I cannot reproduce Bug2, either. The BT function always working properly, even if plug&play or reload driver several times.

But the log is weird to me, it looks like missing fw file on filesystem. Can you please check this problem related to any specific device?
[ 149.874493] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin failed with error -2

Regards,
Deren

@morrownr
Copy link
Owner Author

Hi @deren

The BT function always working properly, even if plug&play or reload driver several times.

I have a laptop computer that uses a wifi card based on the mt7921 chipset. Bluetooth works well. However, the subject here is about a usb wifi adapter that uses the mt7921au chipset. I have found no evidence that this adapter supports bluetooth. Is the capability turned off in hardware? I don't know but am trying to find out.

But the log is weird to me

What I posted is not information from a single log. The first section shows the log entries when the most up to date BT firmware is installed. The second section shows the log entries when I delete the BT firmware and reboot.

The first section of the log with the firmware installed makes me think the driver is trying to bring BT up but it is unable due to the lack of hardware. Bluetooth support is rare on usb wifi adapters. Could it be that the driver, mt7921u, is making an incorrect assumption that BT hardware is there to use?

My mt7921au based usb wifi adapter is showing no sign of support for BT whether the firmware is install or not. This adapter is a Comfast CF-951AX.

Regards,

Nick

@deren
Copy link

deren commented Sep 17, 2022

Hi @morrownr

What I posted is not information from a single log. The first section shows the log entries when the most up to date BT firmware is installed. The second section shows the log entries when I delete the BT firmware and reboot.

Got it. I did not get the point.

I have found no evidence that this adapter supports bluetooth. Is the capability turned off in hardware?

What I have is CF-953AX and can verify BT function working well in the card. Regarding the CF-951AX, there are some information about BT function. ( hope that is real :) )
https://www.sunsky-online.com/p/EDA003280201A/COMFAST-CF-951AX-1800Mbps-USB-3.0-WiFi6-Wireless-Network-Card-Black-.htm

[ 72.869871] Bluetooth: hci1: Opcode 0x c03 failed: -110
[ 74.882933] Bluetooth: hci1: Failed to read MSFT supported features (-110)
[ 76.896658] Bluetooth: hci1: AOSP get vendor capabilities (-110)

I guess you consider the three lines means the BT function not working properly, right? The log do not show up in my test environment(ubuntu2004+kernel 6.0-rc5 + CF-953AX) and I think this is related to BT protocol usage in your host system. Can you see BT still alive in your system, such as desktop UI? For example, I can see the device is running after CF-953AX plugged.

# hciconfig
hci1: Type: Primary Bus: USB
BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:17035 acl:0 sco:0 events:2758 errors:0
TX bytes:678011 acl:0 sco:0 commands:2756 errors:0

Regards,
Deren

@morrownr morrownr changed the title (Hot) Post Bug Reports for the new mt7921au chipset and mt7921u driver here... (Hot) Post your Bug Reports for the new mt7921au chipset and mt7921u driver here... Sep 19, 2022
@morrownr
Copy link
Owner Author

Hi @deren

I guess you consider the three lines means the BT function not working properly, right?

I consider those 3 lines are possibly going to give a hint as to why BT is not working. And it is not working. I wish I was more familiar with BT but I am not so I am having to go slow with my troubleshooting. I also have a little nano BT adapter with a Braodcome chipset. I plugged it in and BT works with it. Mt test distro is Mint 21 (updated to kernel 6.0 rc3) and a short look at the forums tells me Mint is having problems with BT so I am going to suspend my report pending further investigation. I appreciate your help.

Can you see BT still alive in your system,

Yes. It shows in the gui applet that supports BT. In fact, with the nano adapter plugged in, both show. The difference is that I can pair with other BT devices with the nano adapter but I can't get anything with the Mediatek based adapter. I'll continue trying to determine the problem.

Nick

@morrownr
Copy link
Owner Author

@deren

Question: Since you have a Comfast CF-953AX adapter, my question is have you tested AP mode 5 GHz band DFS channel support?

I bring this up due to the MANY users that make use of AP mode. Many products also include usb adapters and AP mode is sometimes an important part of the product. I am contacted at times to serve in a consulting roll so I see many use cases that would benefit greatly from this support... and the 5 Realtek drivers I have up here all support this and it works well. There is a gap in capability that needs to be closed and it doesn't seem to be working for me.

Thanks,

Nick

@leezu
Copy link

leezu commented Sep 28, 2022

On RasPi4B with Raspbian and kernel 6.0.0-rc7-v8+ (as well as earlier kernels), CF-953AX in AP mode and the latest September 2022 Firmware, I can relatively consistently reproduce firmware hangs by running a speedtest and apt upgrade in parallel on the SC7180 Snapdragon 7c. (Having other devices connected and other traffic patterns sometimes also causes the hang).

After the hang, the AP will recover and the following (starting from 4440.067187) is printed in the kernel log.

[Wed Sep 28 12:48:10 2022] mt7921u 2-1:1.3: WM Firmware Version: ____010000, Build Time: 20220908211021
[Wed Sep 28 12:48:11 2022] mt7921u 2-1:1.3 wlxe0e1a934a6a9: renamed from wlan1
[Wed Sep 28 12:48:12 2022] Bluetooth: hci0: Opcode 0x c03 failed: -110
[Wed Sep 28 12:48:13 2022] IPv6: ADDRCONF(NETDEV_CHANGE): ap0: link becomes ready
[Wed Sep 28 12:48:13 2022] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe0e1a934a6a9: link becomes ready
[Wed Sep 28 14:02:00 2022] mt7921u 2-1:1.3: Message 00020003 (seq 12) timeout
[Wed Sep 28 14:02:00 2022] wlxe0e1a934a6a9: failed to remove key (0, 8c:fd:f0:42:20:cf) from hardware (-110)
[Wed Sep 28 14:02:00 2022] mt7921u 2-1:1.3: timed out waiting for pending tx
[Wed Sep 28 14:02:00 2022] ------------[ cut here ]------------
[Wed Sep 28 14:02:00 2022] WARNING: CPU: 2 PID: 1158 at kernel/kthread.c:659 kthread_park+0xb4/0xd0
[Wed Sep 28 14:02:00 2022] Modules linked in: xt_mark nft_chain_nat ctr aes_arm64 aes_generic ccm xt_MASQUERADE iptable_nat ip6table_nat nf_nat tun mt7921u mt7921_common mt76_connac_lib mt76_usb mt76 mac80211 btusb btrtl btintel btbcm bluetooth ecdh_generic ecc libaes libarc4 sg vc4 snd_soc_hdmi_codec bcm2835_codec(C) drm_display_helper brcmfmac rpivid_hevc(C) cec drm_cma_helper bcm2835_v4l2(C) bcm2835_isp(C) brcmutil v3d drm_kms_helper bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig gpu_sched videobuf2_memops cfg80211 snd_soc_core drm_shmem_helper videobuf2_v4l2 snd_compress videobuf2_common snd_bcm2835(C) snd_pcm_dmaengine videodev rfkill raspberrypi_hwmon snd_pcm vc_sm_cma(C) mc snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops uio_pdrv_genirq nvmem_rmem uio ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
[Wed Sep 28 14:02:00 2022]  nft_compat nf_tables nfnetlink drm fuse drm_panel_orientation_quirks backlight ip_tables x_tables ipv6
[Wed Sep 28 14:02:00 2022] CPU: 2 PID: 1158 Comm: kworker/u8:1 Tainted: G         C         6.0.0-rc7-v8+ #4
[Wed Sep 28 14:02:00 2022] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
[Wed Sep 28 14:02:00 2022] Workqueue: mt76 mt7921_mac_reset_work [mt7921_common]
[Wed Sep 28 14:02:00 2022] pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[Wed Sep 28 14:02:00 2022] pc : kthread_park+0xb4/0xd0
[Wed Sep 28 14:02:00 2022] lr : mt76u_stop_tx+0x278/0x330 [mt76_usb]
[Wed Sep 28 14:02:00 2022] sp : ffffffc00938bc50
[Wed Sep 28 14:02:00 2022] x29: ffffffc00938bc50 x28: 0000000000000000 x27: ffffff8049ee8848
[Wed Sep 28 14:02:00 2022] x26: 0000000000000000 x25: ffffff8049e42280 x24: ffffff8049ee2068
[Wed Sep 28 14:02:00 2022] x23: ffffff8049ee4820 x22: ffffff8049ee6020 x21: ffffff8049ee2048
[Wed Sep 28 14:02:00 2022] x20: ffffff8049368c00 x19: ffffff804c8f0000 x18: 0000000000000000
[Wed Sep 28 14:02:00 2022] x17: 0000000000000001 x16: ffffffdcef6b4e40 x15: 0018a9ea46410578
[Wed Sep 28 14:02:00 2022] x14: 000dd98ec5e42494 x13: 0000000000000213 x12: 00000000fa83b2da
[Wed Sep 28 14:02:00 2022] x11: 0000000000000213 x10: 0000000000001a90 x9 : ffffffdccfd9e8a8
[Wed Sep 28 14:02:00 2022] x8 : ffffff80401ed8f0 x7 : 0000000000000001 x6 : ffffffdcf0b0b0c0
[Wed Sep 28 14:02:00 2022] x5 : ffffffdcf09a9000 x4 : ffffffdcf09a90b0 x3 : 0000000000002800
[Wed Sep 28 14:02:00 2022] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000004
[Wed Sep 28 14:02:00 2022] Call trace:
[Wed Sep 28 14:02:00 2022]  kthread_park+0xb4/0xd0
[Wed Sep 28 14:02:00 2022]  mt76u_stop_tx+0x278/0x330 [mt76_usb]
[Wed Sep 28 14:02:00 2022]  mt7921u_mac_reset+0x88/0x2d8 [mt7921u]
[Wed Sep 28 14:02:00 2022]  mt7921_mac_reset_work+0xac/0x1a0 [mt7921_common]
[Wed Sep 28 14:02:00 2022]  process_one_work+0x1dc/0x450
[Wed Sep 28 14:02:00 2022]  worker_thread+0x154/0x450
[Wed Sep 28 14:02:00 2022]  kthread+0x104/0x110
[Wed Sep 28 14:02:00 2022]  ret_from_fork+0x10/0x20
[Wed Sep 28 14:02:00 2022] ---[ end trace 0000000000000000 ]---
[Wed Sep 28 14:02:00 2022] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20220908210919a

[Wed Sep 28 14:02:00 2022] mt7921u 2-1:1.3: WM Firmware Version: ____010000, Build Time: 20220908211021
[Wed Sep 28 14:02:05 2022] mt7921u 2-1:1.3: Message 00020003 (seq 6) timeout
[Wed Sep 28 14:02:06 2022] mt7921u 2-1:1.3: timed out waiting for pending tx
[Wed Sep 28 14:02:06 2022] mt7921u 2-1:1.3: HW/SW Version: 0x8a108a10, Build Time: 20220908210919a

[Wed Sep 28 14:02:06 2022] mt7921u 2-1:1.3: WM Firmware Version: ____010000, Build Time: 20220908211021

@ghost
Copy link

ghost commented Sep 28, 2022

maybe some issues again with usb scatter gather

@leezu
Copy link

leezu commented Oct 1, 2022

@ayyyuki1 possible. Based on above call trace, mt7921u driver does call a mt76_usb function. I'll try reproducing the issue with /sys/module/mt76_usb/parameters/disable_usb_sg set to Y

@morrownr
Copy link
Owner Author

morrownr commented Oct 2, 2022

Based on above call trace, mt7921u driver does call a mt76_usb function. I'll try reproducing the issue with /sys/module/mt76_usb/parameters/disable_usb_sg set to Y

My opinion is that I would like to see either the default setting for scatter-gather be changed or simple clean the code out of mt76. I have seen the problems that it causes with mt7612u based adapters and I have taken the time to do extensive tests to see if it increases speed in any worthwhile level. My conclusion is that I cannot see any increases in speed. I say dump it from the code.

@bjlockie
Copy link

bjlockie commented Oct 2, 2022

I think the problem with scatter gather was suspected to be a bug in the USB hardware of a Raspberry Pi.

@leezu
Copy link

leezu commented Oct 2, 2022

With /sys/module/mt76_usb/parameters/disable_usb_sg=Y I'm also able to reproduce the hang, though it does appear a little harder to reproduce. Raspberry Pi team has recently made progress on a related USB issue and established that it was due to a VL805 firmware bug. raspberrypi/linux#4844 "VIA in Taiwan have reproduced the issue and are investigating. There's not likely to be another software workaround proposed here." "The fix as recommended by VIA is to disable bursts if this sequence of TRBs can occur." There was speculation if this helps with the Mediatek hangs (raspberrypi/linux#5173 (comment)), but I verified that it does not help. Given the history of RPi4 USB Host controller firmware bugs I've opened raspberrypi/linux#5193. I've also opened raspberrypi/linux#5192 to track that on RPi4, disconnecting one USB device causes failure on other USB devices (ie. disconnecting a mass storage device triggers mt7921au errors).

@bjlockie
Copy link

bjlockie commented Oct 3, 2022

Can the firmware of the VIA chip be upgraded?

@leezu
Copy link

leezu commented Oct 4, 2022

Yes.

% sudo rpi-eeprom-update
[...]
  VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 000138a1
    LATEST: 000138a1

@morrownr
Copy link
Owner Author

morrownr commented Oct 8, 2022

On RasPi4B with Raspbian and kernel 6.0.0-rc7-v8+ (as well as earlier kernels), CF-953AX in AP mode and the latest September 2022 Firmware, I can relatively consistently reproduce firmware hangs by running a speedtest and apt upgrade in parallel on the SC7180 Snapdragon 7c. (Having other devices connected and other traffic patterns sometimes also causes the hang).

@leezu

I'm looking to move this bug report up into message 1 with the other bugs. You mentioned the distro and kernel but did not mention:

  • band/channel ?
  • hostapd ? and hostapd.conf
  • WPA3 ?
  • wpa_supplicant version ?
  • 32 bit ?
  • hostapd.log showing anything ?

@bjlockie
Copy link

bjlockie commented Oct 8, 2022 via email

@morrownr morrownr pinned this issue Oct 9, 2022
@leezu
Copy link

leezu commented Oct 12, 2022

@morrownr @bjlockie

I'm looking to move this bug report up into message 1 with the other bugs. You mentioned the distro and kernel but did not mention:

band/channel: 36
hostapd v2.10 and hostapd.conf
WPA3: wpa_key_mgmt=WPA-PSK
wpa_supplicant version: 2.9
32 bit: running with arm_64bit=1 RPi config but getconf LONG_BIT returns 32.
hostapd.log showing anything: Please see the two journals regarding two separate occurrences attached:
journal-no-backtrace.txt
journal-with-backtrace.txt

I also want to know if is using an extension cable.
And is it using a powered USB hub.
I had to use a powered USB hub for the keyboard/mouse of my hdmi switch.

It uses this extension lead https://smile.amazon.com/gp/product/B082HQXRZ1/ as without extension lead, the CF-953AX covers up the LAN port.

@morrownr
Copy link
Owner Author

@leezu

I added your firmware hanging issue as Bug 6. Please check it to see if I did a good job.

Also, I have been running AP mode 5 GHz over the few days with my RasPi4B. It appears I am seeing the same problem. Every few hours I will lose internet access. It can and usually does recover but it can take a long time. I shut down scatter/gather this morning to see if it helps. We will see.

Can I get you to test 2.4 GHz AP mode? Look at Bug 2. I am reporting that 2.4 GHz AP mode is not working. Would like confirmation.

wpa_supplicant version: 2.9

FYI: I think you need 2.10 for WPA3 support. I have a guide to do the upgrade if you want a copy.

Nick

@morrownr morrownr unpinned this issue Feb 2, 2023
@gifter77
Copy link

gifter77 commented May 8, 2023

Regarding bug 6., if I build a vanilla 6.4.rc linux kernel for my raspberry pi 4, I cannot reproduce the issue anymore.

@morrownr morrownr pinned this issue May 8, 2023
@morrownr
Copy link
Owner Author

morrownr commented May 8, 2023

Hi @gifter77

Copy all. Will update.

@gdluca
Copy link

gdluca commented Sep 12, 2024

@morrownr

it will probably generate useless retrans and it is unlikely to have such a busy environment but:

iperf3 -c $destinationip -P 16 -t 3600 --bidir

does it handle well??

How crowded is your 5Ghz?

This is my situation. I also live near an heliport and can't really use JP DFS channels.

@morrownr
Copy link
Owner Author

@gdluca

iperf3 -c $destinationip -P 16 -t 3600 --bidir

In progress. About one-half of the way complete. I had to have some fun so I ran Ookla from a phone. Given the serious underclock on the RasPi4B and everything that is connected of going, the AP is understandably at max performance conditions. I'm controlling via VNC and the other systems connected to it are still connected. It is stable. The adapter has warmed up a little but nothing to be concerned with. The Edup has vent holes.

How crowded is your 5Ghz?

Not crowded at all at my current location. I live in a residential neighborhood. The homes all brick and not so close to each other so congestion is minimal on all channels. I use US DFS on my main router for 160 MHz channel width just to have something to test with totally clean air but my test AP in this case is using channel 36.

@ascendbeing
Copy link

@morrownr I got 4 of the mt7921u/mt7961 that you recommended (fenvi ax1800 non premium). I would like to try "APuP" with these. See https://eko-one-pl.translate.goog/forum/viewtopic.php?pid=304802&_x_tr_sl=pl&_x_tr_tl=en&_x_tr_hl=pl&_x_tr_pto=wapp#p304802
The requirement to do this allegedly is the card has to support 4-addr and it will do this via AP mode not via WDS. It doesn't have to support mesh nor WDS, just AP and 4 addr. I noticed in the iw phy information, the combinations do mention I can have <= 2 interfaces with up to 1 AP mode and up to 2 managed and up to 2 channels.
In the issue reports about WDS and/or 4addr, I could not determine the basic fact of does this or does this not support 4-addr.
I'm going to try this this weekend. I'm not sure if I should expect success. I've never tried APuP. This would be very useful if it works.

@morrownr
Copy link
Owner Author

@ascendbeing

I could not determine the basic fact of does this or does this not support 4-addr.

I can't say one way or another as I have not tried this. If there is a guide, that leads to the question of what Linux wifi drivers do support it. Let us know what you find out.

@ascendbeing
Copy link

yeah I'll let you know. I don't consider iw's output very helpful on that front. some have made guides, translating the output, but that was just for ht_capab field.
if it doesn't pan out I will try some ngff mediateks: 1x mt7922 1x mt7921, or I'll try some ath9k and ath9k-htc. beyond that I'll have run out of stuff to try APuP w/. if I find something that works, I'll be well positioned to share some pseudo-unique insights here.

@morrownr
Copy link
Owner Author

@ascendbeing

1x mt7922

I have a PCIe card with that chip and a M.2 card with the mt7925 chip so if you want me to try something for you, write down the commands and I'll give 'um a try.

@ascendbeing
Copy link

If you want to post an "iw phy" from the mt7925, that might be useful to icdiff -U0 w/ other cards, once we establish whether 4addr works on mt7921au. rn figuring where my cables went then I'll quickly figure it out.

@morrownr
Copy link
Owner Author

@ascendbeing

FYI: I ran iw list just now on the system that has the mt7925 card and then I was doing some digging. I will send you the link to the reference but it was made clear that all mac80211 compliant drivers that support STA and AP modes will support 4addr.

...

Here is the link:

https://wireless.wiki.kernel.org/en/users/documentation/iw#using_4-address_for_ap_and_client_mode

So, you don't check 4addr with iw list or iw phy while looking for 4addr. You look for the supported interface mode:

The mt7921, mt7922 and mt7925 all report the following:

Supported interface modes:
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * P2P-client
		 * P2P-GO

Therefore 4addr should be supported for managed and AP modes.

@ascendbeing
Copy link

@morrownr is that an iron clad rule though? there are some chips out there which are barely on life support. for example, mwl8k.
What I can share about mwl8k is 1. you can't use PMF/MFP. 2. you can't use wpa3 except maybe with sae_require_mfp=0.
mwl8k is a pre-mwlwifi driver for ea3500/ea4500/e4200v2/etc. It's quite good for gn operation (hits 170-200+Mbps regularly, but with a fair few retries--im currently trying it as client to mt7961, to see if it has less retries, being bottlenecked to 2x2 operation, running n on ax AP).
There are similar chips I'd be surprised about whether they have 4addr too. brcmsmac, for one. The RT-N16, which for openwrt is officially supported by b43, can alternatively run brcmsmac, which is broken in similar ways as the mwl8k (no MFP). but brcmsmac is broken on openwrt snapshot rn, at least on n16.

I tried pi3b with Belkin f9k110x's. ended up not being able to login to the Belkin (it's soft bricked, i reflashed it, it's fine). I will pick back up with an e4200v1 w/ the pi3b in my APuP journey after I flash an e2000 to take the place of the 4200v1 so I wont have a tangible update as soon as i wanted.

@morrownr
Copy link
Owner Author

@ascendbeing

is that an iron clad rule though?

If you are asking if all drivers that are in the kernel support this rule, then my answer is that I doubt it.

brcmsmac, for one

When it comes to Linux, I cannot recommend anything Broadcom as their Linux support is not good. Yes, I have a couple of RasPi's but I turn the Broadcom wifi off and use adapters.

There are similar chips I'd be surprised about whether they have 4addr too.

The document indicates that is what is intended, not to reflect how it is in all cases... or at least that is my take. Given that the mt76 drivers are as modern and full featured as it gets for Linux wifi, my opinion is that if any Linux drivers support 4addr, then the mt76 drivers would be likely candidates.

@morrownr
Copy link
Owner Author

@whitslack @gdluca

I have no idea if USB port settings or type of port could be related to the things you gents have been seeing but here is an interesting post on a Debian forum:

https://forums.debian.net/viewtopic.php?t=159402

I regularly give advice for users with otherwise unexplainable problems to try a different USB port or check the USB settings in the BIOS. I am aware that there can be a wide array of usb related settings in various BIOS's that are out there and I am aware that USB3 gen 2 can be problematic.

Separate subject: After many days of using my mt7921au based adapter (Edup) in AP mode in my Pi4B which is seriously underclocked, I have not seen a single problem. The search continues.

@gdluca
Copy link

gdluca commented Sep 17, 2024

@morrownr
thank you for the tests. I think it is enough for me. How much for your rpi4b? lol
I also still think somehow the USB root hub is not playing nice with my mt7921au (no proof..) .
I have been using the adapter on the desktop for weeks and no crash there(also on 6.10.10 now).

@whitslack
Copy link

An interesting data point in this ongoing saga… I installed iperf3 on my desktop (wired gig-E) and laptop (mt7922) and ran a 600-second test of the desktop uploading to the laptop via my router/AP (mt7921u). Averaged 148 Mbit/s and did not hang! (I know the throughput doesn't sound so great, but remember, my router has only USB 2.) And I even performed this test run after having recovered the router from a previous hang without rebooting it.

To be sure, I then ran a bitrate-unlimited UDP iperf3 test and hit 876 Mbit/s from the client (desktop), essentially maxing out its gigabit wired Ethernet link, and received 161 Mbit/s (82% packet loss) on the server (laptop), and still the mt7921u in the AP did not hang.

So it would seem that my mt7921u AP is perfectly happy to blast packets at max line rate to an mt7922 client, but even a modestly quick download (such as streaming a YouTube video) to my Qualcomm Snapdragon 835-based OnePlus 5T smartphone is often enough to hang the AP, and a max-rate download (such as an Ookla speed test) to it will hang it every time.

I might see if I can compile iperf3 for ARM Android and run it on my phone to see if I can reproduce the hangs without involving Ookla. Then maybe I'll put iperf3 on my router/AP box and see if I can still trigger the hangs without involving the Linux software Ethernet bridge. Maybe once this all has been distilled down to a very minimal reproducer, we can hand it to MediaTek, and maybe then they could finally crack this nut.

@morrownr
Copy link
Owner Author

@whitslack

Maybe once this all has been distilled down to a very minimal reproducer, we can hand it to MediaTek, and maybe then they could finally crack this nut.

Sounds like a plan. I'm going to keep going with testing on my Pi4B for now but within a few days I can probably setup my mini-pc that has totally different hw. The answer is there, we just need to find it.

@gdluca
Copy link

gdluca commented Sep 19, 2024

An interesting data point in this ongoing saga… I installed iperf3 on my desktop (wired gig-E) and laptop (mt7922) and ran a 600-second test of the desktop uploading to the laptop via my router/AP (mt7921u). Averaged 148 Mbit/s and did not hang! (I know the throughput doesn't sound so great, but remember, my router has only USB 2.) And I even performed this test run after having recovered the router from a previous hang without rebooting it.

To be sure, I then ran a bitrate-unlimited UDP iperf3 test and hit 876 Mbit/s from the client (desktop), essentially maxing out its gigabit wired Ethernet link, and received 161 Mbit/s (82% packet loss) on the server (laptop), and still the mt7921u in the AP did not hang.

So it would seem that my mt7921u AP is perfectly happy to blast packets at max line rate to an mt7922 client, but even a modestly quick download (such as streaming a YouTube video) to my Qualcomm Snapdragon 835-based OnePlus 5T smartphone is often enough to hang the AP, and a max-rate download (such as an Ookla speed test) to it will hang it every time.

I might see if I can compile iperf3 for ARM Android and run it on my phone to see if I can reproduce the hangs without involving Ookla. Then maybe I'll put iperf3 on my router/AP box and see if I can still trigger the hangs without involving the Linux software Ethernet bridge. Maybe once this all has been distilled down to a very minimal reproducer, we can hand it to MediaTek, and maybe then they could finally crack this nut.

@whitslack
About iperf3 on Android, you can use termux and install it via pkg install iperf3

@ritech
Copy link

ritech commented Sep 29, 2024

mt7921 on allwinner can't work

I used several development boards including Allwinner h3 and h5, and the results were the same. The kernel is 6.6.52

[ 247.918935] page_pool_create() gave up with errno -22
[ 247.924180] mt7921u: probe of 5-1:1.0 failed with error -22

@morrownr
Copy link
Owner Author

Hi @ritech

mt7921 on allwinner can't work

What distro and firmware was in use?

@whitslack
Copy link

[ 247.918935] page_pool_create() gave up with errno -22
[ 247.924180] mt7921u: probe of 5-1:1.0 failed with error -22

@ritech: I suspect something may be funky with your kernel configuration or build. Errno 22 is EINVAL (invalid argument). There aren't too many code paths through which page_pool_create() could return -EINVAL. Notably, it's not the same as -ENOMEM or -E2BIG. Are you trying to use a kernel module for the mt7921u driver? If so, was it built at the same time as the kernel you're running?

@ritech
Copy link

ritech commented Sep 30, 2024

[ 247.918935] page_pool_create() gave up with errno -22
[ 247.924180] mt7921u: probe of 5-1:1.0 failed with error -22

@ritech: I suspect something may be funky with your kernel configuration or build. Errno 22 is EINVAL (invalid argument). There aren't too many code paths through which page_pool_create() could return -EINVAL. Notably, it's not the same as -ENOMEM or -E2BIG. Are you trying to use a kernel module for the mt7921u driver? If so, was it built at the same time as the kernel you're running?

same error openwrt/mt76#898
I tried allwinner processors, but they all failed to work.
The same compilation method works correctly on rockchip

@hyprmann
Copy link

hyprmann commented Oct 20, 2024

Hi @morrownr.

How do I post a feedback? Recently, I saw EDUP AX1672 on your recommended list. It says monitor mode seems to be broken.

So I did bought that adapter. I tested the monitor mode, it worked in my case, in a VM (qemu).

Screenshot_20241020_093511

Screenshot_20241020_095900

@morrownr
Copy link
Owner Author

morrownr commented Oct 20, 2024

Hi @hyprmann

How do I post a feedback?

Right here or you can start a new issue.

Recently, I saw EDUP AX1672 on your recommended list. It says monitor mode seems to be broken.

Oh no. My wording must be poor. That adapter does monitor mode wonderfully. All of the adapters in the mt7921au section do great with monitor mode as do the adapters in the mt7612u and mt7610u sections. I recently added another document under the Plug and Play List to specifically point Kali users and other monitor mode users to specific adapters.

What I was trying to say is that the mt7921u driver currently seems to have a bug in active monitor mode which is specialized feature within monitor mode. Could you point me to where you were reading so I can try to clean up my mess and make this clear?

While I have you. Let me recommend that you stop using the iwconfig command as it has long been depreciated. Use iw instead as it is the modern replacement.

Thanks for the info.

@hyprmann
Copy link

I see. Now you've mentioned it that Active is a feature within monitor. I thought it;s the same as regular monitor mode. Apologies, my bad. Thanks for the recommendation, I'll check iw out. Thanks again, have a nice day!

@Abhishekghosh1998
Copy link

[  167.809230] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  167.857165] r8152 3-2.1.2:1.0 enxa0cec8c9a123: renamed from eth0
[  168.073370] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  169.714608] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  172.385911] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  172.952189] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  172.970136] wlxe84e06ac95bf: authenticated
[  172.972556] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  172.986715] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  173.025476] wlxe84e06ac95bf: associated
[  173.025828] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  310.848366] audit: type=1107 audit(1731334688.003:58): pid=502 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.132" pid=1986 label="snap.firefox.firefox" peer_pid=5332 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[  328.021880] usb 3-2.1.3: USB disconnect, device number 13
[  328.056594] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  329.824564] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  330.168557] usb 3-2.1.3: new high-speed USB device number 14 using xhci_hcd
[  330.324119] usb 3-2.1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  330.324131] usb 3-2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  330.324135] usb 3-2.1.3: Product: Wireless_Device
[  330.324138] usb 3-2.1.3: Manufacturer: MediaTek Inc.
[  330.324140] usb 3-2.1.3: SerialNumber: 000000000
[  330.462062] usb 3-2.1.3: reset high-speed USB device number 14 using xhci_hcd
[  330.665161] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  330.933309] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  332.579019] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  335.231207] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  335.764480] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  335.787656] wlxe84e06ac95bf: authenticated
[  335.812563] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  335.836307] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  335.874127] wlxe84e06ac95bf: associated
[  335.944101] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  336.768476] mt7921u 3-2.1.3:1.0: tx urb failed: -71
[  336.789714] usb 3-2.1.3: USB disconnect, device number 14
[  336.804569] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  339.104545] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  339.456548] usb 3-2.1.3: new high-speed USB device number 15 using xhci_hcd
[  339.624785] usb 3-2.1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  339.624795] usb 3-2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  339.624798] usb 3-2.1.3: Product: Wireless_Device
[  339.624799] usb 3-2.1.3: Manufacturer: MediaTek Inc.
[  339.624800] usb 3-2.1.3: SerialNumber: 000000000
[  339.765964] usb 3-2.1.3: reset high-speed USB device number 15 using xhci_hcd
[  339.965651] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  340.230449] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  341.879653] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  347.307957] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  347.842723] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  347.853980] wlxe84e06ac95bf: authenticated
[  347.868564] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  347.884170] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  347.921534] wlxe84e06ac95bf: associated
[  347.931205] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  348.246736] mt7921u 3-2.1.3:1.0: tx urb failed: -71
[  348.277123] usb 3-2.1.3: USB disconnect, device number 15
[  348.292579] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  350.076552] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  350.424555] usb 3-2.1.3: new high-speed USB device number 16 using xhci_hcd
[  350.580209] usb 3-2.1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  350.580216] usb 3-2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  350.580218] usb 3-2.1.3: Product: Wireless_Device
[  350.580219] usb 3-2.1.3: Manufacturer: MediaTek Inc.
[  350.580221] usb 3-2.1.3: SerialNumber: 000000000
[  350.725963] usb 3-2.1.3: reset high-speed USB device number 16 using xhci_hcd
[  350.937279] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  351.204913] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  352.849153] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  355.497817] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  356.029639] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  356.040273] wlxe84e06ac95bf: authenticated
[  356.076547] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  356.098443] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  356.139382] wlxe84e06ac95bf: associated
[  356.140020] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  356.597093] usb 3-2.1.3: USB disconnect, device number 16
[  359.828549] mt7921u 3-2.1.3:1.0: Message 00020006 (seq 9) timeout
[  359.862165] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  360.040547] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  360.040593] ------------[ cut here ]------------
[  360.040596] WARNING: CPU: 3 PID: 43 at kernel/kthread.c:672 kthread_park+0x94/0xb0
[  360.040604] Modules linked in: ntfs3 ccm mt7921u mt7921_common mt76_connac_lib nf_tables mt76_usb nfnetlink mt76 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr snd_hda_core mei_hdcp mei_pxp snd_hwdep intel_rapl_common snd_pcm x86_pkg_temp_thermal intel_powerclamp kvm_intel snd_seq_midi mac80211 snd_seq_midi_event kvm snd_rawmidi irqbypass rapl snd_seq intel_cstate cfg80211 snd_seq_device libarc4 snd_timer input_leds serio_raw at24 snd mei_me soundcore mei mac_hid binfmt_misc sch_fq_codel hwmon_vid coretemp msr videodev mc parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 r8153_ecm cdc_ether usbnet btrfs blake2b_generic xor raid6_pq libcrc32c r8152 mii uas usb_storage dm_mirror dm_region_hash dm_log i915 nouveau mxm_wmi drm_buddy i2c_algo_bit drm_ttm_helper ttm drm_display_helper gpio_ich cec crct10dif_pclmul crc32_pclmul rc_core polyval_clmulni polyval_generic drm_kms_helper ghash_clmulni_intel
[  360.040686]  cryptd sha256_ssse3 sha1_ssse3 drm ahci xhci_pci video i2c_i801 psmouse lpc_ich i2c_smbus libahci xhci_pci_renesas e1000e wmi hid_generic usbhid hid
[  360.040703] CPU: 3 PID: 43 Comm: kworker/u8:2 Not tainted 6.5.0-28-generic #29~22.04.1-Ubuntu
[  360.040707] Hardware name:  /DH67BL, BIOS BLH6710H.86A.0146.2011.1222.1415 12/22/2011
[  360.040709] Workqueue: mt76 mt7921_mac_reset_work [mt7921_common]
[  360.040722] RIP: 0010:kthread_park+0x94/0xb0
[  360.040726] Code: 31 f6 31 ff c3 cc cc cc cc 0f 0b 4c 8b a3 80 0a 00 00 a8 04 74 a4 0f 0b b8 da ff ff ff 5b 41 5c 5d 31 f6 31 ff c3 cc cc cc cc <0f> 0b b8 f0 ff ff ff eb c9 0f 0b eb c3 66 66 2e 0f 1f 84 00 00 00
[  360.040729] RSP: 0018:ffffbb040018fd38 EFLAGS: 00010202
[  360.040732] RAX: 0000000000000004 RBX: ffff983f52e53300 RCX: 0000000000000100
[  360.040735] RDX: 0000000000000000 RSI: 0000000000000003 RDI: ffff983f52e53300
[  360.040737] RBP: ffffbb040018fd48 R08: 0000000000000000 R09: 0000000000000000
[  360.040739] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9840b2815080
[  360.040740] R13: 0000000000000000 R14: 0000000000000100 R15: ffff983f4b50f6a8
[  360.040743] FS:  0000000000000000(0000) GS:ffff98464f380000(0000) knlGS:0000000000000000
[  360.040745] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  360.040747] CR2: 000036d40066f000 CR3: 00000001094e0004 CR4: 00000000001706e0
[  360.040749] Call Trace:
[  360.040752]  <TASK>
[  360.040755]  ? show_regs+0x6d/0x80
[  360.040761]  ? __warn+0x89/0x160
[  360.040765]  ? kthread_park+0x94/0xb0
[  360.040769]  ? report_bug+0x17e/0x1b0
[  360.040773]  ? handle_bug+0x46/0x90
[  360.040776]  ? exc_invalid_op+0x18/0x80
[  360.040778]  ? asm_exc_invalid_op+0x1b/0x20
[  360.040784]  ? kthread_park+0x94/0xb0
[  360.040789]  mt76u_stop_tx+0x21c/0x330 [mt76_usb]
[  360.040799]  ? __pfx_autoremove_wake_function+0x10/0x10
[  360.040805]  mt7921u_mac_reset+0x6e/0x1b0 [mt7921u]
[  360.040811]  mt7921_mac_reset_work+0x9d/0x190 [mt7921_common]
[  360.040823]  process_one_work+0x240/0x450
[  360.040827]  worker_thread+0x50/0x3f0
[  360.040831]  ? __pfx_worker_thread+0x10/0x10
[  360.040835]  kthread+0xf2/0x120
[  360.040839]  ? __pfx_kthread+0x10/0x10
[  360.040844]  ret_from_fork+0x47/0x70
[  360.040849]  ? __pfx_kthread+0x10/0x10
[  360.040853]  ret_from_fork_asm+0x1b/0x30
[  360.040858]  </TASK>
[  360.040859] ---[ end trace 0000000000000000 ]---
[  360.041490] mt7921u 3-2.1.3:1.0: chip reset failed
[  360.569187] wlxe84e06ac95bf: Driver requested disconnection from AP 00:00:00:00:00:00
[  360.800551] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  361.152554] usb 3-2.1.3: new high-speed USB device number 17 using xhci_hcd
[  361.308127] usb 3-2.1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  361.308134] usb 3-2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  361.308136] usb 3-2.1.3: Product: Wireless_Device
[  361.308137] usb 3-2.1.3: Manufacturer: MediaTek Inc.
[  361.308138] usb 3-2.1.3: SerialNumber: 000000000
[  361.453898] usb 3-2.1.3: reset high-speed USB device number 17 using xhci_hcd
[  361.656779] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  361.921996] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  363.573684] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  366.198171] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  366.726507] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  366.739212] wlxe84e06ac95bf: authenticated
[  366.772550] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  366.790845] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  366.831687] wlxe84e06ac95bf: associated
[  366.869641] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  372.564826] usb 3-2.1.3: USB disconnect, device number 17
[  372.600569] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  374.868552] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  375.216558] usb 3-2.1.3: new high-speed USB device number 18 using xhci_hcd
[  375.375990] usb 3-2.1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  375.375998] usb 3-2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  375.376001] usb 3-2.1.3: Product: Wireless_Device
[  375.376003] usb 3-2.1.3: Manufacturer: MediaTek Inc.
[  375.376006] usb 3-2.1.3: SerialNumber: 000000000
[  375.518041] usb 3-2.1.3: reset high-speed USB device number 18 using xhci_hcd
[  375.723477] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  375.995281] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  377.653588] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  380.305075] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  380.837657] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  380.853464] wlxe84e06ac95bf: authenticated
[  380.888562] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  380.902967] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  380.945099] wlxe84e06ac95bf: associated
[  381.001316] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  382.004867] usb 3-2.1.3: USB disconnect, device number 18
[  382.028563] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  383.792560] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx
[  384.132559] usb 3-2.1.3: new high-speed USB device number 19 using xhci_hcd
[  384.284082] usb 3-2.1.3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  384.284091] usb 3-2.1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  384.284093] usb 3-2.1.3: Product: Wireless_Device
[  384.284096] usb 3-2.1.3: Manufacturer: MediaTek Inc.
[  384.284098] usb 3-2.1.3: SerialNumber: 000000000
[  384.433278] usb 3-2.1.3: reset high-speed USB device number 19 using xhci_hcd
[  384.647035] mt7921u 3-2.1.3:1.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a

[  384.915910] mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959
[  386.554035] mt7921u 3-2.1.3:1.0 wlxe84e06ac95bf: renamed from wlan0
[  389.216416] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:a0
[  389.786304] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:a0 (try 1/3)
[  389.799358] wlxe84e06ac95bf: authenticated
[  389.804557] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:a0 (try 1/3)
[  389.817792] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:a0 (capab=0x1411 status=0 aid=4)
[  389.856314] wlxe84e06ac95bf: associated
[  389.910042] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:a0
[  390.189705] mt7921u 3-2.1.3:1.0: tx urb failed: -71
[  390.196625] usb 3-2.1.3: USB disconnect, device number 19
[  390.220567] wlxe84e06ac95bf: failed to set key (0, 88:b1:e1:ab:f7:a0) to hardware (-19)
[  390.220869] wlxe84e06ac95bf: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-19)
[  390.225109] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
[  391.984553] mt7921u 3-2.1.3:1.0: timed out waiting for pending tx

@morrownr, hello there. I got hold of a edup AX3000. But the usb device keep disconnecting. Any suggestion on what might be going wrong?

@morrownr
Copy link
Owner Author

Hi @Abhishekghosh1998

Any suggestion on what might be going wrong?

It could be a lot of things. Answer some questions:

What distro and version are you running on the system with the Edup adapter? Also, kernel version:

$ uname -r

You are running the Edup in managed mode, correct?

What computer hardware are you using with the Edup adapter?

Very often, problems can be related to the AP/wifi router. Some details about the AP could help.

USB ports can be a problem:

#508

You firmware is dated:

mt7921u 3-2.1.3:1.0: WM Firmware Version: ____010000, Build Time: 20231109190959

You can see how to update it ...

https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md

@Abhishekghosh1998
Copy link

Abhishekghosh1998 commented Nov 11, 2024

@morrownr I am using :

  1. distro: Lubuntu 22.04.5 LTS x86_64
  2. Kernel: 6.5.0-28-generic
  3. CPU: Intel i3-3220 (4) @ 3.300GHz on Intel® Desktop Board DH67BL

yes I am using it in manager mode:

$ iwconfig
lo        no wireless extensions.

eno1      no wireless extensions.

enx26e2b61a2832  no wireless extensions.

wlxe84e06ac95bf  IEEE 802.11  ESSID:"iiscwlan"  
         Mode:Managed  Frequency:2.452 GHz  Access Point: 88:B1:E1:AB:F7:90   
         Bit Rate=130 Mb/s   Tx-Power=3 dBm   
         Retry short limit:7   RTS thr:off   Fragment thr:off
         Power Management:on
         Link Quality=53/70  Signal level=-57 dBm  
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Very often, problems can be related to the AP/wifi router. Some details about the AP could help.

I have been using another 150 Mbps 2.4GHz wifi adaptor based through the rtl8xxxu in kernel driver and that works flawlessly.


EDIT: After updating the firmware:

[  129.807613] mt7921u 2-1.6:1.0: WM Firmware Version: ____010000, Build Time: 20240826151030
[  131.445370] mt7921u 2-1.6:1.0 wlxe84e06ac95bf: renamed from wlan0
[  132.201349] usb 2-1.6: USB disconnect, device number 28
[  134.548529] mt7921u 2-1.6:1.0: Message 00004eed (seq 11) timeout
[  134.550274] mt7921u 2-1.6:1.0: chip reset failed
[  167.240523] usb 2-1.6: new high-speed USB device number 29 using ehci-pci
[  167.351673] usb 2-1.6: New USB device found, idVendor=2109, idProduct=2817, bcdDevice= 3.c4
[  167.351684] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  167.351687] usb 2-1.6: Product: USB2.0 Hub             
[  167.351690] usb 2-1.6: Manufacturer: VIA Labs, Inc.         
[  167.352348] hub 2-1.6:1.0: USB hub found
[  167.352623] hub 2-1.6:1.0: 4 ports detected
[  168.700521] usb 2-1.6.1: new high-speed USB device number 30 using ehci-pci
[  168.859414] usb 2-1.6.1: New USB device found, idVendor=2109, idProduct=2817, bcdDevice= 3.c4
[  168.859424] usb 2-1.6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  168.859428] usb 2-1.6.1: Product: USB2.0 Hub             
[  168.859430] usb 2-1.6.1: Manufacturer: VIA Labs, Inc.         
[  168.859970] hub 2-1.6.1:1.0: USB hub found
[  168.860249] hub 2-1.6.1:1.0: 4 ports detected
[  169.428520] usb 2-1.6.3: new high-speed USB device number 31 using ehci-pci
[  169.587916] usb 2-1.6.3: New USB device found, idVendor=058f, idProduct=8468, bcdDevice= 1.00
[  169.587926] usb 2-1.6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  169.587930] usb 2-1.6.3: Product: Mass Storage Device
[  169.587933] usb 2-1.6.3: Manufacturer: Generic
[  169.587935] usb 2-1.6.3: SerialNumber: 158F84688461
[  169.716536] usb 2-1.6.4: new full-speed USB device number 32 using ehci-pci
[  169.886159] usb 2-1.6.4: not running at top speed; connect to a high speed hub
[  169.890241] usb 2-1.6.4: New USB device found, idVendor=2109, idProduct=0103, bcdDevice=10.03
[  169.890251] usb 2-1.6.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  169.890255] usb 2-1.6.4: Product: USB-C PD3.0 Device
[  169.890257] usb 2-1.6.4: Manufacturer: VLI Inc.
[  169.890260] usb 2-1.6.4: SerialNumber: 0000000000000001
[  169.916587] usb-storage 2-1.6.3:1.0: USB Mass Storage device detected
[  169.916766] scsi host6: usb-storage 2-1.6.3:1.0
[  169.916882] usbcore: registered new interface driver usb-storage
[  169.919188] usbcore: registered new interface driver uas
[  170.012524] usb 2-1.6.1.2: new high-speed USB device number 33 using ehci-pci
[  170.170363] usb 2-1.6.1.2: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[  170.170373] usb 2-1.6.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[  170.170376] usb 2-1.6.1.2: Product: USB 10/100/1000 LAN
[  170.170379] usb 2-1.6.1.2: Manufacturer: Realtek
[  170.170382] usb 2-1.6.1.2: SerialNumber: 000000
[  170.211199] usbcore: registered new device driver r8152-cfgselector
[  170.348573] r8152-cfgselector 2-1.6.1.2: reset high-speed USB device number 33 using ehci-pci
[  170.544084] r8152 2-1.6.1.2:1.0: load rtl8153a-4 v2 02/07/20 successfully
[  170.573891] r8152 2-1.6.1.2:1.0 eth0: v1.12.13
[  170.573946] usbcore: registered new interface driver r8152
[  170.581504] usbcore: registered new interface driver cdc_ether
[  170.583859] usbcore: registered new interface driver r8153_ecm
[  170.643724] r8152 2-1.6.1.2:1.0 enxa0cec8c9a123: renamed from eth0
[  170.934564] scsi 6:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 6
[  170.936114] scsi 6:0:0:1: Direct-Access     Generic- Micro SD/M2      1.08 PQ: 0 ANSI: 6
[  170.936616] sd 6:0:0:0: Attached scsi generic sg1 type 0
[  170.937127] sd 6:0:0:1: Attached scsi generic sg2 type 0
[  170.937994] sd 6:0:0:0: [sdb] Media removed, stopped polling
[  170.938586] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[  170.939370] sd 6:0:0:1: [sdc] Media removed, stopped polling
[  170.940253] sd 6:0:0:1: [sdc] Attached SCSI removable disk
[  172.156518] usb 2-1.6.2: new high-speed USB device number 34 using ehci-pci
[  172.314613] usb 2-1.6.2: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  172.314623] usb 2-1.6.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  172.314627] usb 2-1.6.2: Product: Wireless_Device
[  172.314630] usb 2-1.6.2: Manufacturer: MediaTek Inc.
[  172.314632] usb 2-1.6.2: SerialNumber: 000000000
[  172.456568] usb 2-1.6.2: reset high-speed USB device number 34 using ehci-pci
[  172.645026] mt7921u 2-1.6.2:1.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a

[  172.913789] mt7921u 2-1.6.2:1.0: WM Firmware Version: ____010000, Build Time: 20240826151030
[  174.548245] mt7921u 2-1.6.2:1.0 wlxe84e06ac95bf: renamed from wlan0
[  177.374144] wlxe84e06ac95bf: authenticate with 88:b1:e1:ab:f7:90
[  177.374157] wlxe84e06ac95bf: No basic rates, using min rate instead
[  177.491496] wlxe84e06ac95bf: send auth to 88:b1:e1:ab:f7:90 (try 1/3)
[  177.494503] wlxe84e06ac95bf: authenticated
[  177.508519] wlxe84e06ac95bf: associate with 88:b1:e1:ab:f7:90 (try 1/3)
[  177.518696] wlxe84e06ac95bf: RX AssocResp from 88:b1:e1:ab:f7:90 (capab=0x1431 status=0 aid=1)
[  177.518716] wlxe84e06ac95bf: No basic rates, using min rate instead
[  177.535731] wlxe84e06ac95bf: associated
[  177.570346] wlxe84e06ac95bf: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:b1:e1:ab:f7:90
[  229.874973] kauditd_printk_skb: 41 callbacks suppressed
[  229.874977] audit: type=1400 audit(1731342614.028:53): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2051 comm="snap-confine" capability=12  capname="net_admin"
[  229.874986] audit: type=1400 audit(1731342614.028:54): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2051 comm="snap-confine" capability=38  capname="perfmon"
[  230.031865] audit: type=1400 audit(1731342614.184:55): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/usr/local/share/" pid=2079 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  232.236009] audit: type=1107 audit(1731342616.388:56): pid=495 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.79" pid=2051 label="snap.firefox.firefox" peer_pid=2161 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[  232.244348] audit: type=1107 audit(1731342616.396:57): pid=495 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.79" pid=2051 label="snap.firefox.firefox" peer_pid=2161 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[  279.528609] mt7921u 2-1.6.2:1.0: tx urb failed: -71
[  279.780178] mt7921u 2-1.6.2:1.0: vendor request req:63 off:d02c failed:-71
[  279.864464] mt7921u 2-1.6.2:1.0: tx urb failed: -71
[  279.900503] mt7921u 2-1.6.2:1.0: vendor request req:63 off:d054 failed:-71
[  279.967898] usb 2-1.6.2: USB disconnect, device number 34
[  279.984534] wlxe84e06ac95bf: deauthenticating from 88:b1:e1:ab:f7:90 by local choice (Reason: 3=DEAUTH_LEAVING)
[  281.769124] mt7921u 2-1.6.2:1.0: timed out waiting for pending tx
[  282.085745] usb 2-1.6.2: new high-speed USB device number 35 using ehci-pci
[  282.242701] usb 2-1.6.2: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[  282.242713] usb 2-1.6.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  282.242717] usb 2-1.6.2: Product: Wireless_Device
[  282.242720] usb 2-1.6.2: Manufacturer: MediaTek Inc.
[  282.242722] usb 2-1.6.2: SerialNumber: 000000000
[  282.388579] usb 2-1.6.2: reset high-speed USB device number 35 using ehci-pci
[  282.574751] mt7921u 2-1.6.2:1.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a

[  282.843150] mt7921u 2-1.6.2:1.0: WM Firmware Version: ____010000, Build Time: 20240826151030
[  284.482500] mt7921u 2-1.6.2:1.0 wlxe84e06ac95bf: renamed from wlan0

I still get the same issue.

@morrownr can you recommend some good wifi6 pcie cards?

@morrownr
Copy link
Owner Author

Is the HWE kernel for kernel 6.8 available to you yet? If so, it might be a good upgrade.

If the new kernel doesn't help...

I'll seen similar problems in 2 situations:

  • usb port problems. This could be anything from a worn port to bios settings that are not working well with the adapter. Try other ports.

  • not enough power available via the usb port. This could be caused by too many high powered devices pulling power.

can you recommend some good wifi6 pcie cards?

Understand that this site is about USB and that is where my experience is so recommending specific cards is not something I am good at. With that said, I have one PCIe card and one M.2 card:

The M.2 card uses a mt7925 chip which is WiFi 7. The driver has been in the kernel since 6.7. It performs very well.

The PCIe card uses a mt7922 chip which is WiFi 6e with 160 MHz channel width capability. It can do over 1 Gbps easily with a WiFi 6 AP/router as can the M.2 card above. You should be able to get a PCIe card with a mt7925 chip these days. It kinda depends on what you want to spend and what you want to do with it.

@ascendbeing
Copy link

ascendbeing commented Nov 24, 2024

@morrownr Cause I left you hanging going to give a brief update. I got some of the Linksys Mx4300s when woot was selling their stock of them in drips. So I didn't bother to try MT7921AU WDS configuration.

I forgot where exactly I read it, but allegedly APUP isn't as promising as one would expect. according to some people who have tried it, it can work (idk which device they used--probably not mt7921u), but the delivered bandwidth was LESS THAN with standard WDS. I don't recall if they compared speeds for apup vs mesh, but apup vs wds, wds was according to these 1-2 people (a statistically significant anecdote this isn't) the clear winner. The difference in bandwidth was fairly big, iirc

I'm still learning how to leverage the MX4300. I need to learn how to do dynamic link aggregation with 1x wan and 1x lan to both ports of my gateway device. Until I do that, I can't achieve full bandwidth. Maybe more straightforward to do on a ddwrt box? I have read some, to that effect.

Going past that I want to learn the best ways to setup 802.11s or any better form of mesh topology be it software based (batman or oslr etc) or standard 802.11s. Right now I'm using normal WDS to link some of these. The speeds are better then I was getting with ea3500 for linking buildings, and there's no longer packet loss. The packet loss element may be due to previous AP not supporting LDPC over 2.4. So the 2x2 with LDPC ax setup is running better than the 3x3 n without it probably not shocking.

@morrownr
Copy link
Owner Author

@ascendbeing

I got some of the Linksys Mx4300s...

I picked a MX4300 up also. I think it was for 20 usd and put it aside until such time as OpenWRT support is in place. It might be good for testing or as a backup. Do we have support yet along with instructions?

Going past that I want to learn the best ways to setup 802.11s or any better form of mesh topology...

I have never spent any serious time with mesh because I have really never needed it... or at least I have not thought I needed it. It would be good to get my MX4300 out of the box sometime soon and give it a ride. You are welcome start a new issue to discuss installing OpenWRT on the Linksys MX4300 if you want. I am aware of the Issue in the OpenWRT Dev forum but it wanders all over the place and I seem to stay busy on other things. It would be good to have someone to talk to about setting up the MX4300.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests