2.4ghz wireless interface can't start after after 22.03.1 upgrade MTC Wireless Router WR1201 #11736

F4HTB · 2023-01-08T20:39:41Z

Describe the bug

Hello dear All,

Without exposing all these adventures, I wanted to point out that the 2.4ghz wifi interface no longer start after an upgrade to version 22.03.1 on my WR1201.

I have at home an internet box followed by a WR1201 (called R1) with interfaces in bridge mode and on the remote site the reception is done with a bullet M2 ubiquiti with relayd (called R2) and an ipv6 dhcp interface which itself is connected to a last WR1201 (called R3) in wifi access point mode with bridge interfaces for the internal wifi distribution of the remote site.

I had to migrate to 22 because from 21 because there seemed to be another bug on 21.
As said above, I use to make a wifi bridge an M2 bullet and a second WR1201 router on the remote site.
When I migrated my bullet M2 from the original firmware to openWRT (latest 19.07.9 which works), the lan interface on the Bullet or WR1201 side was constantly switching to blocking and forwarding then blocking etc... I tried the Bullet (R2) on a classic switch, it works.
After having migrated my WR1201 (called R2), in 22, the problem was solved but this time it is the wifi interface of the WR1201 in 2.4ghz which does not start any more. Same problem found on my first WR1201 (called R1).

I therefore concluded that there is a problem of negotiation on the ethernet ports of the WR1201 in 21 solved in 22.
I therefore concluded that there is a problem on the 2.4ghz wifi interface on the WR1201 in 22 since noted twice.
I have test all available 22.X version, alwais same bug.

Thank you for your efforts, if anyone has an idea, I'm interested.

I can provide any additional log if you ever tell me where to look.

Cordially,
PS: Thanks to the creators of openWRT.

WR1201 :

Model MTC Wireless Router WR1201
Architecture MediaTek MT7621 ver:1 eco:3
Target Platform ramips/mt7621
Firmware Version OpenWrt 22.03.1 r19777-2853b6d652 / LuCI openwrt-22.03 branch git-22.245.77528-487e58a
Kernel Version 5.10.146
Here is log from WR1201 :

System Log

Sun Jan 8 21:16:21 2023 kern.err kernel: [ 57.999404] mt76x2e 0000:02:00.0: MCU message 02 (seq 11) timed out
Sun Jan 8 21:16:21 2023 kern.info kernel: [ 58.180732] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
Sun Jan 8 21:16:21 2023 kern.info kernel: [ 58.191725] mt76x2e 0000:02:00.0: Build: 1
Sun Jan 8 21:16:21 2023 kern.info kernel: [ 58.200245] mt76x2e 0000:02:00.0: Build Time: 201607111443____
Sun Jan 8 21:16:21 2023 kern.info kernel: [ 58.215283] mt76x2e 0000:02:00.0: Firmware running!
Sun Jan 8 21:16:21 2023 kern.info kernel: [ 58.229705] ieee80211 phy1: Hardware restart was requested
Sun Jan 8 21:16:22 2023 kern.err kernel: [ 59.279391] mt76x2e 0000:02:00.0: MCU message 02 (seq 14) timed out
Sun Jan 8 21:16:22 2023 kern.info kernel: [ 59.390692] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
Sun Jan 8 21:16:22 2023 kern.info kernel: [ 59.402334] mt76x2e 0000:02:00.0: Build: 1
Sun Jan 8 21:16:22 2023 kern.info kernel: [ 59.410706] mt76x2e 0000:02:00.0: Build Time: 201607111443____
Sun Jan 8 21:16:22 2023 kern.info kernel: [ 59.425905] mt76x2e 0000:02:00.0: Firmware running!
Sun Jan 8 21:16:22 2023 kern.info kernel: [ 59.439745] ieee80211 phy1: Hardware restart was requested
Sun Jan 8 21:16:23 2023 kern.err kernel: [ 60.479508] mt76x2e 0000:02:00.0: MCU message 02 (seq 2) timed out
Sun Jan 8 21:16:23 2023 kern.info kernel: [ 60.611017] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
Sun Jan 8 21:16:23 2023 kern.info kernel: [ 60.622128] mt76x2e 0000:02:00.0: Build: 1
Sun Jan 8 21:16:23 2023 kern.info kernel: [ 60.630377] mt76x2e 0000:02:00.0: Build Time: 201607111443____
Sun Jan 8 21:16:23 2023 kern.info kernel: [ 60.645490] mt76x2e 0000:02:00.0: Firmware running!
Sun Jan 8 21:16:23 2023 kern.info kernel: [ 60.659721] ieee80211 phy1: Hardware restart was requested
Sun Jan 8 21:16:24 2023 kern.err kernel: [ 61.759738] mt76x2e 0000:02:00.0: MCU message 02 (seq 5) timed out
Sun Jan 8 21:16:25 2023 kern.info kernel: [ 61.930730] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
Sun Jan 8 21:16:25 2023 kern.info kernel: [ 61.942111] mt76x2e 0000:02:00.0: Build: 1
Sun Jan 8 21:16:25 2023 kern.info kernel: [ 61.950369] mt76x2e 0000:02:00.0: Build Time: 201607111443____
Sun Jan 8 21:16:25 2023 kern.info kernel: [ 61.965605] mt76x2e 0000:02:00.0: Firmware running!
Sun Jan 8 21:16:25 2023 kern.info kernel: [ 61.979785] ieee80211 phy1: Hardware restart was requested
Sun Jan 8 21:16:26 2023 kern.err kernel: [ 63.039395] mt76x2e 0000:02:00.0: MCU message 02 (seq 8) timed out
Sun Jan 8 21:16:26 2023 kern.info kernel: [ 63.141014] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
Sun Jan 8 21:16:26 2023 kern.info kernel: [ 63.152086] mt76x2e 0000:02:00.0: Build: 1
Sun Jan 8 21:16:26 2023 kern.info kernel: [ 63.160344] mt76x2e 0000:02:00.0: Build Time: 201607111443____
Sun Jan 8 21:16:26 2023 kern.info kernel: [ 63.175406] mt76x2e 0000:02:00.0: Firmware running!
Sun Jan 8 21:16:26 2023 kern.info kernel: [ 63.189716] ieee80211 phy1: Hardware restart was requested

