Talk:Autoreinstallation image

From OLPC
Revision as of 16:12, 2 April 2007 by 160.218.189.60 (talk) (How does this interoperate with bitfrost?)
Jump to: navigation, search

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.

How does this interoperate with bitfrost?

Will a reinstalled laptop need to be re-activated?

My disk is not detected because it takes too long to spin up

If firmware does not see it, but probe-usb from ok prompt does.. just do probe-usb followed by boot.