|
ASUS further lockdown overclock of their routers with introduction of recent firmware. These changes were picked up in 378.56 release of Merlin firmware. ASUS does it in a way that at certain time of the day clkfreq in NVRAM will be over-written to its default value as stored in CFE.
Luckily as of 378.56, the lockdown is pretty simple to workaround. Append the following line to the end of /jffs/scripts/init-start: nvram set clkfreq=x,y
and append these two lines to the end of /jffs/scripts/services-stop: nvram set clkfreq=x,ynvram commit
where x is your CPU clock frequency and y is the DRAM clock frequency. /jffs/scripts/init-start is for cosmetic purpose so that right clock values will be displayed on WebUI. /jffs/scripts/services-stop is the meat and hence we also call nvram commit to persist to flash memory. Note that some users report clkfreq will be restored back to default values overnight. Hence, the cosmetic surgery in /jffs/script/init-start is short-lived. You might skip it altogether. Simply change /jffs/services-stop. To confirm your router is indeed overclocked, type
cat /proc/cpuinfo
The BogoMIPS value is roughly two times the CPU clock frequency in MHz. This is a temporary workaround. Hopefully someone with more brain can figure out a better solution.
| 
/1 
