@shanester: a 30/30/30 should not be necessary, but you should make a restart before performing the update
I made an update yesterday from 24200... everythings fine. Running smooth and well =)
@Kong: the Status -> Sys-Info tab is linked to Setup -> Basic Setup, is this a feature or a bug? This I have recognized in previous releases too... (I had to check this first and therefor I include this question by editing)
Joined: 23 Feb 2009 Posts: 76 Location: Denver, CO
Posted: Tue Sep 23, 2014 19:11 Post subject:
I just performed a dirty flash from 24200 OLD. The new firmware took, and the unit rebooted with all of my settings intact. I'll leave it alone for a few days and report back if there were any issues.
EDIT:
So far,
Time Zone defaulted to "Europe."
Wireless Channel defaulted to "Auto."
I just bought a used wndr4500. I flashed the kong initial .chk file and the router is in a boot loop.
Serial log says kernel panic. I can tftpd the oem firmware on it but I'd like to put dd-wrt on it.
I suspect at some point it must have had tagathas fw on it.
I've looked back through the tread but can't figure out how to get it working with dd-wrt.
Serial log with netgear firmware:
Decompressing...done
CFE for WNDR4500 version: v1.0.3
Build Date: Thu Jul 21 19:28:03 CST 2011
Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes
arch/mips/brcm-boards/bcm947xx/../../../../../../shared/nflash.c:nflash_read 602 unrecovable error. by pass all
nflash: squash filesystem with lzma found at block 11
Creating 2 MTD partitions on "nflash":
0x00000000-0x02000000 : "kernel"
0x00176068-0x02000000 : "rootfs"
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Creating 1 MTD partitions on "brcmnand":
0x02000000-0x07f00000 : "brcmnand"
u32 classifier
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 10
6WIND/LSIIT IPv6 multicast forwarding 0.1 plus PIM-SM/SSM with *BSD API
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
sit0: Disabled Privacy Extensions
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 228k freed
Warning: unable to open an initial console.
Failed to execute /init
[sighandler]: No more events to be processed, quitting.
[cleanup]: Waiting for children.
[cleanup]: All children terminated.
Reading board data...
WSC UUID: 0x1e9ce957bb62a1c33d18772d65f8eb47
NTP synchronized date/time: Mon Mar 4 03:15:48 2013 _________________ I am far from a guru, I'm barely a novice.
I pmed him my serial log on stock and when trying to flash his builds and tagathas.
He said to stay on stock. _________________ I am far from a guru, I'm barely a novice.
He definitely is. Maybe his answer is related to the experiences and researches he already made (just read this older posting and the following)
But does he assume you won't have luck and would rather brick your unit or does he even just don't think it is worth a try?
And what would you do? Stay with stock FW? Sell the unit again? Make some experiments?
Because it looks like a hw failure. After a flash his output from the kernel says it cannot find the rootfs magic, anywhere on the mtd. The flash must be defective in the area where our rootfs is located and these blocks are obviously not detected as defective otherwise they would be skipped on write.
We had other cases before were the old rootfs was still on it thus the kernel tried to boot from the wrong location in that case erasing the flash does the trick, but if if there is no rootfs after a flash, then erasing won't do anything, since you can't write the image correctly. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/