Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
I just installed slack 14. It was the first time I've tried slack. Installation went smoothly, no problems or error messages. After installing, I told it to install lilo, and added windows and ubuntu partitions to the lilo.conf, following the instructions. Reboot, I get the nice slack login screen, choose slack:
[7.396294] usb 3-4: serial number MU418ASA
Seven seconds into boot is as far as it goes! I tried to boot Ubuntu, also stops. Windows will boot, but who wants windows?? Everything worked fine using grub and Ubuntu or Fedora, so I rule out mechanical failure.
Not very impressed with Slackware!!
Didn't have a Ubu disc, so had to reinstall Fedora to get grub back, so that I could complain here!! Why didn't slack boot?? Anyone else had this trouble?
Well I just followed the instructions, I am not a guru like you, just a peasant! It wanted to install a bootloader. I thought LILO woould work as well as Grub. I put it in the MBR, following the instructions. After that, I could not boot into Linux, so it was a bit hard to reinstall grub, even if I knew how to do that!
I agree with tex, you did not need to install yet another bootloader. If you'd have installed Slackware, skipped the lilo install and then just re-run grub2 on one of your existing distros it would have picked it up...
In all honesty as you have not posted up the contents of your /etc/lilo.conf and details of your partitioning schema, this thread seems rather pointless.
Although I am no expert, I have installed other distros, and they work. One presumes LILO functions, as the boot process started. The dvd was fine, I checked it, and as I said, the install did not complain at all.
What got me worried was when Ubuntu also failed to start. Then I said some words about slack which one should not utter in polite company!
Hahahaha, complaining in a slackware forum about slackware is about as sensible as going into a barrio and complaining about the tacos el cabron at a cholos mothers house. At least no bodily harm ensues at a forum.
Why didn't slack boot?? Anyone else had this trouble?
I guess since like was mentioned. No lilo conf. No answer to "Why didn't slack boot".
Same Same with "Anyone else had this trouble".
Hopefully you learned to include documentation in code tags next time (like lilo conf).
Yeah, well 3 didn't work either, so I gave up. Later I had great trouble reinstalling Ubuntu. It installed fine, but then kept saying it cannot find init, and stopped during boot, just like slack. I have no idea what was wrong. I ran 'recovery mode' which threw up the same error as Slack, mentioned above. But as I did not format sda3, the older kernels were still there. I finally got a 3.2 kernel to boot. The touchpad would not work, the sound would not work, but I could run an update. That installed kernel 3.5.something. A reboot using this kernel worked and Ubuntu now works, everything fine. But something weird was happening. I got no errors during install.
I have installed Fedora 18 3 times these last few days, no problem, which kind of negates my theory that my laptop is somehow broken.
A couple of thoughts come to mind about the initial post:
If Grub was installed to the master boot record, attempting to install Lilo to the MBR may not work unless the MBR is first reformatted.
Also, I have never had Slackware's so-called "install Lilo automatically" option work, and I've never had the "expert" Lilo install fail, as long as I did not skip a step (which is admitted easy to do the first time)--except when Grub was previously installed to the MBR. In that case, see above.
In order to figure out what exactly went wrong, we need to know exactly what steps were followed, step by step, to install Lilo.
Without that information, we are just whistling in the dark.
Thanks for that: I really don't know, but I think LILO installed ok, beccause, on boot I had the screen with the Slackware logo and the choice of os. I nearly went and bought a new laptop, although this one is only a year old, but now I have Fedora and Ubuntu and Windows running ok, I don't think there is an mechanical/electronic failure.
A mystery! Next time I try, I will say no to LILO, and just run grub-update after installation!!