Actually the kernel hash changes with every daily build (the kernel version may or may not change), requiring a new set of kmod packages. The old kmod packages are only stored on the server for a week. After that in order to install anything that requires downloading a kmod, you will need to start over with a new snapshot build.
Ok, I see begining to see what I did wrong, and please correct my if I'm wrong because I trying to learn:p
Am I using but this tutorial is only for snapshot builds? And with those you can't install packages after a week because the server don't store kmod packages any more, so to update you need to reinstall the image maker and compile a whole new build.
I was trying yesterday to compile a whole new build following that tutorial, took the whole day because the day before yesterday i compiled my very first build (that build that couldn't install packages because some packages required kmod packages and those are just stored on the server for a week ;))
The second build that I compiled the dumb *** me uploaded the whole .gz file into luci 🤦 so learned a thing or two, lost every setting and was only getting average 50kb/s after the reinstall....
And still turned out as a snapshot build
But if I understand correctly I need to follow this tutorial:
If all you want to do is create a firmware image with a list of packages integrated in it, yes you should use Image Builder.
It is much faster than compiling from source because it is not compiling anything, it is downloading packages from OpenWrt download servers, and just creating the firmware images.
If you use the Image Builder from a Stable release you will not have that problem with kernel version/modules.
The link I gave you is the latest stable release, it is technically a release candidate so something may change from now to final release, but it is very little. It will not change kernel every week so it should not give you that problem.
In the instructiuons I gave you above, when I talked about CONFIG_TARGET_ROOTFS_PARTSIZE= I was talking about the Image Builder, so you can do the same change there too.
i end up only changing the 2 most wanted options in the .config for the APU 2
CONFIG_TARGET_OPTIMIZATION=”-Os -pipe -march=btver2“
i can't change the CONFIG_TARGET_ROOTFS_PARTSIZE because if i do that the flashable .img become the same size, and everything is being build in ram and on hyperv i cannot go over the 8gb ram is someone knows the solution to compact the flashable img down to 250 mb that would be great.
thanks for all the help everything works now the only weird thing is that in the config alle the LUCI packages are enabled. but after flashing LUCI wasnt be found anyware. so:
Ending up use"ing"(my grammar is really bad,sorry) a flashable debian strick, so everytime i'm updating i need to get it of the wall and do this trick below (only works with ext4 images!).
boot to debian than:
Login as username user and password live
and than just:
apt-get install parted
parted list disk
than with the right disk mine was sda
parted /dev/sda print
parted /dev/sda resizepart 2 28G
and if there is a error you need to use the code from the error and after that you can rezize2fs
parted /dev/sda print:
Model: ATA SATA SSD (scsi)
Disk /dev/sda: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 262kB 17.0MB 16.8MB primary ext2 boot
2 17.3MB 286MB 268MB primary
Depends if gzip option is enabled it's is way smaller. Gzips are way smaller, builded a 15gb ext4 openwrt img ending up with a 10mb gzip file.
But for ext4 you still need the size of the ext4 format in ram size.
I haven't found a solution for the bigger images, i only have 18gb ram available even setup a swap storage with the hope if the ram runs out of storage, it will use that storage to end the build.
But still got the error that the size is to big
Edit: I read literally now that swapon needs to be enabled each startup so I gonna try that again.
And found out that nano full builds don't generate ext4 builds, because a weird error while building. It needs to be installed differently, I don't understand it fully but on this forum is more information about some packages
I did the same thing, but there is a quirky thing inside apu2 that after installing and using parted the /dev/sda1 can't being altered without reformating,
So you would need make a new partition to use the rest of the disk size.
So I used a external USB with debian or gparted to resize the disk externally, but it's a hassle to do because I needed a serial connection to make it happen and the router isn't on a accessable location.
So now I build it with a bigger size, also i learn a lot doing it but there is still a lot that i don't know
And installing from debian isn't really a option anymore because I need a vlan on the wan port else I have no internet access, that why i gonna try it with a openwrt USB as backup if something is going wrong.