So I've been playing with cross compiled kernels for my dev boards and now that I got my pi 5 I decieded to compile a custom kernel. I'm able to build the kernel just fine with my toolchain. Looking at the instructions on the offical rpi page it has the install of the kernel a little weird. You copy an Image to the 1st partition and set the name of that kernel in config.txt. You also need to install modules and dtbs. So I did that and uname says I'm running my custom kernel. What I don't understand is that I never made an initramfs for my kernel, and there are still only old kernel and matching initramfs in /boot/. I'm accustomed on most other systems that /boot/ holds the kernel and the matching initramfs that is actualy used to load the OS. I did make some debpkgs from my kernel build and was able to installed them with dpkg and it made an initramfs, but is this necessary? How does a pi load a kernel that has no matching initramfs?? . If there is a kernel in /boot/firmware why does it have a vmlinuz in /boot/ on the 2nd partition?
Statistics: Posted by aspen.vw — Sun Jan 21, 2024 9:14 pm