Hi James, <br><br>Ok. I MIGHT have found the culprit to my "XO 1.5 firmware not updating" issue. I noticed my laptop that's plugged in to a surge protector (the same surge protector that I used when I updated the 1.5) , momentarily dimmed when I moved the surge protector with my foot. I just noticed that today. So I plugged in my XO 1.0 to a wall socket instead to update and both the Sugar and Firmware updated to the latest release build. Will investigate further with XO 1.5 when I'm ready. <br>
<br>However, updating my XO 1.0 to the latest release is not very peachy. I will post it in a separate e-mail as it is a continuing saga of instability. <br><br>Best,<br>Cherry <br>P.S. Thanks for the advice on the Nandblaster!<br>
<br><div class="gmail_quote">On Thu, Sep 2, 2010 at 9:20 PM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thu, Sep 02, 2010 at 05:06:30PM -0700, Cherry Withers wrote:<br>
> To clarify...yes, I used olpc-update not fs-update. I'd like to chase<br>
</div>> the root of this idiosyncrasy [...]<br>
<br>
I've just tested that olpc-update does cause a firmware update ...<br>
installed Q3A45, then installed build os303, on reboot firmware was<br>
updated to Q3A46, then ran olpc-update to os852, on reboot firmware was<br>
updated to Q3A48.<br>
<br>
So whatever the problem is, it doesn't appear to be common to other<br>
laptops. Let me know when you are available to continue investigating.<br></blockquote></div><br>