I was checking the md5sum of bootfw.zip, as James suggested. I noticed that the q2f19.rom generated a different md5sum than the bootfw.zip. And I didn't think the filename was included in the md5sum.
So I copied the contents of the g2f19.4om to a file called bootfw.zip in the /boot folder on the USB stick. The 4button startup no longer stalled. So I suspect that Jerry's hunch was correct. To completely test the solution, I should downgrade the firmware, and make sure it gets upgraded. Which I am about to do. George On Wed, Dec 18, 2013 at 6:36 PM, James Cameron <qu...@laptop.org> wrote: > On Wed, Dec 18, 2013 at 06:20:38PM -0500, George Hunt wrote: > > I'll test Jerry's hypothesis that the q2119 wasn't signed properly > > by substituting an official one. I'm out this evening. So whatever > > happens will need to be in the next 4 hours. > > We've never signed anything called q2119. > > Perhaps you mean q2f19. > > Check your copy is correct. > > q2f19's bootfw.zip has md5sum 8585307de5cc8d6867bf58ef56d59f3a > > To test that it is signed: downgrade a laptop to q2f18, put the file > on a USB drive in the boot directory, insert USB drive into laptop, > hold down the X game key, turn power on. The display should say if > the signature passed or failed. > > The upstream link is > http://dev.laptop.org/pub/firmware/q2f19/bootfw.zip > > -- > James Cameron > http://quozl.linux.org.au/ >
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel