How to use a custom compiled kernel in Cubic (Ubuntu 20.04 arm64)? about cubic HOT 3 CLOSED

Did you install your kernel from the official Ubuntu repositories, did you download the kernel from somewhere else, or did you compile your own kernel?

from cubic.

Did you install your kernel from the official Ubuntu repositories, did you download the kernel from somewhere else, or did you compile your own kernel?

I compiled my own kernel, but it looks like it's the content of the initrd that cubic creates, it does indeed actually miss the entire /scripts/casper folder.

manually unpacking and repacking the initrd using unmkinitramfs and cpio gave me a working image, which was also significantly larger than the one cubic made.

from cubic.

You must have a initrd that matches your vmlinuz file.
You can try executing update-initramfs -u or update-initramfs -k all to generate the initrd file.

Also, it may be hard for Cubic to identify which initrd corresponds to which vmlinuz (this usually happens when you create your own kernel files, as in your case). To overcome this, give your initrd and your vmlinuz files the same unique version name. (This is the portion of the file name following the -). For example, you could name your files:

initrd.img-5.4.0-60-generic
vmlinuz-5.4.0-60-generic

from cubic.