From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265393AbTLHNZx (ORCPT ); Mon, 8 Dec 2003 08:25:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265394AbTLHNZw (ORCPT ); Mon, 8 Dec 2003 08:25:52 -0500 Received: from nat-pool-bos.redhat.com ([66.187.230.200]:22465 "EHLO thoron.boston.redhat.com") by vger.kernel.org with ESMTP id S265393AbTLHNZv (ORCPT ); Mon, 8 Dec 2003 08:25:51 -0500 Date: Mon, 8 Dec 2003 08:25:48 -0500 (EST) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: Ralf Orlowski cc: Linux Kernel Mailing List Subject: Re: crypto support in kernel 2.4.23 In-Reply-To: <200312051909.07265.ralf@orle.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 5 Dec 2003, Ralf Orlowski wrote: > Hi, > > can someone tell me, how I can get the crypto support to work in kernel > 2.4.23. > > When I try to use this, the kernel compiles just fine with crypto activated > in the configuration. But when I then try to load the modules I always get > these error-messages: > > /lib/modules/2.4.23/kernel/crypto/twofish.o: unresolved symbol > crypto_unregister_alg > /lib/modules/2.4.23/kernel/crypto/twofish.o: unresolved symbol > crypto_register_alg > /lib/modules/2.4.23/kernel/crypto/twofish.o: insmod > /lib/modules/2.4.23/kernel/crypto/twofish.o failed > /lib/modules/2.4.23/kernel/crypto/twofish.o: insmod twofish failed > > Does someone know, what is missing here? I couldn't find any documentation, > that already mentions this problem. Please post your .config. - James -- James Morris