Skip to content
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

FS#557 - Nexx wt3020 wifi rx sensitivity low with LEDE 17.01 #8007

Closed
openwrt-bot opened this issue Feb 26, 2017 · 17 comments
Closed

FS#557 - Nexx wt3020 wifi rx sensitivity low with LEDE 17.01 #8007

openwrt-bot opened this issue Feb 26, 2017 · 17 comments
Labels

Comments

@openwrt-bot
Copy link

Greybeard:

The rx sensitivity reported by a Nexx wt3020 is ~ 20dB lower than a comparable tp-link device located sided by side with the Nexx wt3020.
There have been reports of a similar problem with OpenWRT versions.

There is a ticket open with openwrt with a similar reported issue https://dev.openwrt.org/ticket/20369 as well as on the openwrt forum https://forum.openwrt.org/viewtopic.php?id=69042

lede trunk (and openwrt trunk) as of 24/2/17 also display similar poor rx sensitivity.

@openwrt-bot
Copy link
Author

psyborg55:

you need to use this patch lede-project/source@b367eef

@openwrt-bot
Copy link
Author

fabianhu:

I tried hard by setting my repo to the commit mentioned by @psyborg55.
Unfortunately the same result like HEAD (080c6fa):

with LEDE (luci): I see only my own AP with 75% signal strength at < 1m distance
At 5m distance I have no stable connection.

With the original FW I see ~10 more from my neighbors.

does anyone have any directions for me?

@openwrt-bot
Copy link
Author

rogerpueyo:

The patch mentioned above was commited to the master branch, so the snapshot builds already have it.

You may want to give the snapshot compilation a try (if you are familiar with the command line, as they don't include the web GUI). You can find them at https://downloads.lede-project.org/snapshots/targets/ramips/mt7620/.

Try flashing both 17.01.0 and the snapshot and check if there are any differences.

@openwrt-bot
Copy link
Author

Greybeard:

See my comment in the original bug report. No difference between 17.01.0 and snapshot as of 24/2/17. The patch indicates it was committed 20/1/17 so it should have been in the 24//17 snapshot that I tested with.

@openwrt-bot
Copy link
Author

nbd:

Please try the latest snapshot

@openwrt-bot
Copy link
Author

Greybeard:

Tried with LEDE Reboot SNAPSHOT r3975-97d1c49
RX signal still poor
Also noted that with country code set to AU, TX power can supposedly be set to 36dBm!

root@LEDE:~# iw list
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short long limit: 2
Coverage class: 0 (up to 0m)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x2fe
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 2-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 2 usec (0x04)
HT TX/RX MCS rate indexes supported: 0-15, 32
Frequencies:
* 2412 MHz [1] (36.0 dBm)
* 2417 MHz [2] (36.0 dBm)
* 2422 MHz [3] (36.0 dBm)
* 2427 MHz [4] (36.0 dBm)
* 2432 MHz [5] (36.0 dBm)
* 2437 MHz [6] (36.0 dBm)
* 2442 MHz [7] (36.0 dBm)
* 2447 MHz [8] (36.0 dBm)
* 2452 MHz [9] (36.0 dBm)
* 2457 MHz [10] (36.0 dBm)
* 2462 MHz [11] (36.0 dBm)
* 2467 MHz [12] (36.0 dBm)
* 2472 MHz [13] (36.0 dBm)
* 2484 MHz [14] (disabled)
valid interface combinations:
* #{ managed, AP, mesh point } <= 8,
total <= 8, #channels <= 1
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing

@openwrt-bot
Copy link
Author

psyborg55:

next time indicate in your issue report your device use MT7620N

@openwrt-bot
Copy link
Author

Greybeard:

Yes Sir

@openwrt-bot
Copy link
Author

psyborg55:

can you post RF calibration data from your device?

@openwrt-bot
Copy link
Author

Greybeard:

Can point me to info about how to get the rf cal data? I've done a quick search on the lede forum but haven't found anything so far.

@openwrt-bot
Copy link
Author

psyborg55:

run from ssh console: dd if=/dev/mtd2 of=/tmp/mtd2
scp mtd2 file to your PC and post here

@openwrt-bot
Copy link
Author

Greybeard:

result of mtd2 download uploaded

@openwrt-bot
Copy link
Author

psyborg55:

add chanregs 14, 17 and 18 to your rt2800lib.c file like this and rebuild image:

	if (rt2x00_has_cap_external_lna_bg(rt2x00dev)) {
		rt2800_bbp_write(rt2x00dev, 75, 0x68);
		rt2800_bbp_write(rt2x00dev, 76, 0x4C);
		rt2800_bbp_write(rt2x00dev, 79, 0x1C);
		rt2800_bbp_write(rt2x00dev, 80, 0x0C);
		rt2800_bbp_write(rt2x00dev, 82, 0xB6);
	} else {
		rt2800_rfcsr_write_chanreg(rt2x00dev, 14, 0x66);
		rt2800_rfcsr_write_chanreg(rt2x00dev, 17, 0x20);
		rt2800_rfcsr_write_chanreg(rt2x00dev, 18, 0x42);
	}

try checking again if the RSSI got any better

@openwrt-bot
Copy link
Author

Greybeard:

Built a dev system and made the suggested changes in ~/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7620/compat-wireless-2017-01-31/drivers/net/wireless/ralink/rt2x00/rt2800lib.c around line 5287

flashed the wt3020 device and rx signal strength reported as -64/68 compared to -64/66 with 17.01.2 and snapshot r4741-7a8909411c near enough to no change.

As a check a physically adjacent device (a5v11) reports rx signal strength ~-44.

Both wt3020 and a5v11 have rx signal on wr842 (ap) as ~-40.

@openwrt-bot
Copy link
Author

psyborg55:

this is the report i got about mt7620n devices. probably unrelated at all to these registers

@openwrt-bot
Copy link
Author

Greybeard:

I won't be able to get back to this for a couple of weeks. I read a suggestion that the code by padavan doesn't have this issue. I'll see if I can get a copy and do some comparisons to see if there is anything obvious and/or try the code.

@openwrt-bot
Copy link
Author

Greybeard:

Issue still present in 18.06.1
It isn't an issue with a specific device as I have a new device and the reported low rx sensitivity is still present.
Unfortunately I neglected to check with the oem firmware before loading 18.06.1 so it is unknown if oem firmware is any diferent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant