On Wed, 27 Mar 2013 03:33, Carlos E. R.
On Wednesday, 2013-03-27 at 03:25 +0100, Jan Engelhardt wrote:
On Wednesday 2013-03-20 03:29, Cristian Rodríguez wrote:
"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?
Telcontar:~ # modinfo padlock-sha filename: /lib/modules/3.1.10-1.19-desktop/kernel/drivers/crypto/padlock-sha.ko alias: sha256-padlock alias: sha1-padlock alias: sha256-all alias: sha1-all author: Michal Ludvig license: GPL description: VIA PadLock SHA1/SHA256 algorithms support. srcversion: DFE445F053B7F98B381D760 depends: vermagic: 3.1.10-1.19-desktop SMP preempt mod_unload modversions Telcontar:~ # udevadm info --export-db | grep x86cpu Telcontar:~ #
Is that what you expect?
Interesting is, that in the Evergreen 11.2 kernel, the "depends" field is filled: filename: /lib/modules/2.6.31.14-0.8-desktop/kernel/drivers/crypto/padlock-sha.ko .... srcversion: CB8D3DBB1F83B3770836EA3 depends: crypto_algapi vermagic: 2.6.31.14-0.8-desktop SMP preempt mod_unload modversions Can't say when (time/kernel-version) this changed. - Yamaban.