rany2

@Ansuel ``` root@rooter2:~# iwinfo eap2ghz htmode HT20 HT40 HE20 HE40 ``` `VHT20 VHT40` is not in the list

@Ansuel Yes it's an AX system, but it also occurs with an AC router I have.

@backslashxx I haven't had the time to test it yet, but could you report back if `iwinfo >>2ghz interface

@raenye Have a look at: - https://github.com/rany2/mt76/commit/b72ae710b4d77082139d9238404c38f55836a214 - https://github.com/rany2/mt76/commit/8c4d538ed24e26b23c6c6d99be091c75770b38c2 - https://github.com/rany2/mt76/commit/c555acfa7a1830b9718f97a58aa6fbf68112da1e - https://github.com/rany2/mt76/commit/1da209df5742c2d4d4fd8f98b1925f1b0d565dce - https://github.com/rany2/mt76/commit/c48ae4cf191d49d8a9ae2dcebda2e77bc19ce033

Something missing from these patches is txbf enablement for mt7915+... but these are the minimum patches to get it working. At any rate, beamforming is a bit problematic on those...

> > @raenye Have a look at: ... > > Compiling now, thanks. The only change to configuration needed is to set `htmode` to `VHT20` instead of `HT20`, right? >...

@raenye With the old patches you needed additional changes to hostapd.sh to get it working, seems like this is the case here as well unless more changes are made. There's...

@Ansuel He already did that in his patch, he had an extra commit that addressed it.

@raenye I think what he means is, instead of ``` phy->sband_2g.sband.vht_cap.vendor_qam256_supported = true; ``` do ``` phy->sband_2g.sband.vht_cap.vendor_qam256_supported = vht; ```

See https://github.com/openwrt/openwrt/commit/9b56c27a8a08a5c40d38064b9046f42177c94768#commitcomment-124323371. It is a harmless warning.