WARNING: Image file 4/32/4/REAL/4/20/2/19.07.1_imagebuilder/openwrt-imagebuilder-19.07.1-ramips-rt305x.Linux-x86_64/build_dir/target-mipsel_24kc_musl/linux-ramips_rt305x/tmp/openwrt-19.07.1-ramips-rt305x-wr512-3gn-4M-squashfs-sysupgrade.bin is too big
cp: cannot stat '4/32/4/REAL/4/20/2/19.07.1_imagebuilder/openwrt-imagebuilder-19.07.1-ramips-rt305x.Linux-x86_64/build_dir/target-mipsel_24kc_musl/linux-ramips_rt305x/tmp/openwrt-19.07.1-ramips-rt305x-wr512-3gn-4M-squashfs-sysupgrade.bin': No such file or directory
Any more ideas how to save some more kilos to create a really tight image?
Well, maybe, but you're probably not going to like it.
Build the whole system from scratch, enabling only what you need. Optimise the kernel for size, not for speed (the userspace is optimised for size by default). Build-in as many kernel modules as possible. Integrate the configuration in the image itself. Is this a 4/32 device? If so, forget about LuCI.
Good luck!
So what I did for now was to edit my .config file and added this settings to save some bytes:
# CONFIG_KERNEL_CRASHLOG is not set
# CONFIG_KERNEL_DEBUG_INFO is not set
# CONFIG_KERNEL_DEBUG_KERNEL is not set
# CONFIG_PACKAGE_kmod-ppp is not set
# CONFIG_PACKAGE_ppp is not set
# CONFIG_IPV6 is not set
and removed packages for pppoe, IPv6, iptables, opkg and added the minimal luci - still the file output is too big. The same settings (even with iptables and opkg) worked well in lede 17.x and openwrt 18.x for me
I don't even no how much to big the file is. Maybe it's really just a few bytes and smashing out one more unused or bearable package can do the trick?
I'm guess I back to openwrt 18 for now where everything works and hope their will be a openwrt-lite/tiny/whatever which aims to run on our beloved 4/32 devices which are running great since decades and hopefully for another decade or two!
No real solution. Just to get rid of working devices is participating in the planned obsolescence and clearly not carrying about the future (of others?)... I rather keep my devices running
The thing is: the horse is still very much alive and runs much better than on it's first days (with vendor/stock firmware). Even you and others don't like it that they are alive...
The usability constraints of OpenWrt 19.07 on 4/32 devices put them out of reach of most people. I told you what you have to live with if want to tread down that path. The choice is yours.
there is nothing to stop reselling it to someone with less need than you.
on the other hand, planning a purchase for a new router with more space, and of perf, will allow you to see the future.
I bought my 1st router (the WA901nd) without necessarily seeing the problems, but it is clear that if I had known, I would have taken a bigger version, to be quiet for a few years.
we can make mistakes, the important thing is not to repeat the same.
especially since I personally think that today, we have crossed a milestone for performance, and that few people will need more power and bit rate than 1200 mbps.
so you are quiet for a while with a new router.
I have been looking for a long time to improve mine, I made up my mind, and my horse is still not dead, he will just be retired
I have some 4mb routers running 18.x and Luci is included. Not sure why 19.x wouldn’t fit with some effort and for the time being OP can simply use 18.x as base as those 4mb images have Luci.
there are many kinds of limited resources in the world. one of the most important is people's time. if one can purchase a $20 router and use it for probably a decade then this is the right solution to avoid wasted resources.
This caught my eye as I still mess with an old MR3020 once in a while. Mostly as a temp client or trying out new things. My first comment is that if they 4MB doesn't get you, eventually the 32MB ram will. Most of the things I've tried usually hit an unstable situation that becomes very challenging to identify. (due to low memory issue). My basic config was usually travelmate, openvpn and some button switch configs (similar to slide-switch pgk function).
To try and combat it, I made my image tiny, with no Luci (similar to what you are trying) and then setup ext root with Swap partition. I also setup hold button shutdown action to prevent errors on the ext root drive. This configuration upon button switching includes a script that mounts the 4MB ROM and modifies the config section. This way if Ext root doesn't enable for some reason, it will still load the last working config. But, I still agree with others...I ended up moving on from this unless I have a very basic need. (AR300M is my travel router now).
mount -t jffs2 /dev/mtdblock3 /overlay-boot
DEST="/etc/config"
ROMDEST="/overlay-boot/upper/etc/config"
and runs much better than on it's first days (with vendor/stock firmware). Even you and others don't like it that they are alive...