Kernel Log

[ 176.639140] ieee80211 phy1: Hardware restart was requested
[ 177.678915] mt76x2e 0000:02:00.0: MCU message 02 (seq 2) timed out
[ 177.800187] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 177.811168] mt76x2e 0000:02:00.0: Build: 1
[ 177.820093] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 177.835154] mt76x2e 0000:02:00.0: Firmware running!
[ 177.849111] ieee80211 phy1: Hardware restart was requested
[ 178.878912] mt76x2e 0000:02:00.0: MCU message 02 (seq 5) timed out
[ 179.010211] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 179.021188] mt76x2e 0000:02:00.0: Build: 1
[ 179.030109] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 179.045164] mt76x2e 0000:02:00.0: Firmware running!
[ 179.059113] ieee80211 phy1: Hardware restart was requested
[ 180.158955] mt76x2e 0000:02:00.0: MCU message 02 (seq 8) timed out
[ 180.330225] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 180.341209] mt76x2e 0000:02:00.0: Build: 1
[ 180.350140] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 180.365196] mt76x2e 0000:02:00.0: Firmware running!
[ 180.379109] ieee80211 phy1: Hardware restart was requested
[ 181.438917] mt76x2e 0000:02:00.0: MCU message 02 (seq 11) timed out
[ 181.540211] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 181.551208] mt76x2e 0000:02:00.0: Build: 1
[ 181.560136] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 181.575194] mt76x2e 0000:02:00.0: Firmware running!
[ 181.589096] ieee80211 phy1: Hardware restart was requested
[ 182.638911] mt76x2e 0000:02:00.0: MCU message 02 (seq 14) timed out
[ 182.750237] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 182.761263] mt76x2e 0000:02:00.0: Build: 1
[ 182.770180] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 182.785240] mt76x2e 0000:02:00.0: Firmware running!
[ 182.799095] ieee80211 phy1: Hardware restart was requested
[ 183.838915] mt76x2e 0000:02:00.0: MCU message 02 (seq 2) timed out
[ 183.960194] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 183.971170] mt76x2e 0000:02:00.0: Build: 1
[ 183.980114] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 183.995201] mt76x2e 0000:02:00.0: Firmware running!
[ 184.009099] ieee80211 phy1: Hardware restart was requested
[ 185.038901] mt76x2e 0000:02:00.0: MCU message 02 (seq 5) timed out
[ 185.170208] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 185.181191] mt76x2e 0000:02:00.0: Build: 1
[ 185.190132] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 185.205222] mt76x2e 0000:02:00.0: Firmware running!
[ 185.219095] ieee80211 phy1: Hardware restart was requested
[ 186.318900] mt76x2e 0000:02:00.0: MCU message 02 (seq 8) timed out
[ 186.490193] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 186.501170] mt76x2e 0000:02:00.0: Build: 1
[ 186.510118] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 186.525176] mt76x2e 0000:02:00.0: Firmware running!
[ 186.539120] ieee80211 phy1: Hardware restart was requested
[ 187.598904] mt76x2e 0000:02:00.0: MCU message 02 (seq 11) timed out
[ 187.700200] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[ 187.711183] mt76x2e 0000:02:00.0: Build: 1
[ 187.720130] mt76x2e 0000:02:00.0: Build Time: 201607111443____
[ 187.735188] mt76x2e 0000:02:00.0: Firmware running!
[ 187.749090] ieee80211 phy1: Hardware restart was requested

