Posted: Fri Jan 03, 2025 12:54 Post subject: New Build - 01/03/2025 - r58976
Welcome to MediaTek r58976 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp) 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Debug Analyze: stracetcpdump.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
Serial logs were requested to help troubleshoot this issue. The requested log is attached, capturing the bootloop behavior after installing r58976.
Please let me know if additional data captures are required, or if I can provide additional troubleshooting assistance.
did you use the correct baudrate? the log is garbage _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Yikes--my apologies. Not sure what happened there. I was watching the serial data via PuTTY as it rebooted and it was definitely readable, but I stupidly did not check the log before I posted it. Not sure why it looks different than what I saw on the screen.
Here is another log (that I checked) that shows the same behavior, but for an earlier build (r51154).
R6220_bootloop_r51154.txt
Description:
This time, a readable file showing the bootloop behavior.
I downloaded the first file post too and it was totally readable. Weird! _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
OK, I'm crazy now too, because after I read BrainSlayer's post this morning, I tried to open the file on my laptop, and it was garbage.
So apparently, it's a Schroedinger's Cat situation: It's both garbage _and_ readable, until you open it and collapse the waveform into one or the other!
Not that it's important, but I figured out that readability of that file is dependent on which editor I open it in. If I use Notepad, it's garbage. If I use Notepad++, WordPad, or Word, it's readable.
But I still don't know why that happens. ¯\_(ツ)_/¯