ForkWNY
Senior Member
Just a minor issue I've noticed on 3.82.2 beta 2 - when overclocking the router, the nvram clkfreq is reset to default after a reboot. Follow these steps to verify the issue:
1. open up a SSH session to the router and login
2. Run "nvram get clkfreq" the verify cpu frequency of 800 Mhz
3. "set nvram clkfreq=1000,800" to set the CPU to 1 Ghz
4. Reboot router
5. After router has rebooted, run "nvram get clkfreq", and it's set back to 800Mhz.
This wasn't an issue under 3.80.69. Otherwise the beta firmware seems to run alright. Traffic analyzer statistics seem a little flaky but I think this is related to issues with the stock firmware and not Merlin.
1. open up a SSH session to the router and login
2. Run "nvram get clkfreq" the verify cpu frequency of 800 Mhz
3. "set nvram clkfreq=1000,800" to set the CPU to 1 Ghz
4. Reboot router
5. After router has rebooted, run "nvram get clkfreq", and it's set back to 800Mhz.
This wasn't an issue under 3.80.69. Otherwise the beta firmware seems to run alright. Traffic analyzer statistics seem a little flaky but I think this is related to issues with the stock firmware and not Merlin.