MT7621 PCIe DTS issues. (MT76 stopped working with latest updates)

In one command:

$ git clone https://github.com/openwrt/openwrt.git -b openwrt-18.06

On the latest 18.06 still unable to get both wifi radios working. I can get the 2.4GHz to work using the below config, but 5GHz, while showing up as a radio, will not broadcast, only produces the error when I go to enable it:

Invalid sysfs path read for net/tmp.radio1

In my .dts file I have the following

&pcie {
	status = "okay";

	pcie0 {
		mt76@2,0 {
			reg = <0x0000 0 0 0 0>;
			device_type = "pci";
			mediatek,mtd-eeprom = <&factory 0x8000>;
			ieee80211-freq-limit = <2400000 2500000>;
		};
	};

	pcie1 {
		mt76@0,0 {
			reg = <0x0800 0 0 0 0>;
			device_type = "pci";
			mediatek,mtd-eeprom = <&factory 0x0000>;
			ieee80211-freq-limit = <5000000 6000000>;
		};
	};
};

Open to suggestions. Still not sure about the recent changes to the .dtsi files, or PCI driver. Does anyone know which part of this config specifies the sysfs path?

18.06 has no pci or DTS changes

Thanks @neheb, I have looked at the branches and seen the difference. Testing again on master. Does that mean I really don't need to have reg = <nnn>; in the .dts, since it is already specified in the .dtsi?

It's needed. That faulty patch removing all the reg entries was reverted.

Interesting. Then should it match up to what is in the .dtsi file? For example reg = <0x0000 0 0 0 0>; for pcie0, and reg = <0x0800 0 0 0 0>; for pcie1?

no i douibt it

Could I catch you on IRC sometime to ask you some questions about this?

I'm always on IRC

running 1806 on zbt-we1326 here and both wifi radio work, though 2.4Ghz performance is very very weak(sometimes 1Mbps?), 5G is better(40+Mbps), still far from what 11ac can provide, at least both radios are up, need do more performance testing

using stock firmware 2.4Ghz is much better(6x better), it runs an older version of openwrt(BB), mt76 still has lots of catch up to do at the moment as far as performance and stability goes(new mt76 loses connection sometimes too)

Hi,
compiled 18.06 late last week on my WE1326 with 7603/7612 wireless.
OpenWrt 18.06-SNAPSHOT r7108-dba362772e / LuCI openwrt-18.06 branch (git-18.163.60998-c379f00)

Comment: seems to run reasonably reliably. The router is used in a domestic situation, running off an Australian NBN Wireless modem. Not a very highly stressed usage, but everything appears to be working well.
I will re-compile when the source gets updated again, then load my other router, a 3526.

Thanks to the developers,
regards, Doug

Can you post /proc/interrupts output?

Hi,
sorry for the delay. Hope this is what you want:

           CPU0       CPU1       CPU2       CPU3       
  8:    2188857    2188839    2188832    2188824  MIPS GIC Local   1  timer
  9:     599492          0          0          0  MIPS GIC  63  IPI call
 10:          0    2640315          0          0  MIPS GIC  64  IPI call
 11:          0          0    3460655          0  MIPS GIC  65  IPI call
 12:          0          0          0    3139892  MIPS GIC  66  IPI call
 13:     538119          0          0          0  MIPS GIC  67  IPI resched
 14:          0     551493          0          0  MIPS GIC  68  IPI resched
 15:          0          0     605665          0  MIPS GIC  69  IPI resched
 16:          0          0          0     608033  MIPS GIC  70  IPI resched
 18:         12          0          0          0  MIPS GIC  33  ttyS0
 19:          0          0          0          0  MIPS GIC  27  1e130000.sdhci
 20:          0          0          0          0  MIPS GIC  29  xhci-hcd:usb1
 21:   17148195          0          0          0  MIPS GIC  10  1e100000.ethernet
 22:        189          0          0          0  MIPS GIC  30  gsw
 24:     879638          0          0          0  MIPS GIC  31  mt76x2e
 25:    1897372          0          0          0  MIPS GIC  32  mt7603e
ERR:         93

regards, Doug

running zbt1326 + 1806rc1 here with a few PCs, 2.4Ghz is pretty bad and disconnection happens a few times a day(I had to buy a tplink C7 today so we can at least have a reasonable good 2.4G network). have you stress tested your 2.4Ghz? I'm losing confidence on mt76/2.4Ghz with mt7603e chip at least, which this router, and xiaomi mifi 3G both use.

What's a good method to stress test the wireless?

I've tried the openwrt-18.06-rc2 image on a TP-Link RE350 today and noticed that the 5Ghz interface is missing.
Dmesg output: https://pastebin.com/5Lms2esB
Any ideas?

1 Like

Master snapshot doesnt work either: https://pastebin.com/Q9ZuCqgg

I pulled the main repository down yesterday, & got an error during compile. Not sure if that is related.
(pulled down from github).
My current WG3526 has Lede 18.06 that I compiled about a week ago. Everything runs, but for some reason the throughput is really slow. (Hence I was thinking of moving back to 17.01.5)
I am not an expert at this & just bumble along.....

regards, Doug

It seems 5Ghz completely dead on:
system type : MediaTek MT7620A ver:2 eco:6
machine : ZBT-WE826 (16M)

Relevant dmesg entries on boot:

