You need to set it in NVRAM and then propagate it to the CFE as stated in post #16. Otherwise it won't stick.I did update the CFE however bogomips still shows defsult values....weird for me.
"nvram set asuscfeclkfreq=1400,800 && nvram set asuscfecommit=1You need to set it in NVRAM and then propagate it to the CFE as stated in post #16. Otherwise it won't stick.
Yes."nvram set asuscfeclkfreq=1400,800 && nvram set asuscfecommit=1
nvram set clkfreq=1400,800 && nvram commit && reboot"
Do I copy that in putty?
IIRC, those commands just set clkfreq in NVRAM but do not persist over multiple reboots. I don't remember the exact scenario. OTOH, that may be a safer way to test the clkfreq before commiting to a higher freq.I use "nvram set clkfreq=1000,666
nvram commit" which still works.
they are reloaded from cfe every hour (or similar period) in newer firmwares.
86U got 1800MHz out of the box, we are speaking about 68U !!!I couldn't get it to stick anymore... got a 86u look on Newegg they have cheap refurbs sometimes. 86u is millenium falcon.
its working with all firmwares even recent ones if you change it with asuscfe commands!I haven't update the Merlin version since 378.56_2 and heard that later version will not support overclock. 1200Mhz was very stable.
Will someone can provide an update method of overclock for the latest Merlin firmware ?
Thanks
It will revert to the value written in CFE, did you ever change it there?
Might your router original be sold with 1000,800?
Correct commands shown in #16, but dont use 1400 as you probably end up with a nice brick!!!
Change all values to 800, 666 you'd like to have.
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!