hello
I am having problem booting my linux box
I just installed Slackware 9.1 and everything work great...as long as i use a kernel image from the slackware CD. but as soon as i compile my own kernel it won't boot.
I have looked everywhere on google and this site for anyone with an answer but no matter what i try, nothing works so i figured i would just ask.
when i turn on the computer i get this:

LILO 22.5.7.2 Loading Linux....................
BIOS data check successful

Then it doesnt do anything at all.

I have read many different solutions to this problem but none of them have worked, and it seems to only do this when i use my own kernel image. I think i am creating the kernel image the correct way by doing make xconfig first then i do make dep; make bzImage; make modules; make modules_install. i have also tried running make install after that but still no luck

has anyone out there somewhere had this problem and found a way to fix it? this is very frustrating

thank you for any help

--Leo Howard

Are you sure that you have lilo pointing to the right drive and parittion number for the root partition? And what solutions have you tried? Is this immediately after installing Slack; or did you recompile the kernel and then have this problem? Could you please be a little more specific........

-----------------------------------------
PS; If you ran 'make install', you will need to uncomment a line in one of the makefiles to point to the /boot directory (I forget which offhand), otherwise the new kernel image and System.map file will be placed in the root directory ( / ). You can place that kernel image and map file into the /boot directory yourself, though. I don't know if you'll need to run lilo again, but if you do, you'll have to chroot to the mounted partition (chroot <mount point> /bin/bash) and run lilo (or /sbin/lilo), after making sure that the lilo.conf file shows the correct root partition ( / ) and boot drive.

-----------------------------------------
PPS: I did have this problem once, a little while ago, but I forgot how I fixed it. I think it had to changing one of the framebuffer options when configuring the kernel and recompiling. And when recompiling, don't forget to run 'make clean'

hello, thank you for your quick reply

i am only having this problem after i recompile the kernel
here is my /etc/lilo.conf file

####################
boot = /dev/hdc
message = /boot/boot_message.txt
vga = normal

image = /boot/vmlinuz
root = /dev/hdc1
label = Linux
read-only
####################

other solutions i have tried are running make install right after make modules_install,
i have tried append="noapic" in my lilo.conf
and i have tried configuring the kernel with very minimal settings

i am recompiling the kernel because i hope to use this computer as a router on my new home network i will be setting up soon and the default kernel does not have some options i need compiled into it.

i hope i have been a somewhat more specific,

thank you
--Leo Howard

I added this to my reply above, but you already replied again.

Sometimes certain options work better when buitlt in, other times they work better as modules. You might want to keep that in mind when configuring the kernel. The rule of thumb is make it a module if possible and keep the base kernel with minimal support.

In the first part of the lilo.conf, don't you need to specify a kernel image?

Also, if hdc is has several partitions (hdc1, hdc2, etc) I think you have to specify the partition like it is in the second part of the partition(hdc1).

Finally, is the image even going to show up on the lilo screen with no label?

I'm booting two kernels and my section of the lilo is
##############
image = /boot/vmlinz
root = /dev/hda2
label = Linux
read-only

image = /boot/vmlinuz.bak
root = /dev/hda2
label = Backup
read-only
#############

Other than the difference in the partition, his image section is identical to your first image section. And the global section looks okay, other than lilo is installed to hdc and not hda, but it still boots to the lilo startup screen.....