On Wed, 20 Mar 2013 23:47, Carlos E. R.
On Wednesday, 2013-03-20 at 14:38 -0300, Cristian Rodríguez wrote:
El 20/03/13 11:32, Andrey Borzenkov escribió:
Yes, I do.
loading of module is triggered by cryptsetup. It does not load it itself, but may be internally kernel probes for all crypto providers.
Yes, but this is not an internal probe and none of the machines where is see this msg has encrypted filesystems.
Interesting. So you and I get the message for different reasons.
Or... is there a reason the kernel or whatever probes for encrypted filesystems when there is none?
Question to the OP (and all other in this threat): Have you messed with "/etc/sysconfig/kernel" ? Or "/etc/modprobe.d/99-local.conf" ? On my old Evergreen 11.2 box I do not see the error in my logs (neither boot.msg nor allmessages) and I have changed my /etc/sysconfig/kernel to reflect my hardware (INITRD_MODULES, MODULES_LOADED_ON_BOOT) and rebuild the initrd-file, that may be a point to look for. Also the files in: /etc/modprobe.d/* esp. /etc/modprobe.d/99-local.conf are worth a look, as everything I did not need, I've disabled. Most of it via "alias xxxxx off" or "install xxxx /bin/true" on 99-local.conf. - Yamaban.