upgrade to kernel 5.4.13 not working

karthik_holla · 01-20-2020, 06:50 AM

Hello,
I upgraded my system to kernel-5.4.13 and after reboot the system hangs saying
" Loading kernel vmlinuz... Done "
I am using elilo and have copied the new vmlinuz file to /boot/efi/EFI/Slackware.
And tried mounting with a usb and running eliloconfig command too

Thanks

ehartman · 01-20-2020, 07:21 AM

Quote:

Originally Posted by karthik_holla

I am using elilo and have copied the new vmlinuz file to /boot/efi/EFI/Slackware.

And did you generate a new initrd (initial ram disk) too and copied that to the EFI directory? The one there probably is still from your old kernel, so doesn't have the right modules to access your root disk/fs. The package only contains the kernel (and config, System.map) itself as the initrd is installation-dependant.
But it is required for the generic kernel, the huge one often can do without, if your hardware is reasonably standard (and the root fs is one of the ext? varieties).

karthik_holla · 01-20-2020, 08:24 AM

Thanks i forgot to do initrd.
Now i booted using a usb and created initrd using
" mkinitrd -c -k 5.4.13 -m ext4 -f ext4 -r /dev/sda4 "
It gave some errors like /proc/devices/ file not found and created the initrd.gz file.
I copied the file to efi folder too but still not working.

phenixia2003 · 01-20-2020, 08:41 AM

Hello,

Quote:

Originally Posted by karthik_holla

Thanks i forgot to do initrd.
Now i booted using a usb and created initrd using
" mkinitrd -c -k 5.4.13 -m ext4 -f ext4 -r /dev/sda4 "
It gave some errors like /proc/devices/ file not found and created the initrd.gz file.
I copied the file to efi folder too but still not working.

I guess that in addition to ext4 module, other are required for your system.

You can run (as root) the following command to get the recommended mkinitrd command line to run for your system.

Code:

$ /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.4.13

--
SeB

Alien Bob · 01-20-2020, 08:44 AM

Quote:

Originally Posted by karthik_holla

It gave some errors like /proc/devices/ file not found and created the initrd.gz file.
I copied the file to efi folder too but still not working.

When you boot from an external medium, be sure to (bind-) mount the relevant filesystems (not just your physical disk partitions but also /dev /proc and /sys) and do a chroot before you create the initrd.
Read https://docs.slackware.com/howtos:sl...oot_from_media for instance.

karthik_holla · 01-20-2020, 09:31 AM

Thanks. This was my procedure but than too it hangs

Code:

 mount /dev/sda4 /mnt
        mount /dev/sda1 /mnt/boot/efi

mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys

chroot /mnt

Then

Code:

./usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.4.13

Then executed mkinitrd (this time without any errors) as suggested by the generator
Then i copied initrd.gz

garpu · 01-20-2020, 09:52 AM

Did you keep your old kernel around? You can boot with that, run mkinitrd with -k to the correct kernel, then copy the initrd.gz to /boot/efi/EFI/Slackware/. Or you can install the huge kernel when you're booted with USB, reboot, and fix your old one.

karthik_holla · 01-20-2020, 11:13 AM

Slackpkg upgrade will remove old kernel i guess.

ehartman · 01-20-2020, 01:06 PM

Quote:

Originally Posted by karthik_holla

Slackpkg upgrade will remove old kernel i guess.

If you didn't blacklist that, yes.
But I do not know if slackpkg removes the ones in the EFI tree too, I never use it myself, I only selectively update from my own mirror, so all packages are available local.

mumahendras3 · 01-20-2020, 02:08 PM

Quote:

Originally Posted by ehartman

But I do not know if slackpkg removes the ones in the EFI tree too

No, it doesn't. slackpkg only removes those directly under /boot.

karthik_holla · 01-21-2020, 06:42 AM

Any other way to recover my system ?

mumahendras3 · 01-21-2020, 07:35 AM

You can try downgrading to older kernel. Download the older kernel here: https://slackware.uk/cumulative/slac...slackware64/a/

Alien Bob · 01-21-2020, 07:41 AM

Quote:

Originally Posted by karthik_holla

Any other way to recover my system ?

What exactly is the status and the remaining issue now? Errors etc?

karthik_holla · 01-21-2020, 07:49 AM

It just says

Code:

 Loading kernel vmlinuz....done

And hangs

Alien Bob · 01-21-2020, 07:55 AM

Quote:

Originally Posted by karthik_holla

It just says

Code:

 Loading kernel vmlinuz....done

And hangs

Did you copy that initrd file to the correct location on the EFI partition? And does your elilo.conf mention both the correct kernel name AND the correct initrd filename? I suspect not.