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

WRT54G v1.1 - Tomato 1.04 - not respoding periodicaly

Discussion in 'Tomato Firmware' started by neutralman, Jan 28, 2007.

  1. neutralman

    neutralman Network Guru Member

    hello everybody,

    I have Tomato 1.04 installed on WRT54G v1.1
    I have upgraded from HyperWRT Tofu, and did administration, configuration, erase nvram - after upgrade to Tomato

    I setup everything from scratch, and now my router seems to be dead after a while

    I use IPP2P and QOS, PPPoE connected to DSL modem

    how can I find cause of this problem, do I need to paste log from device?
  2. neutralman

    neutralman Network Guru Member

    ok, I've found the solution for this problem

    since I have upgraded from HyperWRT to Tomato (and did nvram reset configuration after) I did setup from scratch on my device

    it kept freezing every 1-2 hours

    I did NVRAM reset configuration again, I flashed Tomato 1.04 again, and did NVRAM reset AFTER flashing also, I've setup everything again, from the scratch, and device is now up for 9 hours without freezing or any problems

    so I would just recommend a few steps for all users:

    1. erase all data in NVRAM memory (trough) - under Administration-Configuration
    2. flash Tomato firmware
    3. erase all data in NVRAM memory (trough) - again

    4. now you have a clean device, you can proceed with setup

    I hope this advice will help somebody.

    Take care,
  3. pharma

    pharma Network Guru Member

    Glad you resolved this! :)
  4. unicorn02

    unicorn02 LI Guru Member

    I also did a full NVRAM erase in Thibor, then flashed and did a full NVRAM erase again. This was recommended to me by the cool dudes here.
    Never had an issue. You did the right thing! :cool:
  5. GhaladReam

    GhaladReam Network Guru Member

    The reason the second erase after flashing is necessary is because when you do it in the older firmware, while it does erase the NVRAM, it restores THAT firmware's defaults. When you then upgrade to Tomato, the previous firmware's defaults are still in NVRAM, requiring a second erase.

Share This Page