hey john, On 21/02/2010 John Martin wrote: > On Sun, Feb 21, 2010 at 7:19 AM, Jonas Meurer <jo...@freesources.org> wrote: > > On 15/02/2010 John Martin wrote: > >> Also attached are: > >> > >> 1. The /boot/initrd.img-2.6.32-trunk-amd64 created when upgrading > >> update-inetd [4.35 -> 4.36] earlier today. > > > > seems like you forgot to attach the initramfs image. > > The silly mailer I'm using doesn't seem to like that file. Now I > attach the contents of my current initrd.img as gotten by cpio as > indicated at the head of the enclosed 'initrd-img-contents'.
all right. where does this driver-policy file come from? it sets MODULES=dep, and thus overwrites MODULES=most from initramfs.conf. maybe that's the problem? > > otherwise other users of encrypted rootfs would have run into the same > > issue. please check any custom changes you made to /etc/initramfs-tools > > and /etc/modprobe.d. > > The only change I have made, apart form what may have been done behind > my back by some package, has been to add usbhid, hid, usbcore, and > nls_base to /etc/initramfs-tools/modules as shown in my message #30 > above on 25 Dec. These should, presumably, be unnecessary however. why did you add the modules in the first place? did you already try to remove them from the file again? > > also, you could apply the attached patch to > > /usr/share/initramfs-tools/scripts/local-top/cryptroot and regenerate > > the initramfs afterwards in order to get some debugging output in the > > boot process. > > That gave me output including something like: > [[...]] > /scripts/local-top/cryptroot: line 1: lsmod: not found > the output of lsmod: ok, substitute lsmod with 'cat /proc/modules' then, and give it a try again. > are the usb keyboard modules loaded? > input any characters to test the keyboard: [[no visible effect]] so the bug is in no way related to cryptsetup. the keyboard doesn't work in your initramfs at all. i strongly believe that modules are missing from initramfs or aren't loaded. > However: > > ,----[ grep -E 'usb|hid|nls_base|lsmod' /tmp/initramfs/initrd.img-contents ] > ./lib/udev/usb_id > ./lib/modules/2.6.32-trunk-amd64/kernel/fs/nls/nls_base.ko > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/usb > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/usb/core > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/usb/core/usbcore.ko > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/hid > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/hid/usbhid > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/hid/usbhid/usbhid.ko > ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/hid/hid.ko > `---- > > So it appears that the four modules for usb keyboard are in the > image. What am I missing now? don't know. maybe some of the modules do conflict, or they're blacklisted, or not loaded for some other reason. i suggest to undo all the changes you did to initramfs configuration and regenerate the initramfs afterwards. > Thank you for your help. Do we have a bit more to go on now? let's see. unfortunately i'm busy with other things at the moment, and only have limited time to help you with debugging an issue that's not even related to the cryptsetup package at all. but let's see ... greetings, jonas
signature.asc
Description: Digital signature
