use latest stable kernel

[Unterstrichmoepunterstrich]

Hello @chschlue

thank you for your time to build it for the B+ model.
I would like to use the kernel 4.18.13. I tried for the B+ model several tries, also included building a own kernel.
How did you build the initrd via cross compile?

Regards

[chschlue]

I didn't cross-build an initrd.
Can you be more precise? What exactly isn't working for you?

[Unterstrichmoepunterstrich]

I didn't cross-build an initrd.

Oh really?
So I can use my desktop to build with the "Debian way" a kernel afaik like

fakeroot make-kpkg --initrd --revision=1.0.custom kernel_image ?

Can you be more precise? What exactly isn't working for you?

before testing your image I used raspbian and this image and tried there to build the patched RPi3 kernel (branch 4.18) with cross compiling. The compiling wasn't a problem, but I didn't had a package with a initrd at the end.

Can you poke me please in the right direction to build a newer kernel for your image?

Thx.

[chschlue]

I built with ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- and got a working kernel image, no black magic involved.
I still don't quite get what you need an initrd for, the kernel image should be able to boot on its own as long as you don't compile vfat and ext4 drivers as modules or something like that.

[Unterstrichmoepunterstrich]

Hello again @chschlue

I built with ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- and got a working kernel image, no black magic involved

I used the similar arch and cross compiler. Just my target was bcmrpi3_defconfig, because I wasn't using your image.

I still don't quite get what you need an initrd for, the kernel image should be able to boot on its own as long as you don't compile vfat and ext4 drivers as modules or something like that.

How did you build the kernel? I would prefer a (debian) package which is easy to remove it.

[chschlue]

I already told you how I did it.
If you prefer a deb package, I don't see why make-kpkg shouldn't work, although I haven't tried myself.