From: Udo van den Heuvel <udovdh@xs4all.nl>
To: Milan Broz <mbroz@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: crypt issue with 2.6.30/gcc 4.4.0?
Date: Sun, 14 Jun 2009 18:10:53 +0200 [thread overview]
Message-ID: <4A35210D.2030603@xs4all.nl> (raw)
In-Reply-To: <4A351D22.3020404@redhat.com>
On 2009-06-14 17:54, Milan Broz wrote:
>> With 2.6.30 I see the Password prompt being repeated, after all the USB
>> messages, as soon as I press the first letter of the password. Each time
>> the password is entered it is not accepted and a new Password: prompt is
>> printed up to a total of three tries.
>
> password prompt in Fedora is handled completely in userspace in initrd
> by plymouth, then it send password to cryptsetup.
Yes. I saw that in mkinitrd source...
> You did provide neither kernel log messages
The kernel is just booting up, messages scroll by fast, no strange stuff
appears as far as I can see.
> nor description of changes to
> your kernel config...
I got the 2.6.29.4 .config, copied it into 2.6.30 tree and added ext4 as
fs and nfs4 server support. Nothing much in the area of where the
problem is?
> Try run it in text mode with full kernel log,
How to retrieve the log?
> also try enable some debug mode in plymouth and check exact error message.
Will have look into possibilties there.
> (Are you using mkinitrd from F11? Also see fedora bug 470740)
Indeed. This looks very much like it, although I use a normal PS/2
keyboard and I'll have to count the asterisks.
Thanks for this tip!!
Udo
prev parent reply other threads:[~2009-06-14 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 13:37 Udo van den Heuvel
2009-06-14 15:16 ` Mikael Pettersson
2009-06-14 15:22 ` Udo van den Heuvel
2009-06-14 15:39 ` Mikael Pettersson
2009-06-14 15:36 ` Udo van den Heuvel
2009-06-14 15:54 ` Milan Broz
2009-06-14 16:10 ` Udo van den Heuvel [this message]
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=4A35210D.2030603@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.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
all inboxes | Powered by JetHome®