El 16/06/13 14:32, Carlos E. R. escribió:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm being more polite and I'm not blaming systemd diretly this time ;-)
Telcontar:~ # date;systemctl status systemd-modules-load.service Sun Jun 16 20:24:44 CEST 2013 systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Sun, 2013-06-16 13:57:46 CEST; 6h ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Main PID: 4703 (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-modules-load.service
Jun 16 13:57:46 Telcontar.valinor systemd[1]: Starting Load Kernel Modules... Jun 16 13:57:46 Telcontar.valinor systemd-modules-load[4703]: libkmod: kmod_config_parse: /etc/modprobe.d/10-unsupported-modules.conf line 10: ignoring bad line starting with 'allow_unsupported_modules'
This is a warning, a harmless one and has already been fixed. libkmod does not support SUSE-SLE "unsupported modules" feature. openSUSE has no "unsupported modules" either, this is an SLE feature.
The "/etc/modprobe.d/10-unsupported-modules.conf" dates from Nov 14 2012, and I don't remember what it was for. Is that one causing trouble?
No, it just issues a warning. you can remove that file anyway, it is not the reason why the service ends with failure, just remove cryptoloop and twofish from MODULES_LOADED_ON_BOOT because they are already loaded. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org