I had the same problem with a Core Duo T2500 after upgrading from edgy to feisty. It is caused by a "wrong" default setting in
/etc/powersave/cpufreq
There is a line
CPUFREQD_MODULE="speedstep-centrino"
telling the powersaved to just try to load the speedstep-centrino kernel module which is the wrong one for turion64 or the Core Duo.
If this is set to the empty string "" the config file states that powersaved will probe for the right module then which seems a good default setting for me.
I had the same problem with a Core Duo T2500 after upgrading from edgy to feisty. It is caused by a "wrong" default setting in cpufreq
/etc/powersave/
There is a line MODULE= "speedstep- centrino"
CPUFREQD_
telling the powersaved to just try to load the speedstep-centrino kernel module which is the wrong one for turion64 or the Core Duo.
If this is set to the empty string "" the config file states that powersaved will probe for the right module then which seems a good default setting for me.