Release notes/8.1.1: Difference between revisions
m (New page: {{subst::OLPC Update.1 Software Release Notes}}) |
mNo edit summary |
||
Line 6: | Line 6: | ||
<center>''for other discussion, see [[Update.1]]''</center> |
<center>''for other discussion, see [[Update.1]]''</center> |
||
== What's new in the |
== What's new in the candidate-708 (8.1.0) release? == |
||
# fix bugs |
# fix bugs |
||
Line 15: | Line 15: | ||
Please also refer to the [http://dev.laptop.org/milestone/Update.1 milestone] and the [http://dev.laptop.org/roadmap official roadmap] for schedule dates and features for each release. |
Please also refer to the [http://dev.laptop.org/milestone/Update.1 milestone] and the [http://dev.laptop.org/roadmap official roadmap] for schedule dates and features for each release. |
||
Pending successful completion of the [[OLPC_SW-ECO_5_Checklist|Release Checklist]], we will release an official 8.1.1 build. Our current release candidate is [http://download.laptop.org/xo-1/os/candidate/708/jffs2/ candidate-708]. |
|||
Line 27: | Line 27: | ||
= What's the recommended way to upgrade? = |
= What's the recommended way to upgrade? = |
||
# Download the [[G1G1 Activity Pack]] (from [http://wiki.laptop.org/images/6/62/G1G1_Activity_Pack_1.zip here]) and unzip it in the base (root) directory of a USB flash drive. You should see two directories (boot and bundles, and a file called customization-2) in the base directory. Commands such as "extract here" in ubuntu / windows will sometimes create a directory with the same name as the zip file, placing the unzipped files within it. If this happens, you will have to move the files to the base directory in order for your XO to see them on boot. (Note that the "boot" directory will contain two zip files, actos.zip and runos.zip. This is normal; these files |
# Download the [[G1G1 Activity Pack]] (from [http://wiki.laptop.org/images/6/62/G1G1_Activity_Pack_1.zip here]) and unzip it in the base (root) directory of a USB flash drive. You should see two directories (boot and bundles, and a file called customization-2) in the base directory. Commands such as "extract here" in ubuntu / windows will sometimes create a directory with the same name as the zip file, placing the unzipped files within it. If this happens, you will have to move the files to the base directory in order for your XO to see them on boot. (Note that the "boot" directory will contain two zip files, actos.zip and runos.zip. This is normal; these files SHOULD NOT be unzipped). |
||
# Plug the XO into an electrical outlet and connect it to the internet. |
# Plug the XO into an electrical outlet and connect it to the internet. |
||
# Run [[Olpc-update]] to the new build. ( terminal -> <tt>su -l</tt> (lowercase L, not 1) -> <tt>olpc-update 703</tt> ) This may take half an hour or more, depending on your internet connection. |
# Run [[Olpc-update]] to the new build. ( terminal -> <tt>su -l</tt> (lowercase L, not 1) -> <tt>olpc-update -f 703</tt> ) This may take half an hour or more, depending on your internet connection. |
||
# Insert the USB flash drive and reboot the XO. It will display text on a black screen as the activities are installed, after which it will power off. |
# Insert the USB flash drive and reboot the XO. It will display text on a black screen as the activities are installed, after which it will power off. |
||
# Remove the USB flash drive. Connect the XO to AC power, so that it will be able to proceed if it determines that a firmware update is needed. |
# Remove the USB flash drive. Connect the XO to AC power, so that it will be able to proceed if it determines that a firmware update is needed. Then power on your XO as per usual. |
||
If you are upgrading from build 69''X'', the build is already separated from the activities in those builds. |
If you are upgrading from build 69''X'', the build is already separated from the activities in those builds. |
||
So you can run <tt>olpc-update 703</tt> and your activities will not be affected. |
So you can run <tt>olpc-update -f 703</tt> and your activities will not be affected. |
||
= Finding Activities = |
= Finding Activities = |
||
OLPC hosts many [[Activities]]. These activities can be installed in en masse onto |
OLPC hosts many [[Activities]]. These activities can be installed in en masse onto 8.1.1 with either: |
||
* a [[Customization key|customization key]] and an [[Activity pack|activity pack]] or |
* a [[Customization key|customization key]] and an [[Activity pack|activity pack]] or |
||
Line 57: | Line 57: | ||
= Improvements from build |
= Improvements from build 703 = |
||
See [[OLPC_SW- |
See [[OLPC_SW-ECO_5]] for a more precise list of the changes, indexed by ticket, that lead from official-703 to [http://download.laptop.org/xo-1/os/candidate/708/jffs2/ candidate-708]. To summarize, we added: |
||
* More accurate Amharic and Kreyól keyboard maps for Ethiopia and Haiti. |
|||
* Open Firmware version Q2D14 which will delay firmware updates until power is available (easing mass laptop updates). |
|||
* First-draft support for the resistive touchpad (''implementation details may change in future releases!''). |
|||
* Better Spanish localization of the library and of the X and console keymaps. |
|||
* Updated wireless drivers and firmware |
|||
* The ability to customize installed activities, boot screens, and activity order via USB key. |
|||
* Support for USB ethernet adapters. |
|||
* [[Rainbow]] prevents faulty activities from damaging many parts of the system configuration. |
|||
* Several UI and library bug fixes. |
|||
* [[OHM power management]] software can be manually enabled to provide better battery life in solo-use situations. |
|||
* The XO announces its build identifier under the "About this XO" palette entry available from the central XO Icon on the Home View. |
|||
* Miscellaneous stability improvements including a new libabiword that fixes a Write sharing crasher. |
|||
Line 78: | Line 76: | ||
== Customization Issues == |
== Customization Issues == |
||
* Customization key won't install if the activities or library directories had already been created as root |
* Customization key won't install if the activities or library directories had already been created as root |
||
== Localization Issues == |
|||
* {{Ticket|6777}} Library bundles cannot use non-ascii characters in their file names |
|||
* {{Ticket|6973}} Haiti keyboard doesn't match keyboard mappings. |
|||
* {{Ticket|6945}} 'Switch [language] group' key non-functional on Amharic keyboards |
|||
Line 89: | Line 81: | ||
* {{Ticket|6773}} TamTamJam: Recorded microphone slots don't playback. ?need to test |
* {{Ticket|6773}} TamTamJam: Recorded microphone slots don't playback. ?need to test |
||
* Couldn't add feeds to news reader because clicking "+"/dropdown on the feeds tab didn't do anything. ?need to test |
* Couldn't add feeds to news reader because clicking "+"/dropdown on the feeds tab didn't do anything. ?need to test |
||
* Read will not share a |
* Read will not reliably share a PDF document. |
||
* {{Ticket|6729}} Read doesn't save the PDFs it opens (when sharing) |
* {{Ticket|6729}} Read doesn't save the PDFs it opens (when sharing) |
||
* {{Ticket|4539}} Sharing in Etoys only works if the laptops are in the same network (on same mesh channel, or connected to same access point). ?need to test |
* {{Ticket|4539}} Sharing in Etoys only works if the laptops are in the same network (on same mesh channel, or connected to same access point). ?need to test |
||
Line 97: | Line 89: | ||
== Touchpad Issues == |
== Touchpad Issues == |
||
* The Nepal pilot reported "jumpy touchpad" problems in dusty conditions. In response, we have [http://lists.laptop.org/pipermail/devel/2008-May/013580.html surveyed known touchpad issues] and have examined potential software work-arounds |
* The Nepal pilot reported "jumpy touchpad" problems in dusty conditions. In response, we have [http://lists.laptop.org/pipermail/devel/2008-May/013580.html surveyed known touchpad issues] and have examined potential software work-arounds . See also [http://www.olpcnews.com/forum/index.php?topic=1996.msg19390]. |
||
= Network Related Issues = |
= Network Related Issues = |
||
*[[USB ethernet adaptors]] will not work at all at first. {{Ticket|6917}} The workaround is to upgrade the olpc-utils package manually to [http://koji.fedoraproject.org/packages/olpc-utils/0.71/1.olpc2/i386/olpc-utils-0.71-1.olpc2.i386.rpm 0.71] or higher, or to enter this command in the [[Terminal]] after becoming [[root]]: <tt>echo 'SUBSYSTEM=="net", KERNEL=="msh*", OPTIONS="last_rule"' > /etc/udev/rules.d/10-olpc-netif.rules</tt> |
|||
== Access Points == |
== Access Points == |
||
* When a number of laptops try to connect to the school server (either over a WiFi AP or a mesh) at one time, random "failure to associate" will occur and the laptops will join a simple mesh instead {{Ticket|4153}} ({{Ticket|5963}} is dup). This is indicated by the network indicator in the home view (it will say "Connected to a simple mesh" instead of "Connected to a school mesh portal" or "Connected to <school_essid>" when hovered over. Simply click on the school Wifi AP or one of the mesh circles in the laptop's neighborhood view to restart the association process. |
* When a number of laptops try to connect to the school server (either over a WiFi AP or a mesh) at one time, random "failure to associate" will occur and the laptops will join a simple mesh instead {{Ticket|4153}} ({{Ticket|5963}} is dup). This is indicated by the network indicator in the home view (it will say "Connected to a simple mesh" instead of "Connected to a school mesh portal" or "Connected to <school_essid>" when hovered over. Simply click on the school Wifi AP or one of the mesh circles in the laptop's neighborhood view to restart the association process. |
Revision as of 00:37, 10 June 2008
What's new in the candidate-708 (8.1.0) release?
- fix bugs
- laptops now suspend when closed & resume when opened, for better battery life
- each activity runs isolated from the others, for better security
- Sugar activities are now released separately, or in "Activity Packs", rather than as part of the operating system release.
Please also refer to the milestone and the official roadmap for schedule dates and features for each release.
Pending successful completion of the Release Checklist, we will release an official 8.1.1 build. Our current release candidate is candidate-708.
Breaking Changes from official-656
Activities must be installed separately.
Motivation: OLPC cannot presently afford to maintain more than one stable build. Therefore, we have decided to provide a "blank slate" which must be customized with activities and content bundles at installation time.
What's the recommended way to upgrade?
- Download the G1G1 Activity Pack (from here) and unzip it in the base (root) directory of a USB flash drive. You should see two directories (boot and bundles, and a file called customization-2) in the base directory. Commands such as "extract here" in ubuntu / windows will sometimes create a directory with the same name as the zip file, placing the unzipped files within it. If this happens, you will have to move the files to the base directory in order for your XO to see them on boot. (Note that the "boot" directory will contain two zip files, actos.zip and runos.zip. This is normal; these files SHOULD NOT be unzipped).
- Plug the XO into an electrical outlet and connect it to the internet.
- Run Olpc-update to the new build. ( terminal -> su -l (lowercase L, not 1) -> olpc-update -f 703 ) This may take half an hour or more, depending on your internet connection.
- Insert the USB flash drive and reboot the XO. It will display text on a black screen as the activities are installed, after which it will power off.
- Remove the USB flash drive. Connect the XO to AC power, so that it will be able to proceed if it determines that a firmware update is needed. Then power on your XO as per usual.
If you are upgrading from build 69X, the build is already separated from the activities in those builds. So you can run olpc-update -f 703 and your activities will not be affected.
Finding Activities
OLPC hosts many Activities. These activities can be installed in en masse onto 8.1.1 with either:
- a customization key and an activity pack or
- with Bert's script
Some commonly installed activity packs include the:
(The Nepal activity pack contains some additional customizations made by OLE Nepal for their pilot).
TO INSTALL AN ACTIVITY PACK:
Improvements from build 703
See OLPC_SW-ECO_5 for a more precise list of the changes, indexed by ticket, that lead from official-703 to candidate-708. To summarize, we added:
- More accurate Amharic and Kreyól keyboard maps for Ethiopia and Haiti.
- First-draft support for the resistive touchpad (implementation details may change in future releases!).
- Updated wireless drivers and firmware
- Support for USB ethernet adapters.
- Several UI and library bug fixes.
Notable Current Bugs
- #6532 SD Card Corruption: partition table gets corrupted on ext3-formatted SD cards on suspend/resume
- #7158 Upgrade from 656 to 703 leaves su unusable when you fallback to 656
- The contents of a USB key didn't show in the journal. So couldn't install activity bundles from the USB through the journal.
Customization Issues
- Customization key won't install if the activities or library directories had already been created as root
Activity Issues
- #6773 TamTamJam: Recorded microphone slots don't playback. ?need to test
- Couldn't add feeds to news reader because clicking "+"/dropdown on the feeds tab didn't do anything. ?need to test
- Read will not reliably share a PDF document.
- #6729 Read doesn't save the PDFs it opens (when sharing)
- #4539 Sharing in Etoys only works if the laptops are in the same network (on same mesh channel, or connected to same access point). ?need to test
(Almost) full activity testing results for Update.1 RC-2, all results are from build 702
Touchpad Issues
- The Nepal pilot reported "jumpy touchpad" problems in dusty conditions. In response, we have surveyed known touchpad issues and have examined potential software work-arounds . See also [1].
Network Related Issues
Access Points
- When a number of laptops try to connect to the school server (either over a WiFi AP or a mesh) at one time, random "failure to associate" will occur and the laptops will join a simple mesh instead #4153 (#5963 is dup). This is indicated by the network indicator in the home view (it will say "Connected to a simple mesh" instead of "Connected to a school mesh portal" or "Connected to <school_essid>" when hovered over. Simply click on the school Wifi AP or one of the mesh circles in the laptop's neighborhood view to restart the association process.
- Sometimes when a number of laptops try to connect to the school server at one time, random laptops may be unable to connect to schoolserver presence service (ejabber) #5908. This is indicated by a greatly reduced number of XO icons in the neighborhood view (compared to a laptop which is connected to the presence service). Simply click on the school Wifi AP or one of the mesh circles in the laptop's neighborhood view to restart the association process (in extreme cases, restart Sugar (CTL + ALT + ERASE) or reboot the laptop).
- Association with WEP/WPA encryption works. However this must be tested for a wider range of access points.
- Sometimes obsolete APs show in the neighborhood view, or an AP is shown more than once. #6909
School Server/ Jabber Server
- To register to a school server and connect to the school jabber server you must
- Ensure that you are connected to the appropriate Network by hovering over the Network circle in the Home View.
- Hover over the XO icon in the main view and select
Register
. - Hover again over the XO icon and verify that the
Register
entry has disappeared. - Restart sugar by pressing
Ctrl+Alt+Erase
. - Confirm you have connected to the jabber server by typing
olpc-netstatus
from the terminal.
- When registering with a school server, you MUST associate with the correct network before clicking
Register
for the first time. Otherwise, you wont be able to register until you restart Sugar (Ctrl+Alt+Erase
) #6857. - You should restart sugar (
Ctrl+Alt+Erase
) to resolve the following bugs- You can't register with the school server. #6857
- You can't connect to the default jabber server alhtough you have registered.#6881
- You connected to the jabber server, and gabble is running, but no XOs, or few XOs are seen in the neighborhood view. #6883,#6884
- You are running both gabble and salut. #6881,#6886
Simple Mesh / Salut
- When XOs leave the mesh, the neighborhood view will notice with a delay between 10-30min.#6282,#5501
- However, when XOs enter the mesh or start an activity it is shown instantly.
- You can refresh the data of the neighborhood view by reconnecting to the mesh.
- Suspend/Resume will not work with salut.
- Chat crash fixed?
UI
- Sometimes in the neighborhood view, when connected to an Access Point a mesh circle continues to blink. This will also show up as two network circles in the Home view. This shows false information, but also causes no harm, so it may be ignored. #5459
- When an XO joins a shared activity its icon should disappear and reappear next to the activity. It happens that the XO icon will just disappear. Its collaboration will work properly, and if it leaves the activity it will show again as normal. You can see the correct number of XOs clustered around the activity by restarting sugar(
Ctrl+Alt+Erase
). However the bug will continue from this point on when new XOs join the same or other activities. #5904