[   11.545469] mt76x2e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[   11.551987] mt76x2e 0000:01:00.0: ASIC revision: 76120044
[   11.565118] mt76x2e 0000:01:00.0: ROM patch build: 20141115060606a
[   11.577024] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[   11.582708] mt76x2e 0000:01:00.0: Build: 1
[   11.586891] mt76x2e 0000:01:00.0: Build Time: 201507311614____
[   11.599992] mt76x2e 0000:01:00.0: Firmware running!
[   11.606108] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   11.633121] PPP generic driver version 2.4.2
[   11.643810] NET: Registered protocol family 24
[   11.773390] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[   11.780857] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[   11.788777] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
[   11.796511] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'

This is what i get when i try to activate interface in logread -f

root@OpenWrt:~# logread -f
Mon Oct 22 23:06:34 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Mon Oct 22 23:06:34 2018 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Mon Oct 22 23:06:34 2018 daemon.err hostapd: nl80211 driver initialization failed.
Mon Oct 22 23:06:34 2018 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Mon Oct 22 23:06:34 2018 daemon.notice hostapd: wlan0: AP-DISABLED
Mon Oct 22 23:06:34 2018 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Mon Oct 22 23:06:34 2018 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Mon Oct 22 23:06:34 2018 daemon.notice netifd: radio0 (18972): cat: can't open '/var/run/wifi-phy0.pid': No such file or directory
Mon Oct 22 23:06:34 2018 daemon.notice netifd: radio0 (18972): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process  path ()
Mon Oct 22 23:06:34 2018 daemon.notice netifd: radio0 (18972): Command failed: Invalid argument
Mon Oct 22 23:06:34 2018 daemon.notice netifd: radio0 (18972): Device setup failed: HOSTAPD_START_FAILED

Just set to enabled from default config:

root@OpenWrt:/tmp# cat /tmp/run/hostapd-phy0.conf
driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=US
ieee80211d=1
ieee80211h=1
hw_mode=a
beacon_int=100
channel=36


ieee80211n=1
ht_coex=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1]
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
ieee80211ac=1
vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3]

interface=wlan0
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
auth_algs=1
wpa=0
ssid=OpenWrt
bridge=br-lan
bssid=fd:ff:ff:ff:ff:ff

While wlan0 present when disabled, it disappears when i try to enable it

root@OpenWrt:/tmp# iw phy phy0 info
Wiphy phy0
	max # scan SSIDs: 4
	max scan IEs length: 2243 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 limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
	Band 1:
		Capabilities: 0x1ff
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT TX/RX MCS rate indexes supported: 0-15
		Frequencies:
			* 2412 MHz [1] (30.0 dBm)
			* 2417 MHz [2] (30.0 dBm)
			* 2422 MHz [3] (30.0 dBm)
			* 2427 MHz [4] (30.0 dBm)
			* 2432 MHz [5] (30.0 dBm)
			* 2437 MHz [6] (30.0 dBm)
			* 2442 MHz [7] (30.0 dBm)
			* 2447 MHz [8] (30.0 dBm)
			* 2452 MHz [9] (30.0 dBm)
			* 2457 MHz [10] (30.0 dBm)
			* 2462 MHz [11] (30.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
			* 2484 MHz [14] (disabled)
	Band 2:
		Capabilities: 0x1ff
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x018001b0):
			Max MPDU length: 3895
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Frequencies:
			* 5180 MHz [36] (23.0 dBm)
			* 5200 MHz [40] (23.0 dBm)
			* 5220 MHz [44] (23.0 dBm)
			* 5240 MHz [48] (23.0 dBm)
			* 5260 MHz [52] (23.0 dBm) (radar detection)
			* 5280 MHz [56] (23.0 dBm) (radar detection)
			* 5300 MHz [60] (23.0 dBm) (radar detection)
			* 5320 MHz [64] (23.0 dBm) (radar detection)
			* 5500 MHz [100] (23.0 dBm) (radar detection)
			* 5520 MHz [104] (23.0 dBm) (radar detection)
			* 5540 MHz [108] (23.0 dBm) (radar detection)
			* 5560 MHz [112] (23.0 dBm) (radar detection)
			* 5580 MHz [116] (23.0 dBm) (radar detection)
			* 5600 MHz [120] (23.0 dBm) (radar detection)
			* 5620 MHz [124] (23.0 dBm) (radar detection)
			* 5640 MHz [128] (23.0 dBm) (radar detection)
			* 5660 MHz [132] (23.0 dBm) (radar detection)
			* 5680 MHz [136] (23.0 dBm) (radar detection)
			* 5700 MHz [140] (23.0 dBm) (radar detection)
			* 5745 MHz [149] (30.0 dBm)
			* 5765 MHz [153] (30.0 dBm)
			* 5785 MHz [157] (30.0 dBm)
			* 5805 MHz [161] (30.0 dBm)
			* 5825 MHz [165] (30.0 dBm)
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 8,
		   total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

	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
	Device supports VHT-IBSS.

root@OpenWrt:/tmp# iw reg get
global
country US: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(57240 - 63720 @ 2160), (N/A, 40), (N/A)

Tried latest master snapshot, latest git for stable branch (18.06).

Can you comment on current state of WE1326. Did you ever got the 5ghz radio to work on it after?
I raised an issue on github