Isn't the NVRAM just a small partition of the flash chip? Maybe it's possible to re-partition the flash to make more space for NVRAM.
Playing and or modifying the nvram in the CFE is a risky adventure and can lead most times into PERMA brick. The only way to recover at that point is jtag, given the router has jtag. Most routers today come with 60/64k nvram, even the E900 for 40.00 comes with 64k nvram.
Last night after doing bit-torrent and netflix, I found my N66U near exhausted. My pings to 192.168.1.1 were 1500+ ms and sometimes dropped packets... I then went to the hard wire and pings were no different... End result I checked serial console and nvram was -104.. After a power cycle all was good. I am running BIG dd-wrt firmware on this device and so far am not very pleased.
It has great range, great speed, and really looks cool, but running out of nvram everyday doesn't make this router worth the $199 they are asking for it.
Fractal, I am not sure all of what you are doing on it, but I haven't had the same problem.
I most likely am not using the device as hard as you are (yet, I still would love to load optware on the device as soon as I can figure out what the hell is wrong with it reading my USB Drives), but, I don't know. Wireless speeds are fine, Router's pings are fine (average is 16 behind a switch).
I know you mentioned you were streaming things from your router's USB ports to your network device. Could it be a fluke with one of the software packages in the firmware. Might there be a flaw with how NTFS is being handled? I am on the mega firmware, but like I said, no problems (other then the USB Drive).
What my current stats are for NVRAM:
NVRAM 29.66 KB / 32 KB
Total Available
97%253392 kB / 262144 kB
Free
93%234836 kB / 253392 kB
Used
7%18556 kB / 253392 kB
Buffers
12%2180 kB / 18556 kB
Cached
31%5804 kB / 18556 kB
Active
7%1253 kB / 18556 kB
Inactive
6%1136 kB / 18556 kB
Fractal, wouldn't it be possible to have something that offloads some of the NVRAM into something like swap space? Or something else that would act as a storage on the device after it has booted?
Edit:
I tried another USB Flash Drive with Ext2, and Ext3 partition tables. Neither of them work. I keep getting this message:
--- /dev/discs/disc0/disc
Status: Not mounted - Unsupported file system or disk not formated
Status: Not mounted - Unsupported file system or disk not formated
I wish we could make dd-wrt save only important settings to nvram like ones that would stop dd-wrt from booting. then make a jffs2 partition for the rest of the settings? to me that is how It should be designed. anyone else think so?
would allow dd-wrt to be future proof for settings/saves on any hardware.
The nvram size on the Asus RT-N16 had been increased from 32KB to 60KB on the Tomato RAF firmware. So, I guess in time, someone will find a way to do the same on RT-N66U. Here are the details:
I wish we could make dd-wrt save only important settings to nvram like ones that would stop dd-wrt from booting. then make a jffs2 partition for the rest of the settings? to me that is how It should be designed. anyone else think so?
would allow dd-wrt to be future proof for settings/saves on any hardware.
If this was possible it would be a really good thing.
Lets say the settings that are not required at boot could be saved to a USB-stick or something.
Maybe there could be an option in the GUI where you could choose where to store such settings...
I wish we could make dd-wrt save only important settings to nvram like ones that would stop dd-wrt from booting. then make a jffs2 partition for the rest of the settings? to me that is how It should be designed. anyone else think so?
would allow dd-wrt to be future proof for settings/saves on any hardware.
If this was possible it would be a really good thing.
Lets say the settings that are not required at boot could be saved to a USB-stick or something.
Maybe there could be an option in the GUI where you could choose where to store such settings...
could build into dd-wrt to look at the nvram at early boot and if the nvram has been reset erase the jffs2 partition as well, just in case it might interfere with booting up IE rolling boot
I am debating getting this router. I keep hearing the one downsize is the 32k of nvram. Can someone explain the downside of that to me? I had ordered an e4200 v1 but refused delivery after reading the over heating issues, which I had on an e3000.
If I leave the stock firmware on the rt-n66u is the nvram a problem?
I have been running this device, I can confirm that there is not enough nvram to run OpenVPN very successfully. The router being nearly $200.00 usd, I would think of all my choices. Asus did a fantastic job putting together a ROBUST, well heat shielded and powerful router 600mhz process/256 mb ram, however the shortness of nvram devalues this router in my opinion.
nvram is used to store settings that you need to keep to survice a reboot, like ssid+ many many many other settings.. The lack of nvram limits its capabilities of what it can store.
My EA2700 from cisco should arrive today, and I will be checking that out.. I am hoping this is a powerhouse and will be a flagship router. Not to mention the router is about $99.00 or so USD.
-Fractal
Thats too bad. Was hoping to eventually getting DD_WRT w/OpenVPN running on this router!
As it stands now, I have Shibby's Tomato firmware currently running on my RT-N66U. Just upgraded today up to the latest build 92 and have enough NVRAM to fit all the certs, ect. for OpenVPN to function under Tomato. What makes the limited NVRAM different under DD-WRT where it won't work?
Thats too bad. Was hoping to eventually getting DD_WRT w/OpenVPN running on this router!
As it stands now, I have Shibby's Tomato firmware currently running on my RT-N66U. Just upgraded today up to the latest build 92 and have enough NVRAM to fit all the certs, ect. for OpenVPN to function under Tomato. What makes the limited NVRAM different under DD-WRT where it won't work?
Thats too bad. Was hoping to eventually getting DD_WRT w/OpenVPN running on this router!
As it stands now, I have Shibby's Tomato firmware currently running on my RT-N66U. Just upgraded today up to the latest build 92 and have enough NVRAM to fit all the certs, ect. for OpenVPN to function under Tomato. What makes the limited NVRAM different under DD-WRT where it won't work?
somms I am curious how much nvram used/free?
Hardly any NVRAM free...barely double digits but it holds steady.
