Nepal: Technical Details

This is a meta-page that compiles various technical work going on to support Nepal's OLPC deployments. Expect a certain amount of flux. For the most up-to-date info, check the OLE Nepal blog or e-mail Bryan Berry at bryan at olenepal dot org.

Logistics

Initial Receipt and Inventory

1. At airport, count # of XO's if individually packed
2. Upon arrival at office, recount XO's and note any discrepancies. Beware of transport loss. It happens
3. Inventory the XO's in a spreadsheet. The spreadsheet should record the XO's serial #, whether it shows any physical damage, or won't boot. Here is a inventory template spreadsheet you can use File:XO-Inventory-template.xls
   • If there is physical damage, put a piece of masking tape on the green top lip of the screen and write "physical damage" w/ a red marker.
   • In case of damage or not booting, put in the damaged stack, but make sure to mark it with masking tape and red marker.
4. Attach a label to the XO that has the Inventory Label as the identifier
5. Write the Serial Number on the bottom of the laptop using a black permanent marker
6. Type the Serial Number in the speadsheet next to the Inventory Number
7. Insert USB key, containing runos.zip and actos.zip, see Procedure for Collecting UUID's and Serial Numbers on the Activation_Key page
   • You should see a message like "SHFxxxxxxxx nnnnnnnnnnnnnnn; Laptop data recorded successfully"
   • The XO will then reboot, remove the USB key and turn it on again
8. Send file to OLPC containing the information needed to get developer keys for each XO to help@laptop.org
9. Once you have done this procedure for half of your XO's backup the laptops.dat and inventory spreadsheet (yes, I am paranoid)