On 12/23/2014 07:40 PM, gregor herrmann wrote: > # ls -la /sys/devices/system/cpu/cpu*/cpufreq > /sys/devices/system/cpu/cpu0/cpufreq: > total 0 > drwxr-xr-x 2 root root 0 Dec 21 14:39 . > drwxr-xr-x 9 root root 0 Dec 21 14:56 .. > -r--r--r-- 1 root root 4096 Dec 21 14:39 affected_cpus > -r--r--r-- 1 root root 4096 Dec 19 00:05 cpuinfo_cur_freq > -r--r--r-- 1 root root 4096 Dec 21 14:39 cpuinfo_max_freq > -r--r--r-- 1 root root 4096 Dec 21 14:39 cpuinfo_min_freq > -r--r--r-- 1 root root 4096 Dec 21 14:39 cpuinfo_transition_latency > -r--r--r-- 1 root root 4096 Dec 21 14:39 related_cpus > -r--r--r-- 1 root root 4096 Dec 21 14:39 scaling_available_governors > -r--r--r-- 1 root root 4096 Dec 21 14:39 scaling_cur_freq > -r--r--r-- 1 root root 4096 Dec 21 14:39 scaling_driver > -rw-r--r-- 1 root root 4096 Dec 21 14:39 scaling_governor > -rw-r--r-- 1 root root 4096 Dec 21 14:39 scaling_max_freq > -rw-r--r-- 1 root root 4096 Dec 21 14:39 scaling_min_freq > -rw-r--r-- 1 root root 4096 Dec 21 14:39 scaling_setspeed
I noticed some additional files in my cpufreq/ directories: -r--r--r-- 1 root root 4096 Dec 23 20:12 bios_limit -rw-r--r-- 1 root root 4096 Dec 23 20:12 cpb -r--r--r-- 1 root root 4096 Dec 23 20:12 freqdomain_cpus -r--r--r-- 1 root root 4096 Dec 23 20:12 scaling_available_frequencies drwxr-xr-x 2 root root 0 Dec 23 20:12 stats I'm curious what your scaling_driver is, when you are not using acpi_cpufreq. And what happens when your current cpufreq driver is unloaded, and instead acpi_cpufreq is loaded (which seems to be more generic and support AMD and Intel CPUs).
signature.asc
Description: OpenPGP digital signature
