OLPC Firmware q2f10

From OLPC

Revision as of 04:55, 1 May 2012 by Quozl (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  This page is monitored by the OLPC team.

Contents

OLPC Firmware Release q2f10

  • many ext2, ext3, and ext4 filesystem driver fixes, relevant if you use a USB drive or SD card with these filesystem types,
  • ASIX USB-LAN driver fixes, only relevant if you have such a device,
  • fix help to cover copy-nand and update-nand,
  • avoid trashing serial terminal emulator display when game keys are used.

Works on XO-1 systems.

Download q2f10.rom
Build date time 2012-04-01 00:44:19 (is behind, see ticket #11823)
Source revision 2960.
EC version 1.2.1
Wireless firmware version 5.110.22.p23

Changes

  • 2959 OLPC - the game key release display was hard to read if the serial terminal emulator had text from a previous boot, so clear the screen first.
  • 2955 ext2fs - test script, remove parted warning
  • 2954 ASIX USB-LAN driver - fixed error in the previous change to this driver. The problem was that only the first open would work, since the phy init code was in a function that is only called after a reset of the USB port.
  • 2953 ext2fs - interpret a zero physical block in the block list of an inode as meaning the block does not exist, OLPC trac ticket #11812
  • 2951 ext2fs - fix debugging mode and a stack comment
  • 2950 ASIX USB-LAN driver - power off the PHY when closing the device, thus eliminating excess power consumption during S3 selftest in (XO-1.75) manufacturing. The disadvantage is that subsequent opens take longer. Test case: ok select net unselect alarm-in-3 strp
  • 2949 ext2fs - avoid duplicate directory creation by mkdir, ticket #11799
  • 2948 OLPC XO-1 - change help to track 12.1.0 decision against ubifs.
  • 2947 ext2fs - fix inode reference count for directories on filesystems without DIR_NLINK, and maintain directory count in group descriptor, ticket #11787
  • 2946 OLPC trac ticket #11786 - fixed bug with file deletion introduced by svn 2817.
  • 2943 disklabel - file spec parsing, avoid treating a-h as partition letter if UFS partition support is disabled.
  • 2939 Ext2/3/4 file system journal recovery - OLPC trac ticket #11762 - Fixed list management problem that could result in missing list nodes in the journal overlay and revocation lists.
  • 2938 ext2 - fix Divide Error on x86 when accessing ext2 filesystems. OLPC ticket #11762


Which Firmware Do You Have?

The best method for finding out what firmware version you have on a laptop depends on whether the laptop is secured or not, and what operating state it is in.

Unsecured Laptop

Obtain the Ok prompt, the firmware version is displayed in the startup banner, thus:

 OLPC ..., ... memory installed, ..., S/N SHF7250024D
 OpenFirmware  q2f10 ...   EC Firmware Ver:...
               ^^^^^

You can also obtain the built date:

 ok .built

This is the date and time that this image of the firmware was built by the release engineer.

Secured Laptop

Power up the laptop with the "check" game button held down. You will be asked to Release the game keys to continue. Release the "check" game button and watch carefully. For a short time the startup banner will be displayed, like this:

 OLPC ..., ... memory installed, ..., S/N SHF7250024D
 OpenFirmware  q2f10 ...   EC Firmware Ver:...
               ^^^^^

Alternatively, if the laptop is already booted, go to the Sugar home view, click on the icon at the centre of the screen and select "My Settings" then "About my Computer." The firmware version is displayed there.

Alternatively, in the Terminal activity or a text console, type:

 cat /proc/device-tree/openprom/model

or

 cat /ofw/openprom/model

With certain older firmware versions, if the operating system will not start, and the laptop is secured, you will not be able to obtain the firmware version using the above methods, so our recommendation is to go ahead and upgrade anyway. The procedure is safe and will not do anything if you already have up-to-date firmware.


Installation

When installing new firmware, you must have a well-charged battery and the AC adapter plugged in. The firmware update code will not proceed otherwise. Possible error messages are:

error message how to fix
AC not present plug in the power cord, check the battery LED is on, then try again.
No external power plug in the power cord, check the battery LED is on, then try again,
No battery plug in the battery, check the latches, then try again, or try another battery,
Battery low allow more time for the battery to charge, then try again, or try another battery.

Unsecured Laptop

This section is for unsecured laptops. Most XO-1.5 and XO-1.75 laptops are unsecured. Most developer XO laptops are unsecured. To unsecure your laptop, follow the instructions at Activation and Developer Keys.

You may install using either:

  • a USB drive or SD card,
  • the laptop's internal drive,
  • a network.

Choose one.

Using a USB drive or SD card

  • check the battery is inserted and locked,
  • check that the power cord is in place and the battery indicator is green,
  • insert the USB drive or SD card,
  • turn on the laptop, and get to the 'ok' prompt. See Ok for more detail. You should see:
ok
  • if the downloaded file is on a USB drive, type:
 flash u:\q2f10.rom
  • if the downloaded file is on an external SD card:
 flash sd:\boot\q2f10.rom
  • wait for the laptop to reboot itself,
  • remove the USB drive or SD card.

(Expert users may remove the USB drive after the message "Got firmware" ... at this stage the file has been read and closed.)

Using the laptop internal drive

An alternate method is to download the firmware file to the laptop internal drive and then install from the internal drive.

  • start the laptop,
  • connect to a wireless or wired network,
su
cd /versions/boot/current/boot/
wget http://dev.laptop.org/pub/firmware/q2f10/q2f10.rom
  • check the battery is inserted and locked,
  • check that the power cord is in place and the battery indicator is green,
  • turn on the laptop, and get to the 'ok' prompt. See Ok for more detail. You should see:
ok
  • if the downloaded file is on an XO-1, type:
flash n:\boot\q2f10.rom
  • if the file is on the internal SD card of an XO-1.5 or XO-1.75:
flash int:\boot\q2f10.rom

Using a network

You will need a compatible USB to ethernet adapter, or an open or WEP wireless access point, connected to the internet.

  • check the battery is inserted and locked,
  • check that the power cord is in place and the battery indicator is green,
  • turn on the laptop, and get to the 'ok' prompt. See Ok for more detail. You should see:
ok
  • if using wireless, type the essid of the wireless network:
essid mynetwork
  • if using a WPA wireless access point, type the WPA key for the network:
wpa passphrase
  • type the flash command using the download link above, but change all slash characters so they are backwards, for example:
flash http:\\dev.laptop.org\pub\firmware\q2f10\q2f10.rom

Secured Laptop

Secured laptops can only use flash firmware that has been signed. All mass-production machines had the latest firmware at the time of manufacture.

Upgrading firmware describes how to upgrade to a newer signed firmware release.

See also

  • Cheat codes for information about how game buttons control startup options.
Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox