Vladimir Konrad <[EMAIL PROTECTED]> writes: > I have discussed possibility of remote access (ssh) for you to the > server and it is agreed that you can do it. If you are interested, I can > e-mail you the IP and the password. There is nothing important on the > server at the moment.
> The kernel source is 2.4.30 from kernel.org. The make-kpkg looks version > 1.94 (make-kpkg --help). Okay, I understand what's going on now. Thank you very much for letting me have temporary access to the system; that helped a great deal in tracking down the problem. You're running into another manifestation of bug #225907, which is already fixed in unstable but which unfortunately won't be fixed for sarge due to how late we are in the release cycle. Under specific situations, OpenAFS tries to build both SMP and UP kernel modules at the same time regardless of the SMPness of the kernel against which it's building. On the Alpha, this results in a compile failure when trying to build the SMP kernel on a UP system. On your SMP system, the result is that both kernel modules are built and then the UP module is copied over top of the SMP module, so that a UP module is actually installed and of course then doesn't work with your kernel. The workaround (and the reason why this isn't RC for sarge) is to build your kernel with CONFIG_MODVERSIONS (symbol versioning) enabled, which is generally recommended anyway. This unconfuses OpenAFS and causes the right module to be built and installed. The version of OpenAFS in unstable fixes the configure script so that it never tries to build both types of kernel at the same time. The problem doesn't appear for Debian kernels since Debian kernels are built with CONFIG_MODVERSIONS enabled. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
