On Thu, 19 Jun 2025, Kevin Oberman wrote:
That looks a bit disappointing. Not that I can claim to really understand
most of it.
compat.linuxkpi.80211.wlan0.dump_stas:
lsta 0xfffff80001333000 sta 0xfffff800013331c0 added_to_drv 1
nl80211_sta_info (valid fields)
0x00004503<BEACON_RX,BEACON_SIGNAL_AVG,SIGNAL_AVG,RX_BITRATE,TX_BITRATE>
connected_time 0 inactive_time 0
rx_bytes 0 rx_packets 0 rx_dropped_misc 0
rx_duration 0 rx_beacon 16464 rx_beacon_signal_avg -46
tx_bytes 0 tx_packets 0 tx_failed 0
tx_duration 0 tx_retries 0
signal 0 signal_avg -47 ack_signal 0 avg_ack_signal 0
You have good singal.
generation 0 assoc_req_ies_len 0 chains 0
rxrate: flags 6<VHT_MCS,SGI> bw 4(80) legacy 0 kbit/s mcs 9 nss 2
he_dcm 0 he_gi 0 he_ru_alloc 0 eht_gi 0
txrate: flags 6<VHT_MCS,SGI> bw 4(80) legacy 0 kbit/s mcs 9 nss 2
he_dcm 0 he_gi 0 he_ru_alloc 0 eht_g
You are on VHT80 with MCS 9 NSS 2 with Short Guard Interval (SGI).
That's the maximum possible on VHT80. That should give you 3-500Mbit/s
RX locally as single user. At least others have reported that.
It'll be a few seconds before the firmware will fully ramp up to use
that but it seems you managed.
Hard to say what's going wrong without much further debugging.
What kind of speedtest were you using?
Do you have any chance to test a local target?
/bz
--
Bjoern A. Zeeb r15:7
