What's new

Overclocking on Asuswrt-Merlin 378.56_2 (RT-AC68U and RT-N66U)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

joegreat

Very Senior Member
First of all the simple observation from the RT-N66U device:
After update of the firmware the overclocking need to be set once via nvram set clkfreq=662,331,165 and nvram commit - and it will survive the restart (hard and soft - see below).
Otherwise the default values of clkfreq=600,300,150 are used.

Now the more complex (and important) behavior on the RT-AC68U device after the update to the version 378.56_2:
I have set the desired overclocking in the init-start script via nvram set clkfreq=1200,666 and nvram commit to overcome the lock-down of the current Asus firmware.

After a hard reset (power toggle) the settings force the CPU to the overclocking performance:
Code:
chief@RT-AC68U:/tmp/home/root# cat /proc/cpuinfo
Processor  : ARMv7 Processor rev 0 (v7l)
processor  : 0
BogoMIPS  : 2398.61
processor  : 1
BogoMIPS  : 2398.61
And the nvram show | grep clk shows: clkfreq=1200,666 - same as the web interface (reading the same value).

But after a soft reset (reboot button in web GUI for reboot command via telnet) the CPU performance is at default speed settings only:
Code:
chief@RT-AC68U:/tmp/home/root# cat /proc/cpuinfo
Processor  : ARMv7 Processor rev 0 (v7l)
processor  : 0
BogoMIPS  : 1599.07
processor  : 1
BogoMIPS  : 1599.07
But still the nvram show | grep clk shows: clkfreq=1200,666 - which is not the true speed!

Conclusion: if you want your router to run faster, do not forget to set the init-start values and always do a power toggle in case you need to restart it!

Update:
Over night the NVRAM variable was reset to clkfreq=800,666 - looks like something is re-reading the CFE values and updating the NVRAM settings...:rolleyes:
But the good news is that BogoMIPS : 2398.61 shows that it's still overclocked.

With kind regards
Joe :cool:
 
Last edited:
Ouch! Our previous conclusion that clkfreq is only overridden on startup is not valid then...

Could you try adding the same nvram statements also into /jffs/scripts/services-stop?

That's the same nvram statements in both /jffs/scripts/init-start and /jffs/scripts/services-stop.
 
init-start might be too early, it's possible that the nvram gets overwritten only later on during the boot process. services-start might be a safer location.
 
init-start might be too early, it's possible that the nvram gets overwritten only later on during the boot process. services-start might be a safer location.
Hi,

Adding the NVRAM settings to service-start does not change the behavior: Only cold start (power toggle) makes overclocking work.

On top: Something is changing the NVRAM clock settings after reboot: Over night it get reset to default. Is there a kind of watchdog who enforces the Bootloader (CFE) settings while the router is running? :rolleyes:

With kind regards
Joe :cool:
 
Ouch! Our previous conclusion that clkfreq is only overridden on startup is not valid then...

Could you try adding the same nvram statements also into /jffs/scripts/services-stop?
Hi,

Interesting: adding the NVRAM clock settings to the service-stop script does the trick:
Now the router is also overclocked when doing a soft boot. But why is this working now?
The init-start is running anyway after boot and set's the overclock values... :eek:

And: What makes the difference for overclocking between a hard reset and the soft one?

With kind regards
Joe :cool:
 
Last edited:
I have an RT-N66U and putty'ed in and set:

nvram set clkfreq=662,331,165
nvram commit

but after a while, on the sysinfo page (http://192.168.1.1/Tools_Sysinfo.asp) it resets the displayed speed to 600MHz... Is the router periodically resetting it's speed or?
 
looks like something is re-reading the CFE values and updating the NVRAM settings...:rolleyes:
Available pairs of CPU/RAM frequencies for RT-N66U is...
Code:
$ cat ./asuswrt/release/src-rt/shared/hndmips.c
...
/* cpu, ddr, axi, proc_PLL, */

{ 200,100,50 0xc0011080, },
{ 300,150,75 0xc00110c0, },
{ 400,200,100 0xc0011100, },
{ 500,250,125 0xc0011140, },
{ 600,300,150 0xc0011180, }, default
{ 632,316,158 0xc00157e8, },
{ 650,325,162 0xc00111a0, },
{ 662,331,165 0xc00111a8, },
 
May be it's an overclocking glitch then. Anyway, better to lower CPU/RAM frequencies to avoid it.
 
Is it wrong to edit the CFE 1.0.2.1 of my RT-AC68U with the Vortex CFE Editor and then flash the updated CFE back to the router?

Example:
Change "clkfreq=800,666" to "clkfreq=1200,800" in the CFE?

Seems like this would persist the clkfreq setting. Will it brick the router? I am not brave enough to try it.

Currently, I'm on 378.55 with clkfreq=1400,800, cpu temp is 57C.

nvram get model
RT-AC68U

nvram get clkfreq
1400,800

nvram get bl_version
1.0.2.1

cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 2798.38

processor : 1
BogoMIPS : 2798.38

Features : swp half thumb fastmult edsp
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc09
CPU revision : 0

Hardware : Northstar Prototype
Revision : 0000
Serial : 0000000000000000
 
Last edited:
Overclocking at the CFE level is a really bad idea. If your router becomes unstable with the new clock settings as it ages, you will have no way of recovering your router.
 
Hi,

Is it safe overclocking the 66u? what are the risks? worst case scenarios?

Also is there any really noticeable increase in performance?

Lastly, would it differ if its overclocked to 630 from 666? is there any noticeable difference? / What is the max overclock one could go with that router?
 
"Change "clkfreq=800,666" to "clkfreq=1200,800" in the CFE?"

The 68U I just bought is at 1000 already. Having played around with OC the performance increase going for 1000 to 1200 was not that great. Fun? Sure. Real world improvement? I saw none.
 
All the steps to d/l, edit, upload and then install a new CFE is in the threads regarding converting a TMOBILE tweaked router back into an ASUS router. No JTAG required.
 
No JTAG required?
Sure, you can set "clkfreq=1400,800" in the CFE and then use mtd-write to flash it. However, if this change causes instability and prevents the router from booting, then a JTAG recovery is the only option.

Currently, I am not aware of any "officially endorsed" JTAG recovery method for the RT-AC68U. When you mess with the factory defaults of the router, you can permanently brick it.
 
The JTAG thread is here (still not sure about AC68):-

http://www.snbforums.com/threads/how-to-asus-routers-jtag-recovery.19077/

But you really need to get this working before you have a problem!

I expect clkfreq only takes effect in CFE boot, for example in the source for some device CFE

https://github.com/RMerl/asuswrt-me...arm/board/bcm947xx/src/bcm947xx_machdep.c#L52

If overclocking note that some memory timings are stored in the nvram header, not plain nvram vars, mucking with these seems dangerous

https://github.com/RMerl/asuswrt-me...ab2/release/src-rt-6.x/include/bcmnvram.h#L29
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top