From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
{{admon/note|This test will take approx. 15 minutes.}} | {{admon/note|This test will take approx. 15 minutes.}} | ||
{{admon/note|If you do not have laptop or enough time feel free to skip this test. In this case please leave the corresponding column in the results table blank.}} | {{admon/note|If you do not have laptop or enough time feel free to skip this test. In this case please leave the corresponding column in the results table blank.}} | ||
{{admon/note|If you complete this test, please also complete the [[QA: | {{admon/note|If you complete this test, please also complete the [[QA:Testcase_Power_Management_tuned_disabled_idle|Tuned off idle]] test.}} | ||
|setup= | |setup= | ||
# Check that you have ''pm-test-day'' package installed: | # Check that you have ''pm-test-day'' package installed: |
Revision as of 15:00, 27 September 2011
Description
This test case measures energy consumed by you system while in active idle with laptop-battery-powersave profile activated.
Setup
- Check that you have pm-test-day package installed:
$ rpm -q pm-test-day
For better results disable screensaver, screen dimming/turning off, transition to sleep mode and cron service:
- Disable screensaver (if applicable).
- Disable sleep mode, in Gnome 3:
$ gnome-control-center power
- Uncheck "On battery power"
- Disable LCD power savings, in Gnome 3:
$ gnome-control-center screen
- Uncheck "Dim screen to save power".
- Set "Turn off after" to max. value.
- Disable cron:
# systemctl stop crond.service
- Disable user PM via gconf (and save previous settings), it needs to be run under user who is logged into desktop:
$ pmtd-pm-user-settings saveoff
- After the test it is possible to restore the previous settings by using the restore parameter instead of saveoff.
How to test
- Enable tuned laptop-battery-powersave profile by:
# tuned-adm profile laptop-battery-powersave
- Run the following command:
# pmtd-measure-idle
- Do not touch your computer until the test completes (cca. 15 minutes).
- Write the output to the results table.
Expected Results
- Energy consumed during the test is written to the stdout.