Well this is the second time that i have posted here with the same issue, I cannot get Yoper to read my newly compile 2.6.7 kernel. I follow all the steps from the following site

http://www.thelinuxbox420.com/kernelguide.html

I everything that I am told to do yet I have no sucess at the system using the new kernel. here is my lilo.conf

Prompt
timeout=60
default=YOS
vga=791
boot=/dev/hda

lba32

bitmap = /boot/yoper_boot.bmp
bmp-colors = 1,,0,2,,0
bmp-table = 120p,173p,1,15,17
bmp-timer = 254p,432p,1,0,0


image=/boot/vmlinuz-2.6.7
label=YOS-2.6.7
read-only
root=/dev/hda5
append = "splash=silent "
initrd=/boot/initrd-2.6.8.1-3.img


other=/dev/hda1
label=Windows

The system.map and the vmlinux have all been adjusted to suite my new kernel. I am beyond frustrated at this point consider this has been my 7th attempt at doing this on the my computer. Please any help would be appreciated.

"initrd=/boot/initrd-2.6.8.1-3.img"

One of your problems seems to be that you are using a 2.6.8 initrd with a 2.6.7 kernel.

Diagnosing your other problems would be easier if you could describe what is happening on the screen when you try to boot YOS-2.6.7.

-------------------------------
Steve Stites

From what i understand is that the initrd is strictly for scsi. As for what happens when I attempt to load the new kernel iis nothing at all. It loads as if I did nothing. any thoughts?

"any thoughts?"

Yes. Your astroturf technique is very poor. You should find an honest way to make a living.

--------------------------
Steve Stites

Did you remember to re-run LILO after modifying /etc/lilo.conf?

ok I have no idea what Jailbait is saying, anyway no I haven't. By running lilo do you mean just opening and editing the file or is there another command that I may be missing?

I think he means /sbin/lilo as root. Which you should do anytime you edit lilo.conf

Yeah i did that yet I still am not able to load the kernel. I even attempted to add a new entry to lilo.conf to see if that would clarify the issue. I run /sbin/lilo to add the entry and no entry appears on the boot menu. I must be missing one simple thing.

Would it make sense if there was a way to dected where the old kernel was and how it is still booting? According to the guide I have removed all the links to the old kernel. Just running through some ideas.