On Monday 13 February 2006 14:58, Michael Biebl wrote: > Me again, > > is this really a kpowersave problem or is it powersaved sending the > wrong current state of the cpu?
This is a problem with CPUs which not support cpufreq. We read the CPU speed from the sysfs dir for cpufreq, but there is in this case (maybe a Celeron or the CPU only support throttling) nothing. We work for the next release, next week on a better solution. Danny _______________________________________________ powersave-devel mailing list [email protected] http://forge.novell.com/mailman/listinfo/powersave-devel
