LinuxQuestions.org - lilo l 01 01 01 01

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - lilo l 01 01 01 01 (https://www.linuxquestions.org/questions/linux-newbie-8/lilo-l-01-01-01-01-a-527473/)

I have the same problem, with a few deviations:
1. I put LILO on a diskette (about a year ago I put it on the MBR, had the same problem and couldn't use my computer for a week. Burn me once shame on you, burn me twice...)
2. My error is L with 07 repeating
3. The error code pops up before LILO's menu shows up.

Would I follow the same guidelines to fix the problem?

Thanks,
David

I would just restore Lilo. It does go pear shape sometimes.

Task B3 of the last link in my signature refers.

I am using Slackware 11's installer, and I have tried to reinstall LILO onto the diskette at least half a dozen times, both simple install and expert mode. I have Linux on I believe the master drive (I just switched them before I installed LILO, power cords werent long enough as is). Windows is on the other drive.

I remember having this error a long time ago and I can't remember for the life of me how I fixed it.

If you physically alter the ribbon cable for the Linux then the partition reference would change and your Linux should not boot.

You must update the new partition reference in

(1) /etc/lilo.conf.
(2) /etc/fstab

and then restore Lilo again.

For example if Linux was in the master drive its partitions would be in hda. When plugged as a slave the Linux will regard the same disk as hdb.

Well, since I posted that, I have been back to my computer, and the old master is still the master, and the old slave is still the slave.

Now when you refer to task B3, does this automatically know that my lilo is on a floppy? I have a feeling that isnt the case.

Thanks,
David

Task B3 is to use any Live CD to restore Lilo into the MBR.

OK, I have two main questions, and apparently I need it spelled out for me lol.

Here is my Lilo (With the useless stuff cut out)

Code:

# Start LILO global section

boot="/dev/hdb3"

message = /boot/boot_message.txt

#prompt

#timeout="0"

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# VESA framebuffer console @ 1024x768x256

vga="795"

...

# Windows bootable partition config begins



image="/boot/vmlinuz"

        root="/dev/fd2"

        label="Linux"

  read-only

# Linux bootable partition config ends

1. Now then, if I want to have LILO on a floppy, and my root partition is /dev/hdb3?

2. Once I have lilo.conf corrected, how would I put it on the floppy? Would I simply put it on the floppy and its good to go?

Thanks,
David

Think you got a wrong idea about Lilo.

The "root=" statement is a hard disk address for Lilo to load the root of the Linux into the memory. Therefore you can't have root=/dev/fd2 because a floppy is too small to store the root filing system of the entire Linux.

I think you could put root=/dev/hdb3 if that is the partition of "/" of your Linux.

To put Lilo on a floppy you do it with the command

Code:

lilo -b /dev/fd0

The above will install Lilo into the floppy that boot up the Linux in hdb3.

ok, thanks a lot for the help, I don't think I put that fd2 on there... but sure enough it's in the lilo.conf. Who knows, I may just be going senial at a very early age lol.

Lilo has been serving many old kernels and it is true one can put a kernel into a floppy in the older days and has the whole system in a floppy (no GUI).

Nowadays it is a lot easier to boot up Lilo in a floppy and let it go into the hard disk to load the kernel and the root of the Linux.

Well I still can't get it to load right, I either get a 99 error code or a 04 code.

I get these warnings when I install LILO:
"Warning: '/proc/partitions' does not exist, disk scan bypassed"
"Warning: The boot sector and map file are on different disks"

This is my LILO file now:

Code:

disk=/dev/hdb bios=0x80

vga="795"

image="/boot/vmlinuz"

root="/dev/hdb3"

label="Linux"

read-only

Whenever I put

Code:

boot="/dev/fd0"

it says that it is ignoring it. I also put

Code:

disk=/dev/hdb bios=0x80

in there because the Linux drive is the second drive, and I remember that will have BIOS treat it like the first one.

What am I doing wrong? What I don't understand is why the LILO config program gives the option to install LILO onto a floppy, but it never works.

You are doing things I do not know.

I would have my lilo.conf as
follow

Code:

boot="/dev/hdb3"

vga="795"

image="/boot/vmlinuz"

root="/dev/hdb3"

label="Linux"

read-only

and then issue the terminal command

Code:

lilo -b /dev/fd0

Well I've gotten further, all the way past the LILO menu, but it still hangs at

Code:

boot: Loading Linux............................

Here is a summary of what is going on.

I am booting from a floppy (/dev/fd0). My Slackware partition is /dev/hdb3. I am using the vmlinuz kernal.

Here is my custom-made lilo.conf (which is in /etc/lilo.conf)
I have LILO on a floppy so I can boot Linux immediately.

Code:

disk=/dev/hdb #this line and 

bios=0x80    #this line tell BIOS to treat hdb as the master                                    drive

map=/mnt/floppy/map #tells LILO where to put the map file (I don't know what that is, just know I need it

default=Linux #which image to boot automatically

boot=/dev/fd0 #which device to put all of this on, the floppy

prompt        #brings up the prompt

timeout=0    #I have it set up just to boot the default image instead of waiting for input

change-rules  #don't know what this is for

reset        #this goes along with the line above, I just see it in all the sample lilo.conf files

#Start Linux partition

image=/boot/vmlinuz 

root=/dev/hdb3 

initrd=/boot/initrd.gz #I think this is the problem, it should start loading everything after saying "Loading Linux" and that is what this is for 

label=Linux 

read-only

#End Linux partition

It gives me no warnings when I run /sbin/lilo. When I then reboot, it goes all the through the menu then just hangs.

I compiled the initrd.gz by typing in

Code:

mkinitrd -c -f reiserfs -r /dev/hdb3

So I think my problem is I may be building initrd.gz wrong. Any ideas?

Thanks,
David

Hallelujah! Just had to switch disk to 0x81, Thanks a lot yall!