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

WRT54GSv3 WDS with Thibor15c lock-up issue

Discussion in 'HyperWRT Firmware' started by rbngan, Aug 11, 2006.

  1. rbngan

    rbngan LI Guru Member

    I have two routers WRT54G routers configured for WDS+Access point using Thibor15c. One is a Version 3 the other Version 2. The v.3 router is locking up so that it has to be power cycled to work once or 2 per day. Does anyone know if it could be the firmware or is there any issues with the v3 router? The v.2 with Thibor15c has not locked up once.
     
  2. rbngan

    rbngan LI Guru Member

    I had to reset it again. Does anyone know what the problem may be?

    The v3 is connected to a satellite modem for Internet service, to a local computer and to a hub where 3 computers and 2 printers are connected.
     
  3. rbngan

    rbngan LI Guru Member

    Could it be going to sleep somehow and can't wake up until it is power cycled?
     
  4. rbngan

    rbngan LI Guru Member

    Ok it seem like it is locking up every 24 hours. Is there a setting in Thibor's 15c that could be doing this?
     
  5. Thibor

    Thibor Super Moderator Staff Member Member

    doubtful; you could try setting cpu_overdrive=1 on the command line and see if it helps, but it was supposed to fix G's only.
     
  6. rbngan

    rbngan LI Guru Member

    My bad, my post is incorrect. I do have G's however, after loading the Thibor 15c it now says WRT54GS so I refer to them as GS. I won't do that any more and i fixed my post but I can't fix the title.

    Should I still try the CPU_overdrive on the V.3?

    BTW when I loaded the V.2 it was from stock firmware, when I loaded the v.3 it was from HyperWRT. I used the two appropriate files from Thibor's site. Does this make any difference?
     
  7. Thibor

    Thibor Super Moderator Staff Member Member

    yes, if you have a G version 3, you should enter "nvram set cpu_overdrive=1;nvram commit" on the command line. this will cure the lockups you've been seeing. how you loaded it don't make any difference.
     
  8. rbngan

    rbngan LI Guru Member

    OK I did it. under Administration/Management/Run Command button (much easier that telenet)

    I also ran the nvram get cpu_overdrive and got a 1 response and nvram get clkfreq got a 200 response. Are those the correct value?

    I'll let you know if the lock up stop.

    Thanks Thibor for all your help
     
  9. rbngan

    rbngan LI Guru Member

    Uptime : 2 days, 20:45:56 . No lock up. so far so good.
     
  10. rbngan

    rbngan LI Guru Member

    Final update. Except for a short power outage, the primary WDS WRT54G Thibor 15c router is running with no lock up issue at all. I have great signal 250' through pine trees to a WDS WRT54G Thibor 15c repeater to a WRT54gsv.4 Stock firmware 200' away used as access point. Thibor's fix worked great just like the firmware. Thank you Thibor for all your time you spend not only in development but follow through with help on this site. Your time makes all our lives so much more enriched.
     
  11. rbngan

    rbngan LI Guru Member

    Not sure what happened. The router started to lock up again about a month ago. This time it is not so frequent.

    It has been running GREAT since 8/15/06. Only changes have been in December we moved the location to a new office, changed modem for our satellite service in January, added 3 servers, 2 workstations to the network and in February we added another WDS node with DD-WRTv23 SP2 (09 15 06)micro on a WRT54Gv5 that is linked to a WRT54Gv2 running Thibors 15c.

    The first time it locked up, I just power cycled the router. The second time the entire configuration was lost. I had to rebuild the entire setup (Yes I know I should have backed up the configuration files)(I did look for a back up but I think I lost it or I never made it). Anyway, I rebuilt it and now I'm being told it is locking up again and the office personnel just turning off the surge protector, count to 10 then turn it back on and it works again. I'm not sure if it lost the set nvram set that Thibor had me complete. I am going to try this step again to see if this fixes it and will let you know - nvram set cpu_overdrive=1;nvram commit
     

Share This Page