[SOLVED] Latest Slackware64 -15.0/isolinux initrd.img when booted with kernel 5.15.145 shows no modules
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Latest Slackware64 -15.0/isolinux initrd.img when booted with kernel 5.15.145 shows no modules
I am scratching my head here.
I find it convenient to maintain a small partition dedicated to booting into the Slackware installer.
I have had this working with the initrd.img supplied with the vmlinuz-huge-5.15.19 kernel.
I just tried updating to using the initrd.img supplied with the vmlinuz-huge-5.15.145. It boots without problem, but my USB keyboard was not recognised, forcing me to use the laptop keyboard. If I run 'lsmod', I see no output.
I do not know when the behaviour changed between the kernel versions. Apparently the slackware.uk cumulative archive does not track the isolinux directory changes.
Just wanted to report my experience, as it may affect anybody building an ISO to install Slackware64.
When I used to do that I'd just stick with the shipped pair of:
slackware64-15.0/kernels/huge.s/bzImage
slackware64-15.0/isolinux/initrd.img
... and never tried to update them.
But, I haven't done any of this since the lilo days. Not even sure how efi and isolinux/efiboot.img fit into the scenario these days.
I just tried updating to using the initrd.img supplied with the vmlinuz-huge-5.15.145.
That 5.15.145 kernel is an update to Slackware 15.0, it is found in ./patches/packages/ . These update kernel packages do not come with a separate initrd. The initrd you find in ./isolinux/ is meant to be used with the Slackware 15.0 boot kernel which is still the original 5.15.19. The initrd contains the modules for just that 5.15.19 kernel.
That 5.15.145 kernel is an update to Slackware 15.0, it is found in ./patches/packages/ . These update kernel packages do not come with a separate initrd. The initrd you find in ./isolinux/ is meant to be used with the Slackware 15.0 boot kernel which is still the original 5.15.19. The initrd contains the modules for just that 5.15.19 kernel.
As I customize the installation media I have also updated the kernel to 5.15.145, but that did require a replacement of all the kernel modules in isolinux/initrd.img. When I did this, I started by installing all kernel modules for 5.15.145 and then manually removed most of the modules not present in previous kernel. However, maybe it would have been faster to use some script in source/installer/
I do exactly the same thing, except that I don't use a dedicated partition... I copy the kernel & initrd.img to the EFI System partition.
I've not tried 'slipstreaming' all of the security patches into the installation iso, but it is probably not a difficult exercise. For me, the first step with a new installation is always 'slackpkg update' anyway, so maybe it's not worth spending the time on.
I do exactly the same thing, except that I don't use a dedicated partition... I copy the kernel & initrd.img to the EFI System partition.
I've not tried 'slipstreaming' all of the security patches into the installation iso, but it is probably not a difficult exercise. For me, the first step with a new installation is always 'slackpkg update' anyway, so maybe it's not worth spending the time on.
Nice to know it works with UEFI systems.
I did report on patching the installer to prefer packages from patches when using the ”Install from FTP/HTTP server” option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.