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
Low-incorrect txpower on Mediatek 7628 (TP-Link 840 ver 6.0) #279
Comments
Also tested version 6.1 and 6.2. Results are the same. Stable but no range. root@telnet-router:~# cat /sys/kernel/debug/ieee80211/phy0/mt76/rate_txpower This seems wrong to me too. Like wrong eeprom reading ?
|
tp-link 840 version 6 eeprom dump: /lib/firmware# hexdump eeprom.bin
|
seeing the same all-zero values for rate_txpower on xiaomi mir3p (mt7621 with dual mt7615)... it's odd that nobody commented on this issue yet |
I extraced factory bin file from same mediatek chip 7628 and from tp-link 840 (mediatek 7628) version 6.0. mediatekhigh-tx.txt Anyone knows where in which line is country code or tx-power ? |
mt7628_eeprom_guideline_v2_00.pdf should contain the relevant information. |
Still no fixes for tp-link 840 version 6,6.1,6.2 and 14 ? |
Correct partition is:partition@10000 { Also this fix in mt76x8.mkdefine Device/tplink_tl-wr840n-v6 Now txpower and everything is okay. Router is usable. |
It seems like txpower is totally incorrect on mediatek 7628 models.
I see -55dB when my laptop is 30 cm away from the router.
Same test with openwrt Tp-link 740 version 4 signal strenght in luci is -27dB. Version 740 power is limited to 18dB (63 mw) so seems like Mediatek (-55dB) are something like 14dB (30mw) which is wrong. Also any changes like country or txpower does not change signal strength in Luci (still -55dB). Testing mediatek 7628 in 5 meters away make signal -80dB.
May be your driver does not set power at all or at least does not respect country regulatory ?
I am using latest OpenWrt SNAPSHOT, r9945-bc85640cdc.
Driver is stable and working good at 1 meter away but next room is not so good.
The text was updated successfully, but these errors were encountered: