Various issues with 5Ghz MT7610E #227

ffrediani · 2019-01-07T19:14:04Z

Using a TP-Link Archer C20 v4 with MT7610E I have installed kmod-mt76x0e which doesn't come by default and it detects the 5Ghz card. Configuring it it works to connect but a few minutes after booting the router the 5 Ghz SSID disappear and doesn't come back soon.

Sometimes the SSID may appear again but for short periods and then disappear again, very intermittently, therefore it is unusable.
Tested with Wifi Analyser and the SSID isn't even advertised.

I tried various different configurations as such:

Changing the mode from AC to N
Using 40 Mhz channel
Changing the channel to use the groups 36-64, 100-140 and 149-165 but made no difference
Changing the Transmit Power from Auto to different levels, but although it shows it on LuCI it doesn't seem to make any difference on the power signal.

If I am not wrong the Maximum Transmit Power for this card is 13dBm but it is possible to configure it with more and it shows up more under "iwinfo wlan1 info"

Also the Scan option doesn't seem to work either.

@nbd168 did you mentioned recently some work has been done on this driver asking us to test or am I mistaken and confused with other chip ? Is there anything else other than related here that is worth to give attention ?

ffrediani · 2019-01-29T13:01:59Z

Hello @nbd168 after upgrading to aa470d8 the same issue happens using various different configurations for this radio.
The SSID barely advertises and appears as available for connecting. It stays invisible or not working most of the time (not even Wifi Analyser detects it). If it appears again it doesn't last much and therefore it is still unusable.

Let us know of anything significant about the improvements for it or any specific feedback you may require we can provide accurately.

Alpha2121 · 2019-03-06T16:54:09Z

I have a c20 v1 with same 5ghz chipset and kmod-mt76x0e driver isn't doing anything for me. I installed latest snapshot with kmod-mt76x0e pre installed, yet the 5ghz radio isn't showing up under wireless settings.. What am i doing wrong?

ffrediani · 2019-03-26T19:17:17Z

Hello @nbd168
Not sure if you have been doing any work on this recently but wanted to feedback that I have done successive upgrades to snapshot version to this TP-Link C20 v4 with kmod-mt76x0e driver now coming by default in the image and had zero improvements since them. Currently using 6fc50ea and Kernel 4.14.107 but all symptoms I have reported in the first message seem to be still present.

Can't make a simple scan, SSID disappear, doesn't connect at all regardless the channel used, etc.

So although the 5Ghz radio is detected and appears in the system it remains unusable.
Let us know you output so we can provide more fine feedback in order to help advance with this driver.

ffrediani · 2019-06-25T14:28:11Z

This issue should never beem closed. It remains the same and MT7610E keeps not working properly at all. It is detected by default snapshot but doesn't work and has the same issues reported.

@nbd168 have you or anyone done any work about this driver ?

I believe the results will be the same if the radio hardware is the same regardless the router, but to mention in more detail the router in case is a TP-Link C20 v4

ffrediani · 2019-06-26T04:44:26Z

Just to update the thread I have updated to Snapshot r10348-577174cf60 with a recent mt76 fix and now it seems to be able to control the Transmit Power correctly. Also the Scan button that has never worked correctly seems to work now.
Will keep testing the other issues found to see if they were fixed.

xavier83 · 2019-09-14T05:05:47Z

Seem like I'm experiencing the same issue but on a different radio.

#199

David-S-McKellen · 2019-09-25T06:22:17Z

I have a c20 v1 with same 5ghz chipset and kmod-mt76x0e driver isn't doing anything for me. I installed latest snapshot with kmod-mt76x0e pre installed, yet the 5ghz radio isn't showing up under wireless settings.. What am i doing wrong?

Hi there I have the same problem
Already installed Kmod-mt76x0e and 5GHz radio isn't showing
Any Suggestion?
Thank you

AndyX90 · 2019-11-09T08:51:42Z

I have a c20 v1 with same 5ghz chipset and kmod-mt76x0e driver isn't doing anything for me. I installed latest snapshot with kmod-mt76x0e pre installed, yet the 5ghz radio isn't showing up under wireless settings.. What am i doing wrong?

Hi there I have the same problem
Already installed Kmod-mt76x0e and 5GHz radio isn't showing
Any Suggestion?
Thank you

Same for me. kmod-mt76x0e installed and no wifi showing.
DMESG-Output:

[ 14.531320] mt76x0e 0000:02:00.0: enabling device (0000 -> 0002)
[ 14.537510] mt76x0e 0000:02:00.0: ASIC revision: 76100002
[ 14.570734] mt76x0e 0000:02:00.0: Firmware Version: 0.1.00
[ 14.845282] mt76x0e 0000:02:00.0: driver does not support default EEPROM
[ 14.850755] mt76x0e: probe of 0000:02:00.0 failed with error -22

EDIT:
System Log:
Sat Nov 9 10:34:32 2019 daemon.notice procd: /etc/rc.d/S96led: Skipping trigger 'phy0tpt' for led 'wifi' due to missing kernel module

Lankaster · 2019-12-18T21:01:04Z

Same problem on Asus RT-AC51U, Openwrt 19.07 (commit d2d12346e8e6dd5fbb6befd4f9e3e1d5304a2e31)

[  112.353442] mt76x0e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[  112.366014] mt76x0e 0000:01:00.0: ASIC revision: 76100002
[  112.379113] mt76x0e 0000:01:00.0: Firmware Version: 0.1.00
[  112.476377] mt76x0e 0000:01:00.0: EEPROM data check failed: ffff
[  112.500587] mt76x0e 0000:01:00.0: driver does not support default EEPROM
[  112.514050] mt76x0e: probe of 0000:01:00.0 failed with error -22
[  112.542572] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[  112.557020] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[  112.572438] ieee80211 phy1: rt2800_init_eeprom: Error - Invalid RF chipset 0xffff detected
[  112.588875] ieee80211 phy1: rt2x00lib_probe_dev: Error - Failed to allocate device

wifi (both 2.4 & 5 ) doesn't work.

Lankaster · 2020-01-17T17:37:43Z

Same problem on Asus RT-AC51U, Openwrt 19.07 (commit d2d12346e8e6dd5fbb6befd4f9e3e1d5304a2e31)

[  112.353442] mt76x0e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[  112.366014] mt76x0e 0000:01:00.0: ASIC revision: 76100002
[  112.379113] mt76x0e 0000:01:00.0: Firmware Version: 0.1.00
[  112.476377] mt76x0e 0000:01:00.0: EEPROM data check failed: ffff
[  112.500587] mt76x0e 0000:01:00.0: driver does not support default EEPROM
[  112.514050] mt76x0e: probe of 0000:01:00.0 failed with error -22
[  112.542572] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[  112.557020] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[  112.572438] ieee80211 phy1: rt2800_init_eeprom: Error - Invalid RF chipset 0xffff detected
[  112.588875] ieee80211 phy1: rt2x00lib_probe_dev: Error - Failed to allocate device

wifi (both 2.4 & 5 ) doesn't work.

In my case calibration data was erased. Stock firmware shows wrong MAC adresses for LAN and WAN (00:11:11:11:11:11, 00:22:22:22:22:22)
hier ist bootlog with errors from stock FW

Aug  1 00:00:37 kernel: MT7610ap:[FullCalibration] Reload from flash! current channel : 42 
Aug  1 00:00:37 kernel: MT7610ap:<==== ReloadLowCalResult() 
Aug  1 00:00:37 kernel: MT7610ap:====> ReloadLowCalResult() 
Aug  1 00:00:37 kernel: MT7610ap:==== 2C70 [ffffffff] ,RXBackup [ffffffff]
Aug  1 00:00:37 kernel: MT7610ap:2C70 [ffffffff] not 0 , backup [ffffffff] 
Aug  1 00:00:37 kernel: MT7610ap:SYNC - BBP R4 to 20MHz.l
Aug  1 00:00:37 kernel: MT7610ap:FullCalibration():  docal = [ffff] valid bit[10]
Aug  1 00:00:37 kernel: MT7610ap:[FullCalibration] Reload from flash! current channel : 36 
Aug  1 00:00:37 kernel: MT7610ap:<==== ReloadLowCalResult() 
Aug  1 00:00:37 kernel: MT7610ap:====> ReloadLowCalResult() 
Aug  1 00:00:37 kernel: MT7610ap:==== 2C70 [ffffffff] ,RXBackup [ffffffff]
Aug  1 00:00:37 kernel: MT7610ap:2C70 [ffffffff] not 0 , backup [ffffffff] 
Aug  1 00:00:37 kernel: MT7610ap:==== 2C70 [ffffffff] ,RXBackup [ffffffff]
Aug  1 00:00:37 kernel: MT7610ap:2C70 [ffffffff] not 0 , backup [ffffffff] 
Aug  1 00:00:37 kernel: MT7610ap:FullCalibration():  docal = [ffff] valid bit[10]
Aug  1 00:00:37 kernel: MT7610ap:[FullCalibration] Reload from flash! current channel : 40 
Aug  1 00:00:37 kernel: MT7610ap:<==== ReloadLowCalResult() 
Aug  1 00:00:37 kernel: MT7610ap:====> ReloadLowCalResult() 
Aug  1 00:00:37 kernel: MT7610ap:==== 2C70 [ffffffff] ,RXBackup [ffffffff]
Aug  1 00:00:37 kernel: MT7610ap:2C70 [ffffffff] not 0 , backup [ffffffff]

ffrediani · 2020-04-04T20:23:56Z

Hello @nbd168
I have a newer report about remaining issues related to MT7610E.
Just for reference the device used here is a TP-Link C20 v4
This was tested with OpenWrt 18.06.8 (installing the extra kmod-7610e package driver) and with 19.07.0 and 19.07.2

When trying to set the channel for 5Ghz radio. It simply doesn't let you do that. You must use it in Auto otherwise when the device boots up the 5Ghz radius simply doesn't broadcast SSID and no clients can connect.
I tried set several different channels from all three groups: 36-64, 100-140 and 149-165 and it didn't work at all. Only if I leave it configured on auto. When set in Auto it always default to channel 36.
When the device boots it may take a little while for the radio to start working and to let clients connect.

Below is my /etc/config/wireless relevant part for the 5Ghz radio:

config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11a'
option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
option country 'US'
option distance '150'
option beacon_int '70'
option txpower '18'
option channel 'auto'
option legacy_rates '0'
option htmode 'VHT40'
option __toggle 'Enable'

rimil0uz · 2020-05-04T11:59:19Z

Hello @nbd168
I have a newer report about remaining issues related to MT7610E.
Just for reference the device used here is a TP-Link C20 v4
This was tested with OpenWrt 18.06.8 (installing the extra kmod-7610e package driver) and with 19.07.0 and 19.07.2

When trying to set the channel for 5Ghz radio. It simply doesn't let you do that. You must use it in Auto otherwise when the device boots up the 5Ghz radius simply doesn't broadcast SSID and no clients can connect.
I tried set several different channels from all three groups: 36-64, 100-140 and 149-165 and it didn't work at all. Only if I leave it configured on auto. When set in Auto it always default to channel 36.
When the device boots it may take a little while for the radio to start working and to let clients connect.

Below is my /etc/config/wireless relevant part for the 5Ghz radio:

config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11a'
option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
option country 'US'
option distance '150'
option beacon_int '70'
option txpower '18'
option channel 'auto'
option legacy_rates '0'
option htmode 'VHT40'
option __toggle 'Enable'

I have exactly the same issue with WAVLINK-WN570HA1 using OpenWRT 19.07.2 Master. If i change channels on 5ghz network the radio can't be started. What's more with the radio set on auto. It allows me to connect for a short time and then in like 5 minutes it starts failing, my devices start needing more than one attemp to connect and late are not able to connect at all. With the radio not showing anymore.

ffrediani · 2020-05-04T19:06:56Z

It was announced today in the OpenWrt-Devel list that there is a plan to release 19.07.3 and 18.06.9 soon. It would be interesting if these issues could be fixed before that happens so they are included in these newer builds.

LorenzoBianconi · 2020-05-05T12:06:17Z

Same problem on Asus RT-AC51U, Openwrt 19.07 (commit d2d12346e8e6dd5fbb6befd4f9e3e1d5304a2e31)

[  112.353442] mt76x0e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[  112.366014] mt76x0e 0000:01:00.0: ASIC revision: 76100002
[  112.379113] mt76x0e 0000:01:00.0: Firmware Version: 0.1.00
[  112.476377] mt76x0e 0000:01:00.0: EEPROM data check failed: ffff
[  112.500587] mt76x0e 0000:01:00.0: driver does not support default EEPROM
[  112.514050] mt76x0e: probe of 0000:01:00.0 failed with error -22
[  112.542572] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[  112.557020] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[  112.572438] ieee80211 phy1: rt2800_init_eeprom: Error - Invalid RF chipset 0xffff detected
[  112.588875] ieee80211 phy1: rt2x00lib_probe_dev: Error - Failed to allocate device

wifi (both 2.4 & 5 ) doesn't work.

@Lankaster have you been able to restore it? what is the tx power @ 5GHz?

Lankaster · 2020-05-05T16:34:39Z

@LorenzoBianconi I bought RT-AC51U with erased calibration data partition. Unfortunately it doesn't possible to do something (see my comment from 17 Jan)

LorenzoBianconi · 2020-05-05T17:00:29Z

@LorenzoBianconi I bought RT-AC51U with erased calibration data partition. Unfortunately it doesn't possible to do something (see my comment from 17 Jan)

My current issue is the tx power on 5GHz band is very weak. IIUC your device has been shipped with corrupted calibration data or has the factory partition been wiped? In the latter case, do you remember what was the signal strength using the stock firmware?

Lankaster · 2020-05-05T17:42:13Z

@LorenzoBianconi factory partition was wiped. Default APs on stock firmware wasn't visible. It didn't make sense for me check something more.

LorenzoBianconi · 2020-05-05T18:01:01Z

@Lankaster I can share my factory partition if you want to try to restore it

senol9000 · 2020-05-11T23:00:39Z

Hi there,
I was facing the disappearing 5Ghz band issue in stock firmware(tp link c20i) so i wanted to try openwrt.
After flashing 19.07 Lede, 5ghz seams to working fine , no dissapering any more however, 5ghz working laggy. Getting too many lost packets when i trying to ping the router.

rimil0uz · 2020-05-14T20:01:24Z

I went back to "original" firmware. And on my Wavlink ac600. I said "" cos could not find the firmware in wavlink website and just downloaded one I found... link: here

The original firmware is really buggy, however the 5GHZ wifi unlike than on Openwrt 19.07.2 works great...

ffrediani · 2020-05-14T20:04:31Z

@nbd168 are you following this ? It would be great to have you input on it as author of mt76
Let me know.

amk316 · 2020-05-18T12:04:51Z

i noticed than i can connect to device after a reboot no problem, but if i reconnect there is no traffic go throw even the wifi is connected.
i also noticed my Samsung S10 do not have any problem, it connect all the time!!

rimil0uz · 2020-05-20T20:33:10Z

Upgraded to Openwrt 19.07.3 still same problem. If i change channer radio fails to boot, if I dont (auto 36) its too weak and authentifications fails.

juhench · 2020-09-08T23:45:10Z

The issue is also present on the Zyxel NBG6515.
openwrt 19.07.03:

