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

Any one have a WRT54GL v1.1 brick from OC?

Discussion in 'Tomato Firmware' started by FattysGoneWild, Apr 4, 2010.

  1. FattysGoneWild

    FattysGoneWild LI Guru Member

    I want to give it a try @250mhz with no additional cooling. If it did brick for you by chance. How did you get it up and running again? I have seen quite a few people on here running them @250mhz with no issues. I know it can vary though from person to person. Maybe I will get lucky? :cool:
     
  2. Toastman

    Toastman Super Moderator Staff Member Member

    Very few people are actually unlucky. I have 370+ WRT54GL's and only one was unstable at 250MHz. It was fine at 240.

    However, you don't need to do anything in any way risky. If you wish to test if it will run, just do not enter the new clock frequency into NVRAM. If it doesn't work, then just pull out the power plug and everything is back to normal.

    You can set this by telnet to the router and enter:

    nvram set clkfreq=250. Do not enter "nvram commit". Don't change it by the GUI (Victek mod).
     
  3. FattysGoneWild

    FattysGoneWild LI Guru Member

    Did not know you can even do that. Thanks Toastman. If it does work and things are stable. Can I then enter it through the gui and reboot it?
     
  4. wasp87

    wasp87 Network Guru Member

    In my experience my speed went down significantly after using 250mhz, so now I just run stock for stability.
     
  5. Toastman

    Toastman Super Moderator Staff Member Member

    Eeek. Just re-read my last post. Actually what I said above was wrong, the router needs to reboot to the new clock speed so it does need to be committed to NVRAM. The one I had that was unstable worked long enough to reset the frequency. In the event of a true "brick" then the answer is JTAG.

    In most cases the router would not hang immediately after reboot, so actually you would have time to change the NVRAM back again before rebooting. As wasp87 said, his still worked also, but he found it was slower.

    My Apologies.
     

Share This Page