modules work, compiled into kernel not

[unixtroll]

Hi,
I followed http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedDeviceUsingLUKS to convert my external disk to a encrypted storage device. Everything is working fine, except the following:
In order to get the encryption done I need
Cryptographic Options ---> Serpent cipher algorithm and
Cryptographic Options ---> SHA256 digest algorithm
loaded.
If I compile these both as modules & load them, a "cat /proc/crypto" shows both algorithms and everything is working flawlessly.
But if I compile both into the kernel, do a "make" and "make install" and then reboot, after that "cat /proc/crypto" doesn't show anything even though both algorithms should be compiled into the kernel.

Not really a serious problem as I could still just use the modules, but since I'd like to encrypt my root partition also, I think it would be better to have the stuff compiled-in instead of having to bother with "insmod" later on.

Any suggestions?

[chrbecke]

Maybe you are not booting the new kernel?

You could check by activating "General Setup->Kernel .config support" and "General Setup->Enable access to .config through /proc/config.gz", rebuild and install your kernel and reboot. You should then be able to see the config of the currently running kernel in /proc/config.gz.

I have never used "make install" to install my new kernels, I always copied arch/i386/boot/bzImage and System.map manually to /boot and adjusted /boot/grub/grub.conf. I always keep my old kernel and add the new kernel as new boot option to my grub.conf, so I can switch between the new and old kernel on boot. Thus I can easily get my system running again in case the new kernel is buggy.