Weird Lilo behavior

[Tayl]

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.

[krohnjw]

use vga=normal, or comment it out altogether. Sounds like it is trying to use frame buffers for the console and you dont have framebuffer support in the kernel That would boot and then give a blank screen but continue to load.

On a side not I have many linux installs using lilo that use a "back" partition, and none have had any problem. If the problem was accessing the partition you would get an error loading the kernel

[Tayl]

Ok, then...that is what I thought. I'll try that and get back to you.

[jkrohn]

I agree that it sounds like a framebuffer issue.

Remember that once you make any changes to lilo.conf you need to re run /sbin/lilo !!!!

If you don't re-run lilo it is as if you never made any changes.

Jkrohn

[Tayl]

Alright, I didn't know I needed to run /sbin/lilo...I made the changes, and it ran ok after I ran /sbin/lilo...Thanks! I enabled the lba32 option, and it boots up correctly. Now...I am still in normal mode, not in the 1024x768 mode. It is weird, since the 2.4.20 kernel should be able to run framebuffers, and I have a system plenty good enough to do it. I don't want to mess with a working system, but why wouldn't I be able to run it with framebuffers? Any suggestions on that front?

Either way, thanks for the help. I'll try to get my multihead display working(after I sober up a bit..I am SO drunk right now ). Again, Thanks!

[Mead]

Your kernel CAN run it, its just a question as to whether or not you've got it enabled in your kernel config.

[Tayl]

Ok, well, that makes sense. What do I need to do to enable framebuffers? Can I just mess in a config file, or will I have to recompile the kernel?

[jkrohn]

You will have to change the kernel config as well as recomile the kernel.

Jkrohn

[flashingcurser]

Slack 9 framebuffer works well with the default kernel. Try a few of the other options in lilo untill you hit on something that works. Try also 256 colors, its the only one that works on this box (slack9 & XP). When installing slackware you did use bare.i kernel right?