new F11-for-XO1 images available for testing

[Paul Fox]

yioryos wrote:
 > 
 > -- On Tue, 7/28/09, James Cameron <quozl at laptop.org> wrote:
 > 
 > > > > You could try reproducing it with a network
 > > connection
 > > > > carrying kernel
 > > > > messages, in case you can catch some evidence
 > > leading to
 > > > > the event.
 > > > 
 > > > The howto of this totally elutes me...

while james' method will work, i think that in this case
it would be easier to simply make the logs persistent, so that
they're available at the next startup.

    1) create the directory /home/olpc/log
    2) save a backup copy of /etc/rsyslog.conf
    3) edit /etc/rsyslog.conf, and change 
	"/var/log/messages" to "/home/olpc/log/messages".
	you can change other occurrences of "/var/log"
	as well, but the messages file is most likely to
	be interesting.
    4) to make the changes take effect, simply reboot, or,
	perhaps safer:  "kill -HUP $(pidof rsyslogd)".  after
	doing this, verify that you're now getting log data in the
	new location.

NOTE!  eventually your logfile(s) _will_ grow too big.  after
debugging this you'll want to either a) switch back to the
original rsyslog.conf, or move the /home/olpc/log/messages file
out of the way and repeat step 4, above.

when you say "The computer will shutdown suddenly (and fast)", do
you mean that the normal splash screen(s) don't appear?  if so,
which?

i'm actually not clear on which images you're testing:  are these
sebastian's SoaS-on-XO, or is this something based on daniel drake's
tree?  if the former, and if the shutdown, or crash, is
reproducible, please disable powerd:
    sudo initctl stop powerd
    sudo mv /etc/event.d/power /home/olpc/powerd.save
and retry.

paul

 > > 
 > > Sorry.
 > > 
 > > 1.  change the root password to something you know,
 > > (by starting
 > > Terminal, then become root, then type "passwd" and follow
 > > the prompts),
 > > 
 > > 2.  determine the IP address, (by ensuring it is
 > > associated with an
 > > access point and then use "ifconfig -a" to see the IP
 > > address),
 > > 
 > > 3.  from another system, "ssh root@${IP} tail -f
 > > /var/log/messages"
 > > where ${IP} is the IP address from step 2,
 > > 
 > > 4.  answer the password prompt, watch the display on
 > > the other system,
 > > and try to reproduce the problem.
 > > 
 > > I'm trying this now.  It hasn't worked, in that it
 > > hasn't suddenly
 > > powered down while I do this tail.  I wonder if it is
 > > causing whatever
 > > is going wrong to not go wrong.
 > 
 > Thanks I'll try it.
 > 
 > > 
 > > > > Also, try seeing if it happens at about the time
 > > that the
 > > > > battery would
 > > > > reach full charge.? I think that's when mine did
 > > it.
 > > > > 
 > > > 
 > > > I _think_ that in all cases was fully charged and
 > > short after I
 > > > unplugged it from the charger.
 > > 
 > > Thanks, no pattern then.
 > > 
 > 
 > Is not a common event. In the 4 days that I'm using os2 happened only 3 times. 
 > The only common thing is that happens shortly after you reboot and get a 
 > (usable) home screen (within the first ~1 min). 
 > Like something is still running in the background and you get some conflict.
 > 
 > 
 > 
 >       
 > 
 > _______________________________________________
 > Fedora-olpc-list mailing list
 > Fedora-olpc-list at redhat.com
 > https://www.redhat.com/mailman/listinfo/fedora-olpc-list

=---------------------
 paul fox, pgf at laptop.org