From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o_Ndou-UqZpr for ; Fri, 18 Jan 2013 20:56:53 +0100 (CET) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 18 Jan 2013 20:56:52 +0100 (CET) Received: by mail-wi0-f171.google.com with SMTP id hn14so5526369wib.10 for ; Fri, 18 Jan 2013 11:56:52 -0800 (PST) Message-ID: <50F9A902.1@gmail.com> Date: Fri, 18 Jan 2013 20:56:50 +0100 From: Milan Broz MIME-Version: 1.0 References: <20130118193332.GA27673@tansi.org> <50F9A497.4000802@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] RHEL6 crypto support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Li Cc: dm-crypt@saout.de On 01/18/2013 08:45 PM, David Li wrote: > I don't have this issue on a standard RHEL6. But this is when I > tested my code on a slightly "customized" RHEL6. I guess something > has been removed but not totally sure. You are missing kernel crypto modules loaded. But because you did not specify what "customized" means, I cannot help, sorry. Just compare what modules are loaded on default install and in your customized version and you will see what is missing. Milan