| View previous topic :: View next topic |
| Author |
Message |
medicineman
n00b
Joined: 17 Oct 2006
Posts: 15
Location: Mcdonough, Georgia, USA
|
 Posted: Thu Aug 28, 2008 8:52 pm Post subject: cryptsetup: CONFIG_DM_CRYPT: is not set [SOLVED] |
 |
|
System:
New install with AMD64 and kernel-2.6.25-gentoo-r7
Some system tools, fcron, syslog-ng, xorg-server, ati-drivers, slim, fluxbox, opera, mc,
thunar, thunar-volman (and dependencies)
Problem:
sys-fs/cryptsetup-1.0.5-r1 was pulled in as a dependency.
It compiles successfully but gives the following message
| Quote: | * Messages for package sys-fs/cryptsetup-1.0.5-r1:
# CONFIG_DM_CRYPT: is not set (required for cryptsetup) |
I have been unable to find this config option in the kernel or by searching my kernel config file.
A quick search in Bugzilla did not get me anywhere.
Snippet from /boot/.config-2.6.25-gentoo-r7
| Quote: | # Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
# CONFIG_CRYPTO_SEQIV is not set
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_ECB is not set
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_LZO is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set
|
After rebooting, the boot process hangs for a time while waiting for uevents. (I am assuming this is related)
I do not really need cryptsetup at the moment. All I really care about is speeding up the boot process and
getting a stable build.
Any ideas?
BTW: I have been away from linux for a while due to a painfully slow internet
connection, so take it easy on me 
Last edited by medicineman on Thu Aug 28, 2008 11:46 pm; edited 1 time in total |
|
| Back to top |
|
 |
skellr
l33t
Joined: 18 Jun 2005
Posts: 988
Location: The Village, Portmeirion
|
| Posted: Thu Aug 28, 2008 9:05 pm Post subject: |
|
|
It's probably hal pulling in cryptsetup with the crypt USE flag.
| Quote: | | After rebooting, the boot process hangs for a time while waiting for uevents. (I am assuming this is related) |
I'm not really sure what causes this. 
If you mount your root partition somewhere else and look in the dev/ directory, is it empty? Make sure it has at least console and null in there. It can boot without them but it boots faster with them. rsync will copy them eaisly.
rsync -a /dev/{null,console} /mnt/tmp/dev/ |
|
| Back to top |
|
|
medicineman
n00b
Joined: 17 Oct 2006
Posts: 15
Location: Mcdonough, Georgia, USA
|
| Posted: Thu Aug 28, 2008 11:45 pm Post subject: |
|
|
Solved
CONFIG_DM_CRYPT was hidden until I enabled other options in the kernel. 
| Code: | <*> Multiple device driver support (Raid and LVM)
<*> Device mapper support
<*> Crypt target support |
I plan to encrypt my /home partition so I will need this eventually.
Unfortunately, it did not solve my boot problem.
I still get this:
| Quote: | Populating /dev with existing devices through uevents...
Waiting for uevents to be processed... |
I probably need to dig around in the kernel options some more to fix it.
Oh well, at least one problem is solved. |
|
| Back to top |
|
|
gohmdoree
Guru
Joined: 12 Oct 2004
Posts: 533
|
| Posted: Mon Dec 27, 2010 3:05 am Post subject: |
|
|
thanks for the clarification. helped me.
what was your fix for the populating /dev with existing devices through uevents? i get the same, but didn't think of it as an issue. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
