What is the correct procedure for building your own kernel from source in Slackwareaarch64?

I've done this many times on x86(_64): make oldconfig, make all, make install, make modules install, make headers install (or similar) followed by mkinitrd in /boot.

However, looking at the /boot folder in slackwareaarch64, the naming conventions seem different and there is an additional os-initrd-mgr file. The naming conventions I think I can figure out (simply rename vmlinuz? Or does make install do this for you?), but is the initrd created in a similar way? Does os-initrd-mgr replace mkinitrd? Or is that solely concerned with firmware?

An "idiot's guide" would be appreciated!



--
Pete

The kernel is the kernel, and that should be ok.

What is different is the boot sequence on your particular SBC, which you don't mention. I can only tell you about my own SBC which is a Raspberry Pi 4. Whether uboot is being used or not affects the naming conventions & files read.

Sorry, I should have mentioned, mine is a Pi 400.

Presumably the way Stuart builds the kernel is some "universal" way? My guess would be that "Image-armv8-x.x.x" is simply "vmlinuz" (in x86 speak) renamed, but the initrd appears to contain much more than just the ext4 module that I would expect on x86.

As I say, I'm quite relaxed in the x86 world, but I have a lot to learn about arm! Hence my request for an "idiot's guide"!

--
Pete

Stuart published a document that comes with the source tree that details the exact steps:

slackwareaarch64-current/source/README_SOURCE.txt

All the tools are available in in slackwarearm-devtools/ on slackware.uk or ftp.arm.slackware.com.

If you wish to make your own Aarch64 SD card images: https://ftp.arm.slackware.com/slackw...tform/aarch64/

It is all written in shell scripts and should be fine if you stick with bash. There are additional README's and man pages for slackkit that should get you started. There are comments everywhere in the code of the toolkit.

If you would like to use other computers on your network as networked build machines, he wrote a tool that will make this happen on x86_64, x86, arm, and aarch64.
slackwarearm-devtools/x-toolchain/

3 members found this post helpful.

Thanks for the pointers!

Looks like I have some reading to do...!



--
Pete

1 members found this post helpful.

People have been asking the same question for years. In an attempt to encourage Slackware ARM users to DIY there's documentation to cover it...

There's this: https://sarpi.penthux.net/index.php?p=rpi-kernel

Then this: https://sarpi.penthux.net/index.php?p=sarpisources

4 members found this post helpful.