The latest firmware for my router, Asus AC68U, is not found by easyddup.
Had to use the 'normal' CLI procedure i.e curl -O etc _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
The latest firmware for my router, Asus AC68U, is not found by easyddup.
Had to use the 'normal' CLI procedure i.e curl -O etc
What's the output of "nvram get DD_BOARD"?
I’ll check later but the most recent build wasn’t picked up on my R7000 either. Have worked flawless until now _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
I posted on the "General Questions" forum that the "Other Downloads" link is missing the newest builds.
Make sure you use an easyddup version dated December 10th 2021 or newer. After that, "Other Downloads" is used as the secondary download location and this problem wouldn't show up. The newest easyddup can even be setup to auto-update itself.
This is why I removed the other downloads from main website logic from things in development for webUI. It's unreliable and requires human intervention. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Mon Oct 24, 2022 0:04 Post subject:
What would the segmentation fault at the end be about? The /opt partition is on a thumbstick and it is writeable.
root@R7800:/opt/easyddup# ./nvram-save.sh
nvram-save.sh: NVRAM User Save Utility - Version 26.3
nvram-save.sh: Saving settings from firmware 50595
nvram-save.sh: Using standard NVRAM variable file: nvram-dd-wrt.ini Version=26.3
nvram-save.sh: Running in Backup Mode
My current installation of easyddup doesn't do a backup of /jffs.
It has worked before as I had three old jffs backups on the stick made by easyddup.
I've just copied the unpacked files to the easyddup directory and changed nothing.
Oh, I have to prefix the script names with ./ to run them in an sh session. I am used to it, but wonder why the prefix is missing from the commands in the instructions.
It looks to me the nvram-save script crashed when it was supposed to read and write the dd-wrt command scripts.
This is based on my understanding/assumptions of how nvram-save works. The code is hard to follow.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Oct 24, 2022 9:10 Post subject:
Its easier to run the script with debug bash|sh -x <scriptname> You also have set -x or set +x and further you have -v which can be done as bash|sh -xv <scriptname>
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Mon Oct 24, 2022 12:58 Post subject:
Thanks. However, the output with -xv was the same as with just -x.
Execution stops right after the fault.
No extra information to be seen. There are an awful lot of output lines and i cannot even find the start, where the command was entered. The terminal buffer isn't full, at the top there's old output.
I've used set -x and set +x before around a portion of a shell script with rsync to have the whole script not stop/crash when some files have gone missing, but go on to the next rsync commands, despite possible errors in the earlier step.
The segmentation fault apparently cannot be ignored despite the -x.
I hope the maker has an idea where in the nvram-save.sh script it happens from looking at where the output in nvram-restore.sh ends.
It looks to me the nvram-save script crashed when it was supposed to read and write the dd-wrt command scripts.
Agreed. Try commenting out with # individually variables rc_startup and rc_shutdown in file nvram-dd-wrt.ini to see who's the culprit (probably rc_startup).
I use a single line /opt/bin/myStartup.sh in rc_startup and that script file hides all my hacks and tweaks and gets backed up through my regular scheduled backups. It also saves nvram space.
My guess is a recent tweak in your dd-wrt startup commands has uncovered a bug/limitation in nvram-save.sh. I'm not the author of nvram-save.sh as stated in the OP but if you narrow down what command in rc_startup causes the failure I could try to fix it.
BTW easyddup run's on busybox's ash and installing bash isn't required. That actually complicated the menu code as ash doesn't have arrays like bash.
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Mon Oct 24, 2022 14:53 Post subject:
Couldn't leave without a quick try since everything was ready for testing.
The culprit is the startup script.
It's pretty long.
I will try and narrow down the offending lines later. It changes often ...
Thank you so much for your help.
I have noticed before dd-wrt has ash. It has quite different syntax in some cases.
Today I used bash after theJoker suggested it, but it was already installed (optware/Entware likely).