On Wednesday 2013-03-20 03:29, Cristian Rodríguez wrote:
In about 3 machines I have the following annoying log message:
modprobe[1062]: FATAL: Error inserting padlock_sha (/lib/modules/3.9.0-rc3-1-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device
I have been seeing that message for years in my machines (or very similar). However, the message went to /var/log/boot.msg, where it did not bother me. Now it goes to messages.log - that's your fault for implementing systemd! :-P
Heh, no . do not shoot the messenger :)
"something" is doing probes the wrong way from the wrong reason. that's all.
Let's see.. $ modinfo padlock-sha filename: /lib/modules/3.7.10-jng11-desktop/kernel/drivers/crypto/padlock-sha.ko [...] alias: x86cpu:vendor:*:family:*:model:*:feature:*00AA* And now check with udevadm info --export-db | grep x86cpu: Got 00AA in it? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org