From: Arno Wagner <arno@wagner.name>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] Kernel update: "Failed to access temporary keystore device."
Date: Fri, 1 Aug 2014 05:57:17 +0200 [thread overview]
Message-ID: <20140801035717.GA28952@tansi.org> (raw)
Hi all,
I just tried to upgrade my kernel from 3.10.48 to 3.14.15
(kernel.org). This is Debian wheezy. After the update, I
get "Failed to access temporary keystore device." when
trying to unlock my LUKS partitions. As far as I can tell
I have not changed anything relevant in the kernel config,
I just did a "make oldconfig" with the old kernel .config.
What is missing here or how do I debug this?
Gr"usse,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
next reply other threads:[~2014-08-01 3:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 3:57 Arno Wagner [this message]
2014-08-01 6:20 ` [dm-crypt] Kernel update: "Failed to access temporary keystore device." Milan Broz
2014-08-03 0:01 ` Arno Wagner
2014-08-03 19:41 ` Milan Broz
2014-08-04 1:13 ` Arno Wagner
2014-08-04 5:50 ` Yves-Alexis Perez
2014-08-04 5:53 ` Arno Wagner
2014-08-04 6:00 ` Yves-Alexis Perez
2014-08-20 23:40 ` Arno Wagner
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=20140801035717.GA28952@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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