Open morrownr opened 6 months ago
I found a few on aliexpress and have one coming to play with.
Hi @ilikenwf
I found a few on aliexpress and have one coming to play with.
I am looking forward to your report. None of us out here in the real world know what kind of shape the mt7925 driver is in so any word would be appreciated.
Thanks
I'm just taking a $30 risk because my QCNFA765 keeps having persistent bugs even despite the fixes and I'm kinda tired of it...I'll take dysfunctional wifi 7 with functional 6E over dysfunctional 6E...
...and I'm sure once this chip is perfected the price will 2x-4x.
FYI: A user report indicates the mt7925 driver does not support the mt7927 chip that you may see. It would be wise to get cards with the mt7925 chip and not the mt7927 until we can sort this out.
If that's the case I can attempt to help sort it or otherwise wait til it is - the linux wireless wiki suggests this chip is supported since kernel 6.7 though? I run Arch...so that's not an issue.
Come to think of it I'm not sure if this really counts as USB or not unless it's using the USB (saying bus here after feels redundant) through the E key slot on my board.
Here is the one I have coming:
https://www.aliexpress.us/item/3256806768193339.html
Appears to be the 7925 so I spoke too soon. Haven't had my coffee yet.
Haven't had my coffee yet.
I am working on my coffee. This is a coffee kind of day.
I am finding more info...see next msg.
MT7925
Wi-Fi 7, WPA3, 2.4/5/6GHz, 4.5Gbps, DBDC, BW 160MHz, 4K QAM, MLO, BT 5.3 LE, MRC, MRU, HDT, 6 nm FCC ID: RAS-MT7925B22M
MT7927
Wi-Fi 7, WPA3, 2.4/5/6GHz, 6.5Gbps, DBDC, BW 320MHz, 4K QAM, MLO, BT 5.3 LE, MRC, MRU, HDT, 6 nm FCC ID: RAS-MT7927 • AMD RZ738
It appears that the only difference between the chips is that the mt7925 supports 160 Mhz channel width and the mt7927 supports 320 MHz channel width.
Indications are that the driver for the mt7927 chip has not been added to the kernel yet.
I have not seen any mt7927s in my travels so far.
I have not seen any mt7827s in my travels so far.
mt7927
https://zfishtek.com/index.php/product/mediatek-mt7927-wireless-lan-card/
mt7925
https://zfishtek.com/index.php/product/mt7925-wireless-lan-card/
1b:00.0 Network controller: MEDIATEK Corp. Device 0717
Subsystem: Foxconn International, Inc. Device e106
Flags: bus master, fast devsel, latency 0, IRQ 236
Memory at bfc00000 (64-bit, non-prefetchable) [size=2M]
Memory at bfe00000 (64-bit, non-prefetchable) [size=32K]
Capabilities: [80] Express Endpoint, IntMsgNum 0
Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
Capabilities: [108] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [200] Advanced Error Reporting
Kernel driver in use: mt7925e
Kernel modules: mt7925e
So far it just works...I don't have a 7 AP, though.
Three words I like to hear... "it just works".
There may be occasional issues with the buffer but that could also be openwrt or interference, or my router, so I have to narrow that down.
At times, if I have issues, I have to restart NetworkManager too, though - it doesn't like being shut off and then immediately back on.
I have noticed a couple of mt7925 M.2 cards on Amazon US this week so I may grab one soon so I can test along with you.
We are talking about a new driver that includes code for a new generation of wireless so it will have bugs. I have been noticing patches going in. It isn't just the Mediatek WiFi 7 drivers but Intel, Qualcomm and Realtek as well. I still have no idea what Realtek's USB strategy is for WiFi 7. Since this site is primarily about USB WiFi, I watch it more closely and I can usually pick up some hints prior to product introduction but not with Realtek this time. Mediatek's driver support plan is well known as USB and PCIe support for WiFi 7 is in the mt7925u and mt7925e drivers that have been in the kernel since 6.7. I expect mt7927 support soon.
Keep us posted as you continue testing.
So far it just works...
Please provide a definition of "works", i.e., what exactly has been tested. Client mode, or AP mode? Does WDS work? Can more than one SSID be created? Is the advertisement of the DBDC capability true?
Well, I'm using it on a client device and so I haven't tried setting up a network on it, though if it weren't for my openwrt devices that would be a killer idea if it were slightly more reliable.
Right now, on kernel 6.9, I find that after running for 12-24 hours I eventually need to reboot to get it running properly. I'm assuming some kernel module issue or perhaps a buffer issue somewhere, but things get slow and then eventually despite having a valid IP, the connection becomes useless - not sure if due to latency/speed or if something else is happening. While I can restart the networking service or reset the card, only a real reboot seems to fix it.
I'm running Arch so sometime I could setup a test network, perhaps, and connect some random devices to it if I need to...I also should have thought to capture a dmesg log before my last reboot, but I'm still drinking my coffee...
@ilikenwf
if it weren't for my openwrt devices that would be a killer idea if it were slightly more reliable...
I just checked and it appears the mt7925 driver is already in the current stable version of OpenWRT:
kmod-mt792x-usb
I think they named it that because it will cover the 7925 and 7927 chips as the 7927 code goes in.
What you seeing in the log?
$ sudo dmesg | grep mt7
I'm a little hesitant to jump all over making a bug report on this driver right now because 6.9 seems to have had some stack issues that need to be resolved before we blame individual drivers.
[ 10.224161] mt7925e 0000:1b:00.0: ASIC revision: 79250000 [ 10.303401] mt7925e 0000:1b:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231227093012a [ 10.647100] mt7925e 0000:1b:00.0: WM Firmware Version: ____000000, Build Time: 20231227093232
Well, that is clean. I'll see about getting my own little card soon so that I can play along.
Can anyone who has MT7925 share the output of "iw list" ? I want to know if 160 MHz is allowed for AP mode . Thanks in advance .
@ilikenwf
Right now, on kernel 6.9, I find that after running for 12-24 hours I eventually need to reboot to get it running properly. I'm assuming some kernel module issue or perhaps a buffer issue somewhere, but things get slow and then eventually despite having a valid IP, the connection becomes useless - not sure if due to latency/speed or if something else is happening. While I can restart the networking service or reset the card, only a real reboot seems to fix it.
The stack is undergoing a lot of work at the moment so folks like you out there on the bleeding edge are helping figure out what needs to be fixed but I am curious in this case if turning off Scatter/Gather would help:
If the result of the following command is Y, then it is on:
grep [[:alnum:]] /sys/module/mt76_usb/parameters/*
To turn it off:
sudo -i echo "options mt76_usb disable_usb_sg=1" >> /etc/modprobe.d/mt76_usb.conf exit sudo reboot
@morrownr I think your previous comment is for a different card. There is no USB WiFi involved in @ilikenwf's setup.
Yes, my card is PCIe
Yes, my card is PCIe
Serious lack of coffee around here this morning. What was I thinking?
FYI @ A Quick Look at MSI's New Roamii Mesh Systems and WiFi 7 USB Dongle
""MSI was also showing off the BE6500 WiFi 7 USB adapter which is a tri-band dongle and the first of its kind that we've seen. It supports speeds of up to 2880 Mbps on the 6 and 5 GHz bands and 688 Mbps on the 2.4 GHz band, assuming you have a suitable WiFi 7 router or access point. It also offers support for MLO and interestingly enough, it also has built in drives, which means you don't need to download drivers to get it up and running. Finally MSI is promising support for Windows 10 and 11, as well as Linux. So far Windows 10 has lacked proper support for WiFi 7 devices, so this is an interesting development.""
Guess it could be based on mt7925?
Guess it could be based on mt7925?
Well, we only have two companies that produce usb wifi chips these days. It has to be either a Mediatek or Realtek chip. The details do appear to match the mt7925 but I have no details at all on what Realtek is up to regarding usb wifi. The fact that Linux support is mentioned by MSI could be a big hint that it is indeed the Mediatek chip.
I'll do some snooping around to see what I can find. I have already found the below link:
https://www.tp-link.com/us/home-networking/usb-adapter/archer-tbe400uh/
TP-Link using a Mediatek chip? Something just froze over if it is true.
FYI: One thing I do know about Realtek and WiFi 7 support for Linux is that Realtek cannot use the same technology as their out-of-kernel drivers have used as there is code in the Linux kernel that will stop Linux wifi 7 drivers that are not fully compliant with modern standards. So things can't be business as usual concerning Realtek and usb wifi 7. They could add usb support to rtw89 but I have not seen any indications of that so far. My best guess right now is that Realtek has simply fallen way behind Mediatek with usb wifi on Linux and maybe on other platforms as well.
Guess it could be based on mt7925?
Well, we only have two companies that produce usb wifi chips these days. It has to be either a Mediatek or Realtek chip. The details do appear to match the mt7925 but I have no details at all on what Realtek is up to regarding usb wifi. The fact that Linux support is mentioned by MSI could be a big hint that it is indeed the Mediatek chip.
I'll do some snooping around to see what I can find. I have already found the below link:
https://www.tp-link.com/us/home-networking/usb-adapter/archer-tbe400uh/
TP-Link using a Mediatek chip? Something just froze over if it is true.
TP-Link is suspect. I would bet it is Realtek. What is the latest kernel they can support with an old-tech driver? All they have to do is support one kernel and they can claim Linux support. I have a TP-Link router and it has the crappiest GUI ever. I'm using OpenWRT on a Raspberry Pi and the TP-Link I just use for the wireless 6 AP. :-) I don't trust TP-Link as a company. I thought of an idea, maybe the will use Mediatek and claim Linux support and then switch to Realtek but keep the same product number.
@bjlockie
TP-Link is suspect.
Agree. I was not advocating this TP-Link product.
What is the latest kernel they can support with an old-tech driver?
I don't remember but this is not new. It was several years ago.
I don't trust TP-Link as a company.
Me either.Too many years of seeing them do things that make it clear that they do not care about Linux.
I thought of an idea, maybe the will use Mediatek and claim Linux support and then switch to Realtek but keep the same product number.
Now hold on. You did not think of that. You are reading it from the TP-Link playbook.
@ilikenwf
Would you mind posting the result of iw list
for your mt7925?
I'd be curious to see what capabilities it is reporting. I think @Muh87 had ask back up the thread so I think he wants to know as well.
Once my laptop gets back to me I can - the backlight died.
@ilikenwf
Would you mind posting the result of
iw list
for your mt7925?I'd be curious to see what capabilities it is reporting. I think @Muh87 had ask back up the thread so I think he wants to know as well.
Thanks for the reminder .
MT7925B22M:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:16.3 Serial controller: Intel Corporation Sunrise Point-LP Active Management Technology - SOL (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #2 (rev f1)
00:1c.3 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #4 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
02:00.0 Network controller: MEDIATEK Corp. Device 7925
03:00.0 Non-Volatile memory controller: Silicon Motion, Inc. SM2263EN/SM2263XT (DRAM-less) NVMe SSD Controllers (rev 03)
[ 3.482955] pci 0000:02:00.0: [14c3:7925] type 00 class 0x028000 PCIe Endpoint
[ 3.482990] pci 0000:02:00.0: BAR 0 [mem 0xf0000000-0xf01fffff 64bit]
[ 3.483012] pci 0000:02:00.0: BAR 2 [mem 0xf0200000-0xf0207fff 64bit]
[ 3.483156] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 3.534834] pci 0000:02:00.0: Adding to iommu group 11
[ 8.419994] mt7925e 0000:02:00.0: enabling device (0000 -> 0002)
[ 8.434691] mt7925e 0000:02:00.0: ASIC revision: 79250000
[ 8.513310] mt7925e 0000:02:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231227093012a
[ 8.856063] mt7925e 0000:02:00.0: WM Firmware Version: ____000000, Build Time: 20231227093232
[ 9.511367] mt7925e 0000:02:00.0 wlp2s0: renamed from wlan0
6.10.0-061000rc2-generic
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 4
max scan IEs length: 427 bytes
max # sched scan SSIDs: 10
max # match sets: 16
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 1 usec (0x03)
HT TX/RX MCS rate indexes supported: 0-15
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x2270ce126dc0b3064e3f00):
HE40/2.4GHz
242 tone RUs/2.4GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Beamformee STS > 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
20MHz in 160/80+80MHz HE PPDU
80MHz in 160/80+80MHz HE PPDU
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0300):
NSEP priority access Supported
EHT OM Control Supported
EHT PHY Capabilities: (0xe80409fe10610c36):
NDP With EHT-LTF And 3.2 µs GI
SU Beamformer
SU Beamformee
Beamformee SS (80MHz): 1
Beamformee SS (160MHz): 1
Number Of Sounding Dimensions (80MHz): 1
Number Of Sounding Dimensions (160MHz): 1
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook size (4, 2) SU Feedback
Codebook size (7, 5) MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Partial BW Feedback
Triggered CQI Feedback
Max Nc: 1
Non-Triggered CQI Feedback
Common Nominal Packet Padding: 2
Maximum Number Of Supported EHT-LTFs: 17
Support of MCS 15: 1
Non-OFDMA UL MU-MIMO (80MHz)
Non-OFDMA UL MU-MIMO (160MHz)
MU Beamformer (80MHz)
MU Beamformer (160MHz)
EHT MCS/NSS: (0x22222200000000000000000000):
EHT bw=20 MHz, max NSS for MCS 0-7: Rx=2, Tx=2
EHT bw=20 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw=20 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw=20 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0220ce120000a000000c00):
HE40/2.4GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0300):
NSEP priority access Supported
EHT OM Control Supported
EHT PHY Capabilities: (0xe80409fe10610c36):
NDP With EHT-LTF And 3.2 µs GI
SU Beamformer
SU Beamformee
Beamformee SS (80MHz): 1
Beamformee SS (160MHz): 1
Number Of Sounding Dimensions (80MHz): 1
Number Of Sounding Dimensions (160MHz): 1
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook size (4, 2) SU Feedback
Codebook size (7, 5) MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Partial BW Feedback
Triggered CQI Feedback
Max Nc: 1
Non-Triggered CQI Feedback
Common Nominal Packet Padding: 2
Maximum Number Of Supported EHT-LTFs: 17
Support of MCS 15: 1
Non-OFDMA UL MU-MIMO (80MHz)
Non-OFDMA UL MU-MIMO (160MHz)
MU Beamformer (80MHz)
MU Beamformer (160MHz)
EHT MCS/NSS: (0x22222200000000000000000000):
EHT bw=20 MHz, max NSS for MCS 0-7: Rx=2, Tx=2
EHT bw=20 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw=20 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw=20 MHz, max NSS for MCS 12-13: Rx=0, Tx=0
Bitrates (non-HT):
* 1.0 Mbps (short preamble supported)
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412.0 MHz [1] (30.0 dBm)
* 2417.0 MHz [2] (30.0 dBm)
* 2422.0 MHz [3] (30.0 dBm)
* 2427.0 MHz [4] (30.0 dBm)
* 2432.0 MHz [5] (30.0 dBm)
* 2437.0 MHz [6] (30.0 dBm)
* 2442.0 MHz [7] (30.0 dBm)
* 2447.0 MHz [8] (30.0 dBm)
* 2452.0 MHz [9] (30.0 dBm)
* 2457.0 MHz [10] (30.0 dBm)
* 2462.0 MHz [11] (30.0 dBm)
* 2467.0 MHz [12] (disabled)
* 2472.0 MHz [13] (disabled)
* 2484.0 MHz [14] (disabled)
Band 2:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339071f6):
Max MPDU length: 11454
Supported Channel Width: 160 MHz
RX LDPC
short GI (80 MHz)
short GI (160/80+80 MHz)
TX STBC
SU Beamformee
MU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
VHT extended NSS: supported
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4c70ce126dc0b3064e3f00):
HE40/HE80/5GHz
HE160/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Beamformee STS > 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
20MHz in 160/80+80MHz HE PPDU
80MHz in 160/80+80MHz HE PPDU
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0300):
NSEP priority access Supported
EHT OM Control Supported
EHT PHY Capabilities: (0xe80409fe10610c36):
NDP With EHT-LTF And 3.2 µs GI
SU Beamformer
SU Beamformee
Beamformee SS (80MHz): 1
Beamformee SS (160MHz): 1
Number Of Sounding Dimensions (80MHz): 1
Number Of Sounding Dimensions (160MHz): 1
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook size (4, 2) SU Feedback
Codebook size (7, 5) MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Partial BW Feedback
Triggered CQI Feedback
Max Nc: 1
Non-Triggered CQI Feedback
Common Nominal Packet Padding: 2
Maximum Number Of Supported EHT-LTFs: 17
Support of MCS 15: 1
Non-OFDMA UL MU-MIMO (80MHz)
Non-OFDMA UL MU-MIMO (160MHz)
MU Beamformer (80MHz)
MU Beamformer (160MHz)
EHT MCS/NSS: (0x22222222222200000000000000):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0c20ce120000a000000c00):
HE40/HE80/5GHz
HE160/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0300):
NSEP priority access Supported
EHT OM Control Supported
EHT PHY Capabilities: (0xe80409fe10610c36):
NDP With EHT-LTF And 3.2 µs GI
SU Beamformer
SU Beamformee
Beamformee SS (80MHz): 1
Beamformee SS (160MHz): 1
Number Of Sounding Dimensions (80MHz): 1
Number Of Sounding Dimensions (160MHz): 1
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook size (4, 2) SU Feedback
Codebook size (7, 5) MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Partial BW Feedback
Triggered CQI Feedback
Max Nc: 1
Non-Triggered CQI Feedback
Common Nominal Packet Padding: 2
Maximum Number Of Supported EHT-LTFs: 17
Support of MCS 15: 1
Non-OFDMA UL MU-MIMO (80MHz)
Non-OFDMA UL MU-MIMO (160MHz)
MU Beamformer (80MHz)
MU Beamformer (160MHz)
EHT MCS/NSS: (0x22222222222200000000000000):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180.0 MHz [36] (23.0 dBm)
* 5200.0 MHz [40] (23.0 dBm)
* 5220.0 MHz [44] (23.0 dBm)
* 5240.0 MHz [48] (23.0 dBm)
* 5260.0 MHz [52] (24.0 dBm) (radar detection)
* 5280.0 MHz [56] (24.0 dBm) (radar detection)
* 5300.0 MHz [60] (24.0 dBm) (radar detection)
* 5320.0 MHz [64] (24.0 dBm) (radar detection)
* 5500.0 MHz [100] (24.0 dBm) (radar detection)
* 5520.0 MHz [104] (24.0 dBm) (radar detection)
* 5540.0 MHz [108] (24.0 dBm) (radar detection)
* 5560.0 MHz [112] (24.0 dBm) (radar detection)
* 5580.0 MHz [116] (24.0 dBm) (radar detection)
* 5600.0 MHz [120] (disabled)
* 5620.0 MHz [124] (disabled)
* 5640.0 MHz [128] (disabled)
* 5660.0 MHz [132] (24.0 dBm) (radar detection)
* 5680.0 MHz [136] (24.0 dBm) (radar detection)
* 5700.0 MHz [140] (24.0 dBm) (radar detection)
* 5720.0 MHz [144] (24.0 dBm) (radar detection)
* 5745.0 MHz [149] (30.0 dBm)
* 5765.0 MHz [153] (30.0 dBm)
* 5785.0 MHz [157] (30.0 dBm)
* 5805.0 MHz [161] (30.0 dBm)
* 5825.0 MHz [165] (30.0 dBm)
* 5845.0 MHz [169] (disabled)
* 5865.0 MHz [173] (disabled)
* 5885.0 MHz [177] (disabled)
Band 4:
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4c70ce126dc0b3064e3f00):
HE40/HE80/5GHz
HE160/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformee
Beamformee STS <= 80Mhz: 3
Beamformee STS > 80Mhz: 3
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
20MHz in 40MHz HE PPDU 2.4GHz
20MHz in 160/80+80MHz HE PPDU
80MHz in 160/80+80MHz HE PPDU
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: managed
EHT MAC Capabilities (0x0300):
NSEP priority access Supported
EHT OM Control Supported
EHT PHY Capabilities: (0xe80409fe10610c36):
NDP With EHT-LTF And 3.2 µs GI
SU Beamformer
SU Beamformee
Beamformee SS (80MHz): 1
Beamformee SS (160MHz): 1
Number Of Sounding Dimensions (80MHz): 1
Number Of Sounding Dimensions (160MHz): 1
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook size (4, 2) SU Feedback
Codebook size (7, 5) MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Partial BW Feedback
Triggered CQI Feedback
Max Nc: 1
Non-Triggered CQI Feedback
Common Nominal Packet Padding: 2
Maximum Number Of Supported EHT-LTFs: 17
Support of MCS 15: 1
Non-OFDMA UL MU-MIMO (80MHz)
Non-OFDMA UL MU-MIMO (160MHz)
MU Beamformer (80MHz)
MU Beamformer (160MHz)
EHT MCS/NSS: (0x22222222222200000000000000):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
HE Iftypes: AP
HE MAC Capabilities (0x00011a081044):
+HTC HE Supported
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0c20ce120000a000000c00):
HE40/HE80/5GHz
HE160/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
Partial Bandwidth Extended Range
PPE Threshold Present
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
EHT Iftypes: AP
EHT MAC Capabilities (0x0300):
NSEP priority access Supported
EHT OM Control Supported
EHT PHY Capabilities: (0xe80409fe10610c36):
NDP With EHT-LTF And 3.2 µs GI
SU Beamformer
SU Beamformee
Beamformee SS (80MHz): 1
Beamformee SS (160MHz): 1
Number Of Sounding Dimensions (80MHz): 1
Number Of Sounding Dimensions (160MHz): 1
Ng = 16 SU Feedback
Ng = 16 MU Feedback
Codebook size (4, 2) SU Feedback
Codebook size (7, 5) MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Partial BW Feedback
Triggered CQI Feedback
Max Nc: 1
Non-Triggered CQI Feedback
Common Nominal Packet Padding: 2
Maximum Number Of Supported EHT-LTFs: 17
Support of MCS 15: 1
Non-OFDMA UL MU-MIMO (80MHz)
Non-OFDMA UL MU-MIMO (160MHz)
MU Beamformer (80MHz)
MU Beamformer (160MHz)
EHT MCS/NSS: (0x22222222222200000000000000):
EHT bw <= 80 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw <= 80 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 8-9: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 10-11: Rx=2, Tx=2
EHT bw=160 MHz, max NSS for MCS 12-13: Rx=2, Tx=2
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5955.0 MHz [1] (12.0 dBm)
* 5975.0 MHz [5] (12.0 dBm)
* 5995.0 MHz [9] (12.0 dBm)
* 6015.0 MHz [13] (12.0 dBm)
* 6035.0 MHz [17] (12.0 dBm)
* 6055.0 MHz [21] (12.0 dBm)
* 6075.0 MHz [25] (12.0 dBm)
* 6095.0 MHz [29] (12.0 dBm)
* 6115.0 MHz [33] (12.0 dBm)
* 6135.0 MHz [37] (12.0 dBm)
* 6155.0 MHz [41] (12.0 dBm)
* 6175.0 MHz [45] (12.0 dBm)
* 6195.0 MHz [49] (12.0 dBm)
* 6215.0 MHz [53] (12.0 dBm)
* 6235.0 MHz [57] (12.0 dBm)
* 6255.0 MHz [61] (12.0 dBm)
* 6275.0 MHz [65] (12.0 dBm)
* 6295.0 MHz [69] (12.0 dBm)
* 6315.0 MHz [73] (12.0 dBm)
* 6335.0 MHz [77] (12.0 dBm)
* 6355.0 MHz [81] (12.0 dBm)
* 6375.0 MHz [85] (12.0 dBm)
* 6395.0 MHz [89] (12.0 dBm)
* 6415.0 MHz [93] (12.0 dBm)
* 6435.0 MHz [97] (12.0 dBm)
* 6455.0 MHz [101] (12.0 dBm)
* 6475.0 MHz [105] (12.0 dBm)
* 6495.0 MHz [109] (12.0 dBm)
* 6515.0 MHz [113] (12.0 dBm)
* 6535.0 MHz [117] (12.0 dBm)
* 6555.0 MHz [121] (12.0 dBm)
* 6575.0 MHz [125] (12.0 dBm)
* 6595.0 MHz [129] (12.0 dBm)
* 6615.0 MHz [133] (12.0 dBm)
* 6635.0 MHz [137] (12.0 dBm)
* 6655.0 MHz [141] (12.0 dBm)
* 6675.0 MHz [145] (12.0 dBm)
* 6695.0 MHz [149] (12.0 dBm)
* 6715.0 MHz [153] (12.0 dBm)
* 6735.0 MHz [157] (12.0 dBm)
* 6755.0 MHz [161] (12.0 dBm)
* 6775.0 MHz [165] (12.0 dBm)
* 6795.0 MHz [169] (12.0 dBm)
* 6815.0 MHz [173] (12.0 dBm)
* 6835.0 MHz [177] (12.0 dBm)
* 6855.0 MHz [181] (12.0 dBm)
* 6875.0 MHz [185] (12.0 dBm)
* 6895.0 MHz [189] (12.0 dBm)
* 6915.0 MHz [193] (12.0 dBm)
* 6935.0 MHz [197] (12.0 dBm)
* 6955.0 MHz [201] (12.0 dBm)
* 6975.0 MHz [205] (12.0 dBm)
* 6995.0 MHz [209] (12.0 dBm)
* 7015.0 MHz [213] (12.0 dBm)
* 7035.0 MHz [217] (12.0 dBm)
* 7055.0 MHz [221] (12.0 dBm)
* 7075.0 MHz [225] (12.0 dBm)
* 7095.0 MHz [229] (12.0 dBm)
* 7115.0 MHz [233] (12.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* tdls_mgmt
* tdls_oper
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* set_multicast_to_unicast
* set_sar_specs
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 1 patterns of 1-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on network detection, up to 10 match sets
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed, P2P-client } <= 2, #{ AP, P2P-GO } <= 1,
total <= 2, #channels <= 2
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports configuring vdev MAC-addr on create.
Device supports randomizing MAC-addr in scans.
Device supports randomizing MAC-addr in sched scans.
max # scan plans: 1
max scan plan interval: 65535
max scan plan iterations: 0
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xb0 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
* [ BEACON_RATE_HT ]: HT beacon rate setting
* [ BEACON_RATE_VHT ]: VHT beacon rate setting
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ ACK_SIGNAL_SUPPORT ]: ack signal level support
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying
* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
* [ AQL ]: Airtime Queue Limits (AQL)
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
* [ BEACON_RATE_HE ]: HE beacon rate support (AP/mesh)
* [ POWERED_ADDR_CHANGE ]: can change MAC address while up
Hi @joshschmelzle
Thanks for posting. What is your opinion of the chip/driver so far?
Thank you so much for the reply . I see it supports 160 MHz as an access point , hopefully it would be possible to get 2400 MBPS when connected to it .
I see it supports 160 MHz as an access point , hopefully it would be possible to get 2400 MBPS when connected to it .
I order an M.2 mt7925 card yesterday so I should have one soon. We'll see what speeds we get. My router is only WiFi 6 but it can push packets fairly well. For testing AP mode, my RasPi4B is setup and runs as a dual band AP but does not support M.2 so I'll have to figure out how to test AP mode.
what is the maximum bandwidth you could achieve with RasPi4B as AP mode ? were you ever able to surpass 1200 MBPS ?
Hi everyone, I bought a Legion 9i and it came with the mt7927 card. I read in this repo that it's basically the same card as the mt7925 but has higher bandwidth. Should the mt7927 card work with the mt7925 driver? If not, is updating the driver to include support for mt7927 a big change? Sorry if this isn't the place to ask these questions, I just want to use my dumb laptop without attachments!
Also, if there's any diagnostics I can do to help out let me know.
Hi @lmcarneiro
Should the mt7927 card work with the mt7925 driver?
Not yet. Support for the mt7927 has not been merged.
If not, is updating the driver to include support for mt7927 a big change?
It is something that Mediatek is going to have to do. Be patient.
Also, if there's any diagnostics I can do to help out let me know.
Just use a supported usb wifi adapter until the driver is available. It is like having a toy that you can't play with.
My M.2 mt7925 arrived last week. I installed it in a Mini PC that I have. The distro is Ubuntu 24.04. The card came to life. Connection was uneventful. Use has been uneventful in managed mode. I do not have a WiFi 7 / 6 GHz capable AP yet so have not tested that. Nothing bad to report regarding wifi at this point.
Bluetooth, on the other hand, did not come up so I investigated. The firmware and driver were in place in Ubuntu 24.04. Further investigation led to the answer. The vid-pid for the bluetooth capability was simply not in the kernel yet but I found a patch that has already gone in so help is already on the way there. I have a PCIe card with the mt7922 chip and the bluetooth works perfectly with it so I would expect the same with the mt7925.
I will continue to monitor linux-wireless for patches that add mt7927 support. Hopefully that comes soon.
@morrownr
Does 160 MHz channel width work? Do you have any speed test results?
@patrakov
Does 160 MHz channel width work?
I can test that, I have a WiFi 6 dual band router that is capable of 160 MHz. It is currently offline. Give me a change to finish the testing that I am doing and I work on this.
Do you have any speed test results?
I just did a quick test with iperf3 with a WiFi 5 dual band router that can handle 80 MHz channel width. It showed 645 Mbps. That is what I would expect. I do have a PCIe card with the mt7922 chip that is in my main dev box that gives me over 1 Gbps with my WiFi 6 router so that is what I will expect from this mt7925 card... I'll get some results posted as able.
@patrakov
Here is an initial test with WiFi 6, 160 MHz:
$ iperf3 -c 192.168.1.1
Connecting to host 192.168.1.1, port 5201
[ 5] local 192.168.1.212 port 43230 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 99.5 MBytes 834 Mbits/sec 0 970 KBytes
[ 5] 1.00-2.00 sec 130 MBytes 1.09 Gbits/sec 0 970 KBytes
[ 5] 2.00-3.00 sec 127 MBytes 1.07 Gbits/sec 0 970 KBytes
[ 5] 3.00-4.00 sec 127 MBytes 1.06 Gbits/sec 0 970 KBytes
[ 5] 4.00-5.00 sec 130 MBytes 1.09 Gbits/sec 0 970 KBytes
[ 5] 5.00-6.00 sec 125 MBytes 1.05 Gbits/sec 0 970 KBytes
[ 5] 6.00-7.00 sec 66.2 MBytes 556 Mbits/sec 2 970 KBytes
[ 5] 7.00-8.00 sec 40.2 MBytes 338 Mbits/sec 3 1.41 KBytes
[ 5] 8.00-9.00 sec 39.5 MBytes 331 Mbits/sec 2 1.03 MBytes
[ 5] 9.00-10.00 sec 43.4 MBytes 364 Mbits/sec 2 1.06 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 928 MBytes 778 Mbits/sec 9 sender
[ 5] 0.00-10.05 sec 925 MBytes 772 Mbits/sec receiver
It is not clear to me why we saw the drop in the last part of the test. I'll have to continue testing. It could be a result of a lot of things. What I do know is that the mt7925 driver is not perfect yet. It can't be because these modern WiFi 6 and 7 drivers are incredibly complex. It is mind bending to me. Like Dorthy once said to Todo, I don't think we are in Kansas anymore.
I think it was last week when I saw a series of 48 patches go through for this driver. I think it was mostly to add capability but I did not have time to investigate all 48 patches. So, for now, my testing shows solid stable managed mode performance on my WiFi 5 router. We did not get the performance I was looking for with the WiFi 6 router as I was expecting sustained performance above 1 Gbps.
I think it is reasonable most Linux users wanting WiFi 7 to expect the mt7925 driver to start solidifying by around time for this years LTS kernel which looks like it will be 6.12.
Update:
I saw another large patch set for the mt7925 flow into linux-wireless yesterday. It consist of 29 patches and adds support for MLO. The addition of MLO support may signal that mt7927 support will be coming soon.
Testing:
I tested with Linux Mint 22 beta today. WiFi works, BT not yet. It appears that anything based on Ubuntu 24.04 should be good to go with the mt7925 chip. Will the recent large patches work their way back into Ubuntu's kernel 6.8? I do not know but there is a good change that it could happen. I'd say the lone patch to get BT going is a really high probability.
I'll forecast that any distro based on this year's LTS or later will be in really good shape with cards and adapters based on the mt7925 and mt7927 chips. It look like the LTS for this year will be 6.12 but I don't make that call so we will see.
I got my MT7925 from taobao for about 15USD. Inserted into my N100 miniPC but nothing show up (lspci). Checked the M.2 slot only supports CNVI. I guess the MT7925 is a NGFF instead of CNVI?
I think only Intel uses cnvi. How do you know if an m2 slot only supports cnvi? I have a laptop that has a cnvi Intel card that I want to replace with a mediatek.
@bjlockie @upsangel
I don't have much experience with these little cards. What is the difference between cnvi and ngff?
It is my understanding that Intel created CNvi so they could offload some of the processing from the M2 card to the CPU so they could make cheaper M2 cards. Pretty stupid idea IMO. :-)
so they could make cheaper M2 cards.
Ouch. Sounds like the Windows Modem thing from back in the 90's. I guess I was lucky that my Mini PC has a ngff slot and the mt7925 card I got is a ngff card. We really don't need this crap.
There may be other cards with the mt7925 chipsets but this is the first one I have seen for sale:
https://zfishtek.com/index.php/product/mt7925-wireless-lan-card/
This is NOT a recommendation for the above product. What this message is about is to point out that the mt7925 chipsets are flowing to product makers. Cards almost always come to market before USB adapters. That is just the way it is so now that we see cards on the market, it probably means that adapters will be available soon. It is hard to say how soon but sometime this year is a reasonable expectation.
The driver for the mt7925 chipset has been in the Linux kernel since kernel 6.7.
Edit: Warning: Cards with the mt7927 chip are available as well but driver support for the mt7927 chip is not in the kernel yet.
If anyone gets a card with a mt7925 chipset, please give us a report.
@morrownr