Autoreinstallation image: Difference between revisions
(Updated to reflect new updater) |
(Fixed update procedure) |
||
Line 3: | Line 3: | ||
=Automatic Reinstallation Image= |
=Automatic Reinstallation Image= |
||
<b>Under construction: do not yet use</b> |
|||
We've worked very hard to make it as easy as possible to update a machine in the field. Until network boot and update is available, this is as easy as it can get. |
We've worked very hard to make it as easy as possible to update a machine in the field. Until network boot and update is available, this is as easy as it can get. |
||
If you have a new B1 system, it is very important to use this procedure first; do not try to use the new "netnandwrite" tool first. The reason is that this procedure automatically fixes a manufacturing error in the identification data that was stored in the system firmware FLASH, and updates the firmware, neither of which is done by the network-based tool. |
|||
<b>NOTE: this procedure creates a USB flash key or disk that when booted on an OLPC laptop, updates its BIOS and installs (OVERWRITES) an operating system image onto NAND flash. NEVER boot this USB flash key or disk unless you intend to update your system, which will entirely erase anything you had on the flash memory of the system.</b> |
<b>NOTE: this procedure creates a USB flash key or disk that when booted on an OLPC laptop, updates its BIOS and installs (OVERWRITES) an operating system image onto NAND flash. NEVER boot this USB flash key or disk unless you intend to update your system, which will entirely erase anything you had on the flash memory of the system.</b> |
||
This procedure works for all types of OLPC hardware, from A-test through B1 systems. It works with both Open Firmware and Linux-as-BIOS installations - but does not work with Insyde BIOS. If you are still running Insyde BIOS, you will first have to upgrade the firmware using procedures described elsewhere. |
|||
<b>This image will only work on a "B-Test" laptop, and not on older "A-Test" motherboards. An update image for "A-Test" boards will come later.</b> |
|||
==System Update Procedure== |
==System Update Procedure== |
||
<b>Before you start: plug in your machine and ensure the battery is charged. It is very important that the update process not be interrupted.</b> |
<b>Before you start: plug in your machine and ensure the battery is charged. It is very important that the update process not be interrupted.</b> |
||
# '''Download''' the file http://dev.laptop.org/~wmb/olpc193_A54.zip. |
# '''Download''' the file http://dev.laptop.org/~wmb/olpc193_A54.zip. |
||
# Get a USB flash key or disk with at least 200 MiB of free space in the primary partition (it doesn't have to be partitioned at all). |
# Get a USB flash key or disk with at least 200 MiB of free space in the primary partition (it doesn't have to be partitioned at all). If your system current has Open Firmware, the filesystem can be either FAT (like a factory-formatted device) or ext2. But it will not work if it partitioned such that the partition type code says "82" (Linux ext) but the actual filesystem inside the partition is FAT. If your system has Linux-as-BIOS, the USB device must have an ext2 filesystem. |
||
# '''Unzip''' the files at the root of the USB flash key or disk drive, thus creating a directory called "boot". (If you drag and drop the files from the zip archive, you'll have to create the "boot" directory manually on the flash or disk drive.) Three files must be in the directory named "boot", for the automatic update to occur: '''q2a54.rom'''; '''nand193.img'''; and '''olpcboot.fth'''. Do not use a flash key or disk for which there have been any errors reported during unzipping: the files may (probably are) damaged. As a further safeguard, the OLPC OFW BIOS checks the integrity of any BIOS flash image before reflashing the BIOS. |
# '''Unzip''' the files at the root of the USB flash key or disk drive, thus creating a directory called "boot". (If you drag and drop the files from the zip archive, you'll have to create the "boot" directory manually on the flash or disk drive.) Three files must be in the directory named "boot", for the automatic update to occur: '''q2a54.rom'''; '''nand193.img'''; and '''olpcboot.fth'''. Do not use a flash key or disk for which there have been any errors reported during unzipping: the files may (probably are) damaged. As a further safeguard, the OLPC OFW BIOS checks the integrity of any BIOS flash image before reflashing the BIOS. |
||
# '''Insert''' the USB flash key into the machine turn on the power. |
# '''Insert''' the USB flash key into the machine. If you have Open Firmware, just turn on the power. If you have Linux-as-BIOS, hit ESC when you see the boot progress bar, then choose the USB key icon and hit Enter. |
||
You will see messages like those in the following section as the system is updated. NAND flash always has some bad blocks: the "Skipping bad block" messages during writing NAND flash are therefore normal, informing you of the bad blocks that will never be used by Linux. |
You will see messages like those in the following section as the system is updated. NAND flash always has some bad blocks: the "Skipping bad block" messages during writing NAND flash are therefore normal, informing you of the bad blocks that will never be used by Linux. |
Revision as of 09:30, 9 December 2006
Automatic Reinstallation Image
We've worked very hard to make it as easy as possible to update a machine in the field. Until network boot and update is available, this is as easy as it can get.
If you have a new B1 system, it is very important to use this procedure first; do not try to use the new "netnandwrite" tool first. The reason is that this procedure automatically fixes a manufacturing error in the identification data that was stored in the system firmware FLASH, and updates the firmware, neither of which is done by the network-based tool.
NOTE: this procedure creates a USB flash key or disk that when booted on an OLPC laptop, updates its BIOS and installs (OVERWRITES) an operating system image onto NAND flash. NEVER boot this USB flash key or disk unless you intend to update your system, which will entirely erase anything you had on the flash memory of the system.
This procedure works for all types of OLPC hardware, from A-test through B1 systems. It works with both Open Firmware and Linux-as-BIOS installations - but does not work with Insyde BIOS. If you are still running Insyde BIOS, you will first have to upgrade the firmware using procedures described elsewhere.
System Update Procedure
Before you start: plug in your machine and ensure the battery is charged. It is very important that the update process not be interrupted.
- Download the file http://dev.laptop.org/~wmb/olpc193_A54.zip.
- Get a USB flash key or disk with at least 200 MiB of free space in the primary partition (it doesn't have to be partitioned at all). If your system current has Open Firmware, the filesystem can be either FAT (like a factory-formatted device) or ext2. But it will not work if it partitioned such that the partition type code says "82" (Linux ext) but the actual filesystem inside the partition is FAT. If your system has Linux-as-BIOS, the USB device must have an ext2 filesystem.
- Unzip the files at the root of the USB flash key or disk drive, thus creating a directory called "boot". (If you drag and drop the files from the zip archive, you'll have to create the "boot" directory manually on the flash or disk drive.) Three files must be in the directory named "boot", for the automatic update to occur: q2a54.rom; nand193.img; and olpcboot.fth. Do not use a flash key or disk for which there have been any errors reported during unzipping: the files may (probably are) damaged. As a further safeguard, the OLPC OFW BIOS checks the integrity of any BIOS flash image before reflashing the BIOS.
- Insert the USB flash key into the machine. If you have Open Firmware, just turn on the power. If you have Linux-as-BIOS, hit ESC when you see the boot progress bar, then choose the USB key icon and hit Enter.
You will see messages like those in the following section as the system is updated. NAND flash always has some bad blocks: the "Skipping bad block" messages during writing NAND flash are therefore normal, informing you of the bad blocks that will never be used by Linux.
The system will automatically poweroff.
If anything goes wrong DO NOT TURN OFF THE MACHINE but please get help from OLPC, preferably immediately on IRC or by email.
Congratulations: you are finished! You can power the machine back on and start use.
Transcript of System Update
Type any key to interrrupt startup Erasing 0 Writing f000 Updating firmware Reading disk:\boot\q2a52.rom Got firmware version: CL1 Q2A5a Q2A Checking integrity ... SPI FLASH is type 13 - Spansion, Winbond, or ST Merging existing manufacturing data Erasing 0 Writing ff000 ... Done Checking existing OS image on NAND FLASH Updating OS image on NAND FLASH Erasing 1d00 Skipping bad block at 0xea000 = page 0x1d40 = eblock 0x75 4ec0 Skipping bad block at 0x2780000 = page 0x4f00 = eblock 0x13c 3ff40 Writing 57a Done Automatic power off in 5 seconds. Please remove the USB disk.