OpenWrt version

r19777-2853b6d652, r16688-fa9a932fdb

OpenWrt target/subtarget

ramips/mt7621

Device

MTC Wireless Router WR1201

Image kind

Official downloaded image

Steps to reproduce

Migrate MTC Wireless Router WR1201 from 21.x to 22.x

Actual behaviour

Wifi interface 2.4ghz dont start.

Expected behaviour

That this interface work as normal

Additional info

No response

Diffconfig

No response

Terms

I am reporting an issue for OpenWrt, not an unsupported fork.

F4HTB · 2023-01-08T20:42:13Z

cat /etc/config/wireless:
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11a'
option path '1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option htmode 'VHT80'
option channel '40'
option cell_density '0'

config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'F4HTB'
option encryption 'psk-mixed'
option key 'cce6f556c44a13c4c3f92dee67'
option disassoc_low_ack '0'

config wifi-device 'radio1'
option type 'mac80211'
option channel '11'
option hwmode '11g'
option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
option htmode 'HT40'
option cell_density '0'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'F4HTB'
option encryption 'psk-mixed'
option key 'cce6f556c44a13c4c3f92dee67'
option disassoc_low_ack '0'

DruvsEgo · 2023-01-08T21:10:32Z

Turn off and on from electricity or
do a reset and set up again, sometimes there are errors when saving or restoring settings.

DragonBluep · 2023-01-09T06:05:26Z

There is a conflict between option hwmode '11g' and option htmode 'HT40'. Please try to reset and reconfigure it in LuCI.

F4HTB · 2023-01-09T10:52:40Z

Dear all, Thanks for your replies.
I hav try a full reset and active the wireless interface.
Nothing nothing worked in your proposals.
After the reset it use this configuration:

config wifi-device 'radio0'
option type 'mac80211'
option path '1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option channel '36'
option band '5g'
option htmode 'VHT80'

config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'

config wifi-device 'radio1'
option type 'mac80211'
option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
option channel '1'
option band '2g'
option htmode 'HT20'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'

But does not work. I can't see OpenWrt in 2.4ghz and alwais same report in log:
Sun Jan 8 21:16:23 2023 kern.err kernel: [ 60.479508] mt76x2e 0000:02:00.0: MCU message 02 (seq 2) timed out

I think 0000:02:00.0 is option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'

Maybe another idea?

Many thanks for the help

khanjui · 2023-01-09T20:28:46Z

Latest snapshot should work fine with that chipset.

F4HTB · 2023-01-10T14:19:57Z

Thanks for reply.

I will try the snapshot asap and give you a repport, but for the moment i need something stable.
Do you think that I should write another ticket for the BULETT M2 about the lan interface problem in version after 19.7?

rwalli · 2023-02-02T17:53:37Z

Latest snapshot should work fine with that chipset.

I have a similar problem as @F4HTB but my router will start and lose 2.4ghz wireless with the same log entries after a few days.

