Stable Upgrade

From OLPC
Revision as of 17:36, 3 December 2007 by AlexL (talk | contribs)
Jump to navigation Jump to search

Network upgrade (only works well from 643 or later)

  1. Go into the virtual terminal: Hold down Alt, Ctrl, and Mesh key f1 small.png (the 'Mesh' key - third key from the left along the top row).
  2. Login in as 'root'
  3. Type: olpc-update <version>
    • The stable version released on December 1 is 'ship.2-649'.
  4. When the download and upgrade are complete and verified; type 'reboot' to start the laptop up in the new version.
  5. After booting into sugar, check the code version as described below.


To Upgrade from a USB stick (will overwrite all saved data)

First you need to create a USB stick with the latest stable build:

  1. Make sure that your USB stick is FAT formatted, not FAT 32, and only contains 1 partition.
  2. Go to the jffs2 download page for stable build, http://download.laptop.org/xo-1/os/official/
  3. Download two files to your local computer: fs.zip (about 200k), and osXXX.img (about 300M); where XXX is the build number.
    • These files will be found in /build_number/jffs2
  4. Put these two files on the USB stick at the root directory. Remove any other files on the USB stick.
  • Copy any files you would like to keep onto another data storage device (usb key, another laptop, etc...)

Next, upgrade your laptop:

  1. Ensure you have both a power adapter and a battery plugged into the laptop.
  2. Insert the USB stick into the laptop while it is powered off.
  3. Hold down all four gamekeys right after pushing the power button.


Check the version of code your laptop is running:

  1. Boot the laptop; and wait until you get the sugar home screen.
  2. Hold down Alt, Ctrl, and 'mesh' (the third key from the left along the top row).
  3. Check the version by reading the label just above the login: OLPC Build 649 (match that against expected build number).
  4. Hold down Alt, Ctrl, and 'home' (the 5th key from the left on the top row) to get back to Sugar UI.


Advanced Upgrades

To upgrade to a non-stable release, you must have a developer's key. Also, consult the Autoreinstallation pages for more details.