Posted: Tue Jun 23, 2020 20:19 Post subject: ea6500 v1 running latest: 43502
After several attempts to TFTP this version, which I wasn't able to do, ended up going back to version 29495. From there used web flash working back up to 43502. Seems ok after being up a few hours...
Saw mentions the last stable release for this router was ~ 33000. Is there a specific reason, or is that the last time someone tried to go higher?
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Jun 23, 2020 20:27 Post subject:
We can't force people to report in the build threads, which they should do to report success or issues. The EA series seems to have a quirky thing about updating, or so I have gathered. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Yes, was definitely running that version. However, it turned out not to be stable. A day later it was rebooted and went into a boot loop. took a while to get it working again on an older version.
What is the latest version you've found to be stable? I went all the way back to 35531
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Thu Jun 25, 2020 14:22 Post subject:
I passed along the bootloop report 3 days ago. I haven't got a specific response on it as it was along with other reporting. Was the bootloop with an nvram reset after flash or no? What is the nvram usage? Are you using the script to keep the nvram usage down? I'm thinking this has to do with the 32k nvram limit bug with the EA-series routers. A serial log would probably help troubleshoot the issue(s). _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I passed along the bootloop report 3 days ago. I haven't got a specific response on it as it was along with other reporting. Was the bootloop with an nvram reset after flash or no? What is the nvram usage? Are you using the script to keep the nvram usage down? I'm thinking this has to do with the 32k nvram limit bug with the EA-series routers. A serial log would probably help troubleshoot the issue(s).
I posted a serial log the other day in the "New Build - 06-19-2020-r43471" thread, I think it got overlooked though, here is the link, I let it bootloop a few times so all the necessary info should be in there.
I can provide a log for newer revisions but I think it will be the same error, I'm not sure if the v1 was effected by the nvram bug or if it was the v2, I think the patch limited the ram on both versions though.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Fri Jun 26, 2020 1:05 Post subject:
otyg wrote:
I posted a serial log the other day in the "New Build - 06-19-2020-r43471" thread, I think it got overlooked though, here is the link, I let it bootloop a few times so all the necessary info should be in there.
I can provide a log for newer revisions but I think it will be the same error, I'm not sure if the v1 was effected by the nvram bug or if it was the v2, I think the patch limited the ram on both versions though.
Edit:
just tried r43516 and it booted ok now,
I'll pass the linked log on.
inetquestion wrote:
Willing to revert to that version again and run the script and gather whatever info you need... Where can I obtain the script?
By serial log, do you mean the syslog messages?
No, I mean you connect a serial USB-UART TTL adapter cable to your router and have putty up and logging the serial console output.
This should be in your startup script to mitigate the 32k nvram bug:
Code:
for line in `nvram show | grep =$ `; do var=${line%*=}; nvram unset $var; done
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Jun 26, 2020 11:01 Post subject:
otyg wrote:
kernel-panic69 wrote:
I passed along the bootloop report 3 days ago. I haven't got a specific response on it as it was along with other reporting. Was the bootloop with an nvram reset after flash or no? What is the nvram usage? Are you using the script to keep the nvram usage down? I'm thinking this has to do with the 32k nvram limit bug with the EA-series routers. A serial log would probably help troubleshoot the issue(s).
I posted a serial log the other day in the "New Build - 06-19-2020-r43471" thread, I think it got overlooked though, here is the link, I let it bootloop a few times so all the necessary info should be in there.
I can provide a log for newer revisions but I think it will be the same error, I'm not sure if the v1 was effected by the nvram bug or if it was the v2, I think the patch limited the ram on both versions though.
Edit:
just tried r43516 and it booted ok now,
these errors are looking very strangw. the first log shows it crashes somewhere serial related. the second boot shows memory allocation error related (dram broken?) the third attempt looked like the original firmware which did not boot too _________________ "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
I passed along the bootloop report 3 days ago. I haven't got a specific response on it as it was along with other reporting. Was the bootloop with an nvram reset after flash or no? What is the nvram usage? Are you using the script to keep the nvram usage down? I'm thinking this has to do with the 32k nvram limit bug with the EA-series routers. A serial log would probably help troubleshoot the issue(s).
I posted a serial log the other day in the "New Build - 06-19-2020-r43471" thread, I think it got overlooked though, here is the link, I let it bootloop a few times so all the necessary info should be in there.
I can provide a log for newer revisions but I think it will be the same error, I'm not sure if the v1 was effected by the nvram bug or if it was the v2, I think the patch limited the ram on both versions though.
Edit:
just tried r43516 and it booted ok now,
these errors are looking very strangw. the first log shows it crashes somewhere serial related. the second boot shows memory allocation error related (dram broken?) the third attempt looked like the original firmware which did not boot too
Yeah strange, my router doesn't go back to stock firmware on failed boots for some reason, it used to when it was newer so dunno if I did something to stop it or if it just broke by itself, it used to be annoying though.
for some reason r43516 is booting ok so hopefully whatever the issue was is fixed, I will see on the next update