Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase
Control: tag -1 wheezy wontfix Control: affects -1 console-tools Control: notfound -1 0.107 Control: found -1 0.108 On Thu, 28 Nov 2013 11:37:54 +0100 Ondřej Vodáčekwrote: > Hello, > > I have upgraded initramfs-tools to version 0.115 and it looks like its fixed. Same keyboard layout like in version 0.107. I don't see any changes between 0.109 and 0.115 that might have fixed this. It appears that initramfs-tools doesn't work properly with console- tools (but does work with kbd). console-tools was removed after wheezy, so this is now moot. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase
Hello, I have upgraded initramfs-tools to version 0.115 and it looks like its fixed. Same keyboard layout like in version 0.107. Regards Ondřej Vodáček -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase
On Tue, Oct 09, 2012, Jean-Luc Coulon wrote: Please send us the file /tmp/i/etc/boottime.kmap.gz Attached Thanks. Well, as far as I can see this is a correct keymap. Se we have to figure out for what reason it hasn't been activated. It is not an Unicode keymap, it is for ISO 8859-1 or ISO 8859-15. Is this the encoding used on your system? Anyway, since your password contains only ASCII symbols, I don't think this can be the source of the problem. Another possibility is that the the initramfs image doesn't contain the gzip binary (yes -- gzip, not gunzip). Two methods to solve this -- either include gzip in the image, or I can change setupcon to generate uncompressed keymap. Considering that the generated boottime.kmap.gz seems to be correct, this is all that can occur to my mind at the moment. On Tue, Oct 09, 2012, Ondřej Vodáček wrote: I have encountered the same problem after upgrading from 0.107 to 0.108. I have my root and home partitions on lvm on an encrypted device. It is definitely a keymap problem. After 3 unsuccessfully tries typing the passphrase a shell (busybox?) appeared and I was able to figure out, that is switched to an English(?) layout. Normally I have a Czech keyboard layout. I was then able to type in the right passphrase and continue booting. Ok, in case we have here the same source of the problem, this confirms that the problem is not Unicode/non-Unicode related. Please try the command loadkeys /etc/boottime.kmap.gz while you are at this busybox shell and tell us the result. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase
Dne 10.10.2012 08:16, Anton Zinoviev napsal(a): On Tue, Oct 09, 2012, Jean-Luc Coulon wrote: Please send us the file /tmp/i/etc/boottime.kmap.gz Attached Thanks. Well, as far as I can see this is a correct keymap. Se we have to figure out for what reason it hasn't been activated. It is not an Unicode keymap, it is for ISO 8859-1 or ISO 8859-15. Is this the encoding used on your system? Anyway, since your password contains only ASCII symbols, I don't think this can be the source of the problem. Another possibility is that the the initramfs image doesn't contain the gzip binary (yes -- gzip, not gunzip). Two methods to solve this -- either include gzip in the image, or I can change setupcon to generate uncompressed keymap. when I run 'ls bin' while I am in the busybox both gzip and gunzip are listed Considering that the generated boottime.kmap.gz seems to be correct, this is all that can occur to my mind at the moment. On Tue, Oct 09, 2012, Ondřej Vodáček wrote: I have encountered the same problem after upgrading from 0.107 to 0.108. I have my root and home partitions on lvm on an encrypted device. It is definitely a keymap problem. After 3 unsuccessfully tries typing the passphrase a shell (busybox?) appeared and I was able to figure out, that is switched to an English(?) layout. Normally I have a Czech keyboard layout. I was then able to type in the right passphrase and continue booting. Ok, in case we have here the same source of the problem, this confirms that the problem is not Unicode/non-Unicode related. Please try the command loadkeys /etc/boottime.kmap.gz the output is: /bin/sh: loadkeys: not found while you are at this busybox shell and tell us the result. Anton Zinoviev Regards Ondřej Vodáček -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase
On Wed, Oct 10, 2012 at 09:32:21AM +0200, Ondřej Vodáček wrote: Please try the command loadkeys /etc/boottime.kmap.gz the output is: /bin/sh: loadkeys: not found Good! It seems we've found the culprit. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689851: initramfs-tools: Wrong keymap at boot while, prompting for the passphrase
Hello, I have encountered the same problem after upgrading from 0.107 to 0.108. I have my root and home partitions on lvm on an encrypted device. It is definitely a keymap problem. After 3 unsuccessfully tries typing the passphrase a shell (busybox?) appeared and I was able to figure out, that is switched to an English(?) layout. Normally I have a Czech keyboard layout. I was then able to type in the right passphrase and continue booting. Regards Ondřej Vodáček -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689851: initramfs-tools: Wrong keymap at boot while prompting for the passphrase
* Jean-Luc Coulon (f5ibh) [Sun Oct 07, 2012 at 09:55:54AM +0200]: I've some encrypted filesystems over lvm. After upgrading from 0.107 to 0.108, it refuses my passphrase at boot. I suppose it is related to the keymap. I've reverted to 0.107 at that fixed the problem. I've then upgraded to 0.109 and I've the same problem again. Once again, I've reverted to 0.107 and the probelm is fixed. Please provide output of: update-initramfs -u -k $(uname -r) -v for your system, both for v0.107 and v0.109. regards, -mika- signature.asc Description: Digital signature
Bug#689851: initramfs-tools: Wrong keymap at boot while prompting for the passphrase
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 08/10/2012 08:15, Michael Prokop a écrit : Please provide output of: update-initramfs -u -k $(uname -r) -v Output attached Regards Jean-Luc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFQcr4GUdGGXzzGnNARAu4EAJsHJjwPnm8xJeDyITT/VScz9x3AiACfRuVJ U4/QSZXGiMrrwTJd8CEHbXc= =d+cc -END PGP SIGNATURE- Keeping /boot/initrd.img-3.6.1-k8-1.dpkg-bak update-initramfs: Generating /boot/initrd.img-3.6.1-k8-1 Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/hid/hid.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/hid/hid-generic.ko Copying module directory kernel/drivers/net (excluding appletalk arcnet bonding can hamradio irda pcmcia tokenring usb wan wimax wireless) Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/dummy.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/slip/slhc.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ppp/ppp_generic.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ppp/pppox.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ppp/pppoe.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ppp/ppp_mppe.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ppp/bsd_comp.ko Adding module /lib/modules/3.6.1-k8-1/kernel/lib/zlib_deflate/zlib_deflate.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ppp/ppp_deflate.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/tun.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/macvlan.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/mii.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ethernet/realtek/r8169.ko W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 Adding module /lib/modules/3.6.1-k8-1/kernel/fs/configfs/configfs.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/netconsole.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/eql.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/ifb.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/slip/slip.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/net/veth.ko Copying module directory kernel/drivers/scsi Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/scsi_mod.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/scsi_transport_iscsi.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/scsi_transport_sas.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/scsi_tgt.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/raid_class.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/sg.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/ata/libata.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/libsas/libsas.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/cdrom/cdrom.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/sr_mod.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/scsi_transport_spi.ko Adding module /lib/modules/3.6.1-k8-1/kernel/lib/crc-t10dif.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/scsi/sd_mod.ko Copying module directory kernel/drivers/block Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/block/loop.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/block/cryptoloop.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/block/pktcdvd.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/block/nbd.ko Copying module directory kernel/drivers/ata Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/ata/pata_atiixp.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/ata/pata_amd.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/ata/libahci.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/ata/ahci.ko Copying module directory kernel/drivers/mmc Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/misc/tifm_core.ko Adding module /lib/modules/3.6.1-k8-1/kernel/drivers/mmc/core/mmc_core.ko Adding module
Bug#689851: initramfs-tools: Wrong keymap at boot while prompting for the passphrase
[Cc-ing Anton as being maintainer of setupcon] * Jean-Luc Coulon [Mon Oct 08, 2012 at 01:50:31PM +0200]: Le 08/10/2012 08:15, Michael Prokop a écrit : Please provide output of: update-initramfs -u -k $(uname -r) -v Output attached [...] Calling hook keymap Adding binary /bin/loadkeys Adding library /lib/libcfont.so.0 Adding library /lib/libctutils.so.0 Adding library /lib/libconsole.so.0 WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger [...] This looks like the culprit. Anton, what do you think about this issue? regards, -mika- signature.asc Description: Digital signature
Bug#689851: initramfs-tools: Wrong keymap at boot while prompting for the passphrase
On Mon, Oct 08, 2012 at 02:59:17PM +0200, Michael Prokop wrote: [Cc-ing Anton as being maintainer of setupcon] Calling hook keymap Adding binary /bin/loadkeys Adding library /lib/libcfont.so.0 Adding library /lib/libctutils.so.0 Adding library /lib/libconsole.so.0 WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger [...] This looks like the culprit. Anton, what do you think about this issue? Unfortunately, no. These warnings should be harmless (X recognises many keysyms that can be ignored on the console). Here is some questionary to the bug reporter that may help us to debug the problem: 1. What is the contents of /etc/default/keyboard? 2. Is the file /etc/default/keyboard correct? Can the symbols of the password be typed properly on the text console after the system has booted completely? 3. Does the password contain some non-ASCII symbols? 4. Does your keymap layout contain dead symbols or other surprises? 5. I suppose the initrd-image can be extracted in the following way: mkdir /tmp/i cd /tmp/i zcat /boot/_initrd_image_ | cpio -i Please send us the file /tmp/i/etc/boottime.kmap.gz Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689851: initramfs-tools: Wrong keymap at boot while prompting for the passphrase
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 08/10/2012 17:06, Anton Zinoviev a écrit : On Mon, Oct 08, 2012 at 02:59:17PM +0200, Michael Prokop wrote: [Cc-ing Anton as being maintainer of setupcon] Calling hook keymap Adding binary /bin/loadkeys Adding library /lib/libcfont.so.0 Adding library /lib/libctutils.so.0 Adding library /lib/libconsole.so.0 WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger WARNING: Unknown X keysym XF86Messenger [...] This looks like the culprit. Anton, what do you think about this issue? Unfortunately, no. These warnings should be harmless (X recognises many keysyms that can be ignored on the console). Here is some questionary to the bug reporter that may help us to debug the problem: 1. What is the contents of /etc/default/keyboard? # If you change any of the following variables and HAL and X are # configured to use this file, then the changes will become visible to # X only if HAL is restarted. In Debian you need to run # /etc/init.d/hal restart # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=microsoftmult XKBLAYOUT=fr XKBVARIANT=oss XKBOPTIONS=compose:lwin,terminate:ctrl_alt_bksp 2. Is the file /etc/default/keyboard correct? Can the symbols of the password be typed properly on the text console after the system has booted completely? Everything is fine whent booted. The system asks for the passphrase. Then it gives up (because of the wrong passphrase. Then the system asks to press ENTER to continue the boot process. It asks then again the passphrase. When I enter the passphrase, it boots normally. 3. Does the password contain some non-ASCII symbols? Ascii both uppercase and lowercase and semi-columns (;) 4. Does your keymap layout contain dead symbols or other surprises? It is a French keymap (basically azerty) so it has dead keys but not used for the password. An other features on the upper row is that numéric keys are shifted (the opposite of us keyboards) 5. I suppose the initrd-image can be extracted in the following way: mkdir /tmp/i cd /tmp/i zcat /boot/_initrd_image_ | cpio -i Please send us the file /tmp/i/etc/boottime.kmap.gz Attached Thanks Jean-Luc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFQcvuyUdGGXzzGnNARAgWQAJwMCmW0btZNGz4TEvMbNR919ZFDpwCfeKmy FCJot1NDiCdNpAPLG2+7Rg4= =glwf -END PGP SIGNATURE- boottime.kmap.gz Description: GNU Zip compressed data
Bug#689851: initramfs-tools: Wrong keymap at boot while prompting for the passphrase
Package: initramfs-tools Version: 0.107 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've some encrypted filesystems over lvm. After upgrading from 0.107 to 0.108, it refuses my passphrase at boot. I suppose it is related to the keymap. I've reverted to 0.107 at that fixed the problem. I've then upgraded to 0.109 and I've the same problem again. Once again, I've reverted to 0.107 and the probelm is fixed. Regards Jean-Luc - -- Package-specific info: - -- initramfs sizes - -- /proc/cmdline BOOT_IMAGE=/vmlinuz-3.6.0-k8-1 root=/dev/mapper/vg00-root_lv ro quiet - -- resume RESUME=UUID=993cd3a8-7837-4c17-bdee-b01ac7bd1d72 - -- /proc/filesystems ext3 fuseblk xfs ext4 - -- lsmod Module Size Used by snd_hrtimer 1597 1 cpufreq_stats 2993 0 cpufreq_conservative 5049 0 cpufreq_userspace 1992 0 xt_multiport1678 1 iptable_filter 1376 1 ip_tables 16898 1 iptable_filter x_tables 16463 3 ip_tables,xt_multiport,iptable_filter cpufreq_powersave942 0 binfmt_misc 6941 1 ext4 421844 4 crc16 1343 1 ext4 jbd2 72041 1 ext4 xfs 695186 4 exportfs3457 1 xfs sha256_generic 10117 2 aes_x86_64 7475 2 aes_generic26058 1 aes_x86_64 cbc 2528 1 dm_crypt 14974 1 it87 27989 0 hwmon_vid 3084 1 it87 loop 17256 0 radeon821556 3 drm_kms_helper 24934 1 radeon ttm58344 1 radeon fuse 64729 3 hid_logitech_dj 9980 0 joydev 9692 0 snd_hda_codec_hdmi 23384 1 snd_hda_codec_realtek57465 1 snd_hda_intel 22932 5 snd_hda_codec 82443 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel snd_pcm_oss21896 0 snd_mixer_oss 15299 1 snd_pcm_oss snd_pcm65295 4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel ftdi_sio 38199 1 snd_seq_dummy 1407 0 powernow_k812344 0 usbserial 28932 3 ftdi_sio snd_seq_oss27288 0 mperf 1123 1 powernow_k8 usbhid 35411 1 hid_logitech_dj snd_seq_midi_event 5388 1 snd_seq_oss snd_seq48394 6 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy kvm_amd47859 0 snd_seq_device 4884 3 snd_seq,snd_seq_oss,snd_seq_dummy kvm 350608 1 kvm_amd snd_timer 17910 3 snd_hrtimer,snd_pcm,snd_seq snd56757 22 snd_hda_codec_realtek,snd_pcm_oss,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_oss,snd_seq_device,snd_mixer_oss k10temp 2770 0 serio_raw 4377 0 pcspkr 1787 0 evdev 9574 20 soundcore 5098 1 snd snd_page_alloc 6801 2 snd_pcm,snd_hda_intel processor 25504 1 powernow_k8 button 4433 0 thermal_sys14115 1 processor ext3 185144 4 mbcache 5522 2 ext3,ext4 jbd55499 1 ext3 raid1 26512 3 md_mod 98696 4 raid1 dm_mirror 12960 0 dm_region_hash 6751 1 dm_mirror dm_log 8161 2 dm_region_hash,dm_mirror dm_mod 68821 72 dm_log,dm_mirror,dm_crypt hid_generic 1097 0 hid83072 3 hid_generic,usbhid,hid_logitech_dj usb_storage45696 0 sg 22106 0 sr_mod 14791 0 sd_mod 36008 10 crc_t10dif 1316 1 sd_mod cdrom 34984 1 sr_mod ahci 21016 10 libahci18655 1 ahci pata_atiixp 4819 0 microcode 8654 0 ohci_hcd 20480 0 r8169 53502 0 mii 3915 1 r8169 libata150364 3 ahci,libahci,pata_atiixp scsi_mod 166531 5 sg,usb_storage,libata,sd_mod,sr_mod ehci_hcd 40382 0 - -- /etc/initramfs-tools/modules hid_generic - -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = yes do_bootfloppy = no do_initrd = yes link_in_boot = no - -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=y COMPRESS=gzip DEVICE= NFSROOT=auto - -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no - -- /etc/crypttab md5_crypt UUID=a58c3614-300f-4715-aefe-58b2477bbc71 none luks - -- /proc/mdstat Personalities : [raid1] md5 : active raid1 sda3[0] sdb3[1]