How do I fix LIL-

[woodyak]

I just recompiled my Linux 6.2 2.2.14 kernel to upgrade it to 2.2.19. I rebooted and it worked fine the first time. I had to recompile to change the NIC. After I recompiled I get a LIL- when LILO tries to start. I have a boot disk to get me in the system. I've tried recompiling the kernel but that doesn't work. This system is only running Linux no other OS's are installed. Please help!!

[bdg1983]

Is this still related to your thread in General (http://www.linuxnewbie.org/cgi-bin/ubbcgi/ultimatebb.cgi?ubb=get_topic&f=1&t=022906)?

Did you rerun /sbin/lilo after the second kernel compile?

I thought that I already responded to a LIL post today. Was that yours as I cannot find it? Deleted?

[woodyak]

Yeah it's the same related problem. I can't get a clean install with a the 2.2.19 kernel. I tried running /sbin/lilo but it does nothing to help. I also found a site that recommended running e2fsk to see if the superblock was damaged. That didn't work either. I'm rebuilding now for the 5th time today.

I can't believe others haven't run into this problem. I'm following the Kernel Compilation instructions posted on this site to the T and everytime I do this my LILO gets hosed. I'm pretty unimpressed with this OS. I've never had this much trouble with Solaris or BSD.

[error27]

I've copied this from your other post.

>>For some reason my LILO is screwed up. I don't have an /etc/lilo.conf file. When I create one my machine doesn't boot so I have to use a boot disk. When I use the lilo command I get a can't find image error. Please point me in the right direction

So basically, you don't have an /etc/lilo.conf file and you expect your machine to work?

>>I'm pretty unimpressed with this OS. I've never had this much trouble with Solaris or BSD.

I'm not impressed with your distro either. What distro is it?

Tell us your partition scheme and maybe someone can create a lilo.conf file for you.

I've got a question for Red Hat users out there. Can linuxconf configure lilo?

[error27]

btw. next time when you install a new kernel don't delete the old one. I have something like 9 different kernels in /boot/

traditionally linux systems have two kernels symlinked. One to /vmlinuz and the other to vmlinuz.old This way you can boot to either kernel from lilo if your new kernel failed.

The kernel you created is almost certainly fine. But Lilo doesn't know where it is. So when you boot it's still looking for the old kernel that was deleted.

[woodyak]

I did save the old kernel. I even tested that I could boot off of it before I dealt with lilo.conf. I then edited the lilo.conf and added a new entry for the new kernel. When I boot it doesn't see either kernel. I've tried booting off of the boot disk and changing the lilo.conf in every way I could think of and then I run /sbin/lilo, but nothing works.

Let me clear something up. My first post had the problem with a missing lilo.conf file. This problem is a clean install and it does have a lilo.conf.

[error27]

post the lilo.conf file and your partition scheme and we'll help you fix it.