Stefan Seyfried wrote:
Thomas Renninger wrote:
Hi,
I like to integrate a post-install script that modifies/adopts configuration
variables according to:
1) powersave version (for updates)
2) kernel version
3) machine specific configurations
after installation.
*1) Powersave Version*
This is mainly the stuff already located in the rpm post-install section.
Maybe we can throw out the 0.7->0.8 version update stuff.
I don't think so.
OK, I will clean it a bit up and still integrate it.
*3) Machine Specific Configurations*
- Possibly add suspend to ram hooks for specific kernels/graphics cards,
Seife?
if we knew what to do on each machine, this would be easy. We don't.
We know some hooks for some drivers/cards. But if you say it's not worth it...,
you are the suspend guy ...
- Add thermal trip point default values exported from BIOS to config files
but please leave thermal management disabled per default - it does not
do much good yet :-)
I'd like to enable it. It already was enabled for a long time and only did break
one machine.
The failure on this machine was that echoing the critical trip point to
/proc/acpi/thermal_zone/*/trip_points did cause a thermal shutdown because of
rounding errors (kernel does not take decimal placed values (Nachkommastellen?)).
However my new approach does only set trip points for thermal_zones that define
a passive trip point. The main feature is to not allow the CPU to exceed a
certain temperature and like that also control fan activity passively.
I would also like to set the passive trip point in the accoustic scheme at a
specific level say 47 degree Celsius statically, that should shut up most fans.
Now, this is the time to play with it, we can still disable it in short term
before the next bigger release.
- Check for appropriate CPU freq module and add it to CPUFREQD_MODULE=""
- Check for all ACPI modules that need to be loaded on that machine and add
them to ACPI_MODULES="" (This also includes the laptop specific ones).
I'd like to have the loading of ACPI modules at one central place. Were
there any reasons not to do so? Whatabout hal, it is started after the
powersaved daemon, but seems to be able to handle the late loading of the
ACPI modules?
acpid is loading the module and caching the list of loaded modules (on
SUSE 10.0, other distributions might also want to solve this with acpid
since it is needed for HAL and ial anyway)
I see. I'd like to avoid probing/loading all ACPI and CPUfreq modules after
each boot up. So then we also need a post-install script for the ACPI daemon to
evaluate which ACPI modules to load. The CPU freq modules will be tested in the
post install script of the powersave daemon, then.
- Disable throttling for all SMP machines and machines that support C2 and
higher states (According to Intel throttling consumes more power than
doing
the tasks quickly and then go to C-states in idle).
- Add a switch_vt hook for ppc on suspend to disk (not sure whether this is
still necessary for their graphics card drivers).
we don't need a hook, just set the apropriate variable to "yes" :-)
This is what the hook is intended to do :)
Any more concerns?
Thomas
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
