I googled for this, but I could not get a clear solution for my problem.
I have compiled a new kernel for my Slackware. Using 2.4.32 before I wanted to upgrade too 2.6.17.4

I did, and got following error when trying to boot the badboy:



So, I use ext2 as my fileformat. And here are my output of cat /etc/lilo.conf:

Hi,
The problem is your lilo.conf setup. But to cover all bases and ensure a successful boot I have included the complete setup after #make modules_install

This is my setup
Copy bzImage to /boot (you can name it Slack - less work editing files when upgrading a kernel). /dir = where ever your kernel source directory is located. eg. /home/user/kernel/linux-2.6.x.x in my case.

#cp /dir/linux-2.6.17.4/arch/i386/boot/bzImage /boot/bzImage-Slack (assumes that your system is x86).
#cp /dir/linux-2.6.17.4/System.map /boot/System.map
#cp /dir/linux-2.6.17.4/System.map /boot/System.map-Slack (give it a name - as above).
#ln -s -f /boot/System.map-Slack /boot/System.map (link your System.map files)
#ls -l /boot/System.map (output should be similar to this; lrwxrwxrwx 1 root root 22 2006-07-14 10:27 /boot/System.map -> /boot/System.map-Slack)(this step is not entirely necessary).

make an initrd.gz (follow Pat's howto supplied with the testing 2.6.13 kernel on your installation disc).

#pico /etc/lilo.conf (opens lilo.conf)

My entry looks like this. Adjust your root partition as required, and name if you gave it one, otherwise omit.

image=/boot/bzImage-Slack
initrd=/boot/initrd.gz
root=/dev/hda7
label=Slack
read-only
vga=792

Then run lilo as superuser.
#lilo

#reboot

Cheers, hope this works for you.

When jumping from 2.4.x to 2.6.x, remember that 2.4.x used modules.conf for module declarations and options, in 2.6 this has to be modprobe.conf

i guess the problem could actually be simpler than it seems. You could have missed to compile the filesystem's support built into the kernel ( and not as a module) try doing that and recompiling. That just might help!