<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 3/10/2013 3:39 PM, Nancie Severs wrote:<br>
<blockquote
cite="mid:1362944357.1238.YahooMailNeo@web121901.mail.ne1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:verdana, helvetica, sans-serif;font-size:12pt">Going
to 12 and 13, I am still getting a % of XOs that get stuck at
the grey dots when booting after the reflash is complete.
Richard Smith figured out that this is a Pretty Boot issue. He
had a workaround that worked on an XO 1.5, but I have not been
successful had getting that to work on an XO 1.0.<br>
</div>
</blockquote>
<br>
I've the same issue with an XO-1 running Release 11.3.1 -- it was
previously running March 6th's 13.1.0<br>
<br>
Now it freezes at the end of prettyboot (once all grey dots have
formed a circle). Sugar's interface never fully boots. 2
workarounds (partially) force Sugar to boot:<br>
<br>
1) Hold down the "check" game key
(<a class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Cheat_codes">http://wiki.laptop.org/go/Cheat_codes</a>) on boot, or<br>
2) Hit the Esc key on boot. Then type "boot" at the
<a class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Ok">http://wiki.laptop.org/go/Ok</a> prompt<br>
<br>
As Nancie asks, how to force this every time on an XO-1? Or perhaps
this is not possible, according to "<span class="mw-headline">Enabling
Verbose Boot from OFW<a href="http://wiki.laptop.org/go/OFW"
title="OFW" class="mw-redirect"></a>" at the bottom of:</span>
<a class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Startup_diagnosis">http://wiki.laptop.org/go/Startup_diagnosis</a><br>
Hauntingly even if such a workaround exists, as the XO's main Power
button does not respond as it should once Sugar has booted (short
taps of the Power button are completely ignored when using the above
workarounds).<br>
<br>
Reflashing to 11.3.1 does not help, very surprisingly.<br>
I even tried reverting firmware from 13.1.0's q2f13 to 11.3.1's
q2f11 at the ok prompt (this is an unsecured XO-1), and subsequent
reflash to 11.3.1. But no dice.<br>
<br>
Nancie's getting something like 10-25% of her newly reflashed XO-1s
ending up in this borked state recently, suggesting a deeper
syndrome?<br>
Is there a pattern that many of these machines are unsecured? That
part's unclear. FYI, I only wrote this up in case it hpoefully
helps others, or someone has the antidote =)<br>
<br>
<br>
Interestingly: the 9-month-old 11.3.1 appears substantially faster
than 13.1.0 on XO-1 in almost all regards. Sad!<br>
Due to Fedora 14 to 18 innards? And/or Sugar's evolution from 0.94
to 0.98? O well. Yioryos Asprobounitis has some time trial numbers
here if anyone needs them.<br>
<pre class="moz-signature" cols="72">--
Help kids everywhere map their world, at <a class="moz-txt-link-freetext" href="http://olpcMAP.net">http://olpcMAP.net</a> !</pre>
</body>
</html>