On 2022/03/16 23:17, Stefan Sperling wrote:
> On Wed, Mar 16, 2022 at 04:11:41PM +0100, Stefan Sperling wrote:
> > This patch adds initial 11ac support to the iwm(4) driver.
> > It allows use of 80 MHz channels and VHT MCS.
>
> Updated patch. Fixes a fatal firmware error on devices which
> do not support MIMO, such as the 3160.
Running with this on my X1Y4, seems OK so far but only been running for
a short while. I'll leave the ethernet cable out so it gets some more
time running.
iwm0 at pci0 dev 20 function 3 "Intel AC 9560" rev 0x11, msix
iwm0: hw rev 0x310, fw ver 46.4e1ceb39.0, address 50:eb:71:7c:af:5b
ifconfig is usually showing VHT-MCS5/6 with occasional blips of 9
$ while true; do ifconfig iwm|grep VHT; sleep .5;done
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS9 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS9 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS5 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS6 mode 11ac)
media: IEEE802.11 autoselect (VHT-MCS9 mode 11ac)
^C
Here are the receiver stats, sender is capable of approx filling
its Gb port:
--- tcpbench server statistics ---
4011036968 bytes received over 132.909 seconds
bandwidth min/avg/max/std-dev = 84.660/244.842/263.122/27.239 Mbps
I didn't note the exact figures before the diff but it was in
the region of 220Mb.
AP is one of the mediatek-based unifis (nanohd) running the latest
non-beta firmware (6.0.14.13634), about 1.5m away from the laptop,
I'm running it with 40MHz chans. ifconfig scan shows:
nwid <snip> chan 136 bssid <snip> 100% HT-MCS31
privacy,spectrum_mgmt,radio_measurement,wpa2
802.11 flags=0<>: beacon, timestamp 267615744056, interval 100,
caps=10421<ESS,PRIVACY,SPECTRUM_MGMT,RADIO_MEASUREMENT>, ssid (<snip>), rates
6M* 9M 12M* 18M 24M* 36M 48M 54M, ds (chan 136), tim 0x01030000, power
constraint 0dB, tpcreport 0x3f00, 195:3 0x011e1e, 70:5 0xf200010000, 51:6
0x0a6870788088, rsn=<version 1,groupcipher ccmp,cipher ccmp,akm PSK,rsncap
0x80>, 4 stations, 0% utilization, admission capacity 976us/s,
htcaps=<20/40MHz,LDPC,SGI@20MHz,SGI@40MHz,TXSTBC,RXSTBC 1 stream,A-MSDU
3839,A-MPDU max 65535,A-MPDU spacing 4.00us,RxMCS 0xffffffff010000000000>,
htop=<40MHz chan 136:132,htprot none,non-greenfield STA,basic MCS set
0x0000000000000000>, 191:12 0xb109cb33aaff1806aaff1806, 192:5 0x000000aaff,
127:8 0x0000000000000040, vendor
0x0050f2020101000003a4000027a4000042435e0062322f00, 40:6 0x00c81e001400, vendor
0x000c4307000000, vendor
0x000ce700000000bf0cb101c0332aff92042aff9204c0050000002affc303010202, vendor
0x00156d00010100010220ec810674acb915ede5, <radiotap v0, tsf 418409187,
12Mbit/s, chan 136, 11n, sig 67dBm, noise -106dBm>
