Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Ignore last comment, though DO update to the latest FMK.
I was able to reproduce the checksum error.
The -nopad is causing that.
Remove -nopad and it should work fine (no guarantees). Be sure you know how to
recover from a potential brick. TP-Links are a pain to recover, often requiring
serial port headers be added.
Original comment by jeremy.collake@gmail.com
on 17 Jul 2013 at 4:13
Isn't v0.99 the latest?
https://code.google.com/p/firmware-mod-kit/downloads/detail?name=fmk_099.tar.gz&
can=2&q=
I tried with this and with using checkout.
Ok I will try again with v0.99
Original comment by adriansp...@gmail.com
on 17 Jul 2013 at 4:15
Ok Well the purpose of using the kit was to make the firmware smaller so I can
enable jffs
Original comment by adriansp...@gmail.com
on 17 Jul 2013 at 4:17
-nopad isn't going to help anything with regards to the actual firmware size.
Padding just makes the file a bit bigger, but the actual firmware.
For the version, I was going by the text in your outpu "Firmware Mod Kit
(build-ng) 0.82"
To make an image smaller:
1. Use the -min switch to cause use of 1MB blocks. That router should have
enough resources to handle block sizes that large. This will improve the
compression ratio.
2. Continue removing packages, as you suggested.
The beauty of OTHER aftermarket firmwares (e.g. Gargoyle is a good consumer
firmware for TP-Links!) is that they use an overlaid JFFS2 partition so that
the entire file system is writable. So it's JFFS2 on top of Squashfs-lzma, with
the squashfs-lzma holding all the static files, so that they can be compressed
tight.
I'd definitely try Gargoyle (based on OpenWrt), or OpenWrt, unless you need
DD-WRT. OpenWrt based firmwares run great on the 3600/4300
Original comment by jeremy.collake@gmail.com
on 17 Jul 2013 at 4:21
Ok thank you for your suggestions, I will have a look
Original comment by adriansp...@gmail.com
on 17 Jul 2013 at 4:22
Good luck! What you'll find most advantageous is the package system. Gargoyle
references the Openwrt repositories. They come with the basics, and if you want
additional functionality, then you install those packages to the writable root
filesystem. Much easier than DD-WRT, where they try to cram everything people
might need into one static image.
For instance, after you flash and ssh into the router:
opkg update
opkg install nano
opkg install htop
To get you nano and htop :)
Original comment by jeremy.collake@gmail.com
on 17 Jul 2013 at 4:27
Original comment by jeremy.collake@gmail.com
on 18 Jul 2013 at 4:19
Original issue reported on code.google.com by
adriansp...@gmail.com
on 17 Jul 2013 at 3:22