Build threads deal with test builds. Use the thread to report information, not to seek it. Specific issues or successes that you have found that relate to that build are welcome but do not ask for assistance with a configuration problem with your router. _________________ -Asus RT-N16 @ BS build 16785 mega
-Asus WL-520GU @ Eko build 13577M vpn-small
-Linksys WRT54G v2 @ Eko build 14583M vpn-small
-D-Link DIR-601 A1 @ BS build 16785
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Wed Nov 17, 2010 18:02 Post subject:
All is well with my WRT610Nv2, but after upgrading from the recommended build in the peacock thread, where has the ext2/ext3 filesystem support gone under the usb tab???
I can't mount any of my drives now... what the hell happened to that??
The drives should auto mount the drive with the correct parameters (depending on the partition). Auto mount is the way to have it automagically done, otherwise you may need a hard reset and then set up from scratch.
Yay! Another build to test when I get home. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
In the meantime, can someone using any UTC offset (i.e. any timezone except GMT) post the output of the following command (either the GUI command shell or the CLI) on this new build?
date; date -u
Here you go:
root@E3000:~# date; date -u
Wed Nov 17 21:23:38 UTC 2010
Wed Nov 17 21:23:38 UTC 2010
Thanks. Assuming you aren't in GMT, it's still broken. :roll:
Basically the UNIX timekeeping implementation has been inherently flawed since the original Linksys code. The "date -u" command should always yield UTC time on a properly synchronized system, and "date" should always differ from "date -u" unless you are standing in a GMT region. Instead, dd-wrt derives localtime from UTC using the offset value you choose in the GUI, but then inexplicably copies this derived value over as kernel time, stored as UTC. This breaks a lot of timing-based interoperability with other devices.
Last edited by star on Wed Nov 17, 2010 20:49; edited 1 time in total
Joined: 22 Oct 2009 Posts: 157 Location: North East - USA
Posted: Wed Nov 17, 2010 21:16 Post subject:
I have upgraded RT-N12 from 15693. It is running in mixed AP mode and everything seems to be fine. Looks like a keeper so far. I will post if there is anything to report. _________________ WNR3500L DD-WRT-18730-Kong Gateway/Firewall/NAS
WRT54G-TM DD-WRT-14929 Mega (heatsink + 250MHz oc)
WHR-G300N DD-WRT-20548(external antennas)
2x E2000 Tomato-Toastman 0501.2 AP (external antennas)
TEW-652BRP Gargoyle 1.5.9 Client Bridge (antenna upgrade + heatsinks + ventilation)
My WRT610Nv1 is crashing within some seconds after bootup with this build (also was with 15508). I used the BIG version.
It works after a 30-30-30, but only until I change some settings (so far it seems it doesn't matter which ones, just a few), then it starts to crash and reboot constantly.