[OLPC-AU] Determining developer lock status

Jerry Vonau jvonau at shaw.ca
Thu Mar 10 03:12:18 EST 2011

On Thu, 2011-03-10 at 15:22 +1100, James Cameron wrote:
> On Thu, Mar 10, 2011 at 03:06:10PM +1100, Sridhar Dhanapalan wrote:
> > We find this to be a bit hit-and-miss - sometimes the prompt shows and
> > sometimes it doesn't. I normally turn on the XO while either holding
> > down the Esc key or tapping it repeatedly. Is there something more
> > reliable? I am trying to get a remote (non-technical) teacher to do
> > this, so it needs to be easy.
> See http://wiki.laptop.org/go/Ok for my standard answer.
> > I forgot to mention another thing - this is for XO-1.1s (XO-1s with an
> > XO-1.5 style trackpad).
> We don't use the term XO-1.1, sorry.  Please don't introduce it.
> The expert method (holding down the escape key while turning on the
> laptop) works fine for me when I test with this type of laptop, on
> Q2E45.  The expert method won't work in some cases though because it
> conflicts with the data stream between the firmware and the keyboard
> during the critical discovery phase.

I like to hold down the check key when booting, then when prompted to
release, hit the escape key. I just do that out of habit now, like to
watch the scrolling text of the boot sequence. 

> With Q2E45, a USB keyboard can also be used to obtain the Ok prompt,
> but it takes an extra moment after the startup sound begins.
> You might also attempt to boot from USB.  If it does not boot an
> unsigned image, then it is probably secure.
> You might also check the manufacturing tags using the Terminal activity,
> but you did ask for simplest, and you didn't say anything initially
> about your hit-and-miss experience.

>From a terminal 'ls /ofw/mfg-data' look for 'ww' for unlocked boxes, if
missing or 'wp' is present, then it's locked.


More information about the Devel mailing list