September 1, 2008 8:59 PM
Brad said:
May I suggest that the open source community here set some standards for what is a community backed load and what is a try at your own risk load? If a load gives you no way to update its firmware - not just make it unlikely, but prohibits you from uploading new (chk) images via its GUI - this load should be heavily posted as for experimental purposes only and not for general use.
...there is very little to warn me against what I've gotten myself into.
Totally, I feel exactly the same way. If you go with the posted firmware, you are stuck - totally. No path to upgrade unless you're a hobbyist that wants to **** around with your router all day. I don't. I've used dd-wrt before, been happy with it, and I just want to install it on this router and have it work.
I followed Nachi's directions for converting a .chk image to a .bin image that he posted in the dd-wrt forums.
dd bs=58 skip=1 if=firmware.chk of=firmware.bin
I converted the .chk image that Nachi provided in that forum to .bin. I was able to upgrade with that but it bricked the router. Great. Seriously, why do we have firmware that won't accept an image of the same type of firmware to upgrade? Or, why aren't both .chk and .bin builds being tested concurrently? And there seems to be such little open source activity around this router despite what this site wants to project to potential customers.
I really don't want to get a serial cable and pop this thing open and start soldering. I wouldn't have installed dd-wrt if this site hadn't promoted the version offered here as working firmware.
Frustrating.