Twenty-nine days up without a single glitch (24200 OLD). Now I'm gonna start enabling features, one at a time, and see where the trouble gets introduced. Maybe I'll give each step a week to settle.
I'm on an old build (22970) that has recently started to act up. Scheduled reboot seems to leave it in an unusable state sometimes, and it's completely unresponsive to a ping or any other traffic. I think the power light has been blinking orange when it's happened (not 100% it was always doing this or just the last few times I've seen it)
Your progress reports are really useful to me as I think I may have changed a small setting (syslog probably) somewhere and not remembered doing it. Otherwise I've tried to leave it untouched as stability is the ultimate 'feature' for me and it's been pretty good for the last 12 months.
Anyway, I'm going to try one of the NEWD builds and see how it does. I remember trying the new driver builds earlier and had some issues with them, so hopefully this time around is better. I'll do a nvram erase and 30/30/30 reset to ensure I've got the new factory defaults loaded.
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.
Funny. So this is weird.
After a long time of inactivity, i decided to go back and see if there was a new build. I was on 23900 NEW.
I saw the 25015-SP1 so i was pretty stoked about it.
I flash and then bam!!!! bricked router.... Noooooo, Not again.....
So i run and try to find my cable and try to remember how i unbricked it.
Anyways, long story short.
I was able to unbrick by using the chk file mentioned a little bit earlier(can't seem to attach the file)
Anyways, since i became a pro at flashing old versions i decided to try a couple.
Btw, after enabling tftpd on the router using the cable, these are the commands i used to push the new firmware
As of now i run the 24200 NEW
25015 and 25015-SP1 create a crash
It seems that only the builds with NEW/OLD firmware choice work for me.
The other one dont.
Posted: Thu Oct 09, 2014 14:19 Post subject: WNDR4500v2 long uptime!
Ever since I put build 24200 of the Kong AC firmware on my WNDR4500v2 61 days ago, I haven't had a single issue with it plus I get full speed on both WiFi and Ethernet! I am a happy geek now
Just look at the awesomeness:
https://imgur.com/NT8EZyW _________________ "Witchcraft to the ignorant, .... Simple science to the learned". - Leigh Brackett.
Can someone post the 24200 OLDD firmware?
I am using the NEWD and my wifi performance drops to shitty level after less than one day. Even after a 303030.
I'd like to try with the OLDD unless someone has a trick
thanks
Anyway, I'm going to try one of the NEWD builds and see how it does. I remember trying the new driver builds earlier and had some issues with them, so hopefully this time around is better. I'll do a nvram erase and 30/30/30 reset to ensure I've got the new factory defaults loaded.
Crossing my fingers...
So 12.5 days later and the 4500 v1 is still working great with no reboots. I did have to change the power output on the 5ghz side as my signal went to hell again right after installing it. Seems that 71mw default setting has a different effect with the NEWD images, once I jumped to 140mw signal was right back where I would expect it to be.
Other than the 5ghz power I haven't done anything beyond setup security and SSIDs.
Here's hoping I can get to that awesome 61 day uptime posted above me!
Anyway, I'm going to try one of the NEWD builds and see how it does. I remember trying the new driver builds earlier and had some issues with them, so hopefully this time around is better. I'll do a nvram erase and 30/30/30 reset to ensure I've got the new factory defaults loaded.
Crossing my fingers...
So 12.5 days later and the 4500 v1 is still working great with no reboots. I did have to change the power output on the 5ghz side as my signal went to hell again right after installing it. Seems that 71mw default setting has a different effect with the NEWD images, once I jumped to 140mw signal was right back where I would expect it to be.
Other than the 5ghz power I haven't done anything beyond setup security and SSIDs.
Here's hoping I can get to that awesome 61 day uptime posted above me!
Also just adding to the log of events; 21.25 days of uptime now, also have a client on the 5ghz side that shows connected for 15 days, and 8 days highest on the 2.4ghz side.
Pretty happy with that, and also all my devices have been snappy and responsive on wireless here. I'm a bit biased towards lower latency then max throughput, and currently the performance is good enough that I'm not looking to tweak things.
So there is no way for me to install either 25015 or 25015-sp1.
I brick my router every time.
Not sure if anyone can help or even if Kong is willing to point towards the right direction but once i was able to roll back to a version that works, and i try to update the firmware, this is what i see during the installation using tftpd:
Code:
write block [1441792] at [0x00160000]
write block [nand_erase_nand: attempt to erase a bad block at page 0x000003001572864] at [0x00180000]
erase/write failed skip block
write block [1572864] at [0x001A000]
I assume that this is the reason.
But if it was really the case, why can i install other firmwares?
same thing 24200
One last thing
When i update a good firmware i see this from the tfptd side and it reboots automatically