synaptic just wanted to remove the "broken" linux headers for the 3.3 kernel... so I let it and rebooted. Scaling still not working.
I've booted into another old kernel and for now it seems to be working, (though in this case working means "going at full power and never backing down" which is better for me than trying to run on half my CPU's cores.
(for ref:)
uptime; uname -r; cpufreq-info
11:54:03 up 6 min, 2 users, load average: 5.50, 4.39, 2.10
2.6.31-23-generic
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.20 GHz
available frequency steps: 1.20 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.20 GHz. The governor "performance" may decide which speed to use within this range.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 1.20 GHz:100.00%, 800 MHz:0.00% (1)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.20 GHz
available frequency steps: 1.20 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.20 GHz. The governor "performance" may decide which speed to use within this range.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 1.20 GHz:100.00%, 800 MHz:0.00%
synaptic just wanted to remove the "broken" linux headers for the 3.3 kernel... so I let it and rebooted. Scaling still not working.
I've booted into another old kernel and for now it seems to be working, (though in this case working means "going at full power and never backing down" which is better for me than trying to run on half my CPU's cores.
(for ref:)
uptime; uname -r; cpufreq-info
The governor "performance" may decide which speed to use
within this range.
The governor "performance" may decide which speed to use
within this range.
11:54:03 up 6 min, 2 users, load average: 5.50, 4.39, 2.10
2.6.31-23-generic
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.20 GHz
available frequency steps: 1.20 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.20 GHz.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 1.20 GHz:100.00%, 800 MHz:0.00% (1)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.20 GHz
available frequency steps: 1.20 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.20 GHz.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 1.20 GHz:100.00%, 800 MHz:0.00%