Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I am wondering if anyone can help me with a problem I have with Lilo. Currently when I try to select an option to boot into either Debian or Windows it comes up with Loading 'label for OS', then does nothing, but if I leave it to timeout it boots the default just fine???
Thanks for the info, I take it from what I read that maybe my question seems too simplified or appears as if I am being lazy.
I am sorry if this is the case.
Basically I have went through lilo.conf with my Debian install and cannot see anything wrong with it, I usually use grub and understand the ins and outs of this file, so found Lilo quite self-explanatory. As I have an exam on Friday and needed to use VS2008 for some code checks in C#, I had to make windows the default and will have to use a live cd to get back at lilo.conf on the hard drive, but if somebody needs to see it to help me then I can get it.
I have read through the web for this problem from the Lilo Configuration guide to troubleshooting guides on the web with no luck.
Before I posted this, I tried IRC and nobody responded to me at all, I even went on the recommended newbie IRC's from DALNET and I think it was called UnderNEt?? - or something like this, going through channels called #linuxhelp, etc... I was able to use chatzilla installed as a plugin in firefox to do this so that was handy.
I really honestly can't see lilo.conf being the problem, but maybe I am wrong, I actually think it maybe a driver problem as I recently upgraded my bios to deal with a crash problem I was having not with linux, but it had shown its head similarly a long time ago in ubuntu. This time it was with a game I got. I updated the video drivers and everything in windows to help with this, with no such luck. So I looked into updating my bios as it was old (2005).
I have a SATA hard disk drive and do not know if this is affecting / causing the problem, but I cannot understand how if lilo.conf is incorrect that leaving it to timeout boots the OS, but selecting it does not - It is quite puzzling to me, as I cannot break down the behaviour to a specific piece of code, unless someone can advise me toward the differences in the code that runs between timeout and selection?
Yeah maybe I will to be fair I was quite happy with grub, although because I choose XFS for my filesystem, I was recommended to use lilo, as there could be problems arising from using grub with this - ah the irony lol
I wasn't pleased when the maintainers switched from lilo to grub - I had to learn about bootloaders all over again, but now I realise grub is indeed "better".
When I used lilo, I had to remember to run /sbin/lilo after any change to lilo.conf Did you remember to do this?
Otherwise, I think we need more information:
Please post the output of fdisk -l commented by yourself, so we know which partitions are what, and your lilo.conf file.