I just got the Beryl AX (GL-MT3000) yesterday and I have been testing the unit for the last 24h (Version: 4.1.2). My unit has a problem with rebooting loops, tested both working as normal AP or as a repeater. I restored factory defaults and the issue is still there. I restored the beta 4.1.2 using the unbrick procedure and same issue.
The general behaviour is a reboot approx every t s, depending t on the config.
A few times it is able to boot correctly and I have been able to play a bit with the device and change the log path to a file in an external usb drive.
I have 2 example log files.
It happens even after restoring to factory defaults or burning a new firmware (with the uboot debrick). If other people are not having issues I will start to think a hardware problem.
I am using Version: 4.1.2, Date Compiled: 2022-12-05 08:17:00 (UTC+00:00), SHA256: 48731a8e819d68cb…
Are you getting the following line in the system log?
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
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.
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.
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.