SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm hoping that someone here can help me recover my trashed Slackware 9 install. Basically, I downloaded swaret (a very impressive tool) and ran an 'upgrade all', which all seemed to run according to plan. I then ran LILO afterwards to make sure that no errors were thrown up, and that it all seemed to work ok, which it did. I rebooted, and everything came up as normal.
'Great!', I thought, 'who says linux is tricky?'
However, the next time I rebooted (having not changed anything at all except getting ALSA going on my machine) the screen filled up with '07 07 07' repeatedly for half a screen. Nothing else happened. By booting from my Slackware CD, I've used cfdisk to switch the bootable drive from /dev/hda2 to /dev/hda1 (where my Windows partition is) I've managed to get into Windows, and it's from there that I'm writing this.
I've tried reinstalling/reconfiguring LILO from the Slackware CD I originally installed from, but this hasn't changed the situation, and I REALLY don't want to start from scratch again unless I have to.
Any help would be gratefully appreciated! And yes, I am a newbie, so please be gentle with me...
OK, I've done that following the on-screen instructions to point the kernel to my own root partition, so the boot parameter that I used was actually along the lines of 'bare.i=dev/hda2'
hda2 being where my Slackware 9 installation resides. This has allowed me to boot into Linux from the cd, and log in as root without needing a password. This is how I got into Linux last time and tried (without success) to reinstall/reconfigure LILO. Any further help much appreciated, thanks...
This has allowed me to boot into Linux from the cd, and log in as root without needing a password.
If you got in without a password, I don't think you actually booted "Your" system...you should still need to login using a valid username and password.
Quote:
'bare.i=dev/hda2'
If this is exactly what you entered, you did not boot your system, which is why you had no luck with repairing Lilo. Instead, do...
bare.i root=/dev/hda2 noinitrd ro
This will boot your system using the bare.i kernel from the cd. You can then log in and reconfigure Lilo. I think you can reinstall Lilo to the mbr using lilo /M /dev/hda...check the man pages and see what switch installs Lilo to the mbr.
I'm pleased to report problem solved. It seems that somehow despite the fact that I was installing LILO to /dev/hda2 and not the MBR LILO was still looking on the MBR.
As you said above, I wasn't booting into my system initially, just the standard Slackware shell for setting up Slackware. Once I'd got past that (thanks again) an uninstall and reinstall of LILO (plus a boot into Windows Recovery Console to write a new MBR to the beginning of the disc) was all it took to get up and running again.
My apologies for being so dozy, and thanks again to all who've helped.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.