Friday, April 19, 2013

CONFIG_DEVTMPFS: is not set when it should be


Problem

emerge  sys-fs/udev

* Messages for package sys-fs/udev-200:

 *   CONFIG_DEVTMPFS:    is not set when it should be.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.


Solution

 You have to check the following  option in your kernel config :

 Device Drivers-> Generic Driver 
* Maintain a devtmpfs filesystem to mount at /dev.  

 For getting the devfs automatically mounted at boot time it makes sense to also enable the option  
* Automount devtmpfs at /dev


Thursday, April 18, 2013

Chromium 26.0.1410.43 Failed

Problème


I tried to build this Chromium version : 26.0.1410.43 but whithout success.



Solution



The only solution I found it's to downgrade package :



 vi /etc/portage/package.mask.
 >www-client/chromium-23.0.1271.97






Merci à http://mindspill.net/computing/linux-notes/gentoo/how-to-downgrade-a-gentoo-package/

Sunday, April 14, 2013

CONFIG_DM_CRYPT: is not set (required for cryptsetup)

Problem

* Messages for package sys-fs/cryptsetup-1.4.3:

*   CONFIG_DM_CRYPT:   is not set (required for cryptsetup)
*
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
* This ebuild introduces a new set of scripts and configuration
* than the last version. If you are currently using /etc/conf.d/cryptfs
* then you *MUST* copy your old file to:
* /etc/conf.d/dmcrypt
* Or your encrypted partitions will *NOT* work.
* Please see the example for configuring a LUKS mountpoint
* in /etc/conf.d/dmcrypt
*
* If you are using baselayout-2 then please do:
* rc-update add dmcrypt boot
* This version introduces a command line arguement 'key_timeout'.
* If you want the search for the removable key device to timeout
* after 10 seconds add the following to your bootloader config:
* key_timeout=10
* A timeout of 0 will mean it will wait indefinitely.
*
* Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use
* a compatibility mode when using cryptsetup-1.1.x. This can be
* done by specifying the cipher (-c), key size (-s) and hash (-h).
* For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup


Solution

- Update kernel
- Check device drivers -> Multiple devices driver support (RAID and LVM) -> Crypt target support 
- emerge sys-fs/cryptsetup

See foolowing links :