Quote Originally Posted by wex
I successfully installed and am running knoppix, I set up my apt sources and downloaded the lastest debian kernel-sources-2.6.4 package off testing. I compiled the kernel without problem, and then I did a dpkg -i MyKernel2.6.4.deb. When I did this it gave me the usual prompt about running lilo and I said yes.... No errors at all, but if I look at lilo.conf there was no new entry for my new kernel image and when I reboot it just takes me to the same old 2.4 kernel. Why isn't dpkg installing my new kernel into lilo????

-ryan
There would be no new entry created the symbolic links just get updated so it looks like the links may be messed up what does this command look like on your system.
Code:
>$ ll /vmlinuz*
lrwxrwxrwx    1 root     root           22 2004-03-31 01:54 /vmlinuz -> boot/vmlinuz-2.6.4-ck2
lrwxrwxrwx    1 root     root           35 2004-03-30 22:49 /vmlinuz.failsafe -> /boot/vmlinuz-2.4.20-bf2.4-failsafe
lrwxrwxrwx    1 root     root           18 2004-03-30 22:49 /vmlinuz.old -> boot/vmlinuz-2.6.4
The sections as they should appear in your lilo.conf.

Code:
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
        label=Linux
        read-only
#       restricted
#       alias=1

image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2

image=/vmlinuz.failsafe
        label=LinuxFailsafe
        read-only
        optional
You will not have the failsafe entry I created that to keep my install kernel for a backup but you should have the other two the vmlinuz should point to the new 2.6.4 kernel's vmlinuz in /boot and the vmlinuz.old should be the old knoppix one. If they are wrong then simply remove them and then recreate for example if I wanted a new link for the 2.6.4-ck2 kernel I am running I would as root ln -s /boot/vmlinuz-2.6.4-ck2 /vmlinuz this after having first rm vmlinuz. You should re-run lilo after changing the link(s) to write the new configuration to the MBR or wherever it is being installed.