[SOLVED] slackware-current hangs on 'Loading initial ramdisk'

ganjaplanet · 12-16-2020, 02:25 AM

After upgrading slackware-current with slackpkg into kernel 5.4.83,
the boot process hangs with the 'Loading initial ramdisk' message which blanks after a few minutes and nothing more happens

I've booted from the installation USB, mounted everything under /mnt and chrooted to /mnt,
then i tried to rebuild initrd image with `mkinitrd -c -k 5.4.83 -m btrfs:ext4` followed by
`grub-mkconfig -o /boot/grub/grub.cfg`, but nothing helps

my /boot is ext4 while / (root partition) is btrfs @ subvolume

thx

avian · 12-16-2020, 02:36 AM

Sorry if this suggestion is a bit obvious. But did you run lilo (or equivalent) after slackpkg ?

ganjaplanet · 12-16-2020, 02:39 AM

sure, i'm using grub2 instead of lilo and ran `grub-mkconfig -o /boot/grub/grub.cfg`

Quote:

Originally Posted by avian

Sorry if this suggestion is a bit obvious. But did you run lilo (or equivalent) after slackpkg ?

gp.d · 12-16-2020, 07:23 AM

for me it sounds like an incomplete ramdisk,
you could run

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

and rebuild the initrd with that output.

kind regards

ganjaplanet · 12-16-2020, 08:16 AM

Quote:

Originally Posted by gp.d

for me it sounds like an incomplete ramdisk,
you could run

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

and rebuild the initrd with that output.

kind regards

yes, that's exaclty what i did, i ran the output of:

`/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.4.83 -r`

followed by

`grub-mkconfig -o /etc/grub/grub.cfg`

both finished without problems

colorpurple21859 · 12-16-2020, 09:06 AM

Quote:

grub-mkconfig -o /etc/grub/grub.cfg`

Shouldn't that be

Code:

grub-mkconfig -o /boot/grub/grub.cfg

ganjaplanet · 12-17-2020, 02:21 AM

Quote:

Originally Posted by colorpurple21859

Shouldn't that be

Code:

grub-mkconfig -o /boot/grub/grub.cfg

yes, of course, just a typing error

BTW it must be due to the specific kernel version. when i downloaded the latest sources of 5.10.1, recompiled them, then everything works fine

ganjaplanet · 12-23-2020, 04:22 PM

The kernel 5.4.83 was just bad, upgrading to later one helped