1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WRT54G v2 overclocking

Discussion in 'Tomato Firmware' started by lanmtl, Jul 10, 2010.

  1. lanmtl

    lanmtl Addicted to LI Member

    Hello,

    I got myself a 20mbits connection but the WRT54G seems unable to keep up with it.
    I do QoS and heavy usenet leeching, that seems to overload the CPU.

    It is currently running at 200Mhz, I was considering overclocking but I read in several places that one should do it only if one has JTAG cable available because it's the only way to recover a bricked overclocked box.

    Have things changed (the posts dated from 2006) or is it still unsafe to do that without a JTAG? Will going from 200 to 210 or 220Mhz make so much of a difference in speeds?

    Thanks!
     
  2. kobik

    kobik Networkin' Nut Member

    You should read the links given by Toastman
    Increasing transmitter power, overclocking, etc.
    Why it is safe to run 150mW and to overclock to 250Mhz
    And I try to clear up some of the misinformation!

    http://www.linksysinfo.org/forums/showpost.php?p=340922&postcount=60
    http://www.linksysinfo.org/forums/showthread.php?t=62430
    http://www.bitsum.com/openwiking/owbase/ow.asp?WRT54G

    from QOS & Other Common Tomato Topics

    I made my OC w/o any problem and it doesn't seems to be something too dangerous if done following the rules.
     
  3. Trademark

    Trademark Network Guru Member

    The v2 (BCM3302 0.7) uses a slightly different set of overclocking frequencies than the newer models (BCM3302 0.8), and will NOT fall back to the next closest frequency if an invalid one is entered. So just to be safe, I would recommend doing the overclocking manually using the Tools>System>Command box. Some passive cooling never hurts either and you will still need a JTAG if things go wrong.

    Valid Frequencies for a v2:

    192,96
    200,100
    216,108
    228,114
    240,120
    252,126
    264,132

    Enter the commands one at a time clicking "Execute" after each (using 228 as an example):

    nvram set clkfreq=228,114
    nvram commit
    reboot
     

Share This Page