• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

LILO problems :) FIXED THANK YOU!!

F

Floydian

Senior member
Hi, I'm having some trouble with LILO for linux mandrake, heres how it goes:
I had it installed right, but then I realized that I wanted to change it, so I tried changing it from the mandrake config utility. The next time I rebooted LILO was no more, and it would just display LIL_ I do have a linux boot disk, but it just goes to the command prompt linux, where I am not too experienced (unfortunately).

How can I repair this?

Thanks in advance,
 
you need to run the command "lilo" as root after making any changes to your lilo.conf file,

try this: bootup using your boot disk at the command prompt login as root, run the lilo command, then reboot
it shold work.

tip: to get into a graphical desktop from the command prompt type "startx"
 
What changes did you make? That error means: LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer.

Just log in as root after booting from the boot disk and then run /sbin/lilo and make sure it does it's thang successfully, then try booting w/o the boot disk and see if that fixes it.
 
OK, tried that, and now it displays LI_
Also, when I try to do startx from the command prompt it says cannot load framebuffer? Anyways, x-windows would start up fine without the boot disk, so thats not as big of a problem (yet).
When I exec'd lilo it said that lba32 and COMPACT may conflict, and that /dev/hdb is not the first drive. Does it matter that I'm trying to boot from the second drive (drive D🙂 how can I change it so that LILO writes itself to my first drive instead? This is the first way I had it where it worked, but I have no idea how to change it back to the first drive (editing the lilo.conf file I'm guessing, but again, I have little experience from command prompt :/)

Thanks again,
 
I take you're dual booting. If you'd like LILO to be your boot manager, then you should comment out the compact statement (it doesn't always work) and then change the boot=/dev/hdxx to boot=/dev/hda. /dev/hda is the raw device which means LILO will be written to the mbr.

Now, if you're dual booting, then you need a statement for your windows partion. You should put something like this where you see statement like this:

other=/dev/hda1
label=win

Then run lilo again to write it, then try booting again.

If you want Windows to boot by default then just put the "other" statement first and it should boot to Windows by default.
 
THANK YOU VERY MUCH!! Ok, so now I know that I have to have the boot stuff on my first drive heh, what a day, thanks again!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top