-
Notifications
You must be signed in to change notification settings - Fork 341
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
mt76x2, mt76x3, mt7615: tx power with mt76 driver is lower than with mediatek driver #657
Comments
Judging from the image, safe to assume you're using a UNII-2 channel. UNII-2 is capped at 20dbi globally, but 23dbi in China and other eastern countries. Or, use a unii-1 channel (like 44) on both routers, that way you can set the openwrt output to 23 legally. Unii-1 is 23dbi global and China. I'd love to see a followup! |
I have the same experience with a MT7621 SoC with a 7612 + 7603e Wifi chips (ZBT WE3526). OEM firmware (OpenWRT derived) with the MediaTek drivers is 4 to 10dB stronger. I also note the OEM 7603 related code loads the 'eeprom' from a file, not the actual flash. So maybe an override is needed in DTS? This issue is also related to what is discussed in #633 |
Hmm... Channel 44 + driver default power in OpenWrt gives approximately the same EIRP as stock firmware. |
Just as I suspected. If you now set the country to China, set a Unii 2 channel and set the output to 26dbi, i think you'll see the same. |
Done some measurements. Two Xiaomi AX3200 routers.
MTK wifi settings are default (maximum power). Signal measured through 3 brick walls. |
I am also experiencing this problem in mt7915. so I am using a workaround by modifying wireless-regdb. |
Can you specify your workaround? |
can you try to turn off sku like this and make another test? |
No difference compared with previous results |
Did you try PA as country? normally it should be possible to set 30dbi if hardware is able to, if yes you can patch a wireless-regdb |
PA gives me 27dBm max. mt76 27dBm signal is lower than mtk default. |
So then youre not capped by the regdb, its either the chipset does max 27dbm or some antenna gain like 3dbi in this case there only the devs can help |
Interesting results, thanks for sharing. One question: did you use 802.11ax or 802.11ac in your tests? I'm asking this because I also have two AX6S and one AX3200 (same device), and while testing 802.11ax performance through a brick wall I've noticed that the 802.11ax performance is worse than 802.11ac (it happens with multiple ax devices, but with an iPhone 13 the problem is even worse). See more details of my test in the forum here. My hypothesis is that mt76 drivers may not be enabling beamforming in 802.11ax that could explain the instability of the signal strength in your tests if you used 802.11ax. If so, you may want to repeat your tests with 802.11ac to compare the results. |
Looking at MediaTek's GPL code, the EEPROM size on the MT7663 is 1536 (0x600). I made the change in the MT76 driver and noticed an average 5dbm increase in signal strength. My config:
I've tested on my TP-Link Archer C6 v3. Not sure if work on other devices. |
I have a MT7621-equipped router (DIR-2640) that does not support 802.11ax. It does not appear beamforming is enabled:
Capturing beacon frames confirm it's not advertising support for beamforming. |
Seems to be enabled on MT7622, a RT3200 var/run/hostapd-wl1.conf:vht_capab=[RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-4][BF-ANTENNA-4][VHT160-80PLUS80][MAX-MPDU-7991][MAX-A-MPDU-LEN-EXP7] |
Sounds great, maybe you could create pull request with this diff? |
ping @nbd168 |
Yes. But I need testers to see if there are improvements in all equipment that uses the MT7663/MT7613 chip. |
I use Xiaomi AX3200 (MT7622/MT7615) Could there be similar changes for this chip? How to find out the EEPROM size for MT7622? |
Is the EEPROM_SIZE for the mt7615 1024 or 1536 (same as mt7663)? |
If you have a MT7613/MT7663 based device, please test latest OpenWrt master. I've increased the EEPROM size without affecting MT7615 |
@nbd168 MT7615 eeprom can be even bigger (0x2600 bytes). This device. Upd. And this too. |
Hey, you may look at GPL code for your device. It's out of my knowledge, but MT7615 EEPROM has iPAiLNA, iPAeLNA, ePAiLNA and ePAeLNA. Looking at mt7615d GPL code, the ePAiLNA, and ePAeLNA has three files with 1200 bytes each, and the other has three files with 1024 bytes each Maybe the stock rom assembled all EEPROM binaries in a single file. |
Apparently everything is fine! |
Can #575 be related to this? |
I noticed that mt7663 tx power is really good with the current SNAPSHOT. Very nice and very closer to stock. Thanks, @nbd168! Also noticed that speed approximately the same with 40 and 80 MHz width. So 40 MHz might be even better. Can anyone else confirm this observations for 7612, 7615? |
@csharper2005 Sorry, I accidentally removed my post. Is it the latest snapshot? |
@sinancetinkaya, I've made a table:
|
I have UniElec u7621-06 16M with mini-PCIe cards: MT7602E, MT7612E 10 dbi antennas attached |
Guys, I tested 7602, 7603, 7612, 7615 myself and didn't find any problems with TX power with current SNAPSHOT. So I decided to close to issue. The finding with strange speed on 7613 and 40MHz / 80 MHz channel width should be investigated separately. |
Hi everybody,
I have had many mt7621 router with different combinations of wireless chips:
Problem:
Example
2 routers mt7603 + mt7615.
OpenWrt config - 20 dBm TX power
Stock config - according to documentation router has 100 mWt tx power (also 20 dBm).
Routers are in the same place. OpenWrt real TX power is lower:
Possible root causes
Do you have similar user experience? I found many similar tickets here and would like to take a closer look at this issue. Maybe someone has more accurate devices for estimating power than a phone.
@nbd168 maybe it's possible to define +delta dBm via dts or some configs? It would be safer than another hacks.
@ptpt52 what do you think?
The text was updated successfully, but these errors were encountered: