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!
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've just installed Slack and try to install the LILO bootloader. I have Win95 on /dev/hda1, /boot on /dev/hdc1 and my root directory is on /dev/hdc2. /dev/hdb is the cdrom. When I run liloconfig it installs fine. I then run lilo once more and receive the message:
Addes Windows *
Added Linux
After reboot the system shows LI and stops. I've tried both superblock and MBR install with the same result. I also tried to update LILO to a newer version but nothing seems to work.
Here is my lilo.conf:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
delay = 50
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/hdc1
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
--------
Is there anybody who can tell me what can be wrong? Thank you in advance.
do you have a directory on /dev/hdc1 called /vmlinuz ? or is the vmlinuz stored on the root of the drive?
usually vmlinuz is stored in the /boot folder...
sounds like your master boot record has problems... to erase the "mbr" master boot record, start the computer with a win9x startup disk an dat the command prompt type "fdisk /mbr" this will remove anything on the mbr. but before you do that i suggest that you look into how to reload lilo. because once its erased all youll be able to use is windblows.
My vmlinuz is located in the root partition ( /), that means on dev/hdc2. I've tried to copy it to /boot (/dev/hdc1) but with no result. In my previons setup there was no boot partition, only the /boot folder, but that didn't work either.
I've also removed LILO with lilo -u and fdisk /mbr and then reinstalled it, but it doesn't help. I still get the LI error.
Can it be something with my cdrom drive, it is installed as /dev/hdb? I've heard somewhere that LILO can't acces more than th two first disks. Or do I need to set some extra parameters in lilo.conf so that LILO can find my /dev/hdc drive at boot time?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.