Operating system image installation methods: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (categorize)
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 9: Line 9:
! references
! references
|-
|-
| XO-1.75 signed
| block signed
| .zd and fs.zip
| .zd and fs.zip
| hold down the four game pad buttons
| hold down the four game pad buttons and then turn on the laptop
| [[Release notes]]
|
|-
|-
| XO-1.75 unsigned
| block unsigned
| .zd alone
| .zd alone
| check if security is disabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disable_the_security_system|disable-security]], interrupt boot, then use the ''fs-update'' command
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disabling_the_security_system|disable-security]], [[Ok|interrupt boot]], then use the ''fs-update'' command
| [[Release notes]]
|
|-
|-
| XO-1.5 signed
| nand signed
| .zd and fs.zip
| hold down the four game pad buttons
| [[F11_for_1.5#Internal_microSD|Fedora 11 for XO-1.5 install to internal microSD]] [[Release_notes/10.1.1]] [[Nandblaster_for_XO-1.5]]
|-
| XO-1.5 unsigned
| .zd alone
| check if security is disabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disable_the_security_system|disable-security]], interrupt boot, then use the ''fs-update'' command
| [[F11_for_1.5]] [[Release_notes/10.1.2]] [[Nandblaster_for_XO-1.5]]
|-
| XO-1 signed
| .img and fs.zip
| .img and fs.zip
| hold down the four game pad buttons
| hold down the four game pad buttons and then turn on the laptop
| [[Clean-install_procedure#Official_releases_and_candidate_builds|Clean Install Procedure]] [[Nandblaster_for_XO-1]]
| [[Release notes]] [[Clean-install_procedure#Official_releases_and_candidate_builds|Clean Install Procedure]] [[Nandblaster_for_XO-1]]
|-
|-
| XO-1 unsigned
| nand unsigned
| .img and .crc
| .img and .crc
| obtain [[Developer_key|developer key]], [[Developer_key#Disable_the_security_system|disable-security]], interrupt boot, then use the ''copy-nand'' command
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disabling_the_security_system|disable-security]], [[Ok|interrupt boot]], then use the ''copy-nand'' command
| [[Clean-install_procedure#Development_builds|Clean Install Procedure]] [[Release_notes/10.1.2]] [[Nandblaster_for_XO-1]]
| [[Release notes]] [[Clean-install_procedure#Development_builds|Clean Install Procedure]] [[Nandblaster_for_XO-1]]
|-
|-
| XO-1 partitioned<br>
| nand partitioned<br>
| .dat and .img
| .dat and .img
| obtain [[Developer_key|developer key]], [[Developer_key#Disable_the_security_system|disable-security]], interrupt boot, then use the ''update-nand'' command
| check if security is enabled, if so obtain [[Developer_key|developer key]] and [[Developer_key#Disabling_the_security_system|disable-security]], [[Ok|interrupt boot]], then use the ''update-nand'' command
| Used by [[DebXO]]. Used by [[UBIFS_initial_experiments|UBIFS experiments]].
| Used by [[DebXO]]. Used by [[UBIFS_initial_experiments|UBIFS experiments]]. See also [[OFW_NAND_FLASH_Updater|Technical description]].
[[OFW_NAND_FLASH_Updater|Technical description]].
|}
|}


The signed installation methods are the same for XO-1.75, XO-1.5 and XO-1. This was by design, since we do not wish to increase the training burden for the deployment teams.
The signed installation methods are the same for XO-4, XO-1.75, XO-1.5 and XO-1. This was by design, since we do not wish to increase the training burden for the deployment teams.

A deployment will typically [[OSBuilder#Signing_preparation|sign their builds]] and [[Firmware_security#Adding_Deployment_Keys_to_Manufacturing_Data|inject deployment keys]] at manufacture or on site.

⚫
The unsigned installation methods depend on the type of internal storage. XO-1 has raw NAND Flash. XO-1.5, XO-1.75 and XO-4 have microSD or eMMC managed Flash.


See also [[Firmware/Storage]].
⚫
The unsigned installation methods depend on the type of internal storage. XO-1 has raw NAND Flash. XO-1.5 and XO-1.75 have microSD or eMMC managed Flash.

Latest revision as of 02:14, 1 January 2014


We use a few different methods to install operating system images.

installation method what files are required how to install references
block signed .zd and fs.zip hold down the four game pad buttons and then turn on the laptop Release notes
block unsigned .zd alone check if security is enabled, if so obtain developer key and disable-security, interrupt boot, then use the fs-update command Release notes
nand signed .img and fs.zip hold down the four game pad buttons and then turn on the laptop Release notes Clean Install Procedure Nandblaster_for_XO-1
nand unsigned .img and .crc check if security is enabled, if so obtain developer key and disable-security, interrupt boot, then use the copy-nand command Release notes Clean Install Procedure Nandblaster_for_XO-1
nand partitioned
 .dat and .img check if security is enabled, if so obtain developer key and disable-security, interrupt boot, then use the update-nand command Used by DebXO. Used by UBIFS experiments. See also Technical description.

The signed installation methods are the same for XO-4, XO-1.75, XO-1.5 and XO-1. This was by design, since we do not wish to increase the training burden for the deployment teams.

A deployment will typically sign their builds and inject deployment keys at manufacture or on site.

The unsigned installation methods depend on the type of internal storage. XO-1 has raw NAND Flash. XO-1.5, XO-1.75 and XO-4 have microSD or eMMC managed Flash.

See also Firmware/Storage.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Operating_system_image_installation_methods&oldid=294431"