<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi,<div><br></div><div>Who decides wich activities are included on the image?</div><div>Can I suggest "I know America"?</div><div><br></div><div><a href="http://activities.sugarlabs.org/en-US/sugar/addon/4464" target="_blank">http://activities.sugarlabs.org/en-US/sugar/addon/4464</a></div><div><br></div><div>The activity has all countries of America (South, Central and North) and Haiti too.</div><div>I attach one capture of the game.</div><div><br></div><div>Regards!</div><div><br></div><div>Alan<br><br><div>> Date: Thu, 19 Dec 2013 12:12:18 +1100<br>> From: quozl@laptop.org<br>> To: georgejhunt@gmail.com<br>> Subject: Re: latest HaitiOS-0.6 very close<br>> CC: holt@unleashkids.org; sora@unleashkids.org; devel@lists.laptop.org; curtathompson@gmail.com; tim@timmoody.com<br>> <br>> Yeah, I can see how you might think the .zip file is the same as the<br>> .rom file, since they have the same version of firmware.<br>> <br>> They are different packaging of the firmware.<br>> <br>> The bootfw.zip contains within it a file data.img which was renamed<br>> from q2f19.rom, and a file data.sig which is the cryptographic<br>> signature for data.img.<br>> <br>> The firmware opens bootfw.zip, reads the file data.sig, checks the<br>> signature, and reads the file data.img, checks the version, and if<br>> newer than current version begins a reflash.<br>> <br>> The signature is critical to the normal firmware upgrade process.<br>> <br>> Illustration:<br>> <br>> $ wget [...]/bootfw.zip [...]/q2f19.rom<br>> $ unzip bootfw.zip<br>> $ md5sum q2f19.rom data.img data.sig<br>> 8ebeb4ada8d59c5031c48b60ecf0899b q2f19.rom<br>> 8ebeb4ada8d59c5031c48b60ecf0899b data.img<br>> eea8805b8d965f4c8f93f8601d23c19c data.sig<br>> $ cmp q2f19.rom data.img && echo same<br>> same<br>> $ <br>> <br>> On Wed, Dec 18, 2013 at 07:39:06PM -0500, George Hunt wrote:<br>> > I was checking the md5sum of bootfw.zip, as James suggested. <br>> > <br>> > I noticed that the q2f19.rom generated a different md5sum than the bootfw.zip.<br>> > And I didn't think the filename was included in the md5sum.<br>> > <br>> > So I copied the contents of the g2f19.4om to a file called bootfw.zip in the /<br>> > boot folder on the USB stick.<br>> > <br>> > The 4button startup no longer stalled. So I suspect that Jerry's hunch was<br>> > correct. To completely test the solution, I should downgrade the firmware, and<br>> > make sure it gets upgraded.<br>> > <br>> > Which I am about to do.<br>> > <br>> > George<br>> > <br>> > <br>> > On Wed, Dec 18, 2013 at 6:36 PM, James Cameron <quozl@laptop.org> wrote:<br>> > <br>> > On Wed, Dec 18, 2013 at 06:20:38PM -0500, George Hunt wrote:<br>> > > I'll test Jerry's hypothesis that the q2119 wasn't signed properly<br>> > > by substituting an official one. I'm out this evening. So whatever<br>> > > happens will need to be in the next 4 hours.<br>> > <br>> > We've never signed anything called q2119.<br>> > <br>> > Perhaps you mean q2f19.<br>> > <br>> > Check your copy is correct.<br>> > <br>> > q2f19's bootfw.zip has md5sum 8585307de5cc8d6867bf58ef56d59f3a<br>> > <br>> > To test that it is signed: downgrade a laptop to q2f18, put the file<br>> > on a USB drive in the boot directory, insert USB drive into laptop,<br>> > hold down the X game key, turn power on. The display should say if<br>> > the signature passed or failed.<br>> > <br>> > The upstream link is<br>> > http://dev.laptop.org/pub/firmware/q2f19/bootfw.zip<br>> > <br>> > --<br>> > James Cameron<br>> > http://quozl.linux.org.au/<br>> > <br>> > <br>> <br>> -- <br>> James Cameron<br>> http://quozl.linux.org.au/<br>> _______________________________________________<br>> Devel mailing list<br>> Devel@lists.laptop.org<br>> http://lists.laptop.org/listinfo/devel<br></div></div> </div></body>
</html>