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

overclocking toastman on wrt54gs v2.1

Discussion in 'Tomato Firmware' started by nlehrer, Nov 16, 2012.

  1. nlehrer

    nlehrer Network Guru Member

    hi,

    i loaded tomato-ND-1.28.7633.3-Toastman-IPT-ND-Std.trx from the upgrade in tomatousb. i told it to erase nvram had no problems. it came up
    Name toast
    Model Linksys WRT54G/GS/GL
    Chipset Broadcom BCM4712 chip rev 2 pkg 2
    CPU Freq 216 MHz
    Flash RAM Size 8 MB
    24 MB free

    i tried using your cpufreq dropdown in miscellaneous to go to 240. i rebooted and the status still showed 216. i used the nvram commands from execute system commands
    nvram set clkfreq=240
    nvram commit
    i reboot and status shows 216.

    what am i doing wrong?

    thanks.
     
  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    If you choose a value besides 240, does it work then?

    As I recall, and it's been a long time since I've played with WRT54Gs, some routers have some frequencies locked out.
     
  3. Toastman

    Toastman Super Moderator Staff Member Member

    Just checked with GL - all valid settings work fine including 240. Never had a G here.
     
  4. nlehrer

    nlehrer Network Guru Member

    it is a Wrt54GS
     
  5. koitsu

    koitsu Network Guru Member

    @Toastman -- if you need any assistance on this, the best I can offer (testing/etc.) is a WRT54G v2 w/ serial port mod, and a WRTSL54GS (note the "SL"). That's the best I can do for testing on older units.

    @nlehher -- There are multiple versions of the WRT54GS, so which model matters (just saying "WRT54GS" doesn't help -- you need to look closely at the bottom of your router): http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54G/GL/GS/GX

    Generally speaking I don't tend to recommend people overclock their routers. There have been established cases where doing so has caused instabilities (one such example is with the USB stack, particularly on the WRT54G v4). The biggest root cause turns out to be overheating; these routers tend to already run "slightly warm" as is, and the SOC is not really intended to handle high temperatures. There are even known out-of-the-box models which are known to overheat during common use, which prompted some vendors to release updated versions of the products which have heatsinks on the SOC. That in itself should give you reason to not overclock.
     
  6. Toastman

    Toastman Super Moderator Staff Member Member

    The issue of whether the router will actually set the selected frequency on the GS - as far as I know it ought to work, but I never saw a GS here so I don't know. Search the forum for old posts to check. I agree with Koitsu on some specific models which are known dogs. The WRT54GL is usually happy at 250MHz but I wouldn't guarantee that all routers will be. Remember that some routers, but not all, were designed for higher clock frequencies than were used by OEM manufacturers. Therefore if you do use those higher frequencies, the CPU can not really be said to be "overclocked" at all. However, the manufacturer of a particular router may have reduced the clock frequency for a good reason - overheating / poor board layout / RAM clock speed timing variations, and so on. And you don't know what that reason was.

    Some WRT54x models handle invalid overclocking gracefully by either resetting to 200Mhz after a reboot or choosing the nearest valid setting. Google for information on this.

    Be prepared if you overclock, that things may not work correctly. If you notice anything going wrong at all, set the clock back before you post about it.

    I have experience of many hundreds of WRT54GL's at 250MHz (The highest valid setting.) I am in a country with very high ambient temperatures, the routers (AP's) are all in sealed enclosures, some in full sunlight, with no extra cooling. I have had no failures.
     
  7. Monk E. Boy

    Monk E. Boy Network Guru Member

    To be fair, he did say it was a WRT-54GS v2.1 in the thread subject.

    The problem I think is that he believes WRT54G statements don't apply because its a WRT54GS. But as we know the two model lines are intricately related, with the same rules applying to both.

    When I had my WRT54GL overclocked I opened it up and stuck a bunch of GPU RAM heatsinks on everything. Then, during a particular hot summer, I found a 12VDC fan that would fit inside the case and rigged up an in-line power adapter. The overclocks made quite a bit of difference for PPTP connections, but that was about it.
     
  8. koitsu

    koitsu Network Guru Member

    Thanks Monk E. Boy, I *completely* missed the version label in the subject line. Simple things like I often overlook... Hmm, I wonder if there's something different about the v2.1 than other models, at least with regards to the CPU clock.

    Also I'm not sure if the NVRAM variable clkfreq on the WRT54GS is a single number; maybe the syntax varies per model, but on my RT-N16, I've 3 numbers. Of course, in the GUI pulldown, I've also 3 numbers, while for nlehrer in the pulldown he only gets one number. I hope it's not something as simple as the parsing code for clkfreq being wrong somehow. The notes section in the GUI states:

    I read this to mean for the WRT54GS (which is MIPSR1), the clkfreq variable should have two values, comma-delimited, and not one. I.e. clkfreq=xxx,yyy vs. clkfreq=xxx.
     
  9. mstombs

    mstombs Network Guru Member

    There was a range of routers, my wrt54gs v1.1 is one of them, where the default clkfreq must be increased to 216Mhz for basic wireless stability (and was done by Linksys firmware as well). It is therefore possible that to try extra frequencies another over-ride nvram var debug_clkfix needs to be set.
     
  10. nlehrer

    nlehrer Network Guru Member

    well, the drop-down does show 2 numbers xxx,yyy. anyway i tried 250 from the drop-down. saved and rebooted. status still says 216. same result when i used 200. it seems this rtr is locked at 216.
     
  11. koitsu

    koitsu Network Guru Member

    nlehrer, can you run the following commands in Tools -> System and provide the output here?

    nvram show | egrep "clkfreq|debug_clkfix"

    Thanks.
     
  12. mstombs

    mstombs Network Guru Member

    ... because on my wrt54gs v1.1 which needs the 216MHz fix ...

     
  13. nlehrer

    nlehrer Network Guru Member


    nvram show | egrep "clkfreq|debug_clkfix"

    clkfreq=216 debug_clkfix=1
     
  14. koitsu

    koitsu Network Guru Member

    Well then that says it all -- the explanation is in mstombs' posts. Simply put it doesn't appear this model of router supports overclocking. You can blame Linksys if you want. :)
     
  15. mstombs

    mstombs Network Guru Member

    I haven't tried first setting debug_clkfix to 0, my 8 year old Linksys router is in regular use so I am not going to try myself. The key thing about the fix was that the router was just not stable with CFE defaults, and the 216MHz patch was a work-around built into original firmware by Linksys associated with some dram timings changes in ~2005. It is possible your newer router doesn't need it? debug_clkfix is Tomato or HyperWRT specific, to be able to turn the fix on/off.

    There's clearly something marginal about the hardware (BCM5325E?)- mine crashes when attempting to use K2.6 firmwares, for example - when exactly same code/setup works fine in a WRT54G-TM (same flash/ram size). my WRT54G-TM has JTAG and serial console so more useful for hacking.... while acting as a warm spare!

    So it is all Linksys's fault, where would be if they hadn't used Linux in the early WRT54Gs and forced to comply with requirements of GPL!
     
    koitsu likes this.
  16. nlehrer

    nlehrer Network Guru Member


    so it would have shown the allowed freqs if it could overclock?
     

Share This Page