MT7610E: TX-Power Values incorrect -> low range
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
My TP-Link Vr200v uses MT7610E for 5GHz. In Stock firmware range is good (signal should be 22dbm), in latest master it is very limited:
Frequencies:
* 5180 MHz [36] (12.0 dBm)
* 5200 MHz [40] (12.0 dBm)
* 5220 MHz [44] (12.0 dBm)
* 5240 MHz [48] (12.0 dBm)
* 5260 MHz [52] (12.0 dBm)
* 5280 MHz [56] (12.0 dBm)
* 5300 MHz [60] (12.0 dBm)
* 5320 MHz [64] (12.0 dBm)
* 5500 MHz [100] (14.0 dBm)
* 5520 MHz [104] (14.0 dBm)
* 5540 MHz [108] (14.0 dBm)
* 5560 MHz [112] (14.0 dBm)
* 5580 MHz [116] (14.0 dBm)
* 5600 MHz [120] (15.0 dBm)
* 5620 MHz [124] (15.0 dBm)
* 5640 MHz [128] (15.0 dBm)
* 5660 MHz [132] (15.0 dBm)
* 5680 MHz [136] (15.0 dBm)
* 5700 MHz [140] (15.0 dBm)
* 5720 MHz [144] (16.0 dBm)
* 5745 MHz [149] (16.0 dBm)
* 5765 MHz [153] (16.0 dBm)
* 5785 MHz [157] (17.0 dBm)
* 5805 MHz [161] (17.0 dBm)
* 5825 MHz [165] (18.0 dBm)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
This Problem is not new and should be fixed since a lot of people are affected with this bug.
I tried to change the val manually (in eeprom.c), but had no luck, this brings no difference.
If i can provide helpful information please let me know! Thank you for your support!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the power values reported by the MT7610E on stock firmware and latest master, then inspect eeprom.c, which the report identifies as a possible location. Reproduce the frequency listing and determine why changing the EEPROM value has no effect. Done means the affected channels report the expected transmit-power range without incorrectly weakening or enabling channels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100