This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
docs:man:installing_pld_linux_based_on_rescue_cd [2019-01-21 19:47] arekm [Prepare to install kernel] |
docs:man:installing_pld_linux_based_on_rescue_cd [2019-01-21 19:52] arekm [Kernel installation] |
||
---|---|---|---|
Line 142: | Line 142: | ||
- | <file># poldek --root /pld -i kernel | + | <file># poldek --root /pld -i kernel</file> |
- | </file> | + | |
+ | or | ||
+ | <file>#poldek --root /pld -i kernel-some-specific-version</file> | ||
+ | |||
+ | You can also install multiple different kernels. | ||
+ | |||
+ | By default kernel installation also generates initrd based on mounted /proc, /sys, /dev files and configured fstab, modprobe.conf and few others configuration files. generated initrd (which by default is initramfs cpio image) is saved in /boot. | ||
+ | |||
+ | If something fails or you want to regenerate initrd manually you can do it using: | ||
+ | |||
+ | <file>/sbin/geninitrd -v -f /boot/initd-XXX-Y.gz XXX-Y</file> | ||
+ | |||
+ | command. Real example: | ||
+ | |||
+ | <file>/sbin/geninitrd -v -f /boot/initd-4.20.3-1.gz 4.20.3-1</file> | ||
+ | |||
+ | //-v// option causes geninitrd to write additional information, so you can see if proper kernel modules are being installed into initrd. | ||
+ | |||
+ | |||
+ | If booting with new initrd fails you can use **debuginitrd** and **debuginitrd=sh** boot kernel cmdline options to debug the problem. | ||
===== Bootloader ===== | ===== Bootloader ===== | ||