Autoreinstallation image/lang-es: Difference between revisions
(sync'ed version = 42931) |
|||
(20 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
<big>Imagen de Reinstalación Automática</big> |
<big>Imagen de Reinstalación Automática</big> |
||
{{OLPC}}{{Translation | lang = es | source = Autoreinstallation image | version = |
{{OLPC}}{{Translation | lang = es | source = Autoreinstallation image | version = 64127}}{{Ongoing Translation}} |
||
{{TOCright}} |
{{TOCright}} |
||
Esta página describe como actualizar la imagen del software en su laptop. El procedimiento de actualización crea una llave o disco USB, que cuando es usado para ''bootear'' la laptop OLPC, actualiza el ''firmware'' e instala una nueva versión de la imagen del sistema operativo en la flash NAND. |
|||
Hemos trabajado muy duro para hacer lo más fácil posible la actualización de una máquina en el terreno. Hasta que el ''booteo'' y actualización vía red este disponible, esta es la forma más fácil. |
|||
'''Este proceso cambia regularmente, por lo tanto lea las instrucciones con atención.''' Algunos cambios importantes están [[#Important Notes|destacados más abajo]]. El procedimiento básico consta de tres etapas: |
|||
La imagen de Autoreinstalación consiste de un ''script'' [[Open Firmware/lang-es|Open Firmware]] que actualiza la memoria flash NAND y el firmware con las últimas versiones estables, sin otro requerimiento excepto el instertar una llave USB previamente preparada y prender la máquina. |
|||
# [[#Preparing the hardware|Preparar el hardware]]; |
|||
# [[#Preparing the autoupdate image|Preparar la imagen de auto-actualización]]; y |
|||
# [[#Upgrading the machine|Actualizar la máquina]]. |
|||
La versión del software a usar depende de: la [[#What kind of laptop is it?|versión del hardware a actualizar]] y si se desea usar una versión estable o experimental de desarrollo del software. Las versiones de desarrollo tienen más funcionalidades, pero también más ''bugs'' (a veces grandes). Las [[Test Group Release Notes/lang-es|Notas de Lanzamiento del Grupo de Pruebas]] describe las versiones de desarrollo. Las [[Software Release Notes/lang-es|Notas de Lanzamiento del Software]] describe el estado de los problemas importantes con los que se pueda haber topado anteriormente. La mayoría de la gente con laptops recientes usa la versión estable. Gente con prototipos de la laptop más viejos puede ser que necesiten usar versiones más viejas. Los desarrolladores pueden querer usar versiones más nuevas. |
|||
; NOTA : este procedimiento crea una llave o disco USB que al ser ''booteado'' en una laptop OLPC, actualiza su BIOS e instala (SOBRE-ESCRIBE) la imagen del sistema operativo sobre la memoria flash NAND. NUNCA ''bootee'' desde esta llave o disco USB a menos que desee actualizar el sistema, que borrará totalmente la memoria flash del mismo. |
|||
{{Translated text | |
{{ Translated text | |
||
This page describes how to update the software image on your laptop. The update procedure creates a USB flash key or disk, that when booted on an OLPC laptop, updates its firmware and installs a new version of the operating system image onto NAND flash. |
|||
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. |
|||
'''This process changes regularly, so please read the instructions carefully.''' Some important changes are [[#Important Notes|noted below]]. The basic procedure has three parts: |
|||
The Autoreinstallation image consists of an Open Firmware script that updates the NAND flash and firmware with the latest stable images, without requiring the user to do more than insert a prepared USB disk and turn on the machine. |
|||
# [[#Preparing the hardware|preparing the hardware]]; |
|||
# [[#Preparing the autoupdate image|preparing the autoupdate image]]; and |
|||
# [[#Upgrading the machine|upgrading the machine]]. |
|||
The software version you choose depends on: [[#What kind of laptop is it?|what version of laptop hardware you are upgrading]] and whether you want to use a stable version or one of the experimental development versions of the software. The development versions have more features, but also many more bugs (sometimes big ones). The [[Test Group Release Notes]] describe the development versions. The [[Software Release Notes]] describe the status of important software problems you may have encountered previously. Most people with recent laptops will use the stable version. People with older laptop prototypes may need to use older versions. Developers may wish to use newer versions. |
|||
<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> |
|||
| display = block}} |
| display = block }} |
||
{{anchor|Important Notes}} |
|||
Este procedimiento funciona para todos los tipos de hardware OLPC, incluyendo las placas A-Test y la mayoría de los B1 (ver [[Autoreinstallation image/lang-es#Workaround for old B1 systems|más abajo para los B1 viejos]]) y todos los B2. Si todavía utiliza la BIOS Insyde, se deberá primero actualizar el firmware siguiendo las instrucciones de como [[Upgrading to LinuxBIOS/lang-es|actualizar a LinuxBIOS]]. |
|||
==Avisos Importantes== |
|||
{{Latest Releases | firmware = inline | server = inline}} |
|||
Si se esta actualizando el ''firmware'', y ocurre algún problem que no se menciona en esta página, <span style="color:red; ">'''no apague la máquina'''</span>; y consiga ayuda de la OLPC, preferentemente por medio de [[IRC/lang-es|IRC]] o por correo electrónico de forma inmediata. |
|||
Las [[Software Release Notes/lang-es|Notas de Lanzamiento de Software]] documentan el estado de los puntos más relevantes de este software. |
|||
{{Translated text | |
|||
This procedure works for all types of OLPC hardware, including A-test boards and most B1 (see [[#Workaround for old B1 systems]]) and all B2 laptops. 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 '''[[Upgrading_to_LinuxBIOS|elsewhere]]'''. |
|||
Firmware q2c24 (en las imágenes de auto-reinstalación "2007-08-17 23:10Z" y "2007-08-18 05:08Z") has sido retirado ya que '''puede ''«brickear»'' máquinas B2'''. Por favor, cerciorése de obtener la última versión de la imagen de auto-reinstalación! |
|||
The [[Software Release Notes]] document the status of the most important issues of this software. |
|||
| display = block}} |
|||
La versión de la imagen de auto-reinstalación es mostrada al inicio del proceso de actualización. También se puede encontrar el ''string'' de la versión al principio del archivo de texto <tt>olpc.fth</tt> en el directorio <tt>boot</tt>. |
|||
Las versiones más recientes del firmware no soportan las placas A-Test o las máquinas pre-B1. No use este procedimiento si tiene alguna de ellas; contáctese con la OLPC para una actualización. |
|||
{{ Translated text | 1= |
|||
If you are upgrading ''firmware'', and anything goes wrong which is not mentioned on this page, <span style="color:red; ">'''do not turn off the machine'''</span>; please get help from OLPC, preferably immediately on IRC or by email. |
|||
Firmware q2c24 (in autoreinstallation images "2007-08-17 23:10Z" and "2007-08-18 05:08Z") has been withdrawn because '''it may brick B2 machines'''. Be sure you get the latest version of the autoreinstallation image! |
|||
The autoreinstallation image version is displayed at the start of the upgrade process. You can also find the version string at the top of the olpc.fth text file in the boot directory. |
|||
Recent firmwares do not support A-test boards or pre-B1 machines. Do not use this process if you have one of these; contact OLPC for an upgrade. |
|||
| display = block }} |
|||
Comenzando con la imagen de auto-reinstalación "2007-08-15 18:23Z", el procedimiento de actualización realiza una copia de respaldo automática de los datos de usuario antes de actualizar y lo reinstancia al finalizar. La llave USB debe ser los suficientemente grande para almacenar tanto la imagen que se va a instalar, así como también todos los archivos que puedan haber sido creados en <tt>/home/olpc</tt>. '''ADVERTENCIA:''' el procedimiento de actualización anterior '''borraba completamente''' la memoria flash del sistema. Asegúrese de cual es la versión de la imagen de auto-reinstalación que está usando; se puede descargar la imagen más nueva del enlace más abajo si no se está seguro. |
|||
A partir de la imagen de auto-reinstalación "2007-08-17 16:35Z" la activación de una máquina previamente no activada después de una actualización ha sido simplificado; vea los detalles abajo. |
|||
A partir del '''Build 542''' (firmware Q2C20e), hemos corregido un ''bug'' que se comía llaves USB formateadas como FAT32. |
|||
* Por favor, re-descargue la imagen de auto-reinstalación (<tt>[http://dev.laptop.org/git/users/cscott/autore/plain/olpc-auto.zip;hb=HEAD olpc-auto.zip]</tt>) y utilice los nuevos archivos. |
|||
* Puede ser deseable reformatear la llave USB o usar un verificador de archivos sobre ella para reparar cualquier anormalidad producida por el viejo firmware. |
|||
A partir del '''Build 525''', hemos agregado el paso de activación al procedimiento de actualización. |
|||
* Es necesario usar el <tt>'''[http://dev.laptop.org/git/users/cscott/autore/plain/olpc-auto.zip]'''</tt>. |
|||
* Debe dejar el disco o llave USB en la máquina después de actualizar, mientras ''rebootea''. |
|||
* Note que las rutinas de activación se encuentran solamente en el ''build'', no en el firmware, con lo cual es posible (hasta próximo aviso) mantener el firmware actualizado aún corriendo el Build 406.15, lo recomendado para aquellos con máquinas B2-1 (ej: 128MB). |
|||
{{ Translated text | 1= |
|||
Starting with autoreinstallation image "2007-08-15 18:23Z", the upgrade process automatically backs up user data before the upgrade and restores it afterward. The USB key must be large enough to hold both the image to be installed and any and all files the user may have created in /home/olpc. '''WARNING''': the old update procedure '''entirely erased''' the flash memory of the system. Be sure you know which version of the autoreinstallation image you are using; download the newest image from the link below if you are not certain. |
|||
As of autoreinstallation image "2007-08-17 16:35Z" activating a previously-unactivated machine after the upgrade has been simplified; see details below. |
|||
As of '''Build 542''' (firmware Q2C20e), we have fixed a bug that corrupted USB keys which were formatted FAT32. |
|||
* Please redownload the autoreinstallation image ([http://dev.laptop.org/git?p=users/cscott/autore;a=blob_plain;f=olpc-auto.zip;hb=HEAD olpc-auto.zip]) and use the new files. |
|||
* You may also want to either reformat your USB key or use a file system checker on it to repair any corruption that may have occurred with the old firmware. |
|||
As of '''Build 525''', we have added an activation step to the update process. |
|||
* You will need to use the '''[http://dev.laptop.org/git?p=users/cscott/autore;a=blob_plain;f=olpc-auto.zip;hb=HEAD new]''' version of the autoreinstallation image files. |
|||
* You must leave the USB flash key or disk in the machine after the upgrade, while it reboots. |
|||
* Note that the activation code is only in the build, not in the firmware, so you can (until further notice) keep your firmware up to date while still running Build 406.15, the current recommendation for those of you with B2-1 (ie, 128MB B2) machines. |
|||
| display = block }} |
|||
A partir del '''Build 406''', se agregó un archivo de ''checksum'' la procedimiento de actualización. |
|||
* Se necesita tanto el archivo '''<tt>.img</tt>''' como el '''<tt>.crc</tt>''' para actualizar. |
|||
Este procedimiento funciona sobre hardware OLPC reciente: |
|||
* La mayoría de las B1 (ver [[#Workaround for old B1 systems|soluciones más abajo]]); y |
|||
* Todas las laptops B2, B3, B4 y C. |
|||
Solo ha sido probado con Open Firmware: |
|||
* Si está usando Linux-as-BIOS o BIOS Insyde, vea la [[#Workaround for LinuxBIOS or Insyde BIOS|solución más abajo]]. |
|||
{{ Translated text | 1= |
|||
As of '''Build 406''', we have added a checksum file to the update process. |
|||
* You will need both the '''<tt>.img</tt>''' file and the '''<tt>.crc</tt>''' file to update. |
|||
This procedure works for recent OLPC hardware: |
|||
* Most B1 (see [[#Workaround for old B1 systems| workaround below]]); and |
|||
* All B2, B3, B4 and C laptops. |
|||
It has only been tested with Open Firmware: |
|||
* If you are running Linux-as-BIOS or Insyde BIOS, see the [[#Workaround for LinuxBIOS or Insyde BIOS| workaround below]]. |
|||
| display = block }} |
|||
{{anchor|What kind of laptop is it?}} |
|||
===¿Qué tipo de laptop es?=== |
|||
Es importante identificar que tipo de Xo laptop usted esta actualizando. |
|||
* A-Test board (Solo tarjeta madre) |
|||
* Máquinas B1 (identificable por un sello '''B1-TEST SAMPLE''' debajo de la batería) |
|||
* Máquinas B2-1 (identificable por unos sellos '''B2-TEST SAMPLE''' y '''B2-1''' hasta '''B2-16''' debajo de la batería) |
|||
* Máquinas B2-2 (identificable por un sello '''B2-7-ext''' debajo de la batería) |
|||
* Maquinas B3 (colored cover-plate; identificable por un sello '''B3-TEST SAMPLE''' debajo de la batería) |
|||
* Maquinas B4 (manija texturizada; colored cover-plate; identificables por unos sellos '''B4-TEST SAMPLE''' y '''B4-1''' hasta '''B4-16''' debajo de la baterial) |
|||
* Preproduccion (maquinas C) (Completamente texturizadas; identificadas por unos sellos '''C-TEST SAMPLE''' y '''C-4''' debajo de la bateria) |
|||
(Vea las [[Hardware_specification#Laptop_Development_Schedule|Laptop Development Schedule]] para una mas detallada descripción de estos sistems de desarrollo.) |
|||
{{ Translated text | |
|||
It is important to identify which kind of XO laptop you are upgrading: |
|||
* A-Test board (bare motherboards) |
|||
* B1 machines (identifiable by a '''B1-TEST SAMPLE''' label under the battery) |
|||
* B2-1 machines (identifiable by '''B2-TEST SAMPLE''' and '''B2-1''' through '''B2-16''' labels under the battery) |
|||
* B2-2 machines (identifiable by '''B2-7-ext''' label under the battery) |
|||
* B3 machines (colored cover-plate; identifiable by a '''B3-TEST SAMPLE''' label under the battery) |
|||
* B4 machines (textured handle; colored cover-plate; identifiable by a '''B4-TEST SAMPLE''' and '''B4-1''' through '''B4-16''' labels under the battery) |
|||
* Preproduction (C machines) (fully textured; identifiable by a '''C-TEST SAMPLE''' and '''C-4''' label under the battery) |
|||
(See the [[Hardware_specification#Laptop_Development_Schedule|Laptop Development Schedule]] for a more detailed description of the various development systems.) |
|||
| display = block }} |
|||
{{anchor|System Update Procedure}} |
{{anchor|System Update Procedure}} |
||
== Procedimiento de Actualización del Sistema == |
|||
==Procedimiento de Actualización del Sistema== |
|||
; Antes de comenzar : enchufe la máquina y verifique que la batería esté cargada. Es '''muy''' importante que el proceso no sea interrumipido. Tomará solamente 2 minutos 15 segundos en total. |
|||
{{anchor|Preparing the hardware}} |
|||
# '''Descargue''' el archivo [http://olpc.download.redhat.com/olpc/autoupdate/olpc406_c11.zip olpc406_c11.zip]<br>md5sum: <code>0de554d266e87344f8d25b7fd2cebb74 olpc406_c11.zip</code> |
|||
===Preparando el hardware=== |
|||
# Utilice una llave o disco USB con por lo menos 300 MiB en su partición primaria (no es necesario que esté particionado) |
|||
Si usted tiene hardware viejo como (A.B1,B2,B3).. y no sabe si esta corriendo una versión mas vieja que Q2C11 (2007-05-06), necesita comprobarlo. (Al tipear <tt>Alt-=</tt> se abrira la consola de desarrollo, donde la actual versión del firmware esta reportada.) Si usted tiene el viejo firmware, entonces solo presione el boton de prendido/apagado; usted no tiene que presionar el botón "X" de la consola de juego mientras presiona el botón de apagado. (los laptops B4, C, y M tienen un firmware mas reciente que Q2C11) |
|||
#* Si su sistema tiene [[Open Firmware/lang-es|Open Firmware]], puede tener un formato FAT (de fábrica) o <tt>ext3</tt>—en cuyo caso, asegurese que el tipo de partición declarada (ej:<tt>83</tt>–Linux <tt>ext2</tt> o <tt>ext3</tt>) sea tal y no FAT. |
|||
#* Si su sitema tiene Linux-como-BIOS, el dispositivo USB tiene que tener una partición primaria y un sistema de archivos tipo <tt>ext2</tt> en ella, ya que el cargador (''bootloader'') Linux buscará en el dispositivo <tt>/dev/sda1</tt> |
|||
# '''[[Unzip|Descompacte]]''' los archivos en la raíz de la llave o disco USB, creando así el directorio <tt>boot</tt>. (De drag-n-drop de los archivos directamente del archivo <tt>.zip</tt> deberá crear dicho directorio manualmente). Para que la actualización se efectúe deben existir tres archivos en el directorio: '''<tt>q2c11.rom, nand406.img y olpc.fth</tt>'''. Un cuarto archivo <tt>'''bzimage'''</tt> debe encontrarse en la raíz. |
|||
#* No utilice un dispositivo USB para el cual se hayan reportado errores en el proceso de descompactación: los archivos pueden estar (probablemente esten) dañados. Como medida de seguridad extra, la BIOS OFW OLPC verifica la integridad de la imagen antes de flashear la BIOS. |
|||
# '''Opcional''' - Si se desea instalar una [[OS images/lang-es|Imagen del SO]] diferente al ''build'' 406, descargue la imagen [[JFFS2/lang-es]] correspondiente del [http://olpc.download.redhat.com/olpc/streams/development/ repositorio], y guardelo como <tt>'''nandXXX.img'''</tt> (siendo <tt>XXX</tt> el número del ''build''). Después edite <tt>'''olpc.fth'''</tt>, remplazando todas las ocurrencias de <tt>'''406'''</tt> por el número de ''build'' del archivo. |
|||
# '''Inserte''' la llave en la máquina, y |
|||
#* Si tiene [[Open Firmware/lang-es|Open Firmware]] Q2C11 o posterior, mantenga una de las "teclas de juego" (''game keys'') cercanas a la pantalla mientras enciende la laptop; y suéltelo una vez que la pantalla se ilumine. |
|||
#* Si tiene [[Open Firmware/lang-es|Open Firmware]], anterior a Q2C11 solo encienda la máquina. |
|||
#* Si tiene Linux-como-BIOS, cuando vea la barra de progreso, presione [[Image:Key esc.jpg]] (Esc), y seleccione el icono USB, y presione [[Image:Key enter.jpg|70px]] (Enter). |
|||
#* Si esta utilizando un '''disco''' USB puede ser necesario interrumpir el proceso de ''booteo'' del [[Open Firmware/lang-es|Open Firmware]] presionando la tecla [[Image:Key esc.jpg]] (Esc), esperar un momento, ingresar <tt>'''probe-usb2'''</tt>, lo cual debería proporcionar opciones extras a las iniciales. Después puede ingresar <tt>'''boot'''</tt> y la actualización debería continuar. Esto se debe a que los discos externos tardan mucho en estar listos. El último firmware debería solucionar esto. |
|||
{{Translated text | |
|||
<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> It will take about 2 minutes and 15 seconds total. |
|||
# '''Download''' the file http://olpc.download.redhat.com/olpc/autoupdate/olpc406_c11.zip <br> md5sum: <code> 0de554d266e87344f8d25b7fd2cebb74 olpc406_c11.zip </code> |
|||
# Get a USB flash key or disk with at least 300 MiB of free space in the primary partition (it doesn't have to be partitioned at all). If your system currently has Open Firmware, the filesystem can be either FAT (like a factory-formatted device) or ext2. But it will not work if it is partitioned such that the partition type code says "83" (Linux ext2 or ext3) but the actual filesystem inside the partition is FAT. If your system has Linux-as-BIOS, the USB device must have a primary partition and an ext2 filesystem on it, as /dev/sda1 is the device that Linux as bootloader looks for. |
|||
# '''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: '''q2c11.rom'''; '''nand406.img'''; and '''olpc.fth'''. A fourth file, '''bzimage''' must be in the root directory. Do not use a flash key or disk for which there have been any errors reported during unzipping: the files may be (probably are) damaged. As a further safeguard, the OLPC OFW BIOS checks the integrity of any BIOS flash image before reflashing the BIOS. |
|||
# (Optional) If you want to install an [[OS images|OS image]] besides build 406, download the appropriate jffs2 image from the [http://olpc.download.redhat.com/olpc/streams/development/ image repository], and save it as '''nandXXX.img''', where XXX is the number of the build. Then, edit '''olpc.fth''', replacing '''406''' everywhere it occurs with the build number in the filename. |
|||
# '''Insert''' the USB flash key into the machine. '''If you have Open Firmware Q2C11 or later, hold down one of the "game keys" next to the screen, while you press the power button to turn on the laptop; then release the game keys when the screen lights up.''' If you have Open Firmware before version Q2C11, 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. |
|||
# If your USB device is a hard disk instead of flash, you may need to interrupt the Open Firmware boot sequence by pressing the Esc key (the upper left key on the keyboard, marked with an X in a circle), waiting a moment, then entering '''probe-usb2'''. You should see additional entries compared to the initial list that Open Firmware displayed. Then you can enter '''boot''' and the update should proceed. This is because many external hard drives take a long time to come ready. The latest firmware should fix this issue, however. |
|||
| display = block}} |
|||
# Conecte su laptop y asegúrese que su batería este cargada. Es muy importante que el proceso de actualización (que toma casi tres minutos) no sea interrumpido. |
|||
Se podrán observar una serie de mensajes como los de la siguiente sección a medida que el sistema es actualizado. La memoria flash NAND siempre tiene algun bloque malo: por lo tanto los mensajes del tipo <tt>"Skipping bad block"</tt> (''salteando bloque malo'') son normales, informando aquellos bloques que Linux jamás usará. |
|||
# Consiga una USB con al menos 300Mib de espacio libre en la partición primaria. |
|||
#* El sistema de archivos debe ser FAT (como un aparato formateado desde fabrica). |
|||
#* No tiene que estar particionada, y no funcionara si tiene el código tipo "83" (Linux ext2 o ext3), aun si el actual sistema de archivos adentro de la partición es. |
|||
{{ Translated text | 1= |
|||
El sistema se apagará solo. |
|||
If you have older (A,B1,B2,B3) laptop hardware, and don't know whether it is running a firmware version older than Q2C11 (2007-05-06), you need to check. (Typing <tt>Alt-=</tt> will take you to the Developer's Console, where the current firmware version is reported.) If you do have the older firmware, then just press the power button; you do not have to hold the X game key and press the power button as instructed below. (B4, C, and M laptops have firmware more recent that Q2C11.) |
|||
# Plug in your laptop and ensure the battery is charged. It is very important that the update process (Which takes about 3 minutes) not be interrupted. |
|||
Si algo sale mal '''NO APAGUE LA MÁQUINA''' y solicite ayuda a la OLPC, preferentemente de forma inmediata vía IRC o por email. |
|||
# Get a USB flash key or disk with at least 300 MiB of free space in the primary partition. |
|||
#* The filesystem should be FAT (like a factory-formatted device). |
|||
#* It does not have to be partitioned, and will not work if it is partitioned such that the partition type code says "83" (Linux ext2 or ext3), even if the actual filesystem inside the partition is FAT. |
|||
| display = block }} |
|||
{{anchor|Preparing the autoupdate image}} |
|||
Felicitaciones! Ha terminado! La próxima vez que encienda la máquina, tendrá la nueva imagen. |
|||
{{Translated text | |
|||
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. |
|||
===Preparando la imagen de auto-actualización=== |
|||
The system will automatically poweroff. |
|||
Estas instrucciones son para cargar una imagen de auto-actualiacion en un disco USB. Las instrucciones para preparar una tarjeta SD son similares. |
|||
If anything goes wrong <b>DO NOT TURN OFF THE MACHINE</b> but please get help from OLPC, |
|||
preferably immediately on IRC or by email. |
|||
NOTA: si usted tiene python disponible y tiene alguna familiaridad con la linea de comandos, entonces la inicializacion del directorio de auto-instalación y la preparacion de la imagen de actualizacion pueden ser [[Autoreinstallation image#Preparing the latest image (automatically) | logradas automáticamente]]. |
|||
Congratulations: you are finished! When you next power the machine on, you'll be running the new image. |
|||
| display = block}} |
|||
{{ Translated text | |
|||
These instructions are for loading an autoupdate image onto a USB flash key or USB disk drive. The instructions for preparing an SD card are similar. |
|||
NOTE: If you have Python available and some familiarity with the command line, then the initialization of the auto-installation directory and the preparation of an update image can be [[Autoreinstallation image#Preparing the latest image (automatically) | accomplished automatically]]. |
|||
| display = none }} |
|||
{{anchor|Initializing the auto-installation directory (manually)}} |
|||
====Inicializando el directorio de auto-instalación (manualmente)==== |
|||
# Descargue [http://dev.laptop.org/git?p=users/cscott/autore;a=blob_plain;f=olpc-auto.zip;hb=HEAD olpc-auto.zip] |
|||
# Unzip '''<tt>olpc-auto.zip</tt>''' en la raiz de una llave o disco USB y al hacer esto se crea un directorio llamado '''boot'''. |
|||
#* Si usted arrastra y deja caer los archivos desde un zip, usted tendra que crear el directorio boot manualmente en el flash drive. |
|||
#* Habra cuatro archivos en el directorio boot inicialmente: <tt>'''olpc.fth''', '''{{Latest Releases/firmware number}}.rom''', '''usbupgos.img''', y '''usbupgrd.img'''</tt>. |
|||
{{ Translated text | 1= |
|||
# Download [http://dev.laptop.org/git?p=users/cscott/autore;a=blob_plain;f=olpc-auto.zip;hb=HEAD olpc-auto.zip] |
|||
# Unzip '''<tt>olpc-auto.zip</tt>''' 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. |
|||
#* There will be four files in the boot directory initially: <tt>'''olpc.fth''', '''{{Latest Releases/firmware number}}.rom''', '''usbupgos.img''', and '''usbupgrd.img'''</tt>. |
|||
| display = block }} |
|||
{{anchor|Preparing the latest image (manually)}} |
|||
====Preparando la imagen más reciente (manualmente)==== |
|||
# Si usted ha anteriormente creado la imagen de auto-instalación, remueva los archivos <tt>.img</tt> y <tt>.crc</tt> del directorio boot del flash o disk drive. (No olvide "Borrar la Basura.") |
|||
# Descargue la ultima imgen de SO (<tt>.img</tt>) y su archivo de checksum (<tt>.crc</tt>). Usted puede escoger entre [http://olpc.download.redhat.com/olpc/streams/development/LATEST-STABLE-BUILD/devel_jffs2/ La ultima imagen estable] y [http://olpc.download.redhat.com/olpc/streams/development/latest/devel_jffs2/ La ultima imagen de desarrollo inestable]. |
|||
#* La imagen es llamada '''<tt>osNNN.img</tt>''' ("<tt>NNN</tt>" representa el numero de construcción de la imagen). El archivo checksum del mismo nombre tiene la extensión '''<tt>.crc</tt>'''. |
|||
#* Si usted esta descargando una construccion anterior a '''Build 530''', los archivos deberan ser renombrados en el sitio de descarga. Por ejemplo, si usted quiere descargar Build 528, usted tendria que descargar '''<tt>olpc-redhat-stream-development-build-528-20070720_0056-devel_jffs2.img</tt>''', y renombrarla '''<tt>os528.img</tt>''', y d ela misma forma para su archivo '''<tt>.crc</tt>'''. |
|||
#* Si usted esta descargando una imagen con un numero no entero, por ejemplo Build 542.3, se necesita renombrarla sin el punto decimal,., '''<tt>os5423.img</tt>''' y '''<tt>os5423.crc</tt>'''. |
|||
# Copie los archivos'''<tt>osNNN.img</tt>''' y '''<tt>osNNN.crc</tt>''' en el directorio '''<tt>boot</tt>''' del flash o disk drive. |
|||
# Uno d elos archivos en el directorio boot debe ser al ultima imagen de firmware, <tt>{{Latest Releases/firmware number}}.rom</tt>. Si la pagina [[Firmware]] tiene un firmware mas nuevo del que usted tiene, descarguelo en el directorio boot. |
|||
#* El firmware sera llamado <tt>qXXXX.rom</tt>, donde <tt>XXXX</tt> es el numero de entrega del firmware en hexadecimales (letters A-F and numbers 0-9). |
|||
# Verifique que estos seis archivos existan en el directorio llamado '''<tt>boot</tt>''' en su llave USB o disco: <tt>'''{{Latest Releases/firmware number}}.rom'''; '''osNNN.img'''; '''osNNN.crc'''; '''usbupgos.img''', '''usbupgrd.img''', y '''olpc.fth'''</tt>, donde <tt>NNN</tt>s es el numero de imagen hacia el cual usted esta actualizando. |
|||
#* No use una llave o disco USB que halla reportado errores durante la descompresión: los archivos podrían estar danados. Como una protección adicional el firmware chequea la integridad de la flash antes de hacer el reflash. |
|||
#* El archivo CRC se requiere aun asi anteriores versiones del firmware no. |
|||
# Ahora usted esta listo para [[Autoreinstallation image#Upgrading the machine | actualizar la maquina]]! |
|||
{{ Translated text | |
|||
# If you have previously created an auto-installation image, remove the <tt>.img</tt> and <tt>.crc</tt> files from the boot directory of the flash or disk drive. (Don't forget to "Empty Trash.") |
|||
# Download the latest build image (<tt>.img</tt>) and its checksum file (<tt>.crc</tt>). You may choose between the [http://olpc.download.redhat.com/olpc/streams/development/LATEST-STABLE-BUILD/devel_jffs2/ the latest stable build] and the [http://olpc.download.redhat.com/olpc/streams/development/latest/devel_jffs2/ the latest unstable development build]. |
|||
#* The image is called '''<tt>osNNN.img</tt>''' ("<tt>NNN</tt>" represents the build number). The checksum file of the same name has the '''<tt>.crc</tt>''' extension. |
|||
#* If you are downloading a build earlier than '''Build 530''', the files on the download site will need to be renamed. For instance, if you want to download Build 528, you would download '''<tt>olpc-redhat-stream-development-build-528-20070720_0056-devel_jffs2.img</tt>''', and rename it to '''<tt>os528.img</tt>''', and likewise for its '''<tt>.crc</tt>''' file. |
|||
#* If you are downloading a build with a non-integer number, e.g., Build 542.3, you need to rename it without the decimal point, e.f., '''<tt>os5423.img</tt>''' and '''<tt>os5423.crc</tt>'''. |
|||
# Copy '''<tt>osNNN.img</tt>''' and '''<tt>osNNN.crc</tt>''' files to the '''<tt>boot</tt>''' directory of the flash or disk drive. |
|||
# One of the files in the boot directory should be the latest firmware image, <tt>{{Latest Releases/firmware number}}.rom</tt>. If the [[Firmware]] page lists a newer firmware release than the one you have, download it to the boot directory. |
|||
#* The firmware will be named <tt>qXXXX.rom</tt>, where <tt>XXXX</tt> is the firmware release number in hexadecimal (letters A-F and numbers 0-9). |
|||
# Verify that these six files exist in the directory named '''<tt>boot</tt>''' on your USB key or disk: <tt>'''{{Latest Releases/firmware number}}.rom'''; '''osNNN.img'''; '''osNNN.crc'''; '''usbupgos.img''', '''usbupgrd.img''', and '''olpc.fth'''</tt>, where the <tt>NNN</tt>s are the build number to which you are updating. |
|||
#* Do not use a flash key or disk for which there have been any errors reported during unzipping: the files may be damaged. As a further safeguard, the firmware checks the integrity of the flash image before reflashing. |
|||
#* The CRC file is required even though earlier firmware did not check for the CRC file. |
|||
# You're now ready to [[Autoreinstallation image#Upgrading the machine | upgrade the machine]]! |
|||
| display = block }} |
|||
{{anchor|Preparing the latest image (automatically)}} |
|||
====Preparando la imagen más reciente (automáticamente)==== |
|||
El script <tt>[[Media:sugar-update.txt|sugar-update.py]]</tt> automatiza los pasos listados arriba para crear un directorio de autoinstalcion y preparar una nueva imagen. Este es un script hecho en python y por ello requiere python para correr. ''Nota importante: Debido a un bug en MediaWiki este script tubo que ser colgado como un archivo <tt>.txt</tt> . Por favor cambie la extensión a <tt>.py</tt> después de la descarga.'' |
|||
; Uso : <tt>sugar-update.py [-'''cdflLqs'''] [-'''b''' imagen] [directorio]</tt> |
|||
; Descripción : Este script creara un directorio boot de una imagen de auto-instalacion dentro del directorio especifico. Si el directorio boot ya existe, este solo bajara los archivos necesarios (<tt>.img, .crc, and .rom</tt>). Cualquiera de estos archivos que ya estén presentes dentro de <tt>boot</tt> seran borrados antes de que la descarga comience. Si no se especifica un directorio, el actual directorio de trabajo sera usado. |
|||
:Este script también tiene soporte automático para downgrades, y anadira cualquier archivo <tt>force.os</tt> necesario en el directorio boot si la imagen presente es mas nueva que las especificada. |
|||
; Opciones : |
|||
:<tt>-'''b''' </tt> Especifique un numero de imagen; por defecto la ultima imagen de desarrollo. |
|||
:<tt>-'''c''' </tt> Crea una a nueva imagen de auto-instalación, reemplazando el directorio boot existente. |
|||
:<tt>-'''d''' </tt> Downgrade forzoso de la actualización; implícito cuando una nueva imagen existe en boot |
|||
:<tt>-'''f''' </tt> Salta actualización de firmware |
|||
:<tt>-'''l''' </tt> Imprime el change log asociado. |
|||
:<tt>-'''L''' </tt> Imprime el change log para la imagen especificada y abandona |
|||
:<tt>-'''q''' </tt> Silencioso; no imprime el progreso. |
|||
:<tt>-'''s''' </tt> Descarga la ultima imagen estable; borrar la opción -b |
|||
; Examples : |
|||
: Si usted esta creando un directorio boot desde el comienzo, usted simplemente querrá usar: |
|||
sugar-update.py /path/to/USBdrive/ |
|||
: Anadiendo la bandera -s a lo de arriba, la ultima imagen sera preparada: |
|||
sugar-update.py -s /path/to/USBdrive/ |
|||
: Para updates frecuentes es útil mostrar el change log par las nuevas imágenes: |
|||
sugar-update.py -l /path/to/USBdrive/ |
|||
{{ Translated text | |
|||
The <tt>[[Media:sugar-update.txt|sugar-update.py]]</tt> script automates the steps listed above for creating an auto-installation directory and preparing a new image. This is a python script, and as such requires python to run. ''Important Note: Due to a bug in MediaWiki this script had to be uploaded as a <tt>.txt</tt> file. Please change the extension to <tt>.py</tt> after downloading.'' |
|||
; Usage : <tt>sugar-update.py [-'''cdflLqs'''] [-'''b''' build] [directory]</tt> |
|||
; Description : This script will create an autoinstallation image boot directory within the specified directory. If the boot directory already exists, it will only download the necessary image files (<tt>.img, .crc, and .rom</tt>). Any of these files already present within this <tt>boot</tt> directory will be deleted before the download begins. If no directory is specified, the current working directory will be used. |
|||
:This script has also has automatic support for downgrades, and will add the necessary <tt>force.os</tt> file to the boot directory if the build image already present there is newer than the build specified. |
|||
; Options : |
|||
:<tt>-'''b''' </tt> Specify a build number; defaults to latest development build |
|||
:<tt>-'''c''' </tt> Create a clean auto-installation image, replacing existing boot directory |
|||
:<tt>-'''d''' </tt> Force downgrade image; implicit when a newer build exists in boot |
|||
:<tt>-'''f''' </tt> Skip firmware update |
|||
:<tt>-'''l''' </tt> Print the associated change log |
|||
:<tt>-'''L''' </tt> Print the change log for the specified build and quit |
|||
:<tt>-'''q''' </tt> Quiet; do not print progress output |
|||
:<tt>-'''s''' </tt> Download the latest stable build; overrides the -b option |
|||
; Examples : |
|||
: If you're creating a boot directory from scratch, you'll simply want to use: |
|||
sugar-update.py /path/to/USBdrive/ |
|||
: By adding the -s flag to the above, the latest stable image will be prepared instead: |
|||
sugar-update.py -s /path/to/USBdrive/ |
|||
: For frequent updates it's useful to show the change log for the new builds: |
|||
sugar-update.py -l /path/to/USBdrive/ |
|||
| display = block }} |
|||
{{anchor|Upgrading the machine}} |
|||
===Actualizando la máquina=== |
|||
{{ Translated text | 1= |
|||
Please follow these steps: |
|||
:(A) Switch off the laptop; |
|||
:(B) Provide power: put in a battery; plug in the laptop; |
|||
:(C) Insert the USB key with the autoupdate image; |
|||
:(D) Switch on the laptop, and watch it carefully; |
|||
::(D.1) hold down the X game key on the bezel above the power button, while you press the power button; then release the game key when the screen lights up. ''(>=Q2C11)'' |
|||
::(D.2) if the laptop says "<tt>Firmware is already current</tt>" you can skip to Step (I) below; if instead you see "<tt>Updating firmware from q2XXX to q2YYY</tt>", then continue with Step (E); |
|||
---- |
|||
:(E) Let the firmware update complete; the laptop will then turn off automatically; |
|||
:(F) Remove all power from the laptop. This step is very important (it resets the embedded controller). <span style="color:red; ">'''Do not remove the USB key'''</span> yet. |
|||
::(F.1) unplug the laptop; take out the battery; |
|||
::(F.2) wait 30 seconds; |
|||
:(G) Put in the battery; plug the machine back in; |
|||
:(H) Switch on the laptop; |
|||
::(H.1) hold down the X game key on the bezel above the power button, while you press the power button; then release the game when the screen lights up. ''(>=Q2C11)'' |
|||
---- |
|||
:(I) The XO will now |
|||
:: boot, to backup the user files, |
|||
:: reboot, to upgrade the base image, |
|||
:: reboot, to restore the user files; |
|||
:: then power down; |
|||
:(J) '''Remove the USB key'''; |
|||
:(K) Power on the laptop again '''without the USB key inserted'''. |
|||
Congratulations: you are running a new build image. |
|||
A sample transcript of the update procedure is shown in [[#Transcript_of_System_Update|following section]]. |
|||
| display = block }} |
|||
{{anchor|Additional notes}} |
|||
====Notas adicionales==== |
|||
{{ Translated text | 1= |
|||
* If you have Open Firmware before version Q2C11 (2007-05-06), turn on the power ''without'' pressing a game key. |
|||
* If you are upgrading an unactivated machine (prior to Build 542), you may see either a message that says, "Could not activate this XO" followed by the serial number of your machine, or else a XO icon in the center of the display with a lock icon in the bottom right corner. [[Image:Locked_XO.png|right|thumb|Icon displayed when activation fails.]] If this happens: turn off the machine; reinsert the USB key; and hold down the 'X' and 'check' game buttons down while turning the power on. (If your XO is pre-B4 and does not have a 'check' button, use the 'O' button instead.) Release the buttons when directed. The system should boot into the new system image and perform activation using the activation lease stored on the USB key; '''Do not remove the USB key''' until you've reached the sugar "XO" screen, or the activation process will fail; |
|||
* If your USB device is a harddisk instead of flash, you may need to interrupt the Open Firmware boot sequence by pressing the Esc key (the upper left key on the keyboard, marked with an X in a circle), waiting a moment, then entering ''<tt>probe-usb2</tt>''. You should see additional entries compared to the initial list that Open Firmware displayed. Then you can enter ''<tt>boot</tt>'' and the update should proceed. This is because many external hard drives take a long time to come ready. Recent firmware should fix this issue. |
|||
* If the machine does not power on, you need to reset the EC: (a) unplug the machine; (b) remove the battery; (c) wait 30 seconds; (d) reinsert the battery; (e) reconnect power (i.e., plug in the machine); and (f) power on the machine.'''This behavior is expected for machines with Li batteries so be prepared for that'''. Please <span style="color:red; ">'''do not remove the USB key'''</span> until the activation process is completed. |
|||
* When removing all power from the laptop, any external USB peripherals should be disconnected, just in case they are faulty and supply current to the system. |
|||
* If anything else goes wrong <span style="color:red; ">'''do not turn off the machine'''</span>; please get help from OLPC, preferably immediately on IRC or by email. |
|||
* After the upgrade, a backup of your user files can be found on the USB key with the name '<tt>backup/<your XO's serial number>/complete.tgz</tt>'. |
|||
| display = block }} |
|||
{{anchor|Transcript of System Update}} |
{{anchor|Transcript of System Update}} |
||
==Transcripción de una Actualización de Sistema == |
|||
==Transcripción de la Actualización del Sistema== |
|||
<pre> |
<pre> |
||
Release the game key to continue |
Release the game key to continue |
||
OLPC B1, 256 MiB memory installed, S/N Unknown |
OLPC B1, 256 MiB memory installed, S/N Unknown |
||
Open Firmware CL1 Q2C08 Q2C |
Open Firmware CL1 Q2C08 Q2C |
||
USB2 devices: |
USB2 devices: |
||
Line 85: | Line 332: | ||
Type the Esc key to interrupt automatic startup |
Type the Esc key to interrupt automatic startup |
||
Boot device: /usb/disk:\boot\olpc.fth Arguments: |
Boot device: /usb/disk:\boot\olpc.fth Arguments: |
||
Autoreinstallation version: 2007-08-15 19:27Z |
|||
Checking existing OS image on NAND FLASH |
|||
Existing OS build is 353 |
|||
Updating OS image on NAND FLASH |
|||
Erasing... |
|||
1800 |
|||
Skipping bad block at 0xc20000 = page 0x1840 = eblock 0x61 |
|||
3ff40 |
|||
Writing 80c blocks |
|||
80b |
|||
Done |
|||
Existing firmware version is q2c08 |
Existing firmware version is q2c08 |
||
Updating firmware |
Updating firmware from q2c08 to q2c25 |
||
Reading disk:\boot\ |
Reading disk:\boot\{{Latest Releases/firmware number}}.rom |
||
Got firmware version: CL1 |
Got firmware version: CL1 Q2C25 Q2C |
||
Checking integrity ... |
Checking integrity ... |
||
SPI FLASH is type 13 - Spansion, Winbond, or ST |
SPI FLASH is type 13 - Spansion, Winbond, or ST |
||
Line 109: | Line 347: | ||
ff000 |
ff000 |
||
... |
... |
||
Powering off |
|||
Done |
|||
</pre> |
</pre> |
||
{{ Translated text | |
|||
'''En la mayoría de los casos, el sistema se apagará automáticamente después de haber terminado la actualización.''' |
|||
'''[Then you remove power, replace power, and turn it back on again...]''' |
|||
{{Translated text | |
|||
| display = block }} |
|||
'''In most cases, the system will power-off automatically after the firmware is updated.''' |
|||
<pre> |
|||
| display = block}} |
|||
OLPC B4, 256 MiB memory installed, S/N Unknown |
|||
OpenFirmware CL1 Q2C25 Q2C |
|||
Can't assign address ranges larger than 32-bits |
|||
{{anchor|Possible Problems}} |
|||
USB2 devices: |
|||
== Posibles Problemas == |
|||
/pci/usb@f,5/wlan@3,0 |
|||
/pci/usb@f,5/scsi@1,0 |
|||
/pci/usb@f,5/scsi@1,0/disk |
|||
USB1 devices: |
|||
Type the Esc key to interrupt automatic startup |
|||
Boot device: /usr/disk:\boot\olpc.fth Arguments: |
|||
Autoreinstallation version: 2007-08-02 23:28Z |
|||
</pre> |
|||
{{ Translated text | |
|||
'''[Boots into Linux]''' |
|||
| display = block }} |
|||
<pre> |
|||
....lots of kernel boot messages.... |
|||
Backing up /home/olpc, size 13487 |
|||
Backing up /security, size 1 |
|||
Total used KB: 13473, disk free KB: 734112 |
|||
Skipping from ignore list: /home/olpc/Library |
|||
tar: Removing leading '/' from member names |
|||
* Es preferible no usar discos USB particionados. De estar particionado: |
|||
Done! |
|||
*# El tipo de la partición debe corresponder con el tipo de sistema de archivos—un sistema de archivos <tt>FAT</tt> en una partición declarada como <tt>ext2</tt> no funcionará. |
|||
*** Done *** |
|||
*# Los archivos del actualizador deben estar en la partición ''booteable'', de no existir tal, en la primera. |
|||
</pre> |
|||
* Los archivos principales (<tt>olpcboot.fth, nandNNN.img, q2bNN.rom</tt>) deben encontrarse en el subdirectorio <tt>/boot/</tt>. Esto ocurre automáticamente si se [[Unzip/lang-es|descompacta]] el archivo, pero si se hace hace por medio del ''drag-n-drop'' a veces disponible en el administrador de archivos (''file manager''), es posible que queden en cualquier otro lugar, y no va a funcionar—deben estar en <tt>/boot/</tt>. El archivo <tt>bzImage</tt>, que es necesario para la actualización de Linux-como-BIOS, va en la raíz. |
|||
{{ Translated text | |
|||
* La versión actual de [[Open Firmware/lang-es|Open Firmware]] no soporta llaves USB que se auto-identifican como de clase <tt>"mass_storage/removable"</tt>, en oposición a las más comunes <tt>"mass_storage/scsi"</tt>, que sí son soportadas. La correción a este inconveniente está en camino, pero no está disponible por el momento. La forma de verificar es insertar la llave USB, encender el sistema y detener el proceso de ''booteo'' en la cuenta regresiva presionando la [[Image:Key esc.jpg]] (Esc) y fijarse en la lista de "Dispositivos USB2". Si muestra un ítem similar a <tt>"/pci/usb@f,5/removable@1,0"</tt> su disco tiene dicho problema. (Si se está corriendo sobre una versión vieja de OFW que no muestra la lista de "Dispositivos USB2" automáticamente, ingrese "<tt>show-devs /usb</tt>" para verla). La solución se encuentra más abajo. |
|||
'''[Reboots]''' |
|||
* El firmware actual tampoco puede utilizar dispositivos USB cuyo tamaño de sector de hardware no sea de 512 bytes. Para determinar el tamaño de sector de su dispositivo, se puede utilizar <tt>fdisk</tt> en Linux, que informará si el tamaño no es de 512 la primera vez que lo acceda. La solución es la misma que para el problema del "removible" más abajo. |
|||
| display = block }} |
|||
* Varios dispositivos Multi-Función no funcionan. |
|||
* Si durante la actualización se ve el siguiente mensaje, intente renombrando el archivo <tt>'''olpc.7th'''</tt> en el directorio "<tt>/boot</tt>" de la imagen de actualización a "<tt>olpc-boot.7th</tt>". |
|||
<pre> |
<pre> |
||
Autoreinstallation version: 2007-08-02 23:28Z |
|||
Trying startup script disk:\boot\olpc-boot.7th |
|||
Can't open boot device |
|||
Existing firmware version is Q2C25 |
|||
Firmware is already current; skipping update |
|||
Existing firmware version is Q2C25 |
|||
Firmware is already current; skipping update |
|||
Activation lease created successfully. |
|||
Checking existing OS image on NAND FLASH |
|||
Existing OS build is 353 .0 |
|||
Updating OS image on NAND FLASH from build 353 .0 to build 542 .0 |
|||
Check file is /pci/usb@f,5/scsi@1,0/disk@0:\boot\OS542.crc |
|||
Erasing... |
|||
3ff40 |
|||
Writing 6fd blocks |
|||
6fc |
|||
Filling with cleanmarkers ... |
|||
Done |
|||
Booting into linux to restore user files. |
|||
</pre> |
</pre> |
||
{{ Translated text | |
|||
* En las placas ATest el servidor X puede no levantar. Puede ser que necesite armar una [[Configuring X on an ATest board/lang-es|configuración personalizada]]. |
|||
'''[Linux boots up again]''' |
|||
{{Translated text | |
|||
| display = block }} |
|||
* It is better if the USB disk is not partitioned. If it is partitioned: |
|||
# The partition type must agree with the filesystem type - a FAT filesystem inside a partition marked ext2 won't work |
|||
# The updater files should be in the partition that is marked as "bootable", or if there isn't one, in the first partition. |
|||
* The main files (olpcboot.fth, nandNNN.img, q2bNN.rom) must be in the boot/ subdirectory. That will happen automatically if you "unzip" the archive, but if you drag-and-drop from a file manager like file-roller, it is possible to put them anywhere, and that won't work. Those files must be in boot/ . (The bzImage file, which is needed to support upgrading from Linux-as-BIOS, goes in the root directory.) |
|||
* The current Open Firmware releases do not support USB keys that identify themselves as class "mass_storage/removable", as opposed to the more common "mass_storage/scsi", which is supported. (The fix for this problem is in the release pipeline, but that doesn't help for upgrading from existing firmware.) The way to check for this is to insert your USB key, power-on the system and stop the auto-boot by typing the Esc key (upper left key) at the countdown. Then look at the list of "USB2 devices". If you see an entry like "/pci/usb@f,5/removable@1,0", your disk has the problem. (If you are running an old version of OFW that does not display the "USB2 devices" list automatically, type "show-devs /usb" to see the list.) The workaround procedure is below. |
|||
* The current firmware also fails with USB devices whose hardware sector size is not 512 bytes. To determine the sector size of your device, you can use fdisk on the device under Linux, and it will tell you when it first accesses the device if the sector size is not 512. The workaround is the same as for the "removable" problem, i.e. the procedure below. |
|||
* Many Multi-Function devices do not work. |
|||
* If during the upgrade you see the following message, try renaming the file '''olpc.7th''' in the '''boot''' directory of the update image to '''olpc-boot.7th'''. |
|||
<pre> |
<pre> |
||
....lots of kernel boot messages.... |
|||
Trying startup script disk:\boot\olpc-boot.7th |
|||
**** Restoring from backup **** |
|||
Can't open boot device |
|||
*** Done *** |
|||
</pre> |
</pre> |
||
{{ Translated text | |
|||
* On an ATest board the X server may fail to start up. You may need to provide [[Configuring X on an ATest board|a custom configuration]]. |
|||
'''The machine powers off. Upgrade is complete.''' |
|||
| display = block}} |
|||
| display = block }} |
|||
{{anchor|Possible Problems}} |
|||
== Posibles problemas == |
|||
* Instalación fallida. Solucion: descargue la nueva imagen de autoreinstalacion ([http://dev.laptop.org/git?p=users/cscott/autore;a=blob_plain;f=olpc-auto.zip;hb=HEAD olpc-auto.zip]) en una nueva USB y trate de nuevo. |
|||
* Autenticación fallida! Solucion: apague, reinserte la USB de autoreinstalacion, presione los botones check y X (use el botton 'O' si usted no tiene el botón 'check') y mientras los sostiene prenda. Deje la USB adentro hasta que se vea el ''prompt'' de Sugar para colocar su nombre. |
|||
* La imagen en la laptop tienen una imagen superior a la de la USB. Solucion: use [[#Downgrading|downgrading instructions below]]. |
|||
* Si el disco USB no esta particionado,las imagenes anteriores a la 552fallaran en activarse. |
|||
* Es mejor si la USB esta particionada pero: |
|||
** El tipo de la partición debe estar en concordancia con el tipo de sistema de archivos; un sistema FAT adentro de una particion marcada como ext2 no funcionara. |
|||
** Los archivos del updater deben estar en la partición marcada como "bootable", o si no hay ninguna, en la primera partición. |
|||
** Hay una situación donde el disco puede parecer tener una tabla de partición y también un sistema de archivos FAT empezando en el. Aun no somos capaces de soportar esta anómala situación |
|||
{{ Translated text | 1= |
|||
* Installation failed. Solution: download the new autoreinstallation image ([http://dev.laptop.org/git?p=users/cscott/autore;a=blob_plain;f=olpc-auto.zip;hb=HEAD olpc-auto.zip]) onto a newly formatted USB key and try again. |
|||
* Authentication failed! Solution: power off, reinsert the autoreinstallation USB key, hold down the X and the 'check' button (use the 'O' button if you don't have a check button) and while holding them turn the power on. Leave the USB key in until you get the Sugar prompt to enter your name. |
|||
* The image on the laptop has a higher build number than the image on the USB flash. Solution: use the [[#Downgrading|downgrading instructions below]]. |
|||
* If the USB disk is not partitioned, builds before 552 will fail to activate. |
|||
* It is better if the USB disk is partitioned, but: |
|||
** The partition type must agree with the filesystem type; a FAT filesystem inside a partition marked ext2 won't work. |
|||
** The updater files should be in the partition that is marked as "bootable", or if there isn't one, in the first partition. |
|||
** There is a situation where a disk can appear to both have a partition table and also have a FAT file system starting in the first sector. We are not yet able to support this anomalous situation. |
|||
* We have seen some USB disks that take several seconds to detect. In those cases, hold the Game Key for 2+ sec or let the count down expire. |
|||
* The main files (<tt>olpc.fth, osNNN.img, osNNN.crc, usbupgos.img, usbupgrd.img, and q2XXX.rom</tt>) must be in the <tt>boot/</tt> subdirectory. |
|||
* The current Open Firmware releases do not support USB keys that identify themselves as class "<tt>mass_storage/removable</tt>" – as opposed to the more common "<tt>mass_storage/scsi</tt>", which is supported. (A fix for this problem is in the release pipeline, but that doesn't help for upgrading from existing firmware.) The way to check for this is to insert your USB key, power-on the system and stop the auto-boot by typing the Esc key (upper left key) at the countdown. Then look at the list of "USB2 devices". If you see an entry like "<tt>/pci/usb@f,5/removable@1,0</tt>", your disk has the problem. (If you are running an old version of OFW that does not display the "USB2 devices" list automatically, type "<tt>show-devs /usb</tt>" to see the list.) The workaround procedure is below. |
|||
* The current firmware also fails with USB devices whose hardware sector size is not 512 bytes. To determine the sector size of your device, you can use <tt>fdisk</tt> on the device under Linux, and it will tell you when it first accesses the device if the sector size is not 512. The workaround is the same as for the "removable" problem, i.e. the procedure below. |
|||
* Many Multi-Function devices do not work. |
|||
* On an ATest board the X Server may fail to start up. You may need to provide [[Configuring X on an ATest board|a custom configuration]]. |
|||
| display = block }} |
|||
{{anchor|Reporting problems}} |
|||
=== Informando problemas === |
|||
Si usted no es capaz de actualizar su imagen por favor dejenos saber: |
|||
# Desde que versión del sistema usted esta actualizando; |
|||
# Hacia que versión esta usted haciendo la actualización; |
|||
# Que tipo de máquina tiene (b1, b2-1, b2-2, b3, b4, etc); |
|||
# Que tipo de medio de instalación esta usted usando (USB, SD, otra cosa?); |
|||
# (Si usted sabe esto) como esta formateado su medio de instalación (FAT16, FAT32, ext2/3, etc) y particionado (no particion, una partition, etc). |
|||
#* Siguió las instrucciones en el paso K ([[#Upgrading_the_machine|arriba]]) cuidadosamente para una máquina sin activar? |
|||
#* Vio usted el siguiente texto en "posibles problemas": "Si el disco USB no esta particionado, los builds antes de 552 fallaran en ser activados."? |
|||
{{ Translated text | |
|||
If you are unable to update your machine, please let us know: |
|||
# What version of the software you were upgrading from; |
|||
# What version you were upgrading to; |
|||
# What type of machine you have (b1, b2-1, b2-2, b3, b4, etc); |
|||
# What type of installation media you were using (USB flash key, SD card, something else?); |
|||
# (if you know this) how your installation media was formatted (FAT16, FAT32, ext2/3, etc) and partitioned (no partition, one partition, etc). |
|||
#* Did you follow the instructions in Step K ([[#Upgrading_the_machine|above]]) carefully for an unactivated machine? |
|||
#* Did you see the following text under "possible problems": "If the USB disk is not partitioned, builds before 552 will fail to activate."? |
|||
| display = block }} |
|||
{{anchor|Workaround for LinuxBIOS or Insyde BIOS}} |
|||
=== Solución para LinuxBIOS o Insyde BIOS === |
|||
{{ Translated text | 1= |
|||
If you are running LinuxBIOS, this process will probably not work (it has not been tested). The [http://wiki.laptop.org/index.php?title=Autoreinstallation_image&oldid=49797 old version of this procedure] may work for you. |
|||
If you are still running Insyde BIOS, you will first have to upgrade the firmware using procedures described '''[[Upgrading_to_LinuxBIOS|elsewhere]]'''. |
|||
| display = block }} |
|||
{{anchor|Workaround for old B1 systems}} |
{{anchor|Workaround for old B1 systems}} |
||
=== |
=== Solución para viejos sistemas B1 === |
||
{{ Translated text | |
|||
Si se tiene un sistema '''B1''' que nunca ha sido actualizado, es muy importante que utilice el procedimiento de reinstalación en esta página primero; no intente usar la nueva herramienta "<tt>netnandwrite</tt>". La razón es que este procedimiento corrige automáticamente un error de fabricación en los datos de identificación almacenados en la FLASH del firmware, y actualiza el firmware, ninguno de los cuales es realizado por la herramienta basada en la red. También, algunos firmwares viejos no actualizarán la máquina con el ''script'' de auto-actualización. Si el procedimiento anterior no funciona, siga los siguientes pasos: |
|||
If you have a '''B1''' system that has never been upgraded, it is very important to use this page's Autoreinstallation procedure for your first update; do not try to use the "netnandwrite" tool. 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. Also, some old firmware will not update with the auto-update script. If the standard procedure above doesn't update, instead, follow these steps: |
|||
# Inserte la llave con el auto-actualizador |
|||
# Insert the autoupdater key; |
|||
# Encienda la laptop y cuando diga "<tt>Press a key to interrupt</tt>" presiona una tecla; |
|||
# boot up the laptop and when it says "<tt>Press a key to interrupt</tt>" then press any key; |
|||
# En el cursor de 'Ok' ingrese "<tt>flash disk:\boot\q2c11.rom</tt>". La máquina se apagará cuando termine. |
|||
# at the Ok prompt type "<tt>flash disk:\boot\{{Latest Releases/firmware number}}.rom</tt>". The machine will turn off when finished. |
|||
# Encienda nuevamente la máquina y cargue el auto-actualizador normalmente; (Reflasheará la NAND con el nuevo ''build'') |
|||
# power up again and boot the autoupdater normally; (It will reflash the NAND with the new build.) |
|||
{{Translated text | |
|||
| display = block }} |
|||
If you have a '''B1''' system that has never been upgraded, it is very important to use this page's Autoreinstallation procedure for your first update; 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. Also, some old firmware will not update with the auto-update script. If the standard procedure above doesn't update, instead, follow these steps:Instead, follow these steps: |
|||
#Insert the autoupdater key; |
|||
#boot up the laptop and when it says "Press a key to interrupt" then press any key; |
|||
#at the Ok prompt type "flash disk:\boot\q2c11.rom". The machine will turn off when finished. |
|||
#power up again and boot the autoupdater normally; (It will reflash the NAND with the new build.) |
|||
| display = block}} |
|||
{{anchor|Some additional details}} |
|||
{{anchor|Workaround for "Removable" or large-sector devices}} |
|||
=== Solución para "Removibles" o dispositivos con sectores grandes === |
|||
==Algunos notas adicionales== |
|||
* Apague el sistema |
|||
* Saque el disco USB con la imagen del actualizador |
|||
* ''Bootee'' Linux desde la NAND FLASH |
|||
* Inserte el disco USB |
|||
* Copie el archivo <tt>/bzImage</tt> del actualizador del sistema de archivos que se encuentra en el disco USB a <tt>/ofw.bzi</tt> en la raíz de la NAND FLASH de la máquina OLPC, ej: |
|||
mount /dev/sda1 /mnt |
|||
cp /mnt/bzImage /ofw.bzi |
|||
* Apague Linux |
|||
* Encienda, y presione la barra espaciadora en la cuenta regresiva del [[Open Firmware/lang-es|Open Firmware]] |
|||
* En el cursor 'Ok' del [[Open Firmware/lang-es|Open Firmware]], ingrese lo siguiente, y el procedimiento de actualización debería proceder automáticamente: |
|||
ok null$ to ramdisk boot nand:\ofw.bzi |
|||
{{Translated text | |
|||
* Shut down the system |
|||
* Remove the USB disk that has the updater image |
|||
* Boot Linux from NAND FLASH |
|||
* Insert the USB disk |
|||
* Copy the file /bzImage from the updater filesystem on the USB disk file to /ofw.bzi in the root directory of the NAND FLASH on the OLPC machine, e.g. |
|||
mount /dev/sda1 /mnt |
|||
cp /mnt/bzImage /ofw.bzi |
|||
* Shutdown Linux |
|||
* Power on, and type space during the Open Firmware auto-boot countdown |
|||
* At the Open Firmware "ok" prompt, type the following, and the update procedure should then proceed automatically: |
|||
ok null$ to ramdisk boot nand:\ofw.bzi |
|||
| display = block}} |
|||
{{anchor|Downgrading}} |
{{anchor|Downgrading}} |
||
=== Volver |
=== Volver a versiones anteriores === |
||
{{ Translated text | |
|||
Si quiere cargar un ''build'' más viejo al que se encuentra en la XO, recibirá un mensaje informando que el software se encuentra actualizado. Para forzar una versión anterior, en el curosr <tt>OK</tt> ingrese: |
|||
<b>Note: DO NOT DOWNGRADE Q2Cxx firmware to Q2Bxx firmware.</b> This will destroy the manufacturing information. For details, see [[Firmware]]. |
|||
copy-nand disk:\boot\nandXXX.img |
|||
Cuando termine, saque el USB y rebootee la XO. Puede ser necesario ejecutar el comando <tt>copy-flash</tt>. |
|||
If you tried to load a build that is older than the one currently installed on your XO, then you will have gotten a message that the software is up to date. Follow this procedure to load an older version: |
|||
| display = block }} |
|||
{{anchor|Automatic downgrade}} |
|||
====Volver automáticamente==== |
|||
'''Nota:''' los firmwares recientes requieren la presencia de un archivo <tt>'''CRC'''</tt>; ej: <tt>\boot\nandXXX.crc</tt> |
|||
{{ Translated text | |
{{ Translated text | |
||
Note: I don't believe this method works (the force.os didn't work for me). I have updated the manual version. |
|||
If you are trying to load a build that is older than the one on the XO, you will get a message that the software is up to date. To force it to load an older version, at the OK prompt type: |
|||
# Download the <tt>osNNN.img and osNNN.crc</tt> files for the old build into the <tt>boot/</tt> directory of your autoreinstallation key. Make sure that the boot directory contains both the <tt>osNNN.img and osNNN.crc</tt> files to which you are downgrading, but not any newer os image. |
|||
copy-nand disk:\boot\nandXXX.img |
|||
# Create a new file in the <tt>boot</tt> subdirectory with the name '<tt>force.os</tt>'. (It does not matter what is in it; it just matters that the subdirectory exists and has that name.) This will cause the autoreinstallation script to try to install the image in <tt>boot/</tt>, regardless of whether it is older or newer than the current build on your XO. |
|||
# Follow the standard [[#Upgrading the machine|autoreinstallation procedure above]]. |
|||
| display = block }} |
|||
{{anchor|Manual downgrade}} |
|||
When it completes, remove the USB and reboot the XO. You may also need to do a copy-flash command. |
|||
====Volver manualmente==== |
|||
{{ Translated text | |
|||
'''Note:''' the recent firmware requires a '''CRC''' file to be present; e.g., \boot\nandXXX.crc |
|||
You can also downgrade by using the copy-nand command at the OK prompt. |
|||
copy-nand u:\boot\os525.img |
|||
After the copy, you need to activate your laptop: |
|||
# reboot the machine holding the 'X' and 'check' game-pad keys; (If your XO does not have a 'check' key, use the 'O' key.) |
|||
# leave the USB stick in while it writes the activation code. |
|||
(Note that automatic backup of user files will fail with this technique.) |
|||
| display = block }} |
| display = block }} |
||
{{anchor|Reinstalling the same image}} |
|||
[[Category:OS]] |
|||
====Reinstalando la misma imagen==== |
|||
{{ Translated text | |
|||
If you want to reinstall the *same* image you've currently got, you should find an earlier '''stable''' build, use the downgrade procedure, and then the standard upgrade procedure to your new image. |
|||
| display = block }} |
|||
{{anchor|Resetting the EC}} |
|||
===Reseteando al CE=== |
|||
{{ Translated text | |
|||
There is a capacitor on the reset line of the EC that controls how long the reset signal is asserted. This capacitor is the wrong value so the reset timing is invalid. This means that when you reset the EC with the power enabled there is a good chance it will not boot correctly. |
|||
If the EC does not reset correctly then the laptop will not start. Any laptop that is earlier than CTest may have this problem. |
|||
The only way to guarantee that the EC is fully reset after you upgrade the firmware is to power it off. The only way to really power off the EC is to remove the external power and the battery. Even when the power to the laptop CPU is off the EC is still powered. The capacitors in the system will hold their charge for several seconds after you remove power. You have to wait 10 seconds to make sure that all the capacitors have discharged. |
|||
The reason you do not remove the USB disk is that when the laptop powers off the upgrade procedure is not finished. You still have to boot with the USB disk so that it updates the OS image. |
|||
| display = block }} |
|||
{{anchor|Customizing Nand / Generating CRC files}} |
|||
===Personalizando la Nand / Generando archivos CRC=== |
|||
Usted puede crear una imagen [[Customizing_NAND_images|personalizada]], pero usted necesitara luego generar un archivo CRC, por favor siga estas instrucciones: |
|||
<pre> |
|||
git clone git://git.fedoraproject.org/git/pilgrim |
|||
cd pilgrim/crcimg |
|||
make |
|||
./crcimg myfile.img |
|||
</pre> |
|||
La salida esta en <tt>myfile.crc</tt> |
|||
{{ Translated text | |
|||
You can create a [[Customizing_NAND_images|custom]] build, but you will then need to generate a CRC file; please follow these instructions: |
|||
<pre> |
|||
git clone git://git.fedoraproject.org/git/pilgrim |
|||
cd pilgrim/crcimg |
|||
make |
|||
./crcimg myfile.img |
|||
</pre> |
|||
The output is in <tt>myfile.crc</tt> |
|||
| display = none }} |
|||
{{anchor|Cheat codes}} |
|||
===Cheat codes=== |
|||
Hay algunas opciones de booteo descritas [[Cheat codes|aqui]]. |
|||
{{ Translated text | |
|||
There are some boot options that are described [[Cheat codes|here]]. |
|||
| display = none }} |
|||
[[Category:Firmware]] |
[[Category:Firmware]] |
||
[[Category:Hardware]] |
[[Category:Hardware]] |
Latest revision as of 21:25, 6 February 2011
Imagen de Reinstalación Automática
- This is an on-going translation
Esta página describe como actualizar la imagen del software en su laptop. El procedimiento de actualización crea una llave o disco USB, que cuando es usado para bootear la laptop OLPC, actualiza el firmware e instala una nueva versión de la imagen del sistema operativo en la flash NAND.
Este proceso cambia regularmente, por lo tanto lea las instrucciones con atención. Algunos cambios importantes están destacados más abajo. El procedimiento básico consta de tres etapas:
La versión del software a usar depende de: la versión del hardware a actualizar y si se desea usar una versión estable o experimental de desarrollo del software. Las versiones de desarrollo tienen más funcionalidades, pero también más bugs (a veces grandes). Las Notas de Lanzamiento del Grupo de Pruebas describe las versiones de desarrollo. Las Notas de Lanzamiento del Software describe el estado de los problemas importantes con los que se pueda haber topado anteriormente. La mayoría de la gente con laptops recientes usa la versión estable. Gente con prototipos de la laptop más viejos puede ser que necesiten usar versiones más viejas. Los desarrolladores pueden querer usar versiones más nuevas.
This page describes how to update the software image on your laptop. The update procedure creates a USB flash key or disk, that when booted on an OLPC laptop, updates its firmware and installs a new version of the operating system image onto NAND flash.
This process changes regularly, so please read the instructions carefully. Some important changes are noted below. The basic procedure has three parts:
The software version you choose depends on: what version of laptop hardware you are upgrading and whether you want to use a stable version or one of the experimental development versions of the software. The development versions have more features, but also many more bugs (sometimes big ones). The Test Group Release Notes describe the development versions. The Software Release Notes describe the status of important software problems you may have encountered previously. Most people with recent laptops will use the stable version. People with older laptop prototypes may need to use older versions. Developers may wish to use newer versions.
Avisos Importantes
Si se esta actualizando el firmware, y ocurre algún problem que no se menciona en esta página, no apague la máquina; y consiga ayuda de la OLPC, preferentemente por medio de IRC o por correo electrónico de forma inmediata.
Firmware q2c24 (en las imágenes de auto-reinstalación "2007-08-17 23:10Z" y "2007-08-18 05:08Z") has sido retirado ya que puede «brickear» máquinas B2. Por favor, cerciorése de obtener la última versión de la imagen de auto-reinstalación!
La versión de la imagen de auto-reinstalación es mostrada al inicio del proceso de actualización. También se puede encontrar el string de la versión al principio del archivo de texto olpc.fth en el directorio boot.
Las versiones más recientes del firmware no soportan las placas A-Test o las máquinas pre-B1. No use este procedimiento si tiene alguna de ellas; contáctese con la OLPC para una actualización.
Firmware q2c24 (in autoreinstallation images "2007-08-17 23:10Z" and "2007-08-18 05:08Z") has been withdrawn because it may brick B2 machines. Be sure you get the latest version of the autoreinstallation image!
The autoreinstallation image version is displayed at the start of the upgrade process. You can also find the version string at the top of the olpc.fth text file in the boot directory.
Recent firmwares do not support A-test boards or pre-B1 machines. Do not use this process if you have one of these; contact OLPC for an upgrade.Comenzando con la imagen de auto-reinstalación "2007-08-15 18:23Z", el procedimiento de actualización realiza una copia de respaldo automática de los datos de usuario antes de actualizar y lo reinstancia al finalizar. La llave USB debe ser los suficientemente grande para almacenar tanto la imagen que se va a instalar, así como también todos los archivos que puedan haber sido creados en /home/olpc. ADVERTENCIA: el procedimiento de actualización anterior borraba completamente la memoria flash del sistema. Asegúrese de cual es la versión de la imagen de auto-reinstalación que está usando; se puede descargar la imagen más nueva del enlace más abajo si no se está seguro.
A partir de la imagen de auto-reinstalación "2007-08-17 16:35Z" la activación de una máquina previamente no activada después de una actualización ha sido simplificado; vea los detalles abajo.
A partir del Build 542 (firmware Q2C20e), hemos corregido un bug que se comía llaves USB formateadas como FAT32.
- Por favor, re-descargue la imagen de auto-reinstalación (olpc-auto.zip) y utilice los nuevos archivos.
- Puede ser deseable reformatear la llave USB o usar un verificador de archivos sobre ella para reparar cualquier anormalidad producida por el viejo firmware.
A partir del Build 525, hemos agregado el paso de activación al procedimiento de actualización.
- Es necesario usar el [1].
- Debe dejar el disco o llave USB en la máquina después de actualizar, mientras rebootea.
- Note que las rutinas de activación se encuentran solamente en el build, no en el firmware, con lo cual es posible (hasta próximo aviso) mantener el firmware actualizado aún corriendo el Build 406.15, lo recomendado para aquellos con máquinas B2-1 (ej: 128MB).
As of autoreinstallation image "2007-08-17 16:35Z" activating a previously-unactivated machine after the upgrade has been simplified; see details below.
As of Build 542 (firmware Q2C20e), we have fixed a bug that corrupted USB keys which were formatted FAT32.
- Please redownload the autoreinstallation image (olpc-auto.zip) and use the new files.
- You may also want to either reformat your USB key or use a file system checker on it to repair any corruption that may have occurred with the old firmware.
As of Build 525, we have added an activation step to the update process.
- You will need to use the new version of the autoreinstallation image files.
- You must leave the USB flash key or disk in the machine after the upgrade, while it reboots.
- Note that the activation code is only in the build, not in the firmware, so you can (until further notice) keep your firmware up to date while still running Build 406.15, the current recommendation for those of you with B2-1 (ie, 128MB B2) machines.
A partir del Build 406, se agregó un archivo de checksum la procedimiento de actualización.
- Se necesita tanto el archivo .img como el .crc para actualizar.
Este procedimiento funciona sobre hardware OLPC reciente:
- La mayoría de las B1 (ver soluciones más abajo); y
- Todas las laptops B2, B3, B4 y C.
Solo ha sido probado con Open Firmware:
- Si está usando Linux-as-BIOS o BIOS Insyde, vea la solución más abajo.
- You will need both the .img file and the .crc file to update.
This procedure works for recent OLPC hardware:
- Most B1 (see workaround below); and
- All B2, B3, B4 and C laptops.
It has only been tested with Open Firmware:
- If you are running Linux-as-BIOS or Insyde BIOS, see the workaround below.
¿Qué tipo de laptop es?
Es importante identificar que tipo de Xo laptop usted esta actualizando.
- A-Test board (Solo tarjeta madre)
- Máquinas B1 (identificable por un sello B1-TEST SAMPLE debajo de la batería)
- Máquinas B2-1 (identificable por unos sellos B2-TEST SAMPLE y B2-1 hasta B2-16 debajo de la batería)
- Máquinas B2-2 (identificable por un sello B2-7-ext debajo de la batería)
- Maquinas B3 (colored cover-plate; identificable por un sello B3-TEST SAMPLE debajo de la batería)
- Maquinas B4 (manija texturizada; colored cover-plate; identificables por unos sellos B4-TEST SAMPLE y B4-1 hasta B4-16 debajo de la baterial)
- Preproduccion (maquinas C) (Completamente texturizadas; identificadas por unos sellos C-TEST SAMPLE y C-4 debajo de la bateria)
(Vea las Laptop Development Schedule para una mas detallada descripción de estos sistems de desarrollo.)
It is important to identify which kind of XO laptop you are upgrading:
- A-Test board (bare motherboards)
- B1 machines (identifiable by a B1-TEST SAMPLE label under the battery)
- B2-1 machines (identifiable by B2-TEST SAMPLE and B2-1 through B2-16 labels under the battery)
- B2-2 machines (identifiable by B2-7-ext label under the battery)
- B3 machines (colored cover-plate; identifiable by a B3-TEST SAMPLE label under the battery)
- B4 machines (textured handle; colored cover-plate; identifiable by a B4-TEST SAMPLE and B4-1 through B4-16 labels under the battery)
- Preproduction (C machines) (fully textured; identifiable by a C-TEST SAMPLE and C-4 label under the battery)
(See the Laptop Development Schedule for a more detailed description of the various development systems.)
Procedimiento de Actualización del Sistema
Preparando el hardware
Si usted tiene hardware viejo como (A.B1,B2,B3).. y no sabe si esta corriendo una versión mas vieja que Q2C11 (2007-05-06), necesita comprobarlo. (Al tipear Alt-= se abrira la consola de desarrollo, donde la actual versión del firmware esta reportada.) Si usted tiene el viejo firmware, entonces solo presione el boton de prendido/apagado; usted no tiene que presionar el botón "X" de la consola de juego mientras presiona el botón de apagado. (los laptops B4, C, y M tienen un firmware mas reciente que Q2C11)
- Conecte su laptop y asegúrese que su batería este cargada. Es muy importante que el proceso de actualización (que toma casi tres minutos) no sea interrumpido.
- Consiga una USB con al menos 300Mib de espacio libre en la partición primaria.
- El sistema de archivos debe ser FAT (como un aparato formateado desde fabrica).
- No tiene que estar particionada, y no funcionara si tiene el código tipo "83" (Linux ext2 o ext3), aun si el actual sistema de archivos adentro de la partición es.
- Plug in your laptop and ensure the battery is charged. It is very important that the update process (Which takes about 3 minutes) not be interrupted.
- Get a USB flash key or disk with at least 300 MiB of free space in the primary partition.
- The filesystem should be FAT (like a factory-formatted device).
- It does not have to be partitioned, and will not work if it is partitioned such that the partition type code says "83" (Linux ext2 or ext3), even if the actual filesystem inside the partition is FAT.
Preparando la imagen de auto-actualización
Estas instrucciones son para cargar una imagen de auto-actualiacion en un disco USB. Las instrucciones para preparar una tarjeta SD son similares.
NOTA: si usted tiene python disponible y tiene alguna familiaridad con la linea de comandos, entonces la inicializacion del directorio de auto-instalación y la preparacion de la imagen de actualizacion pueden ser logradas automáticamente.
Inicializando el directorio de auto-instalación (manualmente)
- Descargue olpc-auto.zip
- Unzip olpc-auto.zip en la raiz de una llave o disco USB y al hacer esto se crea un directorio llamado boot.
- Si usted arrastra y deja caer los archivos desde un zip, usted tendra que crear el directorio boot manualmente en el flash drive.
- Habra cuatro archivos en el directorio boot inicialmente: olpc.fth, Q2E41.rom, usbupgos.img, y usbupgrd.img.
- Unzip olpc-auto.zip 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.
- There will be four files in the boot directory initially: olpc.fth, Q2E41.rom, usbupgos.img, and usbupgrd.img.
Preparando la imagen más reciente (manualmente)
- Si usted ha anteriormente creado la imagen de auto-instalación, remueva los archivos .img y .crc del directorio boot del flash o disk drive. (No olvide "Borrar la Basura.")
- Descargue la ultima imgen de SO (.img) y su archivo de checksum (.crc). Usted puede escoger entre La ultima imagen estable y La ultima imagen de desarrollo inestable.
- La imagen es llamada osNNN.img ("NNN" representa el numero de construcción de la imagen). El archivo checksum del mismo nombre tiene la extensión .crc.
- Si usted esta descargando una construccion anterior a Build 530, los archivos deberan ser renombrados en el sitio de descarga. Por ejemplo, si usted quiere descargar Build 528, usted tendria que descargar olpc-redhat-stream-development-build-528-20070720_0056-devel_jffs2.img, y renombrarla os528.img, y d ela misma forma para su archivo .crc.
- Si usted esta descargando una imagen con un numero no entero, por ejemplo Build 542.3, se necesita renombrarla sin el punto decimal,., os5423.img y os5423.crc.
- Copie los archivososNNN.img y osNNN.crc en el directorio boot del flash o disk drive.
- Uno d elos archivos en el directorio boot debe ser al ultima imagen de firmware, Q2E41.rom. Si la pagina Firmware tiene un firmware mas nuevo del que usted tiene, descarguelo en el directorio boot.
- El firmware sera llamado qXXXX.rom, donde XXXX es el numero de entrega del firmware en hexadecimales (letters A-F and numbers 0-9).
- Verifique que estos seis archivos existan en el directorio llamado boot en su llave USB o disco: Q2E41.rom; osNNN.img; osNNN.crc; usbupgos.img, usbupgrd.img, y olpc.fth, donde NNNs es el numero de imagen hacia el cual usted esta actualizando.
- No use una llave o disco USB que halla reportado errores durante la descompresión: los archivos podrían estar danados. Como una protección adicional el firmware chequea la integridad de la flash antes de hacer el reflash.
- El archivo CRC se requiere aun asi anteriores versiones del firmware no.
- Ahora usted esta listo para actualizar la maquina!
- If you have previously created an auto-installation image, remove the .img and .crc files from the boot directory of the flash or disk drive. (Don't forget to "Empty Trash.")
- Download the latest build image (.img) and its checksum file (.crc). You may choose between the the latest stable build and the the latest unstable development build.
- The image is called osNNN.img ("NNN" represents the build number). The checksum file of the same name has the .crc extension.
- If you are downloading a build earlier than Build 530, the files on the download site will need to be renamed. For instance, if you want to download Build 528, you would download olpc-redhat-stream-development-build-528-20070720_0056-devel_jffs2.img, and rename it to os528.img, and likewise for its .crc file.
- If you are downloading a build with a non-integer number, e.g., Build 542.3, you need to rename it without the decimal point, e.f., os5423.img and os5423.crc.
- Copy osNNN.img and osNNN.crc files to the boot directory of the flash or disk drive.
- One of the files in the boot directory should be the latest firmware image, Q2E41.rom. If the Firmware page lists a newer firmware release than the one you have, download it to the boot directory.
- The firmware will be named qXXXX.rom, where XXXX is the firmware release number in hexadecimal (letters A-F and numbers 0-9).
- Verify that these six files exist in the directory named boot on your USB key or disk: Q2E41.rom; osNNN.img; osNNN.crc; usbupgos.img, usbupgrd.img, and olpc.fth, where the NNNs are the build number to which you are updating.
- Do not use a flash key or disk for which there have been any errors reported during unzipping: the files may be damaged. As a further safeguard, the firmware checks the integrity of the flash image before reflashing.
- The CRC file is required even though earlier firmware did not check for the CRC file.
- You're now ready to upgrade the machine!
Preparando la imagen más reciente (automáticamente)
El script sugar-update.py automatiza los pasos listados arriba para crear un directorio de autoinstalcion y preparar una nueva imagen. Este es un script hecho en python y por ello requiere python para correr. Nota importante: Debido a un bug en MediaWiki este script tubo que ser colgado como un archivo .txt . Por favor cambie la extensión a .py después de la descarga.
- Uso
- sugar-update.py [-cdflLqs] [-b imagen] [directorio]
- Descripción
- Este script creara un directorio boot de una imagen de auto-instalacion dentro del directorio especifico. Si el directorio boot ya existe, este solo bajara los archivos necesarios (.img, .crc, and .rom). Cualquiera de estos archivos que ya estén presentes dentro de boot seran borrados antes de que la descarga comience. Si no se especifica un directorio, el actual directorio de trabajo sera usado.
- Este script también tiene soporte automático para downgrades, y anadira cualquier archivo force.os necesario en el directorio boot si la imagen presente es mas nueva que las especificada.
- Opciones
- -b Especifique un numero de imagen; por defecto la ultima imagen de desarrollo.
- -c Crea una a nueva imagen de auto-instalación, reemplazando el directorio boot existente.
- -d Downgrade forzoso de la actualización; implícito cuando una nueva imagen existe en boot
- -f Salta actualización de firmware
- -l Imprime el change log asociado.
- -L Imprime el change log para la imagen especificada y abandona
- -q Silencioso; no imprime el progreso.
- -s Descarga la ultima imagen estable; borrar la opción -b
- Examples
- Si usted esta creando un directorio boot desde el comienzo, usted simplemente querrá usar:
sugar-update.py /path/to/USBdrive/
- Anadiendo la bandera -s a lo de arriba, la ultima imagen sera preparada:
sugar-update.py -s /path/to/USBdrive/
- Para updates frecuentes es útil mostrar el change log par las nuevas imágenes:
sugar-update.py -l /path/to/USBdrive/
The sugar-update.py script automates the steps listed above for creating an auto-installation directory and preparing a new image. This is a python script, and as such requires python to run. Important Note: Due to a bug in MediaWiki this script had to be uploaded as a .txt file. Please change the extension to .py after downloading.
- Usage
- sugar-update.py [-cdflLqs] [-b build] [directory]
- Description
- This script will create an autoinstallation image boot directory within the specified directory. If the boot directory already exists, it will only download the necessary image files (.img, .crc, and .rom). Any of these files already present within this boot directory will be deleted before the download begins. If no directory is specified, the current working directory will be used.
- This script has also has automatic support for downgrades, and will add the necessary force.os file to the boot directory if the build image already present there is newer than the build specified.
- Options
- -b Specify a build number; defaults to latest development build
- -c Create a clean auto-installation image, replacing existing boot directory
- -d Force downgrade image; implicit when a newer build exists in boot
- -f Skip firmware update
- -l Print the associated change log
- -L Print the change log for the specified build and quit
- -q Quiet; do not print progress output
- -s Download the latest stable build; overrides the -b option
- Examples
- If you're creating a boot directory from scratch, you'll simply want to use:
sugar-update.py /path/to/USBdrive/
- By adding the -s flag to the above, the latest stable image will be prepared instead:
sugar-update.py -s /path/to/USBdrive/
- For frequent updates it's useful to show the change log for the new builds:
sugar-update.py -l /path/to/USBdrive/
Actualizando la máquina
- (A) Switch off the laptop;
- (B) Provide power: put in a battery; plug in the laptop;
- (C) Insert the USB key with the autoupdate image;
- (D) Switch on the laptop, and watch it carefully;
- (D.1) hold down the X game key on the bezel above the power button, while you press the power button; then release the game key when the screen lights up. (>=Q2C11)
- (D.2) if the laptop says "Firmware is already current" you can skip to Step (I) below; if instead you see "Updating firmware from q2XXX to q2YYY", then continue with Step (E);
- (E) Let the firmware update complete; the laptop will then turn off automatically;
- (F) Remove all power from the laptop. This step is very important (it resets the embedded controller). Do not remove the USB key yet.
- (F.1) unplug the laptop; take out the battery;
- (F.2) wait 30 seconds;
- (G) Put in the battery; plug the machine back in;
- (H) Switch on the laptop;
- (H.1) hold down the X game key on the bezel above the power button, while you press the power button; then release the game when the screen lights up. (>=Q2C11)
- (I) The XO will now
- boot, to backup the user files,
- reboot, to upgrade the base image,
- reboot, to restore the user files;
- then power down;
- (J) Remove the USB key;
- (K) Power on the laptop again without the USB key inserted.
Congratulations: you are running a new build image.
A sample transcript of the update procedure is shown in following section.
Notas adicionales
- If you are upgrading an unactivated machine (prior to Build 542), you may see either a message that says, "Could not activate this XO" followed by the serial number of your machine, or else a XO icon in the center of the display with a lock icon in the bottom right corner. If this happens: turn off the machine; reinsert the USB key; and hold down the 'X' and 'check' game buttons down while turning the power on. (If your XO is pre-B4 and does not have a 'check' button, use the 'O' button instead.) Release the buttons when directed. The system should boot into the new system image and perform activation using the activation lease stored on the USB key; Do not remove the USB key until you've reached the sugar "XO" screen, or the activation process will fail;
- If your USB device is a harddisk instead of flash, you may need to interrupt the Open Firmware boot sequence by pressing the Esc key (the upper left key on the keyboard, marked with an X in a circle), waiting a moment, then entering probe-usb2. You should see additional entries compared to the initial list that Open Firmware displayed. Then you can enter boot and the update should proceed. This is because many external hard drives take a long time to come ready. Recent firmware should fix this issue.
- If the machine does not power on, you need to reset the EC: (a) unplug the machine; (b) remove the battery; (c) wait 30 seconds; (d) reinsert the battery; (e) reconnect power (i.e., plug in the machine); and (f) power on the machine.This behavior is expected for machines with Li batteries so be prepared for that. Please do not remove the USB key until the activation process is completed.
- When removing all power from the laptop, any external USB peripherals should be disconnected, just in case they are faulty and supply current to the system.
- If anything else goes wrong do not turn off the machine; please get help from OLPC, preferably immediately on IRC or by email.
- After the upgrade, a backup of your user files can be found on the USB key with the name 'backup/<your XO's serial number>/complete.tgz'.
Transcripción de la Actualización del Sistema
Release the game key to continue OLPC B1, 256 MiB memory installed, S/N Unknown Open Firmware CL1 Q2C08 Q2C USB2 devices: /pci/usb@f,5/wlan@3,0 /pci/usb@f,5/scsi@1,0 /pci/usb@f,5/scsi@1,0/disk USB1 devices: Type the Esc key to interrupt automatic startup Boot device: /usb/disk:\boot\olpc.fth Arguments: Autoreinstallation version: 2007-08-15 19:27Z Existing firmware version is q2c08 Updating firmware from q2c08 to q2c25 Reading disk:\boot\{{Latest Releases/firmware number}}.rom Got firmware version: CL1 Q2C25 Q2C Checking integrity ... SPI FLASH is type 13 - Spansion, Winbond, or ST Merging existing manufacturing data Erasing 0 Writing ff000 ... Powering off
[Then you remove power, replace power, and turn it back on again...]
OLPC B4, 256 MiB memory installed, S/N Unknown OpenFirmware CL1 Q2C25 Q2C Can't assign address ranges larger than 32-bits USB2 devices: /pci/usb@f,5/wlan@3,0 /pci/usb@f,5/scsi@1,0 /pci/usb@f,5/scsi@1,0/disk USB1 devices: Type the Esc key to interrupt automatic startup Boot device: /usr/disk:\boot\olpc.fth Arguments: Autoreinstallation version: 2007-08-02 23:28Z
[Boots into Linux]
....lots of kernel boot messages.... Backing up /home/olpc, size 13487 Backing up /security, size 1 Total used KB: 13473, disk free KB: 734112 Skipping from ignore list: /home/olpc/Library tar: Removing leading '/' from member names Done! *** Done ***
[Reboots]
Autoreinstallation version: 2007-08-02 23:28Z Existing firmware version is Q2C25 Firmware is already current; skipping update Existing firmware version is Q2C25 Firmware is already current; skipping update Activation lease created successfully. Checking existing OS image on NAND FLASH Existing OS build is 353 .0 Updating OS image on NAND FLASH from build 353 .0 to build 542 .0 Check file is /pci/usb@f,5/scsi@1,0/disk@0:\boot\OS542.crc Erasing... 3ff40 Writing 6fd blocks 6fc Filling with cleanmarkers ... Done Booting into linux to restore user files.
[Linux boots up again]
....lots of kernel boot messages.... **** Restoring from backup **** *** Done ***
The machine powers off. Upgrade is complete.
Posibles problemas
- Instalación fallida. Solucion: descargue la nueva imagen de autoreinstalacion (olpc-auto.zip) en una nueva USB y trate de nuevo.
- Autenticación fallida! Solucion: apague, reinserte la USB de autoreinstalacion, presione los botones check y X (use el botton 'O' si usted no tiene el botón 'check') y mientras los sostiene prenda. Deje la USB adentro hasta que se vea el prompt de Sugar para colocar su nombre.
- La imagen en la laptop tienen una imagen superior a la de la USB. Solucion: use downgrading instructions below.
- Si el disco USB no esta particionado,las imagenes anteriores a la 552fallaran en activarse.
- Es mejor si la USB esta particionada pero:
- El tipo de la partición debe estar en concordancia con el tipo de sistema de archivos; un sistema FAT adentro de una particion marcada como ext2 no funcionara.
- Los archivos del updater deben estar en la partición marcada como "bootable", o si no hay ninguna, en la primera partición.
- Hay una situación donde el disco puede parecer tener una tabla de partición y también un sistema de archivos FAT empezando en el. Aun no somos capaces de soportar esta anómala situación
- Authentication failed! Solution: power off, reinsert the autoreinstallation USB key, hold down the X and the 'check' button (use the 'O' button if you don't have a check button) and while holding them turn the power on. Leave the USB key in until you get the Sugar prompt to enter your name.
- The image on the laptop has a higher build number than the image on the USB flash. Solution: use the downgrading instructions below.
- If the USB disk is not partitioned, builds before 552 will fail to activate.
- It is better if the USB disk is partitioned, but:
- The partition type must agree with the filesystem type; a FAT filesystem inside a partition marked ext2 won't work.
- The updater files should be in the partition that is marked as "bootable", or if there isn't one, in the first partition.
- There is a situation where a disk can appear to both have a partition table and also have a FAT file system starting in the first sector. We are not yet able to support this anomalous situation.
- We have seen some USB disks that take several seconds to detect. In those cases, hold the Game Key for 2+ sec or let the count down expire.
- The main files (olpc.fth, osNNN.img, osNNN.crc, usbupgos.img, usbupgrd.img, and q2XXX.rom) must be in the boot/ subdirectory.
- The current Open Firmware releases do not support USB keys that identify themselves as class "mass_storage/removable" – as opposed to the more common "mass_storage/scsi", which is supported. (A fix for this problem is in the release pipeline, but that doesn't help for upgrading from existing firmware.) The way to check for this is to insert your USB key, power-on the system and stop the auto-boot by typing the Esc key (upper left key) at the countdown. Then look at the list of "USB2 devices". If you see an entry like "/pci/usb@f,5/removable@1,0", your disk has the problem. (If you are running an old version of OFW that does not display the "USB2 devices" list automatically, type "show-devs /usb" to see the list.) The workaround procedure is below.
- The current firmware also fails with USB devices whose hardware sector size is not 512 bytes. To determine the sector size of your device, you can use fdisk on the device under Linux, and it will tell you when it first accesses the device if the sector size is not 512. The workaround is the same as for the "removable" problem, i.e. the procedure below.
- Many Multi-Function devices do not work.
- On an ATest board the X Server may fail to start up. You may need to provide a custom configuration.
Informando problemas
Si usted no es capaz de actualizar su imagen por favor dejenos saber:
- Desde que versión del sistema usted esta actualizando;
- Hacia que versión esta usted haciendo la actualización;
- Que tipo de máquina tiene (b1, b2-1, b2-2, b3, b4, etc);
- Que tipo de medio de instalación esta usted usando (USB, SD, otra cosa?);
- (Si usted sabe esto) como esta formateado su medio de instalación (FAT16, FAT32, ext2/3, etc) y particionado (no particion, una partition, etc).
- Siguió las instrucciones en el paso K (arriba) cuidadosamente para una máquina sin activar?
- Vio usted el siguiente texto en "posibles problemas": "Si el disco USB no esta particionado, los builds antes de 552 fallaran en ser activados."?
If you are unable to update your machine, please let us know:
- What version of the software you were upgrading from;
- What version you were upgrading to;
- What type of machine you have (b1, b2-1, b2-2, b3, b4, etc);
- What type of installation media you were using (USB flash key, SD card, something else?);
- (if you know this) how your installation media was formatted (FAT16, FAT32, ext2/3, etc) and partitioned (no partition, one partition, etc).
- Did you follow the instructions in Step K (above) carefully for an unactivated machine?
- Did you see the following text under "possible problems": "If the USB disk is not partitioned, builds before 552 will fail to activate."?
Solución para LinuxBIOS o Insyde BIOS
Solución para viejos sistemas B1
If you have a B1 system that has never been upgraded, it is very important to use this page's Autoreinstallation procedure for your first update; do not try to use the "netnandwrite" tool. 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. Also, some old firmware will not update with the auto-update script. If the standard procedure above doesn't update, instead, follow these steps:
- Insert the autoupdater key;
- boot up the laptop and when it says "Press a key to interrupt" then press any key;
- at the Ok prompt type "flash disk:\boot\Q2E41.rom". The machine will turn off when finished.
- power up again and boot the autoupdater normally; (It will reflash the NAND with the new build.)
Algunos notas adicionales
Volver a versiones anteriores
Note: DO NOT DOWNGRADE Q2Cxx firmware to Q2Bxx firmware. This will destroy the manufacturing information. For details, see Firmware.
If you tried to load a build that is older than the one currently installed on your XO, then you will have gotten a message that the software is up to date. Follow this procedure to load an older version:
Volver automáticamente
Note: I don't believe this method works (the force.os didn't work for me). I have updated the manual version.
- Download the osNNN.img and osNNN.crc files for the old build into the boot/ directory of your autoreinstallation key. Make sure that the boot directory contains both the osNNN.img and osNNN.crc files to which you are downgrading, but not any newer os image.
- Create a new file in the boot subdirectory with the name 'force.os'. (It does not matter what is in it; it just matters that the subdirectory exists and has that name.) This will cause the autoreinstallation script to try to install the image in boot/, regardless of whether it is older or newer than the current build on your XO.
- Follow the standard autoreinstallation procedure above.
Volver manualmente
You can also downgrade by using the copy-nand command at the OK prompt.
copy-nand u:\boot\os525.img
After the copy, you need to activate your laptop:
- reboot the machine holding the 'X' and 'check' game-pad keys; (If your XO does not have a 'check' key, use the 'O' key.)
- leave the USB stick in while it writes the activation code.
(Note that automatic backup of user files will fail with this technique.)
Reinstalando la misma imagen
If you want to reinstall the *same* image you've currently got, you should find an earlier stable build, use the downgrade procedure, and then the standard upgrade procedure to your new image.
Reseteando al CE
There is a capacitor on the reset line of the EC that controls how long the reset signal is asserted. This capacitor is the wrong value so the reset timing is invalid. This means that when you reset the EC with the power enabled there is a good chance it will not boot correctly.
If the EC does not reset correctly then the laptop will not start. Any laptop that is earlier than CTest may have this problem.
The only way to guarantee that the EC is fully reset after you upgrade the firmware is to power it off. The only way to really power off the EC is to remove the external power and the battery. Even when the power to the laptop CPU is off the EC is still powered. The capacitors in the system will hold their charge for several seconds after you remove power. You have to wait 10 seconds to make sure that all the capacitors have discharged.
The reason you do not remove the USB disk is that when the laptop powers off the upgrade procedure is not finished. You still have to boot with the USB disk so that it updates the OS image.
Personalizando la Nand / Generando archivos CRC
Usted puede crear una imagen personalizada, pero usted necesitara luego generar un archivo CRC, por favor siga estas instrucciones:
git clone git://git.fedoraproject.org/git/pilgrim cd pilgrim/crcimg make ./crcimg myfile.img
La salida esta en myfile.crc
Cheat codes
Hay algunas opciones de booteo descritas aqui.