What did the lilo entry look like when it complained? The setup you are using now does not use Suse's lilo at all. It just adds an entry in Mandrake's copy of lilo to load the Suse kernel and inital RAM disk.On Thursday 10 March 2005 01:13 am, Mikkel L. Ellertson wrote:
I tried it first, but lilo complained about 'no root partition found'
Let me guess - the second copy of lilo is the one that complained, right? If so, check your /etc/lilo.conf in Suse, and make sure it is correct. Make sure you run lilo in Suse after you make any changes in that copy of the config file. The thing you have to remember here is that you will be using two separate lilo installs to boot Suse. The version from Mandrake handles booting Mandrake, and Windows. To boot Suse, it will hand control over to the Suse lilo install, and it will handle booting Suse.
No, the one that complained is Mdk's lilo. That's why then I googled and found the way to 'load' Suse's lilo from Mdk by mounting the partition in Mdk.
Note: If you used "image=/dev/hda10" instead of "other=/dev/hda10", then you might get the 'no root partition found' error. I am not sure what the first error would be, but lilo stops at the first error it finds.
Mikkel --
Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
