<div dir="ltr">FYI:<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Richard A. Smith</b> <span dir="ltr"><<a href="mailto:richard@laptop.org">richard@laptop.org</a>></span><br>
Date: Wed, Oct 15, 2008 at 3:56 AM<br>Subject: [support-gang] The great battery experiment<br>To: OLPC Developer's List <<a href="mailto:devel@laptop.org">devel@laptop.org</a>>, sugar <<a href="mailto:sugar@laptop.org">sugar@laptop.org</a>>, Support Gangsters <<a href="mailto:support-gang@laptop.org">support-gang@laptop.org</a>>, OLPC Community Support <<a href="mailto:community-support@lists.laptop.org">community-support@lists.laptop.org</a>><br>
<br><br>As I reported in my report that went to community news I'm looking for<br>
power use and battery life information.<br>
<br>
Here's a modified version of what I sent in for community news:<br>
<br>
========<br>
Richard would like to call for help from the G1G1, developer, and<br>
testing community. Gathering large amount of data to establish a good<br>
power baseline is a very time consuming task. Repeated power runs tests<br>
take around 6 hours to run. Richard would like to request that all the<br>
developers, G1G1 users, and testers that are active do a power testing<br>
run and send the resulting log file to Richard.<br>
<br>
If a large amount of people run 1 or 2 logs then Richard will have a<br>
wealth of data to process.<br>
<br>
The steps: (Please follow these steps as close as possible so the data<br>
is apples to apples)<br>
<br>
1) Download the latest olpc-pwr-log:<br>
<br>
wget <a href="http://dev.laptop.org/%7Ersmith/olpc-pwr-log" target="_blank">http://dev.laptop.org/~rsmith/olpc-pwr-log</a><br>
<br>
2) Copy this into your XO where you can run it from a VT.<br>
<br>
VT in this case means Virtual Terminal. A VT is the text console that<br>
you get to by pressing the Ctrl-Alt-F1 key. F1 in the XO case is the<br>
mesh key which is to the right of the magnifying glass. For more<br>
information on the VT:<br>
<br>
<a href="http://wiki.laptop.org/go/Virtual_terminal" target="_blank">http://wiki.laptop.org/go/Virtual_terminal</a><br>
<br>
3) Fully charge the battery of your XO and leave the external power<br>
plugged in.<br>
<br>
3a) Please remove _all_ external devices connected to the XO. This<br>
includes SD cards, USB keyboards, USB disks, etc. External devices will<br>
skew the power readings and create situations where the CPU will not<br>
go idle.<br>
I'm not really concerned with what your network is doing. Thats one of<br>
the things I want to see is how much variability there is in the<br>
readings. So association to an access point or running mesh is fine.<br>
However, please don't disable the WLAN with the extreme power magement<br>
seting.<br>
<br>
If you wish to record a brief note on what you had the network doing you<br>
can do so by adding a message after './olpc-pwr-log' It will be copied<br>
into the log file as a note. See 5)<br>
<br>
4) Switch to a VT and cd to where the olpc-pwr-log script is. Running<br>
from a VT is very important. The output on the VT console will prevent<br>
the system from going into idle-suspend if you have that enabled.<br>
<br>
5) ./olpc-pwr-log [message]<br>
<br>
[message] is any descriptive text you want to provide about this log.<br>
Useful info would be if you were connected to an AP or in the mesh. Its<br>
not required though.<br>
<br>
6) The moment you see the first line of log output (ie right after it<br>
says it found a battery and a series of numbers displays) pull the<br>
external power. The status should go from 'Full' to 'Discharging' on<br>
the next print which should be in about 15 seconds.<br>
<br>
7) Let the system run untouched until it dies. Do not switch back into<br>
sugar. If you go back into sugar the DPMS power saving will kick in in<br>
20 minutes and turn off the dcon.<br>
<br>
After a while of inactivity the console screen blanker will kick in and<br>
the text on the screen will go a bit screwy. Don't worry its a known<br>
bug. Just ignore it. If however your screen goes dark and gray (No<br>
backlight and looks just like the powered is off) then DPMS screen saver<br>
has kicked in and turned off your DCON. Please review the earlier steps<br>
and try to figure out why DPMS activated. If you have to you can<br>
disable DPMS with by using xset:<br>
<br>
"xset -dpms"<br>
<br>
8) Mail the logs or any questions you have to <a href="mailto:richard@laptop.org">richard@laptop.org</a> or find<br>
me on IRC in the devel room.<br>
<font color="#888888"><br>
--<br>
Richard Smith <<a href="mailto:richard@laptop.org">richard@laptop.org</a>><br>
One Laptop Per Child<br>
_______________________________________________<br>
support-gang mailing list<br>
<a href="mailto:support-gang@lists.laptop.org">support-gang@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/support-gang" target="_blank">http://lists.laptop.org/listinfo/support-gang</a><br>
</font></div><br><br clear="all"><br>-- <br>The best material model of a cat is another, or preferably the same, cat. <br>--Norbert Wiener, Philosophy of Science, 1945<br>
</div>