Posted: Tue Nov 26, 2019 15:07 Post subject: U-Boot version command
Hi,
Is there a command I can run in DDWRT Web GUI or telnet to return the U-Boot version? I want to avoid opening and connecting serial for all the routers that I want to check.
I am specifically looking to run it on linksys EA8500 but I suppose it would work for any device running U-Boot.
This may be router specific but this works on
wndr3700v4 and wzr-hp-ag300h.
Code:
strings /dev/mtd0|grep -i u-boot
alright then, WTH
on EA8500 you gotta look in MTD9
Code:
root@EA8500:~# strings /dev/mtd9 | grep -i u-boot
U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Mar 16 2015 - 16:29:21)
Press any key within 10s to take control of U-Boot
CBT U-Boot ver: %s
** Invalid partition type "%.32s" (expect "U-Boot")
Warning: U-Boot configured device %s at address %llx,
u-boot
U-Boot BUG at %s:%d!
root@EA8500:~#
---------
you can get the u-boot date and go from that U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Mar 16 2015 - 16:29:21) = CBT U-Boot ver: 1.0.9 from console-log_r31780M.txt
This may be router specific but this works on
wndr3700v4 and wzr-hp-ag300h.
Code:
strings /dev/mtd0|grep -i u-boot
alright then, WTH
on EA8500 you gotta look in MTD9
Code:
root@EA8500:~# strings /dev/mtd9 | grep -i u-boot
U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Mar 16 2015 - 16:29:21)
Press any key within 10s to take control of U-Boot
CBT U-Boot ver: %s
** Invalid partition type "%.32s" (expect "U-Boot")
Warning: U-Boot configured device %s at address %llx,
u-boot
U-Boot BUG at %s:%d!
root@EA8500:~#
---------
you can get the u-boot date and go from that U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Mar 16 2015 - 16:29:21) = CBT U-Boot ver: 1.0.9 from console-log_r31780M.txt
Absolutely right - I just tried it...damn you are fast.
I was hoping it would return the CBT U-Boot ver but I think I can infer by the date. If I am guessing right:
1.0.9 = U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Mar 16 2015 - 16:29:21)
1.0.12 = U-Boot 2012.07 [Standard IPQ806X.LN,r40331] (Oct 12 2015 - 17:00:55)
On the EA8500, the GUI/telnet reboot works fine with new BS releases on 1.0.9 but does not properly start up the wired switch on GUI/telnet reboot on 1.0.12 (a power cycle is needed to properly reboot with a working wired switch).
On the EA8500, the GUI/telnet reboot works fine with new BS releases on 1.0.9 but does not properly start up the wired switch on GUI/telnet reboot on 1.0.12 (a power cycle is needed to properly reboot with a working wired switch).
magnum226,
about what I was always thinking but still really don't know why
I think, Kong even said one time that the EA8500 had a buggy switch --- I never agreed with him 'bout that but maybe it just depends on what u-boot version the silly Linksys people used.
DD-WRT devs could prolly make it right for both EA8500 u-boot versions but I have NO ideal how to tell them how
----
EDIT:
somebody might mention this in https://svn.dd-wrt.com//timeline
BS may look into it iffin he gets time for such.
However I have NO idea if he ever got an EA8500.
I don't have any EA8500 with U-Boot ver over 1.0.9 and mine seem fine so I couldn't test anything anyways.
On the EA8500, the GUI/telnet reboot works fine with new BS releases on 1.0.9 but does not properly start up the wired switch on GUI/telnet reboot on 1.0.12 (a power cycle is needed to properly reboot with a working wired switch).
magnum226,
about what I was always thinking but still really don't know why
I think, Kong even said one time that the EA8500 had a buggy switch --- I never agreed with him 'bout that but maybe it just depends on what u-boot version the silly Linksys people used.
DD-WRT devs could prolly make it right for both EA8500 u-boot versions but I have NO ideal how to tell them how
Bribe them with beer? It always works on me..
The only reason it is a big deal for me is I schedule nightly reboots which on the slightly newer U-Boot versions would cause the switch to stop working if I upgrade to new BS releases.
Remember - a reboot a day keeps the router doctor away! (sorry, I am disappointed in myself that I actually typed that..)
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Tue Nov 26, 2019 19:34 Post subject:
magnum226 wrote:
Remember - a reboot a day keeps the router doctor away! (sorry, I am disappointed in myself that I actually typed that..)
You should never have to reboot any kind of Linux unless you upgrade the kernel, or in this case, upgrade the firmware. When I had my backup E2500 on stock firmware up all the time, the only time it got rebooted after configuration was to upgrade the firmware, and I think I only had to do that initially and one other time. The uptime between was over 60 days, IIRC. Kinda like what my uptime is currently on my R7000P on 40270M kongac. It's probably sitting at around 65 days uptime without a reboot and still works just fine. The same is true on several R7800s I manage these days, or was true. It hasn't been all that long since I switched most of them over to Kong's OpenWRT. If you have to reboot it daily, there is a problem. _________________ "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
Remember - a reboot a day keeps the router doctor away! (sorry, I am disappointed in myself that I actually typed that..)
You should never have to reboot any kind of Linux unless you upgrade the kernel, or in this case, upgrade the firmware. When I had my backup E2500 on stock firmware up all the time, the only time it got rebooted after configuration was to upgrade the firmware, and I think I only had to do that initially and one other time. The uptime between was over 60 days, IIRC. Kinda like what my uptime is currently on my R7000P on 40270M kongac. It's probably sitting at around 65 days uptime without a reboot and still works just fine. The same is true on several R7800s I manage these days, or was true. It hasn't been all that long since I switched most of them over to Kong's OpenWRT. If you have to reboot it daily, there is a problem.
I completely agree with all you said. I don't have to reboot daily, but I choose to as it can't hurt. I do so nightly in the wee hours of the morning when no one is awake.
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Tue Nov 26, 2019 20:00 Post subject:
Back in my Slackware PC router days, it was only when I did kernel upgrades, and I tried to only do those upgrades when absolutely necessary. Everything else was a matter of upgrading the package and at most, restarting the process on the fly. When I started using Debian on a separate PC, I was so glad to see how much easier those processes were. RedHat, before RHEL, well. RedHat is RedHat ... it's way too Windows. Couldn't do upgrades for anything without rebooting. Seemed like a waste of time. Anyhow, sorry for the tangent /ADHD sucks _________________ "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
On the EA8500, the GUI/telnet reboot works fine with new BS releases on 1.0.9 but does not properly start up the wired switch on GUI/telnet reboot on 1.0.12 (a power cycle is needed to properly reboot with a working wired switch).
magnum226,
about what I was always thinking but still really don't know why
I think, Kong even said one time that the EA8500 had a buggy switch --- I never agreed with him 'bout that but maybe it just depends on what u-boot version the silly Linksys people used.
DD-WRT devs could prolly make it right for both EA8500 u-boot versions but I have NO ideal how to tell them how
----
EDIT:
somebody might mention this in https://svn.dd-wrt.com//timeline
BS may look into it iffin he gets time for such.
However I have NO idea if he ever got an EA8500.
I don't have any EA8500 with U-Boot ver over 1.0.9 and mine seem fine so I couldn't test anything anyways.