[pkg-cryptsetup-devel] Bug#562427: Bug#562427: Fwd: Bug#562427: cryptsetup: Cannot enter luks pass phrase with USB keyboard during boot

John Martin jam101 at gmail.com
Mon Feb 15 22:12:33 UTC 2010


On Mon, Feb 15, 2010 at 4:14 AM, Jonas Meurer <jonas at freesources.org> wrote:
> hey John,
>
> On 26/12/2009 John Martin wrote:
>> On Fri, Dec 25, 2009 at 3:18 PM, Christoph Anton Mitterer
>> <christoph.anton.mitterer at physik.uni-muenchen.de> wrote:
>> > Quoting John Martin <jam101 at gmail.com>:
>> >>
>> >> How do we make that right?
>> >
>> > Add the required modules to  /etc/initramfs-tools/modules
>> >
>> >> Were modules usbhid, hid, usbcore, nls_base in the "most" but lost
>> >> with the "blacklist usbkbd" that appeared in the strings of the
>> >> initrd.img?
>> >
>> > Don't think so.... this should just control loading of modules, not their
>> > inclusion.
>> >
>> > But I agree that they should be there if MODULES=most...
>> > Is there perhaps something in /etc/initramfs-tools/conf.d/resume which
>> > overrides this?
>>
>> ,----[ cat /etc/initramfs-tools/conf.d/resume  ]
>>  RESUME=/dev/mapper/athene-swap
>> `----
>>
>> Nothing under  /etc/initramfs-tools looks suspicious to me.
>>
>> Now I try
>>
>> # cat <<EOF >>/etc/initramfs-tools/modules
>> >
>> > usbhid
>> > hid
>> > usbcore
>> > nls_base
>> > EOF
>>
>> ,----[ sudo update-initramfs -u -v -k $(uname -r) | egrep
>> 'usbhid|hid|usbcore|nls_base' ]
>>  Adding module /lib/modules/2.6.32-trunk-amd64/kernel/fs/nls/nls_base.ko
>>  Adding module /lib/modules/2.6.32-trunk-amd64/kernel/drivers/usb/core/usbcore.ko
>>  Adding module /lib/modules/2.6.32-trunk-amd64/kernel/drivers/hid/hid.ko
>>  Adding module /lib/modules/2.6.32-trunk-amd64/kernel/drivers/hid/usbhid/usbhid.ko
>> `----
>>
>> Reboot but no joy.  Same as before.
>
> are you sure that your booloader uses the updated initramfs image?

Yes.

> do you use a selfcompiled kernel?

No.

> does 'lsmod' on the running system contain any usb/keyboard modules > that you didn't include in the initramfs image?

No.

> please attach the output of
> 'sh -x mkinitramfs -o /tmp/initramfs-$(uname -r) 2> /tmp/initramfs.log'

Attached.

Also attached are:

1.  The /boot/initrd.img-2.6.32-trunk-amd64  created when upgrading
update-inetd [4.35 -> 4.36]  earlier today.

2.  Some current system info.

> btw, this bug seems to belong to initramfs-tools instead of cryptsetup.

Many thanks for your continued attention to this.

jam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: initramfs.log
Type: text/x-log
Size: 76176 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100215/fa1f3241/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug-cryptosetup-info
Type: application/octet-stream
Size: 22212 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100215/fa1f3241/attachment.obj>


More information about the pkg-cryptsetup-devel mailing list