_Robb_
DD-WRT User
Joined: 14 Jan 2012
Posts: 324
Location: Wr PL
|
 Posted: Sun Mar 01, 2015 15:10 Post subject: |
 |
| Unixworld wrote: | Robb, thanks for answering.
I have followed yours and other guys' posts here,
and have saved following "for"-loop :
| Code: | nvram show | grep =$ | wc -l
for line in `nvram show | grep =$ `; do var=${line%*=}; nvram unset $var; done
nvram commit |
Limiting the NVRAM via this loop is actually the VERY FIRST thing
I always do when I start configuring my router.
I save above code block as a "startup script", "apply settings"
and reboot the router.
I always do this i nthis way - however, this does not fix the reboot loop
I have been experiencing so far with any build I have tried.
Thanks in advance for any hints and help,
Cheers |
The problem is not that the nvram must be 32K after reboot.
But it must be 32K before reboot.
We add that script to startup, so that it's automatically decreasing nvram at startup.
But if you
1) save changes to any variable to nvram
2) click around in GUI (YES! just clicking)
You have to check the nvram size and run this script after you have finished all your activities.
This 32K nvram bug is like AIDS. You have to learn to live with it. It will not get fixed.
_________________
http://www.speedtest.net/result/3915993898.png
DO NOT 30-30-30 or erase nvram newer routers! It can brick them.
EA6700: Build 27745 (nvram below 32K, ipv6 - HE 6in4)
E4200: Build 26587
WRT54GL: Retired - waiting in the closet for an emergency. |
|
