Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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'm having difficulty booting my slackware 8.1 box (It's been like that since I installed). I can only boot the machine using a boot disk and I worried the boot floppy will eventually become damaged as so may floppies do.
When I try and boot from the HD it nothing happens - it doesn't even attempt to load Lilo. Below is my lilo.conf
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda2
message = /boot/boot_message.txt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
# VESA framebuffer console @ 1024x768x256
vga = 773
other = /dev/hdb1
label = DOS
table = /dev/hdb
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Slackware 8.1 - 2.4.18
I tried running lilo from the console and this is what I got:
Fatal: First sector of /dev/hdb1 doesn't have a valid boot signature
I worried the boot floppy will eventually become damaged as so may floppies do.
You can make exact replacas of any floppy with the 'dd' utility.
The simple formula is:
dd if=/dev/fd0 of=myfloppy.img (to create image file)
dd if=myfloppy.img of=/dev/fd0 (to a blank floppy to create copy)
I can't make much out of your lilo config without partition info. What is installed where and what boots? Was lilo installed at boot or did you configure it later? If you configured it later did you run '/sbin/lilo'? Where is lilo installed? MBR? Other partition?
Thanks for the info on dd - I"ll make an image of the boot floppy
I want to boot /dev/hda2
Lilo was installed in initally configued by Slack setup and has never worked. I honestly don't know where lilo is installed in the MBR or somewhere else. Admittedly I've had several distros on this machine (all one at a time) The progression has gone Win2k, RH 8, Debian, Slack 8.1
You probably want to check 'man lilo.conf' to confirm your lilo.conf seems to make sense.
Off hand, the "boot = /dev/hda2" would seem to be incorrect.
I am not on my PC at home but "boot = /dev/hda" would put lilo in the MBR, I think.
What does boot up now?
If lilo is in your MBR, it will boot to the lilo menu when your PC starts. If it is installed to another partition it needs some other boot manager to boot it first. That is probably why lilo does not show up when you start your PC.
The reason I asked what boots now is because it could be a short time to get lilo configured to boot everything you want.
Once again, I could give better advice at home with more access to my usual system and documents.
If you are feeling brave you could change the "hda2" to "hda" run '/sbin/lilo' and see what happens.
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
The error message you are getting may be because you don't
have /dev/hdb1 marked as bootable. This needs to be the case
for a bootable non-linux partition.
You can check/fix this from fdisk on the linux box.
Your next problem is that you have spaces in the
label=Slackware 8.1 - 2.4.18 field. My version of LILO 22.3.3
doesn't allow that. Get rid of the spaces.
2damncommon is correct, you need to have something on the MBR.
I would suggest changing the boot=/dev/hda2 to boot=/dev/hda.
Is there a reason you have the change-rules section? You don't
have anything else in the lilo.conf that changes those rules to
other than default, so why reset them? I would comment out that.
(the change-rules and the reset lines).
When you installed Slack, was there an error message when the installation program tried to write LILO? When I moved to Slack 8.1 from RH7.2, LILO wouldn't write to the MBR because GRUB was still there from my RH install. In fact, LILO wouldn't install to the bootable partition either. It wasn't until I nuked the MBR with the DOS version of fdisk (fdisk /mbr) that LILO would install properly. Now it lives quite happily in my MBR.
I've also seen a thread here at LQ that demonstrated how to use dd to wipe out anything on your MBR that might be keeping LILO from writing.
By the way, thank you for posting HOW you solved the problem. Way too many times I read threads where the ending is "I fixed it!" with absolutely no explanation of how they actually solved the problem. Or even worse, the thread just sort of dies a slow, ugly death from neglect because the person asking the question never bothers to follow up at all.
For a newb like me, its those solution steps that are critical!