From: Milan Broz <mbroz@redhat.com>
To: "Karl O. Pinc" <kop@meme.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Password is not accepted
Date: Wed, 21 Sep 2011 05:05:51 +0200 [thread overview]
Message-ID: <4E79548F.8080206@redhat.com> (raw)
In-Reply-To: <1316570636.4663.3@mofo>
On 09/21/2011 04:03 AM, Karl O. Pinc wrote:
> This is all driven by the initramfs. What happens is that,
> sometimes, the screen goes black for perhaps 15 or more
> seconds starting about 3 or 4 seconds after the luks
> password prompt. Attempts to enter the password or portion
> thereof during this time always result in failure.
> I believe I've seen the same problem without the screen
> going black as well. If I wait a long time to enter the
> password all is well.
I had problems with late reset of usb devices
(with connected usb keyboard).
When I start to enter passphrase (in initramfs), usb kernel
module resets usb devices (perhaps just initialization)
and usually it cause lost of some entered characters.
Waiting few seconds helps - maybe this is the similar case
or just problem with another hw interfering (like gpu).
To debug such issues - boot kernel, intramfs (dracut or whatever
it is) with full debug to console, check what is logged
immediately before it happens.
(If it is too quick, just use some camera and record screen
or log it to serial console.)
With passphrase entered in late init where things run in
parallel (like systemd these days) even more magic can happen;-)
Milan
next prev parent reply other threads:[~2011-09-21 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D0CA156632144B8DB62D5E253C5AF6E8@adminDator>
2011-09-20 23:43 ` [dm-crypt] Password is not accepted Arno Wagner
2011-09-21 2:03 ` Karl O. Pinc
2011-09-21 3:05 ` Milan Broz [this message]
2011-09-21 12:57 ` ken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E79548F.8080206@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=kop@meme.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox