Re: [OLPC-AU] Determining developer lock status
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. Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] Determining developer lock status
I'm still awaiting feedback from the school (getting information out of remote schools is often hard). I'm trying to ascertain whether their CL1As are developer locked. According to the production info on your SKU (SKU 67) all your CL1As where shipped unlocked. -- Richard A. Smith One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] Determining developer lock status
On Thu, Mar 10, 2011 at 06:13:04PM +1100, Sridhar Dhanapalan wrote: I was out there a year ago to assist in the initial deployment, but at the time I was quite green and so didn't know what to look for. I do remember that we used NANDblaster clone an installation from one of our own CL1 XO-1s to the school's CL1As (turning each on while holding the four game keys). Would that be an indication that they are not locked? Yes. The only NANDblaster function that will work to a secure laptop is nb-secure [1]. nb-clone (which is what you did) requires an non-secure target laptop set. Otherwise the security system would be bypassed. On using the four game keys ... quote This works for both secure and non-secure systems. If the system is secure, the sender must be sending a signed image; otherwise the receiver will stop before writing to it NAND, saying Placement spec bad signature!./quote [2] 1. http://wiki.laptop.org/go/Nandblaster_for_XO-1#NANDblasting_a_Signed_NAND_Image_File 2. http://wiki.laptop.org/go/Nandblaster_for_XO-1#..._with_Game_Buttons -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] Determining developer lock status
On 11 March 2011 06:02, Richard Smith rich...@laptop.org wrote: I'm still awaiting feedback from the school (getting information out of remote schools is often hard). I'm trying to ascertain whether their CL1As are developer locked. According to the production info on your SKU (SKU 67) all your CL1As where shipped unlocked. Thanks everyone. I've just confirmed with the school that they have SKU 67, and that they are not developer locked. *sigh of relief* Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] Determining developer lock status
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. 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. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] Determining developer lock status
On 10 March 2011 15:22, James Cameron qu...@laptop.org wrote: On Thu, Mar 10, 2011 at 03:06:10PM +1100, Sridhar Dhanapalan wrote: 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. Noted. I'm still awaiting feedback from the school (getting information out of remote schools is often hard). I'm trying to ascertain whether their CL1As are developer locked. We want to install our own build, along with deployment keys and firmware, via USB through an olpc.fth script. I was out there a year ago to assist in the initial deployment, but at the time I was quite green and so didn't know what to look for. I do remember that we used NANDblaster clone an installation from one of our own CL1 XO-1s to the school's CL1As (turning each on while holding the four game keys). Would that be an indication that they are not locked? Thanks, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
