Search results

...ost laptops running [[Release notes/8.2.0|release 8.2.0]] received through the [[G1G1 2008|2008 Give One, Get One]] program. ...low are the latest believed to work with release 8.2.0 (or more precisely, the 8.2 build stream).

This page describes the problems with recovering from an extremely discharged battery when using a These problems were first discussed in the March 9-10 XO design review meeting in Cambridge.

This is the candidate firmware for the production build of the B2 boards. It will also work on B1 and ATest boards. # Perform the auto-reinstall procedure at http://wiki.laptop.org/go/Autoreinstallation_im

See [[OLPC_SW-ECO_5]] for a more precise list of the changes, indexed by ticket, that lead from milestone Update.1 (release 8.1. These changes build on the improvements in Update.1 (AKA 8.1.0 AKA Build 703);

=== From the Internet (G1G1 owners, use this) === ''With the [[8.2.0]] release or later pre-release images called [[joyride]]:''

...dded keyjector script for XO-1.5, also tweaked XO-1 keyject.bth to reflect the latest olpc.bth . * OLPC XO-1.5 - trac 10344 - Fixed the kb-suspend command to freeze the screen properly, so it doesn't fade out between keystrokes.

...does not work on Atest because support for Atest has been eliminated from the EC microcode.<br> ====How to get the ok prompt====

...nstall activities and content bundles, and optionally a new OS image, from the USB flash drive onto an XO. ...on top of a signed OLPC build. You may want to include a named [[activity pack]] in your customization stick.

...ng operation and perform other tasks associated with starting and stopping the laptop. ...allowing the XO's main processor to boot from one of the code segments in the SPI Flash.

...uage pack, activities, see also separate customization requirement below). The solution must be faster than imaging via USB sticks for imaging more than 1 Workflow example for the network case above: <br>

*check for any SD card left in the laptop by a prior owner, ...necessary to upgrade the firmware and then charge the battery, rather than the other way around, but you can only do this if you have a spare battery.),

...does not work on Atest because support for Atest has been eliminated from the EC microcode.<br> ...S2 driver problem that caused files to disappear from the point of view of the firmware under certain obscure situations.

...r systems. Do not use it on pre-B1 boards - it will brick them because of the EC microcode.<br> ...After that has happened you must not install anything from the B series of the firmware. If you do then <u>you will erase</u> your manufacturing data.'''

...pt pre-B1. Do not use it on pre-B1 boards - it will brick them because of the EC microcode. ...After that has happened you must not install anything from the B series of the firmware. If you do then <u>you will erase</u> your manufacturing data.'''

.../ticket/6532 may be corrupted] by builds 703-709. Do not use SD cards with the XO with builds in this range.</span> == What's new in the official-703 (8.1.0) release? ==

...r systems. Do not use it on pre-B1 boards - it will brick them because of the EC microcode.<br> ...After that has happened you must not install anything from the B series of the firmware. If you do then <u>you will erase</u> your manufacturing data.'''

...to develop a Puppy Linux Educational derivative, specially built to run in the XO hardware. * Create a Puppy Linux distribution with a good pack of educative applications.

...r systems. Do not use it on pre-B1 boards - it will brick them because of the EC microcode.<br> ...2-bits". To the best of my knowledge that problem is innocuous apart from the spurious message.

...or later. Do not use it on pre-B1 boards - it will brick them because of the EC microcode.<br> ...After that has happened you must not install anything from the B series of the firmware. If you do then <u>you will erase</u> your manufacturing data.'''

...does not work on Atest because support for Atest has been eliminated from the EC microcode.<br> ...ashing the SPI FLASH, giving the EC time to detect the battery. Otherwise the check for battery presence fails.