Problem upgrading latest Slackware 64-current to kernel 5.4.29
by gauchao from LinuxQuestions.org on (#51KYG)
Hi. Slackware 64-current with elilo (it is a UEFI machine) -
Today I have upgraded Slackware 64-current with the new Kernel 5.4.29 (It had 5.4.28)
After upgrading, I have ran #eliloconfig and then I rebooted
Upon reboot, I got the message "no kernel modules found" (I guess it was something like this) and the system froze.
I rebooted with Slackware install disk and took a look at /boot and /boot/efi/EFI/Slackware - I found that vmlinuz-* had different dates under /boot/efi/EFI/Slackware and /boot.
I figured that might be the problem (different copies of vmlinuz*) and so I followed the instructions in /boot/README.initrd by PV - #mkinitrd -c -k 5.4.29 -m etx4 in order to recreate a directory /boot/initrd-tree containing the initrd's filesystem.
System rebooted fine. No error messages anymore.
What could have happened? Hasn't eliloconfig work? I am new to current and elilo; all my machines are running 64-stable and lilo. I appreciate any suggestion!
Today I have upgraded Slackware 64-current with the new Kernel 5.4.29 (It had 5.4.28)
After upgrading, I have ran #eliloconfig and then I rebooted
Upon reboot, I got the message "no kernel modules found" (I guess it was something like this) and the system froze.
I rebooted with Slackware install disk and took a look at /boot and /boot/efi/EFI/Slackware - I found that vmlinuz-* had different dates under /boot/efi/EFI/Slackware and /boot.
I figured that might be the problem (different copies of vmlinuz*) and so I followed the instructions in /boot/README.initrd by PV - #mkinitrd -c -k 5.4.29 -m etx4 in order to recreate a directory /boot/initrd-tree containing the initrd's filesystem.
System rebooted fine. No error messages anymore.
What could have happened? Hasn't eliloconfig work? I am new to current and elilo; all my machines are running 64-stable and lilo. I appreciate any suggestion!