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

Why nvram set clkfreq work for me?

Discussion in 'HyperWRT Firmware' started by teknoman, May 2, 2006.

  1. teknoman

    teknoman LI Guru Member

    Hi everybody

    I am using a Linksys WRT54G v.3 and I'm using the thibor14(thank you thibor!) but when I tried running the following commands

    nvram set clkfreq=200
    nvram commit
    reboot (also tried rebooting using the GUI)

    the setting does not stay after rebooting (it shows clkfreq=216).

    I used "nvram get clkfreq" after "nvram commit" and it lists it at clkfreq=200, which is how I would like it.

    Oh if you're curious as why to I'm downclocking the speed I am just setting it back to correct speed based on specifications listed on wikipedia. Also hopefully this might resolves some minor issues I am having with the router dropping wireless once in a while and forgetting my port forwarding settings.

    Thank you
  2. slamcat

    slamcat Network Guru Member

    Actually changing the clock freq is done on boot up, and the firmware sets it at 216 based on some things found that actually help the router. You may be breaking something, IIRC, by trying to set it to 200. Thibor and those more in the know would probably be better versed on why the freq was set to 216 to begin with.
  3. Avenger20

    Avenger20 Network Guru Member

    If I'm correct Linksys changed the default from 200 to 216 as a dirty fix for a hardware error (V2.2/V3 ?) that caused large file transfers to get corrupted.
  4. Thibor

    Thibor Super Moderator Staff Member Member

    you are indeed correct. the fix is applied on startup dependant on model so leave it be
  5. teknoman

    teknoman LI Guru Member

    Ok thank you everybody for your responses... I guess I'll have to live with resaving my settings every once in a while...
  6. Toxic

    Toxic Administrator Staff Member

    and dont forgot to live with the large file transfer errors now if you are underclocking

Share This Page