Rebooting loop Beryl AX (GL-MT3000)

defibos · 2022-12-20T18:33:47.340Z

Hi,
tested with the original charger, different generic usb-c PD chargers like Baseus, UGreen, Orico, … and usb-a chargers with 5V/3A, monitoring also the charge with usb power meters. Also power banks. And different types of cables.
This was my first guess, but not the issue.

defibos · 2022-12-20T18:35:18.425Z

defibos:

Tue Dec 20 12:51:18 2022 daemon.notice procd: /etc/rc.d/S15firmware.sh: grep: /etc/wireless/mediatek/mt7981.dbdc.b0.dat;/etc/wireless/mediatek/mt7981.dbdc.b1.dat: No such file or directory

Anyone getting this line?
Can anyone upload a healthy log file?
Thanks.

cafebug · 2022-12-20T19:05:55.734Z

Sorry, my Syslog was flooded by other repeated warning message, so no “normal” syslog for you.

I think the message is complaining about the 2 Wi-Fi data files are missing.

Can you check the 2 data files are located under the directory “/etc/wireless/mediatek” first ?
( mt7981.dbdc.b0.dat & mt7981.dbdc.b1.dat )

圖片790×292 35.2 KB

defibos · 2022-12-20T20:00:35.153Z

In a healthy boot I have those files

Screenshot_2022-12-20_19-55-20767×273 53.6 KB

However, as soon as I restart the healthy boot I enter in a loop of restarts.

cafebug · 2022-12-20T20:22:36.880Z

It seems our files are different in (date, size) ?
Can you check the ‘uname -a’ command to see if we are in the same firmware ?

圖片782×337 15 KB

jdub · 2022-12-20T20:36:07.465Z

FWIW, I’ve got the Nov 29 date, so yours may be the oddball, @cafebug.

image1148×484 88.8 KB

(also FWIW, I got mine before Nov 29, and the current firmware came out Dec 5, so I have no idea what the Nov 29 date actually represents.

defibos · 2022-12-20T20:39:33.951Z

My guess is that race condition during boot causing sometimes a failure because some files are not located. I attach 2 log collections:

fully healthy boot:
logread healthy.zip (27.6 KB)

several attempts with failures and a final sucess:
logread error and healthy (several attempts).zip (42.8 KB)

defibos · 2022-12-20T20:44:25.051Z

Probably compiled 29 Nov and released 5 Dec. They usually have a few days/1 week delay for stability checks.

I think they are not fully consistent with versioning for beta releases during the beta testing, that is why we have the 26Oct and 29Nov for 4.1.2. That is why it makes sense to add the md5/sha256.

jdub · 2022-12-20T21:02:50.058Z

Compile time shows as 12/5 though, not release time.

defibos · 2022-12-20T21:38:09.531Z

I get

Screenshot_2022-12-20_21-35-29

Screenshot_2022-12-20_21-36-06739×46 7.81 KB

Did you modify the /etc/wireless/meditak/ files?

jdub · 2022-12-20T21:48:29.413Z

No. I’m assuming the ones with the timestamps of basically now are auto updated by the OS.

cafebug · 2022-12-21T05:14:46.716Z

Well, I don’t touch any Mediatek file.

alex_zheng · 2022-12-21T09:17:01.525Z

Could you get some tools like PL2303 to get the sys log during startup(need to open the case )?

defibos · 2022-12-21T09:34:14.376Z

Hi,
I changed the log file to the external usb drive.
The log files attached above contain the logs with reboot attempts and a few successes (I logged to luci in the successes, which is logged).
I think the issue is related to the files described above not being found during the boot process.

What part is missing? Last line before crash?

JerryZhao · 2022-12-21T09:56:16.501Z

This is not the reason of reboot.
Could you connect UART to your router?

defibos · 2022-12-21T10:11:35.048Z

JerryZhao:

Could you connect UART to your router?

I have to order one.
It can take some days before I get the unit. Is there I can do meanwhile?

alex_zheng · 2022-12-21T10:11:56.689Z

I double Checked the log file. And there is no useful information for reboot problem. So I doubt whether it reboot or not.
Could you please tell me what phenomenon that make you think it rebooted?
Our engineer is also help to confirm the log file.

defibos · 2022-12-21T10:15:12.687Z

When you plug the device the lights start to indicate activity and the wifi networks appears after 20/30s. A few moments after that lights turn off and the cycle starts again.

alex_zheng · 2022-12-21T11:05:22.194Z

Thank you for the addition info . So maybe the device is not reboot. we wonder if the LED behaviour is wrong when the network is in the rebooting loop.
So the device is always in the loop or you need to do something to trigger it ?
Any device is pluging on the Beryl AX ?
Please forgive me so many questions, because I want to know more details

alex_zheng · 2022-12-22T10:39:18.599Z

Could you please to help to update the info ?