Installation progress will be displayed. Green colour will fill
grey
blocks. It will take about
five
minutes. Once finished,
the laptop will reboot automatically. You may remove the USB or SD drive during or after the reboot.

The USB or SD drive can be used on other laptops.
If installation progress is not displayed, you may be running an old firmware version which does not recognise the fs4.zip file. Rename fs4.zip to fs.zip and trying again.
If you see a message Boot failed then either:

Installation progress will be displayed. Green colour will fill
grey
blocks. It will take about
five
minutes. Once finished,
the laptop will reboot automatically. You may remove the USB or SD drive during or after the reboot.

The USB or SD drive can be used on other laptops.
If installation progress is not displayed, you may be running an old firmware version which does not recognise the fs2.zip file. Rename fs2.zip to fs.zip and trying again.
If you see a message Boot failed then either:

Installation progress will be displayed. Green colour will fill
grey
blocks. It will take about
ten
minutes. Once finished,
the laptop will reboot automatically. You may remove the USB or SD drive during or after the reboot.

The USB or SD drive can be used on other laptops.
If installation progress is not displayed, you may be running an old firmware version which does not recognise the fs1.zip file. Rename fs1.zip to fs.zip and trying again.
If you see a message Boot failed then either:

Installation progress will be displayed. Green colour will fill
yellow
blocks. It will take about
five
minutes. Once finished,
the laptop will reboot automatically. You may remove the USB or SD drive during or after the reboot.

The USB or SD drive can be used on other laptops.
If installation progress is not displayed, you may be running an old firmware version which does not recognise the fs0.zip file. Rename fs0.zip to fs.zip and trying again.
If you see a message Boot failed then either:

Update

You may wish to update from a previous version of the operating system. This method preserves most user data, the Sugar Journal and installed Sugar Activities, but does not preserve certain operating system customizations such as additional packages.

(Update is distinct from install. If you have followed the install procedures above, then you need not follow this section.)

Preparation

To prepare for an operating system update:

remove as much saved content as you no longer need,

remove any large activities you no longer need (in the Home view, erase them),

After the Update

Sugar will attempt to update its Activities -- you should be online for the Activity Updater to complete.

Known problems

This section lists significant known issues that we hope to solve in future releases.

If deployments have solid plans and schedules to deploy this release but feel blocked by some of these issues in particular, they are encouraged to get in contact with OLPC far in advance of the installation date. OLPC may be able to produce a limited scope point-release fixing highlighted issues.

XO-4 may hang before suspend in an ad-hoc network, workaround is to deploy the previous version of the 8787 firmware, see ticket #12767,

XO-4 may lose wireless network if associated with a WPA2 access point while automatically sleeping and waking, problem can be reduced by decreasing the enthusiasm of the power management system, workaround is to reboot, ticket #12779,