LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Lilo Screwed Up Out Of Nowhere (https://www.linuxquestions.org/questions/linux-software-2/lilo-screwed-up-out-of-nowhere-128753/)

sovietpower 12-24-2003 09:12 PM

Lilo Screwed Up Out Of Nowhere
 
I have a dual boot Slack 9.1/Win XP Home system.

The Partitions are as follow

/dev/hda1 WinXP Home 60Gb
/dev/hda2 Linux Swap 1024Kb
/dev/hda3 Linux Ext2 or something not reiser and not journaling. Rest of my 80Gb hard drive

When I start my system it gives me a bunch of numbers 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 then stops. I am using Lilo and it is installed on the Master Boot Record. The only way I am able to access my Slack 9.1 partition is to put in the Slack 9.1 cd and boot my /dev/hda3 partition. I looked in /etc/lilo.conf and it looks messed up it is as follows:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda3
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends

I dunno what happened it worked fine before someone help me!!!!

-Evan

Nu-Bee 12-24-2003 11:47 PM

Backup...backup...backup.

sovietpower 12-24-2003 11:49 PM

That doesn't help

sarahan 12-25-2003 12:21 AM

I don't really know what went wrong, but it looks to me like slack rewrote your lilo.conf back to defaults (the windows section is missing entirely). Can you remember what you did just before it decided to quit working?

Nu-Bee 12-25-2003 12:22 AM

Quote:

Originally posted by sovietpower
That doesn't help
It would have.

Skyline 12-25-2003 12:29 AM

Quote:

boot = /dev/hda3
Perhaps you might want to change this back to

boot=/dev/hda

for starters - ie instructing LILO to re-install on the MBR

once you've made the change, then run

/sbin/lilo

to re-install the loader and new map.

( edit it in an xterm with gedit or kedit )

If this works to boot back into Slack normally from the hard drive, then put your old Win entry back in and again run /sbin/lilo afterwards

sarahan 12-25-2003 12:47 AM

umm, yeah, what he said. just thought of re-editing your lilo.conf and re-running lilo. hopefully that will work. good luck.

and as a side note, making a post from links (or lynx) has been a very interesting thing that makes me really appreciate a gui and the use of a mouse.

sovietpower 12-25-2003 11:23 AM

actually I uninstalled Lilo and put Grub on I am having problems with that, you are right Slack overwrote my Lilo config and I have no clue why, I don't remember what I was doing. Grub is a little more confusing as it won't boot my Slack either geez damn boot loaders.

sarahan 12-26-2003 11:40 AM

post your grub.conf and i'll try and help you find any problems with it that would make slack not boot


All times are GMT -5. The time now is 10:41 PM.