nvram_rw does contain code that looks for the start of the nvram and does seem to have the crc check commented out, but there are various other uses of NVRAM_SPACE which could cause problems...
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Mon Jun 18, 2012 14:13 Post subject:
Anybody updated to the new firmware yet to ssh in and issue an nvram command to find out the size/free? _________________ Peacock Thread-FAQ -- dd-wrt Wiki
And yet the nvram_64K code is there in the GPL tarball. It's even enabled in the default build options (target.mak), and it seems to mostly work based on my test with build 140 - I haven't had the chance to compile build 144 yet. So, either they released 144 without it because it's still not 100% working, or they forgot to enable it when they built the firmware.
One theory that I have is they might not have enabled it in their release because one of the side-effects of upgrading to a build with 64K support is you end up with wiped out settings. While not an issue for an expert user, this would be an issue for a regular home user that wasn't prepared for this.
In my case, I will probably release separate 32K and 64K versions of my custom builds, due to this.
I must be going crazy, but could I get some help (or confirmation) of USB Storage Devices working with the latest build DD-WRT v24-sp2 (06/08/12) big (SVN revision 19342)?
I have tried just about everything I can think of, mainly because I am trying this with linux partitions (ext2 mainly) and not FAT/NTFS drives. FAT/NTFS drives work fine on the device, but EXT does not as far I can tell.
Log files can be found here:
The ext3 correct symbols issue starts here:
http://svn.dd-wrt.com/attachment/ticket/2580/putty.txt#L277
Mounting the ext2 usb drive & the inability to write to it with rw access starts here:
http://svn.dd-wrt.com/attachment/ticket/2580/putty.txt#L579
The router crashed when the ext2 usb drive was mounted with noatime and I attempted to create a directory:
http://svn.dd-wrt.com/attachment/ticket/2580/putty.txt#L709
Dec 31 19:00:07 kernel: _nvram_init: allocat header: 2280980480, size= 32768
that's what it shows for me too in the system log within the UI
maybe it is changed but requires the proper command via telnet to check?
No, they compiled this release without the nvram_64k option. If you run "nvram show" over telnet, it will still report 32 KB, while recompiling with the nvram_64K option does show 64 KB.
I know it's probably too early to tell, but what's the probable verdict? Is this thing gonna kp after 2 hours of use with these changes Asus have made? Or should I be clicking the order button on a N66U and register interest in the AC66U as well?