hey,
On 04/09/2009 Paul Millar wrote:
On Thursday 03 September 2009 19:43:28 Jonas Meurer wrote:
[...] please run the following command:
# sh -x mkinitramfs -o /tmp/initramfs 2/tmp/initramfs.log
and send /tmp/initramfs.log to the bugreport.
Attached.
Incidentally, I opened up
On Saturday 05 September 2009 12:50:35 Jonas Meurer wrote:
thanks. please also send me the output of the following commands:
# ls -l /dev/mapper
vedrfolnir:~# ls -l /dev/mapper
total 0
crw-rw 1 root root 10, 60 2009-09-04 19:06 control
lrwxrwxrwx 1 root root 7 2009-09-04 19:06
On Saturday 05 September 2009 12:50:35 Jonas Meurer wrote:
could you try downgrading to cryptsetup 2:1.0.7-1, regenerating the
initramfs and see whether the bug disappears? if it's related to device
files in /dev/mapper being links to /dev/dm-* then the bug should be
reproducible with old
hey,
On 02/09/2009 Paul Millar wrote:
After upgrading a few packages (listed below) I discovered my laptop was
unable to boot. The laptop
uses a Luks partition with LVM (this was using a standard guided partitioning
option back when I was
installing Debian). The boot fails at around
hey,
On 03/09/2009 Linus Lüssing wrote:
Yes, I'm having the same problem here. I updated cryptsetup yeseterday to
2:1.07-2 and now I can't boot my usual 2.6.30-1-amd64 anymore.
My other kernels on this machine seem unaffected, just my usual
kernel-image does not boot. So I can select/boot
5 matches
Mail list logo
