You need to do a factory reset to update the nvram....the tools page makes a call directly to the CFE.@john9527
Was able to grab the RT-AC-56U CFE v1.0.2.9 and edited the settings. Was able to use mtd-write. Funny thing. The nvram get bl_version is still 1.0.1.9 but the 18E3 "Tools", "Sysinfo" shows CFE 1.0.2.9
Thanks for providing the system log! I can see the problem (or at least a symptom)...but I don't know what would cause it. Your system time is jumping all over the place.....between Sept 11 and Sept 12 and back. Are you doing anything special with your ntp servers?No change for me with 19E2.
Sorry, I was out of commission for most of the weekend but am back now. I have a syslog for you that I took after a router reboot. The reboot took 2 minutes and 33 seconds. I will have it uploaded to dropbox and will pm the link to you shortly. Thanks.@InkyRag - I need some help since I can't recreate it. Can you capture a syslog (upload to a file sharing site and post a link - or PM me the link)?
Actually, everything looks good....Sorry, I was out of commission for most of the weekend but am back now. I have a syslog for you that I took after a router reboot. The reboot took 2 minutes and 33 seconds. I will have it uploaded to dropbox and will pm the link to you shortly. Thanks.
Edit: Rebooting the an access point with the same firmware also took 2 minutes and 33 seconds. I remember that Tomato ARM had a similar problem a while back. Maybe related to the Tomato code that was incorporated in this build?
Please describe 'dead'...that doesn't tell much.I upgraded from 18E3 to 19E2 and my router is now dead
What is the best procedure to get back to 18E3?
EDIT: Sorry forgot to mention I'm using RT-AC68U
I was measuring boot time based on the web interface telling me that the reboot had completed.Actually, everything looks good....
so boot = 4+12+52+8 = 1 min 16 sec (actually this is about right since you are not running many services). How are your measuring the boot time?
After this your Ring-Doorbell keeps requesting and being granted an IP address by the router. The router is doing everything right, it's the Doorbell that's generating repeated DHCP requests. If you haven't already, try assigning a fixed address for it.
All that does it load a timer to the browser and counts down (and is set at a high enough value to cover folks that run a 'typical' mix of services). It doesn't actually get status for the boot process. For me (running a lot of extras) it can actually come back a few seconds before the reboot is actually complete. I've thought about trying to dynamically set the boot timer based on what services are being used, but it's never been a high enough priority.I was measuring boot time based on the web interface telling me that the reboot had completed.
Thanks, I managed to get back to 18E3 using the "ASUS Firmware Recover utility"Please describe 'dead'...that doesn't tell much.
If that doesn't recover it, you'll need to use the ASUS Firmware Recover utility.
If you are willing, could you try the V19B4 release (that would help to narrow down the patch that could be causing a problem).Anything more you want me to check?
On the Wireless>Professional page for 2.4GHz, disable the reduce USB3 interference setting.It will appear as something like "sdb" and mount to the expected mountpoint under its label, only to disappear and reappear as "sda" and mount as "{label}(1)".
Care to tell me the drawbacks of that setting disabled? I have no clue what it does...On the Wireless>Professional page for 2.4GHz, disable the reduce USB3 interference setting.
Just updated less than an hour ago, so still keeping my fingers crossed! Updated remotely over SSH via VPN, bold move...EDIT: Oh, and thanks for verifying that someone besides me can update from 18E3 to 19E2 without problems![]()
When enabled, that forces the USB3 port to run at USB2 speeds. The higher USB3 speeds can in theory interfere with the 2.4 GHz band. In the process of doing that, it first brings up the port as USB3, then USB2. When it switches is what causes the change in mount points.Care to tell me the drawbacks of that setting disabled? I have no clue what it does...
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!