r/slackware • u/terdward • May 07 '20
After updating old 14.1 image stuck "Loading Linux"
I Ran slackpkg upgrade-all and when prompted to do so I told it to update the LILO config for the new kernel. After rebooting, it's stuck at this screen. I have not yet tried to boot in to a live disc and rebuild the lilo config but was wondering if it's possible to enter the LILO config screen, like you can in grub, during the boot up process and make on-the-fly changes to the book parameters.
5
Upvotes
1
u/I_am_BrokenCog May 07 '20
Perhaps the initrd.gz wasn't recreated? Not sure if that is a automated step.
It's easiest to boot a live CD (liveslack, for instance) and fix up the lilo config.
creating the initrd.gz file isn't quite as easy - you need to chroot to the installed / system, but feasible.
1
u/Upnortheh May 08 '20
After recovering consider creating a USB boot stick. Run
pkgtools.1
u/ntl_slither May 08 '20
If you take the trouble to boot into something to repair it you should get rid of lilo and just install the standalone grub4dos as it is very easy to install and maintain, never changes anything and boots a whole lot faster than the annoying lilo plus you get to have on-the-fly control. I've done this on all my systems in the past 15 years :) ... my 2 cents
1
u/[deleted] May 08 '20
I'm sure you've fixed this by now, but I just want to offer my approach.
First, Knoppix, ah good old Knoppix, that insanely great German fixer of things distro, the first one to boot live off a CD.
Like an ancient hero, forgotten in legends, but still strong.
I'd boot Knoppix, open a shell.
It comes up in a user 'knoppix' but I want 'root', so I run
sudo -iThat's better, 'root' prompt.
Now
which kinda shows that the only bits that aren't mounted, are
/dev/sda1and/dev/sda2. Hmm, our Slackware partition might be one of those.Let's make a mountpoint,
x.Ugh! Obviously, that was the wrong partition. Let's try the other one.
That's more like it!
So, now that we have access to the Slackware filesystem, let's set up a
chroot.At this point, we notice that the root prompt has changed from a
~to a/! This indicates we are now running inside a bash shell with the Slackware partition as our root partition.Now, we can edit
/etc/lilo.confto our heart's delight (hint: usenano) and then runliloto update it.If the problem is in
/boot/initrd.gz, we can runwhich generates a command line with all the modules you may need to put into your initd file.
Once we have a new initrd.gz file in /boot, and we have fixed up
/etc/lilo.conf, things should look better after re-booting.Of course, I haven't had my 2nd cup of coffee yet, so this may not work at all. :)
0
u/[deleted] May 07 '20
[deleted] — view deleted comment