build-ng.sh ended with an error of firmware size comparison

[nwmonster]

build-ng.sh ended with an error of firmware size comparison

[GoogleCodeExporter]

Yes, there's a reason build-ng refuses to build firmware images larger than the 
original: it could very well end up bricking the device.

The issue here is not specific to the build-ng script, but to the compression 
level used by mksquashfs. We use the same squashfs tools that dd-wrt makes 
available via their code repository, so if dd-wrt can compress the file system 
better than we can, it could very well be that they are using a different 
version of mksquashfs than is available via their code repository.

Here's a question: can you re-build the firmware successfully without any 
modifications? 

Probably the only thing you can do here is to minimize the size of the squashfs 
file system; if you can get rid of any files in there to make the file system 
smaller, that will help, but BE CAREFUL! Deleting the wrong things can brick 
your device.

Original comment by [email protected] on 8 Oct 2011 at 11:52

[GoogleCodeExporter]

OK, just tried this myself and without any modifications to the firmware image 
it re-builds fine and build-ng reports that there are 0 free bytes available in 
the firmware image. So if you want to add something to the file system, you're 
probably going to have to remove other things.

Question though, if you're just adding some shell scripts to the firmware 
image, can't you just drop them in the JFFS2 partition without having to modify 
the firmware update file?

Original comment by [email protected] on 9 Oct 2011 at 12:54

[GoogleCodeExporter]

Closing as invalid; all tools are working as intended.

Original comment by [email protected] on 9 Oct 2011 at 2:53

• Changed state: Invalid

[GoogleCodeExporter]

Thanks for your comments. I also tried to rebuildi other dd-wrt firmwares for 
netgear and tp-link, and met no any problems. It seems that only buffalo 
firmwares have such issue. I hope someone can show how to customize buffalo 
fireware. 

My current solution is to choose Netgear as the testbed.

Original comment by [email protected] on 10 Oct 2011 at 2:43

[GoogleCodeExporter]

Well, you can modify the Buffalo firmware, just remove things that you don't 
want/need and then you can add your scripts.

Original comment by [email protected] on 10 Oct 2011 at 8:29