Quote Originally Posted by hw-tph
Have you tried installing a 2.4.22 kernel on the P120 previously? If that's the case you might be installing the modules in a previously used directory (/lib/modules/<uname -r>).

If you can get as far as logging in to this computer with the new kernel, try just running update-modules as root.

The build directory should have nothing to do with the resulting kernel package.

hw
No I didn't installed any previous 2.4.22 kernels. But to be honest, after rebuilding the kernel package with a different config on the P4, I kind of forgot to remove the /lib/modules/2.4.22.2003-sep-25 directory... so if there were modules with unresolved symbols left over from my first... they might be the troublemakers then. But I have to check that first.

About just saying [no] and installing the kernel-image completely... hmmm... I avoided that, because I didn't want to reboot my server with an half-broken kernel-image set up. But it seems so that I simply have to do that. Since I only have one VGA monitor and managed the server completely via SSH, I wanted to wait with the physical procedure of switching the VGA cable between both PCs as long as possible. :P

Thanks, you helped me a lot by pointing out some the obvious mistakes I may have done. It's a long time ago since I maintained my GNU box, so I've forgotten a lot. That's why I post.

If it fails, I'll come back.
Cheers.