LinuxQuestions.org - [SOLVED] Slackware 14.2 Install mkinitrd ERROR: No /lib/modules/4.4.14-smp kernel modules tree found for kernel " 4.4.14-smp"

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware 14.2 Install mkinitrd ERROR: No /lib/modules/4.4.14-smp kernel modules tree found for kernel " 4.4.14-smp" (https://www.linuxquestions.org/questions/slackware-14/slackware-14-2-install-mkinitrd-error-no-lib-modules-4-4-14-smp-kernel-modules-tree-found-for-kernel-4-4-14-smp-4175632119/)

Slackware 14.2 Install mkinitrd ERROR: No /lib/modules/4.4.14-smp kernel modules tree found for kernel " 4.4.14-smp"

Hello. I am following this guide http://ftp.slackware.com/pub/slackwa...ADME_CRYPT.TXT and am at the point where ive set up my partitions, created an encrypted root partition as /dev/mapper/cryptroot (the original device is /dev/sda1) and finished with the installed and edited the installer and chrooted into /mnt.

When I try to run

Code:

mkinitrd -c -k 4.4.14-smp -m ext4 -f ext4 -r cryptroot -C /dev/sda1

I get

Code:

ERROR: No /lib/modules/4.4.14-smp kernel modules tree found for kernel " 4.4.14-smp"

is it because 4.4.14-smp is just 4.4.14 as I am using the 64bit install? I am afraid to test though so I posted here first. I just tested it and looks like it went through fine so I guess that's it...

Yes, for 64-bit you should use 4.4.14 rather than 4.4.14-smp.

Quote:

Originally Posted by volkerdi (Post 5868651)

Yes, for 64-bit you should use 4.4.14 rather than 4.4.14-smp.

Hi volkerdi, I should probably make another post...but I plan on writing a doc guide anyway.

I need some help with the instructions if you may. In the same instructions in OP I am at "If you have another OS on your computer" it says to change

Code:

"boot = /dev/mapper/cryptroot"

Code:

boot = /dev/sdx4"

with sdx4 corresponding to the boot partition made earlier....is this ONLY if I have another OS on the computer? With "boot = /dev/mapper/cryptroot" in my lilo.conf when I run lilo I get an error about only linear boot devices supported....guess I should change it to the boot partition?

I had to change boot=/dev/mapper/cryptroot to boot=/dev/sda which is the disk that contains my root and boot partitions in order for lilo to execute. I also added the appropriate line in /etc/crypttab as per instructions. Now when I boot it says

Code:

Unlocking LUKS encrypted device '/dev/sda1' as luks mapped device 'lukssda1'

Is that okay to read lukssda1? During the install I used /dev/mapper/cryptroot. Also, I am unable to enter anything. Not sure if it is ky keyboard not being recognized or what yet.

howdy laxware:

Quote:

"when I run lilo I get an error about only linear boot devices supported..."

I assume you got your luks+lvm setup going by now... but if not, that above error is what happens if you run lilo before chrooting into your luks+lvm setup... if you chroot into your mounted luks+lvm setup before running lilo (or mkinitrd for that matter) then the /usr/usr/mkinitrd/mkinitrd-command-generator.sh shell script detects the luks setup and adds the appropriate -C flag to the initrd command; and lilo detects the luks setup and won't complain that only linear boot devices are supported.

In lilo's image configuration, my root entry for my luks+lvm image looks like root=/dev/cryptvg/root (here, I wrote cryptvg, because that is what is used in README_CRYPT.txt instructions)... but on my setups, I use the hostname for cryptvg, because I put luks+lvm on bootable external usb-ssd, and if I used cryptvg as the volume group name on every setup, it would try to make two /dev/cryptvg/root when I mount external ssd... so I started using hostname for cryptvg to avoid that conflict.