openwrt / openwrt/mt76

mt7628: changing TX power do not work

Open
#981 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
888
Forks
436
PR merge metrics
No merged PRs in 30d

Description

When using mt7628 device with mt76/mt7603 driver in AP mode it seems that changing tx power functionality is broken. Using the iw dev wlanX-X set txpower X command seems to set the tx power as displayed in iwinfo Tx-Power field but when scanning the mt7628 AP multiple times and changing the tx power level the signal value doesn't change even when tx power i set to 0.

Current behaviour:

  • mt7628 device with mt76/mt7603 driver running in AP mode
  • Set the tx power level using iw dev wlanX-X set txpower X command
  • In iwinfo output Tx-Power field displays correct value
  • Scanning the AP and changing its tx power, doesn't seem to effect signal strength

Issue:

  • Although TX power levels can be set and are reported correctly by iwinfo, they do no appear to have any real effect on the RF output.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the mt7628 AP case with the mt76/mt7603 driver, using iw dev wlanX-X set txpower X, iwinfo, and repeated scans. Trace the tx-power setting path and verify that changing the reported level changes the actual RF signal; done means the configured levels affect scan-observed signal strength, including at 0.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.