I am trying to install Slack 9 so it dual-boots with Windows XP, and the installation went fine. Then, after I rebooted, Lilo loads up, and it has the Slackware and Windows option, so I select Slackware....it says "Loading Slackware......" and then...blank. Confused, I tried again. Same behavior. Getting kind of scared, I tried the Windows option, and THAT booted, so at least I have something. Also, I tried using my Linux bootdisk, and THAT works. Works great. Just using Lilo doesn't let it boot.

So I did some searching, and found that Lilo has trouble working if the partition is a ways back in the disk...which I did. My main partition is Windows, which takes up 25 gigs of my 40 gig hard drive. Then Slack9 takes up the last 15 gigs. So I tried everything it said on the stuff I found through google, and still nothing. I have version 22.4.1 of Lilo, which is supposed to support the lba32 option and let it work.

I'll add my lilo.conf file at the end, so you can read it. Now, just a few minutes ago, I booted into Slackware, and let it run...I noticed that my CPU light on the front of my case was flashing, like Linux was actually loading. Intrigued, I waited until it stopped and typed "root" and then my root password. It flashes for a second, as if responding to my input. I then tried "reboot", and lo and behold, it rebooted! So I guess that it IS booting correctly, but just not displaying it to my screen? Also, after it rebooted, I selected Slackware again, and this time manually restarted it in the middle of the apparent boot-up process. I then used my bootdisk to get into the Slack partition, and while booting, said that the "partition was uncorrectly unmounted and had to be checked" or whatever that error message is when you don't shut down properly. So...it WAS loading? I don't know. I set the option in lilo to just do normal VGA, none of the extra stuff, so....

Here is my lilo.conf file:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
lba32
# VESA framebuffer console @ 1024x768x256
#vga = 773
# 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
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda5
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = Windoze
table = /dev/hda
# DOS bootable partition config ends

All of the partition targets are right....any suggestions? I'm stumped.

To check if it IS booting...

in one of the etc/rc.d files, run output something silly to a file, and check to see what happened.
alternatively you could check the last modified dates on /var/log entries.

I had a similar problem, without the possibly booting behaviour. My solution was as follows.
Using any Linux boot disk (freshmeat.org) I mounted by hard-drive, chrooted to /mnt/mylinuxdrive. Installed a new version of LILO (currently I use 22.5.7.2), ran lilo, and rebooted. Then everything was OK.

I have a 40gig HD, Laptop, with Windows taking the first 25 Gigs, so it should be a similar situation to you.

Cheers,

-tjm

Alright, well...I followed some instructions from another board. Turns out I wasn't running /sbin/lilo after I changed the lilo.conf file, which meant it wasn't using the new config file. It works now, although I still can't use the framebuffer version, I have to use the normal version, which is weird since I have a system plenty good enough to use it, and the 2.4.20 kernel should be able to do that, right?

Either way, I am able to boot into the command line of Slack 9 now. I'll set up my multihead display tomorrow(after I sober up...I am so drunk right now. ), and see if that works out. Thanks!