Hi,
Bear with me, this is a long email. Ideally, if you're reading it, you're
involved or interested in dracut. If you don't think anybody will read it here,
please point me to the right place.
My setup is: / is unencrypted, on /sdd1. /sdd2 contains a luks volume, which in
turn contains an lvm volume with swap (and another partition.)
Lots of things happened, I'm going to try to summarize:
I'm using wheezy with wheezy backports. Installing kernel 3.16.0 (suspend and
hibernate don't work for me in 3.2.0) pulled in dracut.
Out of the box, dracut's initrd prompted me for a password, but the keyboard was
not active (generic logitech wired usb keyboard.) Thankfully, the 3.2.0 kernel
booted, without passphrase prompt (init system's cryptdisks-early.sh unlocked
the luks volume.)
Googling led to me including hid-generic in /etc/dracut.conf.
However, 3.2.0 doesn't know about hid-generic, and now "dpkg-reconfigure dracut"
won't create a new initrd for it. (which was good, since I had a working initrd
dracut refused to mess up, but it's still undesired behaviour in general.) But
it will generate a new initrd for 3.16.0.
With hid-generic and 3.16.0, the keyboard worked, and I could type in my pass
phrase. After typing it in, nothing happened (at all, even with kopts rdshell
rinitdebug and no quiet.) I could also type and see the input, and noticed the
keymap was the wrong one (I'm using Dvorak, this was ANSI.)
I got dracut to boot the 3.16.0 kernel by enabling host-only mode. Now dracut
complains when making initrds:
E: i18n_vars not set! Please set up i18n_vars in configuration file.
E: No KEYMAP.
Debian bugs #640101 [0] and #664678 [1] suggest this shouldn't happen. I don't
know how to remedy the situation. Now I know for sure that the wrong keymap will
be loaded, if any!
Regardless, dracut doesn't prompt me for a passphrase (root volume is NOT
encrypted) and /etc/init.d/cryptdisks-early.sh is run only after some initial
console initialization, so I could easily give my pass phrase and boot. At this
point, suspend works, but hibernate doesn't.
When I hibernate, the disk image gets written correctly (kernel log messages
tell me so.) On boot, dracut ignores the image, and just does a normal init.
A Fedora bug [2] led me to include resume=UUID=
in kopts. Since I have debug messages on, I see dracut outputting a large-ish
amount of shell code to the console (this doesn't seem to get logged to a file.)
It ends in "sleep 0.5." Predictably, it flickers every half a second as it is
being reprinted several times. It seems there is a max counter on this, as after
some iterations it just falls back into cold boot, which works and brings me to
my system's login screen. This [3] is probably the code in question.
To summarize my problems:
* Dracut requires hid-generic to recognize usb keyboard at initrd boot
* hid-generic is applied to all kernels on dpkg-reconfigure dracut, which will
then fail on older kernels.
* Even with a recognized keyboard dracut doesn't seem to check the pass phrase
correctly, or continue booting
* The keymap isn't getting set correctly
* host-only mode seems to be required to boot my particular setup at all
* host-only mode seems to interfere with Debian's custom way of setting the
keymap (which doesn't seem to be working in the first place.)
* Out of the box, resume doesn't work
* Including the resume= kopt does not work either
I'm happy to have a working system, but I'm unhappy with the amount of work it
took, and I'm also unhappy that hibernate is not working.
Should I report any/all of the above bullet points as bugs? How can I get dracut
to resume from hibernate on my setup?
Versions, as reported by apt-cache show:
dracut: 020-2
linux-image-3.16.0-0.bpo.4-amd64: 3.16.7-ckt2-1~bpo70+1
lvm2: 2.02.95-8
cryptsetup: 2:1.4.3-4
(all in wheezy or wheezy-backports)
I'm not using systemd. I've attached some relevant config and log
files. dracut.log is from last initrd creation, kern.log from last
boot. Configuration files are in the current (bootable with 3.16.0, but not
hibernateable state)
If any additional information should be provided, please do tell me. Thanks!
Regards,
Aleks
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640101
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664678
[2] https://bugzilla.redhat.com/show_bug.cgi?id=781728
[3]
https://github.com/haraldh/dracut/blob/bea41b898a93e4437640817964861bbb694b01e6/modules.d/99base/init.sh#L174
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="rdshell rdinitdebug
resume=UUID=8981a3b5-07d4-4ceb-a7b2-f4f5865970b1"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required)
