On Sun, 10 Jun 2012 23:25:02 +0100 Jon Dowland <j...@debian.org> wrote:
> On Sun, Jun 10, 2012 at 08:28:10AM -0400, Celejar wrote: > > Hi, > > > > I have my rootfs on lvm on top of a luks (cryptsetup) encrypted volume. > > System has been working fine since installation with stock Debian, as > > well as self-built kernels (2.6.x - 3.3.8, grub2), using a ram > > disk (initramfs) with cryptsetup included to unlock the luks volume on > > boot. With recent 3.4.x kernels (stable branch, 3.4.1 / 3.4.2), th > > system fails to unlock the luks volume, reporting: > > > > cryptsetup: evms_activate not available > > > > [or something like that - typing from memory] > > > > Running amd64 stable, with some backports stuff, on a Lenovo Thinkpad > > t61. Any idea what this is? > > Are the failing kernels hand built or are they packaged? Hand built from vanilla upstream sources. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120610221913.222a3ec0.cele...@gmail.com
