Why special builds for 64kb of nvram? On my wrt320n(BS r21676) it shows 30.41KB/64KB and if i remember correctly the router has only 32kb.. bug?
No, it's not a bug, it's kernel 3.x, which defaults to 64 kB NVRAM on all routers. Kernel 2.6 builds still have the nvxxk limit. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
So, since the Linksys WRT610Nv2 can be converted to an E3000, does that mean it's safe to use nv60k builds in the WRT610Nv2 (without converting it to an E3000)?
So, since the Linksys WRT610Nv2 can be converted to an E3000, does that mean it's safe to use nv60k builds in the WRT610Nv2 (without converting it to an E3000)?
Cross-posting a question into this thread since this also deals with general compatibility:
I have a Cisco/Linksys E1200 v1 (Broadcom, 4MB flash/64k NVRAM) running
dd-wrt.v24-18946_NEWD-2_K2.6_openvpn_small-nv64k (04/07/12 from eko).
I'd like to try running a more recent build such as 25628 (dd-wrt.v24-25628_NEWD-2_K2.6_openvpn_small.bin), but I am worried that I might brick the router in the process because the filename doesn't contain "nv64k."
Based on all of the information I have found in the database and the forums, it appears that I *must* use the nv64k versions of each build. However, none of the openvpn_small versions after 18946 eko seem to have this designation in the file name.
Are the latest "openvpn_small" vbuilds compatible with the nv64k requirement (i.e. is the "nv64k implied even though it is not explicitly included)?