[SOLVED] Boot process hangs after LILO completes (-12.0)
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My Sony VAIO notebook running Slackware-12.0 booted, ran, and shut down cleanly as recently as yesterday afternoon. This morning I try booting and the process hangs.
When the LILO display comes up, I press [Enter] for the default 220.127.116.11 kernel, I see Loading linux-18.104.22.168, followed by a stream of dots across the screen, then the LILO box disappears, the cursor returns on a new line, and the system sits. No hard drive activity light, nothing.
Can I re-install (or do a re-upgrade) from the distribution cdroms without losing the contents of /home and /usr/local?
What's the recommended procedure to recover from this and return the system to working?
you can always boot from the slackware 1 cd to do maintenence. just pop it in and boot it, adn when it comes up to ask for which kernel to boot, there should be a saying that says "In a pinch you can boot your slackware using this command" use that command. it should be something like root=/dev/hda1 rdinit=ro or something. just remember to replace your hard drive placement (hda1,sda2,sda1,etc)
you can always boot from the slackware 1 cd to do maintenence. just pop it in and boot it, and when it comes up to ask for which kernel to boot, there should be a saying that says "In a pinch you can boot your slackware using this command" use that command. it should be something like root=/dev/hda1 rdinit=ro or something. just remember to replace your hard drive placement (hda1,sda2,sda1,etc)
OK. I did this, booting hugesmp.s from /dev/hda6 rdinit=ro and up it came. I logged in as a user and used ssh to copy over kernel-generic-smp-22.214.171.124_smp-i686-2_slack12.0.tgz from my main workstation/server. I re-installed this kernel package, but when I tried to reboot, the system hung as before.
It's not the kernel, apparently, and the hard drive is working OK. What do I check next? As this is a new experience in my 10+ years running linux I'm at a total loss what might be wrong.