[   12.748223] mt76x0e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[   12.760867] mt76x0e 0000:01:00.0: ASIC revision: 76100002
[   12.797555] mt76x0e 0000:01:00.0: Firmware Version: 0.1.00
[   12.869106] urngd: jent-rng init failed, err: 2
[   12.946854] mt76x0e 0000:01:00.0: driver does not support default EEPROM
[   12.960368] mt76x0e: probe of 0000:01:00.0 failed with error -22
[   12.977888] kmodloader: done loading kernel modules from /etc/modules.d/*
[   21.470171] random: crng init done

Hardware on the Zyxel NBG6515:
MT7620A
MT7530WU (Switch)
MT7610EN (presumably handling all WiFi, 2.4 GHz, and 5 GHz?)

It is rather unfortunate, everything else seems to work.

juhench · 2020-09-17T21:53:31Z

Zyxel: NBG6515
The problem persists on 19.07.4. Having tried all driver combinations, WLAN still does not come up. Also, copying the stock "factory" contents to the flash does not change anything. Stock MTD was saved before flashing from TFTP-booted openWRT.

Ported from: openwrt#286 Should fix: openwrt#199 openwrt#227 At least fix problem on DIR-510L with 5GHz: clients most times can not connect. Detailed issue description openwrt#227 Also this duplicates: openwrt#287 but current code base does not have these changes.

suppenkasper0815 · 2021-11-04T14:23:51Z

Hi, yes I tried it also with factory radio again. There is now just 11 dBm again in "driver default" vaulue mode and still no connection to my router... I regred to have switched... before with 21.01 it was at least working and I can't remember what else I changed to bring it to fly...

Do you have progress in finding the issue?

Edit: Just a notice. To geht the 23 dBm for 5 GHz you need to change the values to "28". With these values I see at least 23 dBm in "default driver" mode, even when it is still not working again and I can only choose until 10 dBm in Drop Down.

ArtemiisFowl · 2021-11-04T14:26:21Z

Sounds not good.
I did not continue working at the problem since it works for me stable with high tx power for weeks now and i don't have the time for debugging this deep, i'm sorry :(

Devmax21 · 2021-11-30T20:27:03Z

Hi. I think that a function static inline s8 s6_to_s8(u32 val) in mt76x0/eeprom.h https://github.com/openwrt/mt76/blob/master/mt76x0/eeprom.h#L26 is wrong.
It should be

static inline s8 s6_to_s8(u32 val)
{
        s8 ret = val & GENMASK(6, 0);
        if (ret & BIT(6))
                ret -= BIT(6);
        return ret;
}

As you can see in archer c2 src
https://github.com/zaccareal/openwrt-archer-c2/blob/5d4302a487741edc367a0cd6f5e331cd7a8cde6d/package/mediatek/drivers/mt7610e/src/chips/mt76x0.c#L2933
we should check BIT(6) (40h) but not bit(5) (20h).
There is a patch for this issue. You can try it and check /sys/kernel/debug/ieee80211/phy0/mt76/rate_txpower
040-patch_eeprom.txt

Devmax21 · 2021-12-02T09:34:23Z

One more fix #632
With this fix I get a correct values

cat /sys/kernel/debug/ieee80211/phy0/mt76/rate_txpower 
       CCK:  1  1  1  1
      OFDM:  8  8  8  8  5  5  1  1
      STBC:  1  1  1  1  1  1  1  1  1  1
        HT:  8  8  8  8  5  5  1  1  1  1  1  1  1  1  1  1
       VHT:  8  8  8  8  5  5  1  1 28 28

Devmax21 · 2021-12-03T20:33:00Z

The my previous fixes are wrong. I think that some stock firmware doesn't use eeprom for power calculation. And mt76 can't calculate correct max power level based on eeprom.
We can add base power in code (7 for Archer c2 in my case)

--- a/mt76x0/eeprom.c   2021-11-30 21:18:06.227231124 +0200
+++ b/mt76x0/eeprom.c   2021-12-03 21:58:24.049096669 +0200
@@ -277,7 +277,7 @@
        }
 
        data = mt76x02_eeprom_get(dev, addr);
-       *tp = data >> (8 * idx);
+       *tp = (data >> (8 * idx)) + 7;
        if (*tp < 0 || *tp > 0x3f)
                *tp = 5;
 }

or use MT_EE_5G_TARGET_POWER and MT_EE_2G_TARGET_POWER as power for channels (0x1c in my case in eeprom for 5G).

--- a/mt76x0/eeprom.c   2021-11-30 21:18:06.227231124 +0200
+++ b/mt76x0/eeprom.c   2021-12-03 21:54:39.489338609 +0200
@@ -228,7 +228,7 @@
        int i, idx = 0;
        u16 data;
 
-       if (mt76x0_tssi_enabled(dev)) {
+       if (!mt76x0_tssi_enabled(dev)) {
                s8 target_power;
 
                if (chan->band == NL80211_BAND_5GHZ)

The result is, that txpower really increased.
But this is not fix. This is a hack)

Neustradamus · 2021-12-09T00:44:20Z

To follow this ticket

rozhuk-im · 2022-02-18T03:21:33Z

@Devmax21 thanks for trying, hope this may help.

MediaTek MT7610E, without any extra paches.

0db

       CCK: -18 -18 -18 -18
      OFDM: -18 -18 -18 -18 -18 -18 -18 -18
      STBC: -18 -18 -18 -18 -18 -18 -18 -18 -18 -18
        HT: -18 -18 -18 -18 -18 -18 -18 -18 -18 -18 -18 -18 -18 -18 -18 -18
       VHT: -18 -18 -18 -18 -18 -18 -18 -18 -18 -18

1db

       CCK: -16 -16 -16 -16
      OFDM: -16 -16 -16 -16 -16 -16 -16 -16
      STBC: -16 -16 -16 -16 -16 -16 -16 -16 -16 -16
        HT: -16 -16 -16 -16 -16 -16 -16 -16 -16 -16 -16 -16 -16 -16 -16 -16
       VHT: -16 -16 -16 -16 -16 -16 -16 -16 -16 -16

2db

       CCK: -14 -14 -14 -14
      OFDM: -14 -14 -14 -14 -14 -14 -14 -14
      STBC: -14 -14 -14 -14 -14 -14 -14 -14 -14 -14
        HT: -14 -14 -14 -14 -14 -14 -14 -14 -14 -14 -14 -14 -14 -14 -14 -14
       VHT: -14 -14 -14 -14 -14 -14 -14 -14 -14 -14

3db

       CCK: -12 -12 -12 -12
      OFDM: -12 -12 -12 -12 -12 -12 -12 -12
      STBC: -12 -12 -12 -12 -12 -12 -12 -12 -12 -12
        HT: -12 -12 -12 -12 -12 -12 -12 -12 -12 -12 -12 -12 -12 -12 -12 -12
       VHT: -12 -12 -12 -12 -12 -12 -12 -12 -12 -12

4db

       CCK: -10 -10 -10 -10
      OFDM: -10 -10 -10 -10 -10 -10 -10 -10
      STBC: -10 -10 -10 -10 -10 -10 -10 -10 -10 -10
        HT: -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10 -10
       VHT: -10 -10 -10 -10 -10 -10 -10 -10 -10 -10

5db

       CCK: -8 -8 -8 -8
      OFDM: -8 -8 -8 -8 -8 -8 -8 -8
      STBC: -8 -8 -8 -8 -8 -8 -8 -8 -8 -8
        HT: -8 -8 -8 -8 -8 -8 -8 -8 -8 -8 -8 -8 -8 -8 -8 -8
       VHT: -8 -8 -8 -8 -8 -8 -8 -8 -8 -8

6db

       CCK: -6 -6 -6 -6
      OFDM: -6 -6 -6 -6 -6 -6 -6 -6
      STBC: -6 -6 -6 -6 -6 -6 -6 -6 -6 -6
        HT: -6 -6 -6 -6 -6 -6 -6 -6 -6 -6 -6 -6 -6 -6 -6 -6
       VHT: -6 -6 -6 -6 -6 -6 -6 -6 -6 -6

7db

       CCK: -4 -4 -4 -4
      OFDM: -4 -4 -4 -4 -4 -4 -4 -4
      STBC: -4 -4 -4 -4 -4 -4 -4 -4 -4 -4
        HT: -4 -4 -4 -4 -4 -4 -4 -4 -4 -4 -4 -4 -4 -4 -4 -4
       VHT: -4 -4 -4 -4 -4 -4 -4 -4 -4 -5

8db

       CCK: -2 -2 -2 -2
      OFDM: -2 -2 -2 -2 -2 -2 -2 -2
      STBC: -2 -2 -2 -2 -2 -2 -2 -2 -2 -2
        HT: -2 -2 -2 -2 -2 -2 -2 -2 -2 -2 -2 -2 -2 -2 -2 -2
       VHT: -2 -2 -2 -2 -2 -2 -2 -2 -2 -5

9db

       CCK: -1 -1 -1 -1
      OFDM: -1 -1 -1 -1 -1 -1 -1 -1
      STBC: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
        HT: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
       VHT: -1 -1 -1 -1 -1 -1 -1 -1 -2 -5

rozhuk-im · 2022-02-18T10:04:12Z

F/W: http://www.netlab.linkpc.net/download/software/openwrt/DIR-510L/orig/mt8610.bin
Tool: https://github.com/rsa9000/mtkeepmgr

./mtkeepmgr -F mt8610.bin 
[EEPROM identification]
  ChipID        : 7610h
  Version       : 1.0
  Chip          : MT7610

[Device identification]
  MacAddr       : 00:0c:43:26:60:78
  PCIDevID      : 7610h
  PCIVenID      : 14C3h
  PCISubsysDevID: 7610h
  PCISubsysVenID: 14C3h
  USB Vendor ID : FFFFh
  USB Product ID: FFFFh

[ASIC data]
  CMB aux option: 1FFFh
  XTAL opt???   : FFEFh

[NIC configuration]
  Cfg0          : FD11h
    RxPath      : 1
    TxPath      : 1
    PA 2GHz     : Internal
    PA 5GHz     : External
    PA current  : 8 ma
  Cfg1          : 0808h
    RF Ctrl     : Driver
    Ext. TxALC  : Disable
    LNA 2GHz    : Internal
    LNA 5GHz    : External
    CardBus Acc.: Enable
    40MHz 2G SB : Disable
    40MHz 5G SB : Disable
    WPS button  : Disable
    40MHz 2GHz  : Enable
    40MHz 5GHz  : Enable
    Ant. divers.: Diversity
    Int. TxALC  : False
    Coexistance : False
    DAC test    : False
  Cfg2          : 00FFh
    RxStream    : 15
    TxStream    : 15
    CoexAnt     : False
    XtalOpt     : 0
    RxTempComp. : Enable
    CalibInFlash: False

[Misc params]
  FreqOffset    : 56h
  TempOffset    : -1

[Country region code]
  2GHz country  : 00h (#0)
  5GHz country  : 19h (#25)

[External LNA gain]
  2GHz (1-14)   : 00h (0 dB)
  5GHz (36-64)  : 0Bh (11 dB)
  5GHz (100-128): 08h (8 dB)
  5GHz (132-165): 04h (4 dB)
  5GHz mid chan : 64h (100)
  5GHz higt chan: 9Bh (155)

[BBP RSSI offsets]
  2GHz Offset0  : 00h (0 dB)
  2GHz Offset1  : 00h (0 dB)
  5GHz Offset0  : 00h (0 dB)
  5GHz Offset1  : 00h (0 dB)

[Tx power target]
  2GHz (20MHz)  : FFh (16.0 dBm, default)
  5GHz (20MHz)  : 1Ah (13.0 dBm)

[Tx power delta]
  2GHz 20/40MHz : FFh (0.0 dBm, default)
  5GHz 20/40MHz : 80h (+0.0 dBm)
  5GHz 20/80MHz : 81h (-0.5 dBm)

[Per channel power table]
  Subband: 2.4 GHz
  Channel:     1    2    3    4    5    6    7    8    9   10   11   12   13   14
  Raw    :   00h  00h  00h  00h  00h  00h  00h  00h  00h  00h  00h  00h  00h  00h
  Pwr,dBm:   2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5
  Subband: 5 GHz (low)
  Channel:    36   38   40   44   46   48   52   54   56   60   62   64
  Raw    :   12h  12h  12h  12h  12h  12h  11h  11h  11h  11h  11h  11h
  Pwr,dBm:   9.0  9.0  9.0  9.0  9.0  9.0  8.5  8.5  8.5  8.5  8.5  8.5
  Subband: 5 GHz (middle)
  Channel:   100  102  104  108  110  112  116  118  120  124  126  128  132  134  136  140
  Raw    :   02h  02h  02h  02h  02h  02h  03h  03h  03h  03h  03h  03h  03h  03h  03h  04h
  Pwr,dBm:   1.0  1.0  1.0  1.0  1.0  1.0  1.5  1.5  1.5  1.5  1.5  1.5  1.5  1.5  1.5  2.0
  Subband: 5 GHz (hight)
  Channel:   149  151  153  157  159  161  165  167  169  171  173
  Raw    :   04h  04h  04h  05h  05h  05h  05h  FFh  FFh  FFh  FFh
  Pwr,dBm:   2.0  2.0  2.0  2.5  2.5  2.5  2.5  2.5  2.5  2.5  2.5

[Per rate power table]
                  .---------- Raw --------..--------- Power, dBm --------.
                  | 2.4GHz|   5GHz|   STBC||   2.4GHz|     5GHz|     STBC|
  CCK 1M/2M       :    00h                        0.0                     
  CCK 5.5M/11M    :    00h                        0.0                     
  OFDM 6M/9M      :    00h     00h                0.0       0.0           
  OFDM 12M/18M    :    00h     00h                0.0       0.0           
  OFDM 24M/36M    :    00h     00h                0.0       0.0           
  OFDM 48M/54M    :    00h     00h                0.0       0.0           
  HT/VHT MCS 0/1  :    00h     00h     00h        0.0       0.0       0.0 
  HT/VHT MCS 2/3  :    00h     00h     00h        0.0       0.0       0.0 
  HT/VHT MCS 4/5  :    00h     00h     00h        0.0       0.0       0.0 
  HT/VHT MCS 6/7  :    00h     00h     00h        0.0       0.0       0.0 
  VHT MCS 8/9     :            3Fh                         -0.5           

[TSSI temperature compensation]
  Tx AGC step   : 1.0 dBm (default)
  5GHz boundary : 255 (channel)
  5GHz group 1  : {  -2   -2   -2   -2   -2   -2   -2   -1   -2   -2   -2   -2   -2   -2   -2}
  5GHz group 2  : {  -2   -2   -2   -2   -2   -2   -2   -1   -2   -2   -2   -2   -2   -2   -2}

Looks like eeprom load code is broken in driver.
I hope there is enough information to debug it.

theparasol · 2022-04-21T23:12:04Z

More research done here: #633

knuxyl · 2022-07-18T04:13:46Z

Same issue with a Wavlink AC600, it uses MT7610E for 5GHz.

vdemidov · 2022-08-23T11:27:59Z

Same issue with my Wavlink AC600 (WL-WN570HA1) on OpenWrt 22.03.0-rc6 r19590-042d558536

ffrediani · 2022-08-23T11:32:27Z

@vdemidov what issue exactlly ? Could you describe it please ?
Some of the issues previously reported seems to have been fixed in previous versions.

vdemidov · 2022-08-23T11:54:13Z

For 5Gz WiFi if I specifi channel differnt from "auto" - problems with client connection and data transfer only short time after router reboot. When I set Channel: "auto" and all other option to driver_default it's possible to connect but Iperf3 show very bad speed. Something like 700 kbit/s/ And connection very unstable.
For 2.4Gz WiFi all works as expected.
On OEM firmware 5Gz Wifi also works perfect up to 95 MBit/s

vdemidov · 2022-08-23T11:58:12Z

Sorry. But looks like with any setting it stop work after 5 minutes after reboot.
In dmesg:
[ 47.284699] br-lan: port 3(wlan1) entered blocking state
[ 47.295264] br-lan: port 3(wlan1) entered forwarding state
[ 51.771192] mt76x0e 0000:01:00.0: MAC error detected

Settings:
config wifi-device 'radio1'
option type 'mac80211'
option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
option band '5g'
option cell_density '0'
option channel 'auto'
option htmode 'VHT80'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option wmm '0'
option dtim_period '3'
option disassoc_low_ack '0'
option key '5gAccessKey'
option ssid '5G'
option encryption 'psk2+ccmp'

vdemidov · 2022-08-23T12:21:49Z

Iperf3 Result
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 344 KBytes 2.81 Mbits/sec 0 37.1 KBytes
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 0 68.4 KBytes
[ 5] 2.00-3.00 sec 117 KBytes 959 Kbits/sec 0 125 KBytes
[ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 0 125 KBytes
[ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 125 KBytes
[ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec 1 125 KBytes
[ 5] 6.00-7.00 sec 117 KBytes 958 Kbits/sec 0 125 KBytes
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 125 KBytes
[ 5] 8.00-9.00 sec 117 KBytes 958 Kbits/sec 0 125 KBytes
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 0 125 KBytes
[ 5] 10.00-11.00 sec 117 KBytes 958 Kbits/sec 0 125 KBytes
[ 5] 11.00-12.00 sec 117 KBytes 958 Kbits/sec 0 125 KBytes
[ 5] 12.00-13.00 sec 0.00 Bytes 0.00 bits/sec 0 125 KBytes
[ 5] 13.00-14.00 sec 128 KBytes 1.05 Mbits/sec 0 125 KBytes
[ 5] 14.00-15.00 sec 123 KBytes 1.00 Mbits/sec 0 125 KBytes

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-15.00 sec 1.15 MBytes 644 Kbits/sec 1 sender
[ 5] 0.00-15.00 sec 948 KBytes 518 Kbits/sec receiver

thiagohd · 2022-08-23T12:29:49Z

@vdemidov can you confirm if your router doens't have problems with 2.4 GHz TX power? I have 3 Wavlink AC600 (WL-WN570HA1) as yours, and their TX power doesn't effectively change, even though I can "change" the power in LuCI to up to 30 dBm when the Country is configured as Taiwan. Stock firmware has a much stronger signal strength.

2.4G eeprom content:

root@OpenWrt_192:/sys/kernel/debug/ieee80211/phy0/mt76# hexdump eeprom
0000000 7628 0202 3f80 fd5d 2eb8 0000 0000 0000
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020 0000 0000 0020 0000 3f80 fd5d 2cb8 3f80
0000030 fd5d 2db8 3611 000e ffff 0100 0000 0000
0000040 0000 0011 0000 0000 0030 0000 0000 0000
0000050 0082 9400 b840 cac0 942a 9594 ca40 0002
0000060 0000 0000 0000 0000 0000 0000 0000 0000
*
00000a0 c6c6 c4c4 c0c4 c4c0 c4c4 c4c4 c0c0 0000
00000b0 0000 0000 0000 0000 0000 0000 0000 0000
00000c0 0311 1410 1014 0000 1a00 2a22 3531 3501
00000d0 4039 4d46 7f7f 007f 0000 0000 0000 0000
00000e0 1d11 1d11 351c 351c 351e 351e 1917 1917
00000f0 0002 0000 809e 8880 000a 0000 0000 0000
0000100 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000120 0000 0000 0000 0000 0000 0000 0000 0077
0000130 1d11 1d11 7f15 7f15 7f17 7f17 3b10 3b10
0000140 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000200 0000 0000 0000 0000 0000 0000 0000 0000
*
0000400

5G eeprom

root@OpenWrt_192:/sys/kernel/debug/ieee80211/phy1/mt76# hexdump eeprom
0000000 7610 0100 3f80 fd5d 2fb8 7610 14c3 0000
0000010 0000 7610 14c3 0000 0000 0c00 4643 0100
0000020 ffff 9fff ffef 3e30 9b3c ffff ffff ffff
0000030 ffff ffff fd11 1008 ffff 0149 ffff 9999
0000040 888c 07ff 0c00 0000 0b00 0000 0a00 ffff
0000050 80ff 0000 0000 0000 0000 0000 0000 0000
0000060 0000 0000 0000 0000 0000 0000 0000 ffff
0000070 ffff ffff ffff ffff 1a1b 1819 1617 1615
0000080 1816 1918 1717 1617 1616 1515 1415 1414
0000090 1313 1213 1312 1614 1716 ff19 ffff ffff
00000a0 ffff ffff ffff ffff ffff ffff ffff ffff
*
00000d0 ffff 811a 7440 0095 0000 0000 9b64 0000
00000e0 3d3d 3c00 3d3d 3c00 3d3d 3c00 3d3d 3c00
00000f0 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000120 0707 0004 0707 0004 0606 0004 ff3f ffff
0000130 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000200

vdemidov · 2022-08-23T12:38:15Z

@thiagohd How to check? I didn't see mach differnce in speed on 2.4Gz with OEM firmware but doesn't check this carefull.

vdemidov · 2022-09-13T09:33:48Z

After update to OpenWrt 22.03.0 r19685-512e76967f 5G wifi doesn't work.
config wifi-device 'radio1'
option type 'mac80211'
option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
option band '5g'
option cell_density '0'
option htmode 'VHT40'
option channel 'auto'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option disassoc_low_ack '0'
option encryption 'psk2+ccmp'
option key 'Password'

Log:

Tue Sep 13 12:26:39 2022 daemon.notice hostapd: wlan1: ACS-COMPLETED freq=5180 channel=36
Tue Sep 13 12:26:39 2022 daemon.notice hostapd: wlan1: interface state ACS->HT_SCAN
Tue Sep 13 12:26:40 2022 kern.info kernel: [65533.040155] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Tue Sep 13 12:26:40 2022 kern.info kernel: [65533.053002] br-lan: port 5(wlan1) entered blocking state
Tue Sep 13 12:26:40 2022 kern.info kernel: [65533.063576] br-lan: port 5(wlan1) entered forwarding state
Tue Sep 13 12:26:40 2022 daemon.notice netifd: Network device 'wlan1' link is up
Tue Sep 13 12:26:40 2022 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED
Tue Sep 13 12:26:40 2022 daemon.notice hostapd: wlan1: AP-ENABLED
Tue Sep 13 12:26:42 2022 kern.err kernel: [65534.529812] mt76x0e 0000:01:00.0: MAC error detected
Tue Sep 13 12:26:43 2022 kern.err kernel: [65535.549887] mt76x0e 0000:01:00.0: MAC error detected
Tue Sep 13 12:26:45 2022 kern.err kernel: [65537.669763] mt76x0e 0000:01:00.0: MAC error detected
Tue Sep 13 12:26:46 2022 kern.err kernel: [65539.009771] mt76x0e 0000:01:00.0: MAC error detected
Tue Sep 13 12:26:47 2022 kern.err kernel: [65540.249742] mt76x0e 0000:01:00.0: MAC error detected
Tue Sep 13 12:26:48 2022 kern.err kernel: [65541.259760] mt76x0e 0000:01:00.0: MAC error detected
Tue Sep 13 12:26:49 2022 kern.err kernel: [65542.269835] mt76x0e 0000:01:00.0: MAC error detected

Message "mt76x0e 0000:01:00.0: MAC error detected" repeat until disable 5G Wifi

Unknown78 · 2022-10-05T03:33:09Z

@ffrediani @nbd168 I'd like to install the latest openwrt on my TP-Link Archer C20 v4, but seeing how many issues there are in this thread, I'm worried for the stability.

Could we have a summary on what issues that've been fully fixed, partially fixed and still not fixed?

alexhorner · 2022-10-08T22:02:52Z

Just want to appear here with an issue on my TP-Link Archer C2

I have only just found this thread in the MT7610E, the C2 has a MT7610EN.

Seems to be specific devices which do not work with my MT7610EN, not sure how much information is particularly helpful, but here is the forum thread I started for my issue https://forum.openwrt.org/t/5ghz-not-working-with-only-some-devices-1-works-3-dont/139080

I doubt the information I have collected contributes significantly to this conversation, especially as I do not know what differentiates the working and non-working clients, but I am more than happy to do further testing. I would prefer not flashing too much onto this device as it is in active use at the moment, but if needs be I will.

alexhorner · 2022-10-09T16:14:34Z

Just want to appear here with an issue on my TP-Link Archer C2

I have only just found this thread in the MT7610E, the C2 has a MT7610EN.

Seems to be specific devices which do not work with my MT7610EN, not sure how much information is particularly helpful, but here is the forum thread I started for my issue https://forum.openwrt.org/t/5ghz-not-working-with-only-some-devices-1-works-3-dont/139080

I doubt the information I have collected contributes significantly to this conversation, especially as I do not know what differentiates the working and non-working clients, but I am more than happy to do further testing. I would prefer not flashing too much onto this device as it is in active use at the moment, but if needs be I will.

My connection issue appears to be resolved in the latest OpenWRT snapshot. Speeds don't appear to be the most amazing ever, capping out around 35Mbit/s between two clients on my device, but thats a whole lot better than nothing!

EDIT: I can also confirm that this is resolved (with the same speed warning) in stable release 22.03.1 too

suppenkasper0815 · 2022-11-07T17:29:50Z

Hey, thanks for your fast answer. I changed now the values from 0x8080 from 0C and 0E to 18 for all until 0x808F. I see a diffrence for channel 100. It increased from 10 dBm to 15 dBm, but not als you mentioned like 24 dBm oder maybe 30 dBm what is allowed. I also tried to change country code, no diffrences. Channel 36 and 52 are still untouched something with 10 dBm an 9 dBm in my case. also CH 132, 149 and 161 are unfortunately just 10 dBm. - I saw several more vaules with 0E in the following and pre-lines. Should I try to change these vaules also? - For me it was somehow clear when I saw the 0C vaules, that it means 10 dBm, but with 18 as you mentioned it should be 24 dBm (hex to dec). Any other ideas which vaules have to be set to solve it?

Update: Just wanna tell that I see no diffrence in behavior, when we change the hexcode like describes we'll see the 23 dBm, but there is not more TX-Power out of the device.

Edit: I did a wrong conclusion. There was a second route active which was able to transport 100 Mbit/s.

I think the driver problems have a lot to do with the DFS problem of Mt7610.

I have an spare Archer C2 here with original firmware and just noticed that's just possible to use ch 36-48 no other spektrum because of DFS. So I think that's unfortunate our major problem.

Anyway does someone know how to backup the mtd8 radio partition before flashing openwrt?

In WDS mode on channel 36 on my fritzbox 7490 the rx performance is around 300 Mbit/s measured with iperf3 and around 200 Mbit/s tx

cgm999 · 2022-11-08T07:59:52Z

@suppenkasper0815 try to fix the value for register 2320 with a shell script every second (check my other post about issues) .. and see if that makes your connection good

sanitariu · 2022-11-14T15:54:10Z

Still not working. Just tested latest git on a TP-Link Archer C20 version 5.
5Ghz -14 dbm which is 25 mw too low ! 5Ghz does not work / pass through walls so good as 2.4Ghz and
distributing the signal with even lower TX-Power makes it really bad after 4 meters away.
5Ghz on mediatek (7628) is not really usable at the moment.

Still the same today :) Seems like we will never have a good mediatek driver... or maybe these are mediatek possibilities :)

ffrediani · 2022-11-14T20:28:29Z

I guess after Mediatek ended their request to @nbd168 he did not develop it anymore.
We have tried to get some information from him a few times but either he doesn't want or is not willing to talk about.

sanitariu · 2022-11-21T11:05:27Z

This issue is similar to 633. I have now good results !!! Check this thread : #633

orangepizza mentioned this issue Jan 11, 2019

low tx power m7610e #216

Closed

ffrediani mentioned this issue Jan 29, 2019

2.4g issue remains #188

Closed

ffrediani mentioned this issue Apr 8, 2019

MT7628: Clients keep disconnecting. #169

Closed

ffrediani mentioned this issue Jun 25, 2019

mt76x0e - problem with 5GHz #275

Closed

Devmax21 mentioned this issue Dec 3, 2021

MT76x0: Correct s6_to_s8 function #631

Closed

dmsza mentioned this issue Dec 5, 2021

mt76 TX power not working in multiple chipsets (mt7610, mt7613, mt7615, mt7603) #633

Open

freed00m mentioned this issue Feb 7, 2022

mt76-tx phy1 Tainted #551

Open

DragonBluep mentioned this issue Apr 25, 2022

mt76x0: change Tx band power to 1 dBm per step #665

Closed

Various issues with 5Ghz MT7610E #227

Various issues with 5Ghz MT7610E #227

Comments

ffrediani commented Jan 7, 2019

ffrediani commented Jan 29, 2019

Alpha2121 commented Mar 6, 2019

ffrediani commented Mar 26, 2019

ffrediani commented Jun 25, 2019

ffrediani commented Jun 26, 2019 • edited Loading

xavier83 commented Sep 14, 2019 • edited Loading

David-S-McKellen commented Sep 25, 2019

AndyX90 commented Nov 9, 2019 • edited Loading

Lankaster commented Dec 18, 2019

Lankaster commented Jan 17, 2020

ffrediani commented Apr 4, 2020

rimil0uz commented May 4, 2020 • edited Loading

ffrediani commented May 4, 2020

LorenzoBianconi commented May 5, 2020

Lankaster commented May 5, 2020

LorenzoBianconi commented May 5, 2020

Lankaster commented May 5, 2020

LorenzoBianconi commented May 5, 2020

senol9000 commented May 11, 2020 • edited Loading

rimil0uz commented May 14, 2020 • edited Loading

ffrediani commented May 14, 2020

amk316 commented May 18, 2020

rimil0uz commented May 20, 2020

juhench commented Sep 8, 2020

juhench commented Sep 17, 2020

suppenkasper0815 commented Nov 4, 2021 • edited Loading

ArtemiisFowl commented Nov 4, 2021

Devmax21 commented Nov 30, 2021 • edited Loading

Devmax21 commented Dec 2, 2021

Devmax21 commented Dec 3, 2021

Neustradamus commented Dec 9, 2021

rozhuk-im commented Feb 18, 2022

rozhuk-im commented Feb 18, 2022

theparasol commented Apr 21, 2022 • edited Loading

knuxyl commented Jul 18, 2022

vdemidov commented Aug 23, 2022 • edited Loading

ffrediani commented Aug 23, 2022

vdemidov commented Aug 23, 2022

vdemidov commented Aug 23, 2022 • edited Loading

vdemidov commented Aug 23, 2022

thiagohd commented Aug 23, 2022

vdemidov commented Aug 23, 2022

vdemidov commented Sep 13, 2022 • edited Loading

Unknown78 commented Oct 5, 2022 • edited Loading

alexhorner commented Oct 8, 2022

alexhorner commented Oct 9, 2022 • edited Loading

suppenkasper0815 commented Nov 7, 2022 • edited Loading

cgm999 commented Nov 8, 2022

sanitariu commented Nov 14, 2022

ffrediani commented Nov 14, 2022

sanitariu commented Nov 21, 2022

ffrediani commented Jun 26, 2019 •

edited

Loading

xavier83 commented Sep 14, 2019 •

edited

Loading

AndyX90 commented Nov 9, 2019 •

edited

Loading

rimil0uz commented May 4, 2020 •

edited

Loading

senol9000 commented May 11, 2020 •

edited

Loading

rimil0uz commented May 14, 2020 •

edited

Loading

suppenkasper0815 commented Nov 4, 2021 •

edited

Loading

Devmax21 commented Nov 30, 2021 •

edited

Loading

theparasol commented Apr 21, 2022 •

edited

Loading

vdemidov commented Aug 23, 2022 •

edited

Loading

vdemidov commented Aug 23, 2022 •

edited

Loading

vdemidov commented Sep 13, 2022 •

edited

Loading

Unknown78 commented Oct 5, 2022 •

edited

Loading

alexhorner commented Oct 9, 2022 •

edited

Loading

suppenkasper0815 commented Nov 7, 2022 •

edited

Loading