what's your uptime with the snapshot?

khanjui · 2023-02-03T15:31:11Z

Latest snapshot should work fine with that chipset.

I have a similar problem as @F4HTB but my router will start and lose 2.4ghz wireless with the same log entries after a few days.

what's your uptime with the snapshot?

I don't have any "hardware restart" on my log and my uptime is almost 12 days. I stopped using 2.4 GHz, I only have 5 GHz AP on.

t0p4 · 2023-03-13T07:03:51Z

I have the same problem, the router loses the 2.4GHz wireless network with the same log entries. only reboot helps to start it but only for a few days

rwalli · 2023-03-13T08:30:03Z

only reboot helps to start

reboot did not help for me, only disconnecting power helps.

DragonBluep · 2023-03-13T10:59:10Z

Recently I suffered the same problem on a device. This is because the reset pin of PCIe NIC is not properly controlled. You can try to find it.
ref: 6f2c95f

F4HTB · 2023-03-13T11:01:12Z

@DragonBluep Many Thanks, but I think we are not competent enough to make the modification ourselves. :-)

DragonBluep · 2023-03-13T11:16:01Z

Try to boot your device until wireless is turned on.
Run this script to see which GPIO crash your wireless:

#!/bin/sh
GPIOCHIP=480
BASE=$(cat /sys/class/gpio/gpiochip${GPIOCHIP}/base)
NGPIO=$(cat /sys/class/gpio/gpiochip${GPIOCHIP}/ngpio)
max=$(($BASE+$NGPIO))
gpio=$BASE
while [ $gpio -lt $max ] ; do
	echo $gpio > /sys/class/gpio/export
	[ -d /sys/class/gpio/gpio${gpio} ] && {
		echo out > /sys/class/gpio/gpio$gpio/direction
 
		echo "[GPIO$gpio] Trying value 0"
		echo 0 > /sys/class/gpio/gpio$gpio/value
		sleep 5s

		echo $gpio > /sys/class/gpio/unexport
	}
	gpio=$((gpio+1))
done

If the script doesn't work, try to change the first line GPIOCHIP=448 or GPIOCHIP=416 and run again.

frollic · 2023-07-17T18:30:59Z

The radio seems to work in 23.05.0-RC2.

if we're meant to watch the system log while the script runs it's quite
impossible to see if any of these calls actually crash the radio, since it's
constantly looping.

root@OpenWrt:/tmp# ./a.sh
[GPIO480] Trying value 0
[GPIO481] Trying value 0
[GPIO482] Trying value 0
[GPIO483] Trying value 0
[GPIO484] Trying value 0
sh: write error: Resource busy
[GPIO485] Trying value 0
[GPIO486] Trying value 0
[GPIO487] Trying value 0
[GPIO488] Trying value 0
[GPIO489] Trying value 0
[GPIO490] Trying value 0
[GPIO491] Trying value 0
[GPIO492] Trying value 0
[GPIO493] Trying value 0
[GPIO494] Trying value 0
[GPIO495] Trying value 0
[GPIO496] Trying value 0
[GPIO497] Trying value 0
[GPIO498] Trying value 0
sh: write error: Resource busy
[GPIO500] Trying value 0
[GPIO501] Trying value 0
sh: write error: Resource busy
sh: write error: Resource busy
sh: write error: Resource busy
sh: write error: Resource busy
sh: write error: Resource busy
[GPIO507] Trying value 0
[GPIO508] Trying value 0
[GPIO509] Trying value 0
[GPIO510] Trying value 0
[GPIO511] Trying value 0

root@OpenWrt:/tmp# ./a.sh
[GPIO448] Trying value 0
[GPIO449] Trying value 0
[GPIO450] Trying value 0
[GPIO451] Trying value 0
sh: write error: Resource busy
[GPIO452] Trying value 0
[GPIO453] Trying value 0
[GPIO454] Trying value 0
[GPIO455] Trying value 0
[GPIO456] Trying value 0
[GPIO457] Trying value 0
[GPIO458] Trying value 0
[GPIO459] Trying value 0
[GPIO460] Trying value 0
[GPIO461] Trying value 0
[GPIO462] Trying value 0
[GPIO463] Trying value 0
[GPIO464] Trying value 0
[GPIO465] Trying value 0
[GPIO466] Trying value 0
[GPIO467] Trying value 0
[GPIO468] Trying value 0
[GPIO469] Trying value 0
[GPIO470] Trying value 0
[GPIO471] Trying value 0
[GPIO472] Trying value 0
[GPIO473] Trying value 0
[GPIO474] Trying value 0
[GPIO475] Trying value 0
[GPIO476] Trying value 0
[GPIO477] Trying value 0
[GPIO478] Trying value 0
[GPIO479] Trying value 0

