hello,

to a new debian (testing) installation I compiled the 2.6.24 kernel. It compiled (not the debian way but via make && make modules_install) and the bzImage went to /boot/vmlinuz-2.6.24-xen
With mkinitramfs I made the initrd-2.6.24.

The problem:

update-grub only detects the old kernel (2.6.22), not my newly built. When I edit /boot/grub/menu.lst manually he complains on restart that /lib/modules/2.6.24/modules.dep is not there. Although it is there!

My boot directory looks like:

-rw-r--r-- 1 root root 80542 2008-02-03 14:46 config-2.6.22-3-686
drwxr-xr-x 2 root root 4096 2008-02-03 14:37 grub
-rw-r--r-- 1 root root 5869569 2008-02-03 14:46 initrd-2.6.24
-rw-r--r-- 1 root root 5860275 2008-02-03 14:46 initrd.img-2.6.22-3-686
-rw-r--r-- 1 root root 5457295 2008-02-03 14:46 initrd.img-2.6.22-3-686.bak
-rw-r--r-- 1 root root 810034 2008-02-03 14:46 System.map-2.6.22-3-686
-rw-r--r-- 1 root root 1359376 2007-11-12 12:56 vmlinuz-2.6.22-3-686
-rw-r--r-- 1 root root 1449176 2008-02-03 14:26 vmlinuz-2.6.24-xen

I suspected that I missed some ext3 option. But I tried both building ext3 as module and "star".

What to do? Thanks in advance!!

Ok I somehow cornered the problem and found a solution (uff )
First, why did update-grub not find the new kernel image? Well after compiling the kernel with make && make modules_install it is "obviously" not enaugh to just copy the bzImage somewhere in the boot directory, no you got to type make install. Then something happens which makes update-grub recognize your kernel image.

Second, why did the kernel not find my modules? Well, actually this is something I do not understand fully *g*. It is not enough to compile ext3 support hard into the kernel, of course you have to do so with your IDE support, too. After that was done everything worked fine, without the initrd.img. So something does not work with mkinitramfs. There seems to be another command, namely mkinitrd, for making initrd s. Maybe I have chosen the wrong command, who knows. But on my machine there was no mkinitrd, even after (maybe I screwed up here) installing an initrd-tools.rpm.

Cheers