PowerManagementConfiguration

Differences between revisions 5 and 7 (spanning 2 versions)
⇤ ← Revision 5 as of 2005-04-25 00:43:55 →
Size: 1037
Editor: intern146
Comment: + mpt
← Revision 7 as of 2005-04-26 01:14:34 → ⇥
Size: 2163
Editor: intern146
Comment: write up initial implementation plan and note packages affected; add rationale
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
  * People: MatthewGarrettLead, OliverGravertSecond[[BR]]   * People: MatthewGarrettLead, OliverGrawertSecond[[BR]]
Line 21: Line 21:
Currently, the user must edit a file in /etc to enable suspend to ram, and to select which services will be restarted. Also, it's currently impossible to configure how the system should behave in various situations, such as on lid close.
All of these points should be configurable via a graphical UI
Line 23: Line 26:
 * Enable suspend to RAM
 * Have system suspend to RAM when lid is closed
 * Select whether screen should be locked when lid is closed
 * Configure advanced/debugging options for ACPI infrastructure(?) (POST_VIDEO, USE_DPMS)		  * Enable suspend to RAM
 * Configure system behaviour when lid closes
 * Configure system behaviour for low and critical battery
Line 30: Line 32:
 * GnomePower(?)  * [http://gnome-power.sf.net GnomePower]
   * Needs to be integrated with current collection of
     acpi-support scripts for functionality.
   * UI needs to be cleaned up for use by basic users and
     only expose the required functionailty
 * Integrate battery applet into HAL/Gnome-Power
 * Extend hwdb to ask about suspend functionality
Line 32: Line 40:
=== Data Preservation and Migration === Use data from hwdb to create a blacklist in breezy+1 of cards/models that don't work properly with vbetool. [[BR]]
Investigate alternative solutions for vbetool in situations where it can't work.[[BR]]
Notify users of proprietary drivers that suspend/hibernate will not work for them.[[BR]]
Line 36: Line 46:
 * gnome-power - NEW
 * acpi-support - scripts move under the aegis of gnome-power , modularised so they work cross platform rather than being x86 specific.
 * pbbuttonsd (should be replaced with pmud for minimal functionality)
 * acpid - all scripts removed, merely echoes out to HAL.
 * pmud - merely echoes out to HAL
 
Line 37: Line 53:
 

Power Management Configuration

Status

Introduction

A user interface is needed for configuring power management preferences.

Rationale

Currently, the user must edit a file in /etc to enable suspend to ram, and to select which services will be restarted. Also, it's currently impossible to configure how the system should behave in various situations, such as on lid close. All of these points should be configurable via a graphical UI

Scope and Use Cases

  • Enable suspend to RAM
  • Configure system behaviour when lid closes
  • Configure system behaviour for low and critical battery

Implementation Plan

  • [http://gnome-power.sf.net GnomePower]

    • Needs to be integrated with current collection of
      • acpi-support scripts for functionality.
    • UI needs to be cleaned up for use by basic users and
      • only expose the required functionailty
  • Integrate battery applet into HAL/Gnome-Power
  • Extend hwdb to ask about suspend functionality

Use data from hwdb to create a blacklist in breezy+1 of cards/models that don't work properly with vbetool. BR Investigate alternative solutions for vbetool in situations where it can't work.BR Notify users of proprietary drivers that suspend/hibernate will not work for them.BR

Packages Affected

  • gnome-power - NEW
  • acpi-support - scripts move under the aegis of gnome-power , modularised so they work cross platform rather than being x86 specific.
  • pbbuttonsd (should be replaced with pmud for minimal functionality)
  • acpid - all scripts removed, merely echoes out to HAL.
  • pmud - merely echoes out to HAL

User Interface Requirements

Outstanding Issues

PowerManagementConfiguration (last edited 2008-08-06 16:31:02 by localhost)