root@OpenWrt:/tmp# ./a.sh
[GPIO416] Trying value 0
[GPIO417] Trying value 0
[GPIO418] Trying value 0
[GPIO419] Trying value 0
sh: write error: Resource busy
[GPIO420] Trying value 0
[GPIO421] Trying value 0
[GPIO422] Trying value 0
[GPIO423] Trying value 0
[GPIO424] Trying value 0
[GPIO425] Trying value 0
[GPIO426] Trying value 0
[GPIO427] Trying value 0
[GPIO428] Trying value 0
[GPIO429] Trying value 0
[GPIO430] Trying value 0
[GPIO431] Trying value 0
[GPIO432] Trying value 0
[GPIO433] Trying value 0
[GPIO434] Trying value 0
[GPIO435] Trying value 0
[GPIO436] Trying value 0
[GPIO437] Trying value 0
[GPIO438] Trying value 0
[GPIO439] Trying value 0
[GPIO440] Trying value 0
[GPIO441] Trying value 0
[GPIO442] Trying value 0
[GPIO443] Trying value 0
[GPIO444] Trying value 0
[GPIO445] Trying value 0
[GPIO446] Trying value 0
[GPIO447] Trying value 0
root@OpenWrt:/tmp#

DragonBluep · 2023-10-24T14:33:54Z

Please test this one. openwrt-mt76x2.tar.xz.zip

frollic · 2023-12-08T11:22:27Z

upgraded to 23.05.2, still working.

F4HTB added the bug issue report with a confirmed bug label Jan 8, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

2.4ghz wireless interface can't start after after 22.03.1 upgrade MTC Wireless Router WR1201 #11736

2.4ghz wireless interface can't start after after 22.03.1 upgrade MTC Wireless Router WR1201 #11736

F4HTB commented Jan 8, 2023

F4HTB commented Jan 8, 2023

DruvsEgo commented Jan 8, 2023

DragonBluep commented Jan 9, 2023

F4HTB commented Jan 9, 2023

khanjui commented Jan 9, 2023

F4HTB commented Jan 10, 2023

rwalli commented Feb 2, 2023

khanjui commented Feb 3, 2023

t0p4 commented Mar 13, 2023

rwalli commented Mar 13, 2023

DragonBluep commented Mar 13, 2023

F4HTB commented Mar 13, 2023

DragonBluep commented Mar 13, 2023

frollic commented Jul 17, 2023 •

edited

DragonBluep commented Oct 24, 2023

frollic commented Dec 8, 2023

2.4ghz wireless interface can't start after after 22.03.1 upgrade MTC Wireless Router WR1201 #11736

2.4ghz wireless interface can't start after after 22.03.1 upgrade MTC Wireless Router WR1201 #11736

Comments

F4HTB commented Jan 8, 2023

Describe the bug

OpenWrt version

OpenWrt target/subtarget

Device

Image kind

Steps to reproduce

Actual behaviour

Expected behaviour

Additional info

Diffconfig

Terms

F4HTB commented Jan 8, 2023

DruvsEgo commented Jan 8, 2023

DragonBluep commented Jan 9, 2023

F4HTB commented Jan 9, 2023

khanjui commented Jan 9, 2023

F4HTB commented Jan 10, 2023

rwalli commented Feb 2, 2023

khanjui commented Feb 3, 2023

t0p4 commented Mar 13, 2023

rwalli commented Mar 13, 2023

DragonBluep commented Mar 13, 2023

F4HTB commented Mar 13, 2023

DragonBluep commented Mar 13, 2023

frollic commented Jul 17, 2023 • edited

DragonBluep commented Oct 24, 2023

frollic commented Dec 8, 2023

frollic commented Jul 17, 2023 •

edited