FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

LinkBack Thread Tools
Old 11-16-2009, 10:25 PM
Mark Hedges
Default Bug#555676: crypto boot broke due to gnome-vfs=>devicekit-disks which removed dmsetup=>cryptsetup?

I also had the problem of not being able to boot with crypto
disks using the stock kernel, which started recently.

Finally I realized the initramfs cryptsetup scripts were
missing. I remembered gnome-vfs (or something) had
preferentially installed devicekit-disks. devicekit-disks
suggests cryptsetup, but cryptsetup requires dmsetup, which
conflicts with devicekit-disks, so cryptsetup was removed.
Then when the initrd image updated, it no longer booted.
Luckily update-initramfs did not update my custom kernel or
it would have been very inconvenient.

If cryptsetup is not on your system, try installing it
again, and running update-initramfs for the kernels that
won't boot.

I guess I will file a bug report on... cryptsetup? It
should depend on either dmsetup or devicekit-disks? I'll
see what they think.


To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Thread Tools

All times are GMT. The time now is 01:59 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org