Hi all !
Previously, with all the packages, the image weighed 6.9, but now with the same packages 7.3 and the probability that it will install is zero, I tried earlier.
What is the reason, compression ?
Is there any way to fix this? Just recently everything was fine.
You talking about routers?
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
Kernel is bigger, packages are bigger.
Nothing's broken. There's been clear warnings for a long time that devices with 8MB flash would be insufficient for future OpenWRT installs.
If only it were that simple, I'd go and buy a new router, but they just aren't available.
Most new models with 4 MB of memory, where there is memory, have no support or the router itself is of a dubious company.
There really is no choice of a normal company that has been proven over the years with the required amount of memory.
I only have three routers, plus friends, in total I service 10 routers and all of them need to be replaced? Friends won't want to buy them, they'll say it's too expensive
So what is your suggestion, or your question? How can we help you?
The default image itself on TP-Link Archer C20 V5 weighs 5.7 mb
Adding all the same packages as before, the image goes off scale for 7.3 mb
If you update them via OPKG, then it weighs an update of 20 kilobits.
Collecting the image, it goes off scale.
Therefore, I say that the problem is compressed
Which packages?
What does that mean? What do you "update via opkg"? Do you mean install packages? And then install the very same packages?
Take us through your process, the more detail the better.
Why can I update the packages via OPKG and I still have a place, but if you collect everything with the same packages too, there is no place left, why
I'm sorry, I don't know what that means. Again, take us through your process rather than describing it.
https://firmware-selector.openwrt.org/
On August 8, everything could be collected normally, but from an hour there is no, what has changed
Again, please take us through your process. We cannot guess which packages you are trying to install.
Any packages, no values ​​have any, the image grows in front of the eyes, the problem is in the compression of the image
As I understand it, the compression of the installation image differs from the compression of additional packages
That is, the image itself in one compression format, and any additional packages in another compression format, so the size of the image has increased
No, both of them land in the same squashfs filesystem. All packages, base and custom selection, are compressed the same way at the same time.
I just ran a few tests, and the generated image sizes don't seem to exceptionally increase in size. I suspect your particular problem has to do with your selection of packages.
downloaded the image 23.05.3 and everything is the same, the problem is in the generator itself https://firmware-selector.openwrt.org
Do not quote me on this ... and i do not have time to test this, but I'm almost certain, if you build your own image with the said packages included, the size(weight as you call it) would be less. I have a million things on my mind right now but I am sure a this is a correct statement. how much less ... i really don't remember. I just recall back in the 4mb device days, i rode my little tp-link 703n until the very end, and I recall a notable size different from an image with packages compiled into the firmware vs an image with packages added after the fact.
check https://firmware-selector.openwrt.org the problem is there
Please tell us your "installed packages" selection.
As has been requested several times, please provide the exact recipe for your images including the device brand/model and the additional packages you are adding. Additionally, provide a reference version that you’re using as the “size okay” benchmark and the versions that you say are now too heavy.
Without the specifics, nobody can actually help. And, in the off chance that there is a bug, it can never even be investigated without details to reproduce the issue.