Your message dated Wed, 28 Apr 2010 12:20:10 +0200 with message-id <20100428102010.GA4865@resivo.wgnet.de> and subject line Re: [pkg-cryptsetup-devel] Resolved for me (Was: Re: Bug#568008: ...) has caused the Debian Bug report #568008, regarding linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 568008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568008 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian bug reports <submit@bugs.debian.org>
- Subject: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device
- From: Julian Gilbey <jdg@debian.org>
- Date: Mon, 1 Feb 2010 20:23:03 +0000
- Message-id: <20100201202303.GA13213@polya.uklinux.net>
Package: linux-image-2.6.32-trunk-amd64 Version: 2.6.32-5 Every time I boot - and I'm using crypto file systems - I get the series of messages (copied from bootlog): Starting early crypto disks...sda2_crypt (starting)... Unlocking the disk /dev/sda2 (sda2_crypt) Enter passphrase: modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-trunk-amd64/kernel/drivers/crypto/padlock-sha.ko): No such device Key slot 0 unlocked. Any ideas what this FATAL error is about and whether it is a problem? Julian
--- End Message ---
--- Begin Message ---
- To: "Mader, Alexander (N-MSR)" <Alexander.Mader@niles.de>
- Cc: 568008-done@bugs.debian.org
- Subject: Re: [pkg-cryptsetup-devel] Resolved for me (Was: Re: Bug#568008: ...)
- From: Jonas Meurer <jonas@freesources.org>
- Date: Wed, 28 Apr 2010 12:20:10 +0200
- Message-id: <20100428102010.GA4865@resivo.wgnet.de>
- In-reply-to: <4BD68C0D.4050503@niles.de>
- References: <4BBECEA7.3080300@niles.de> <4BD68C0D.4050503@niles.de>
On 27/04/2010 Mader, Alexander (N-MSR) wrote: > Hello, > > apparently the default encryption in cryptsetup changed with some > update. After adding "cipher=<cipher>" to /etc/crypttab the > cryptsetup worked correctly. yes, that is documented in /usr/share/doc/cryptsetup/NEWS.Debian.gz. closing this bug. thanks for further debugging. > The kernel module error message remains but that's not important for > me any more :-) that's another known issue. it can be ignored. greetings, jonasAttachment: signature.asc
Description: Digital signature
--- End Message ---