Talk:Autoreinstallation image: Difference between revisions
(Please fix main page to say this procedure is for B2's as well as A's and B1s.) |
(Remove B2 item; answer q re firmware rev; improve formatting) |
||
| Line 1: | Line 1: | ||
== Downgrading to an older OS image if desired == |
|||
(optional) if you need to downgrade to a previous version of the OS image for testing purposes, edit the ''boot/olpcboot.fth'' file and change both the test of current version and file used by ''copy-nand'', for example to force a downgrade to build 193: |
(optional) if you need to downgrade to a previous version of the OS image for testing purposes, edit the ''boot/olpcboot.fth'' file and change both the test of current version and file used by ''copy-nand'', for example to force a downgrade to build 193: |
||
* change ''os-build# d# NNN < [if]'' |
* change ''os-build# d# NNN < [if]'' |
||
* into..... ''os-build# d# 193 = not [if]'' |
|||
* change ''disk:\boot\nandNNN.img'' |
* change ''disk:\boot\nandNNN.img'' |
||
* into..... ''disk:\boot\nand193.img'' |
|||
-------- |
-------- |
||
How do we determine what the current version of the flash and image are? |
== How do we determine what the current version of the flash and image are? == |
||
The current version of your firmware is displayed on the screen at power-on (e.g. Q2B73). |
|||
== Autoreinstallation works on B2 laptops too == |
|||
I don't know where in the OS image it contains its own build ID; perhaps nowhere! |
|||
| ⚫ | |||
It works fine on B2's and is the recommended way to upgrade your firmware & software. |
|||
OLPC staff: Please fix the main page to say so! |
|||
The Autoreinstallation page doesn't say anything about B2's. It says the image is good "for all types of OLPC hardware, from A-test through B1 systems". Please correct. |
|||
== changelog and such? == |
|||
| ⚫ | |||
The name of each autoreinstallation image includes the name of the software release |
The name of each autoreinstallation image includes the name of the software release |
||
as well as the name of the firmware release. E.g. olpc303_B76.zip includes software |
as well as the name of the firmware release. E.g. olpc303_B76.zip includes software |
||
release 303 and firmware release B76. There is no good documentation for the software |
release 303 and firmware release B76. There is no good documentation for the individual software builds, but see generally the [[OLPC Software Release Notes]]. Each firmware release has a page that describes the improvements in it; see for example [[OLPC Firmware Q2B76]]. |
||
releases, but see generally the [[OLPC Software Release Notes]]. Each firmware release has a page that describes the improvements in it; see for example [[OLPC Firmware Q2B76]]. |
|||
Revision as of 21:37, 13 March 2007
Downgrading to an older OS image if desired
(optional) if you need to downgrade to a previous version of the OS image for testing purposes, edit the boot/olpcboot.fth file and change both the test of current version and file used by copy-nand, for example to force a downgrade to build 193:
- change os-build# d# NNN < [if]
- into..... os-build# d# 193 = not [if]
- change disk:\boot\nandNNN.img
- into..... disk:\boot\nand193.img
How do we determine what the current version of the flash and image are?
The current version of your firmware is displayed on the screen at power-on (e.g. Q2B73). I don't know where in the OS image it contains its own build ID; perhaps nowhere!
How are we to know the pros and cons of each version?
The name of each autoreinstallation image includes the name of the software release as well as the name of the firmware release. E.g. olpc303_B76.zip includes software release 303 and firmware release B76. There is no good documentation for the individual software builds, but see generally the OLPC Software Release Notes. Each firmware release has a page that describes the improvements in it; see for example OLPC Firmware Q2B76.