slarm64 - upgrading the kernel
by pchristy from LinuxQuestions.org on (#5KJAG)
I wonder if someone could post an "Idiot's Guide" to upgrading the kernel in slarm64?
I do it all the time in x86_64 systems using a script I wrote:
Code:installpkg /path/to/Slackware/slackware64-current/slackware64/a/kernel-generic-*.txz
installpkg /path/to/Slackware/slackware64-current/slackware64/a/kernel-modules-*.txz
installpkg /path/to/Slackware/slackware64-current/slackware64/k/kernel-source-*.txz
upgradepkg /path/to/Slackware/slackware64-current/slackware64/d/kernel-headers-*.txz(followed by mkinitrd and linking the various bits and bobs to the generic names, finally re-running lilo or grub-mkconfig)
However, I'm confused by the slarm64 boot system. There appear to be two parallel systems available, selected by changing the line in the /boot/config.txt file between u-boot.bin and Image.
I usually run the Image file, as in the early days with my Pi-400 I had a few issues I was trying to nail down! Either version now seems to work OK, but "Image" gives me a display of four raspberries during the initial part of boot (one for each core, like the penguins on x86_64))
In my boot partition are several files that appear to be associated with the kernel - boot process. There is a vmlinuz-5.10.9 file, which speaks for itself, along with a uInitrd-5.10.9 file and a uInitrd file, both of which appear to be identical (why?). There is also an Image file, which is much larger than the vmlinuz file, and is the file I assume is called by config.txt
My question is how are all these files related, and - in the case of the Image file - how is it created?
I would like to upgrade to the 5.12 series kernel, but my lack of familiarity with Arm64 is holding me back. I can see hints of what is happening, but don't know how to proceed.
Any advice gratefully accepted! :)
--
Pete
I do it all the time in x86_64 systems using a script I wrote:
Code:installpkg /path/to/Slackware/slackware64-current/slackware64/a/kernel-generic-*.txz
installpkg /path/to/Slackware/slackware64-current/slackware64/a/kernel-modules-*.txz
installpkg /path/to/Slackware/slackware64-current/slackware64/k/kernel-source-*.txz
upgradepkg /path/to/Slackware/slackware64-current/slackware64/d/kernel-headers-*.txz(followed by mkinitrd and linking the various bits and bobs to the generic names, finally re-running lilo or grub-mkconfig)
However, I'm confused by the slarm64 boot system. There appear to be two parallel systems available, selected by changing the line in the /boot/config.txt file between u-boot.bin and Image.
I usually run the Image file, as in the early days with my Pi-400 I had a few issues I was trying to nail down! Either version now seems to work OK, but "Image" gives me a display of four raspberries during the initial part of boot (one for each core, like the penguins on x86_64))
In my boot partition are several files that appear to be associated with the kernel - boot process. There is a vmlinuz-5.10.9 file, which speaks for itself, along with a uInitrd-5.10.9 file and a uInitrd file, both of which appear to be identical (why?). There is also an Image file, which is much larger than the vmlinuz file, and is the file I assume is called by config.txt
My question is how are all these files related, and - in the case of the Image file - how is it created?
I would like to upgrade to the 5.12 series kernel, but my lack of familiarity with Arm64 is holding me back. I can see hints of what is happening, but don't know how to proceed.
Any advice gratefully accepted! :)
--
Pete