Boot loader lilo for two Redhat versions
 

Hi Friends,

I am in a total confusion. I have two versions of redhat in my system. RH 7.1 and RH 9.0 . I kept RH 7.1 because my winmodem is supported by only that kernel of RH 7.1. This OS is working fine in every aspect.

But I wanted to have a new kernel and new packages and graphics. So I decided to install one more version of RH ie 9.0. So I installed it in another partition. After installing, I changed the LILO of the new OS to incorporate the old one too. I did it. I entered to the new OS it was fine and beautiful. But when I entered into the Old OS, after cleaning drive part of start up, it gave the error "modules not found in path /lib/moduels-New kernel version/" But the modues for the old OS recides in the path "/lib/modules/kernel version/" But I did not change anything except the LILO and it worked fine.


Please tell me what is the problem and what is the mistake I made.

Please help me as I am confused. Thanks in Advance.

Waiting for your reply.... Bye..

You changed the kernel selection in your lilo.conf, but chances are you didn't change some of the other pointers there. Your System.map file can have an effect, as can the fact that you're pointing your lilo to one kernel, but loading up the rest of the system from another partition. The lilo man pages should help you figure out your specific problem, as can some of the docs at www.tldp.org

This is a normal problem for a newbie, and I'd love to tell you exactly what to fix, but not only do I think it would be better for you to learn this on your own, but you didn't post your lilo.conf :)

Just kidding. Mostly, lilo.conf setups are highly personalized, so it's best to get to know them well, as they are one of the most important parts of starting your system.

Also, are you absolutely sure that your winmodem is only supported by RH 7.1? Often driver pages lag distro versions, but kernels often can handle drivers in later versions. Not are they better tested, but occasionally a driver is added to the kernel, meaning your winmodem driver might already be supported without an extra driver. Usually the biggest problem is getting the info from the winmodem manufacturer. Once that's done, the work can be built on that base. (Somewhat unlikely with winmodems, but very possible, seeing as you have a driver for such an old version.)