Talk:Autoreinstallation image

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). Each OS image contains its own build ID in /boot/olpc_build (e.g. 385). You can also see the OS image version in the Developer Console (from a graphical screen, press Alt-= .) It's supposed to show the firmware revision too, but on my machine it says "None".

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. The OLPC Software Release Notes and the Test Group Release Notes contain some information about the various images available. Each firmware release has a page that describes the improvements in it linked from the Firmware page. You can see an index of all firmware-related pages, including all the release notes, at Category:Firmware.

How does this interoperate with bitfrost? Will a reinstalled laptop need to be re-activated?

At the moment, activation is in the code base but cryptography is not available. The autoreinstallation procedure thus generates an unsigned activation lease which will work with the current development builds. When cryptography and real signatures are turned on in the activation procedure, the autoreinstallation scripts will be updated to preserve any existing activation leases.

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

If firmware does not see it, but probe-usb from the ok prompt does... just do probe-usb followed by boot. In later firmware revs, more time has been allocated between power-up and accessing USB drives. Please report a bug in TRAC if your USB drive doesn't work cleanly with the latest firmware version.

How to force an autoreinstallation

Rename the nandNNN.img and nandNNN.crc files to (say) nand9999.img and nand9999.crc. See the notes on in the article regarding the perils of using this trick for firmware images.

The transcript of an update doesn't include any output about activation

Doesn't the autoinstall script at least tell you when it writes a lease on your USB or SD card? In the transcript it doesn't.

the README file in olpc-auto.zip is obsolete

It doesn't match the latest instructions, e.g. it references old firmware as the latest.

The "latest stable build" link leads to 406, not to 542.

There's no option (in the text of the Autoreinstallation image page) to download the "new stable" release for 256MB machines; the "stable" is 406 and the "latest" is the bleeding edge. I had to find 542 via the link in the little box on the home page of the wiki.