OLPC

From Sugar Labs
Revision as of 15:32, 21 July 2012 by Satellit (talk | contribs) (→‎Alternate versions of Sugar: Sugar Network - XO-1 and XO-1.5)
Jump to navigation Jump to search
  Information on this page is specific to the OLPC XO laptop.

OLPC (One Laptop per Child) is a non-profit association developing the low-cost laptop—the "XO Laptop". The Sugar project was originally started in support of the XO laptop, which has a number of features specific to Sugar, most notably, a number of keys dedicated to the interface.

Using Sugar on an XO

This section tries to capture a number of OLPC-specific hints to using Sugar.

Keyboard shortcuts

The XO laptop has dedicated keys that can be used in navigating the Sugar interface. Please see the keyboard shortcuts page in the OLPC wiki.

USB Ethernet adapters

See the USB Ethernet Adapters page for a list of options.

Click

To “click”, press once on the left-hand touchpad button—the button with the × symbol at the front of the touchpad.

Getting connected

Please refer to the Wi-Fi Connectivity page in the OLPC wiki for details about how to connect an OLPC XO laptop to the Internet.

Alternate versions of Sugar

1 Hexokinase Factory / Sugar 0.94.1
XO-1 and XO-1.5
How to install on XO-1 and XO-1.5

Release Testing

See OLPC/12.1.0

Random Notes

XO-1

XO-1.5

XO-1.75

XO-3

Wireless Loss

  • Loss of wireless AP on XO-1.5 due to aggressive suspend and resume
  • Go to Control Panel/Power and uncheck powersaving

Mesh Networking Deprecated

XO-1.5's do not have Mesh networking support, so they use 802.11 Ad-hoc
networks.  XO-1's default to Mesh networks at the moment for compatibility,
because that is what they historically have done.
Once an XO-1.5 starts an Ad-hoc network, the XO-1's will spot that network
within a minute or two, and use the same Mayan numeral as the XO-1.5 to
indicate its presence.  If all the XOs leave an Ad-hoc network it
disappears; but Network Manager/Sugar cache its presence for a while in case
a scan accidentally missed a network.
When an XO-1 sees an Ad-hoc networks they are all filled in as "occupied",
because an XO-1 does not show the unfilled variants to allow an XO-1 to
start them.
This behavior has been around since OLPC build 10.1.3 (860) & Sugar 0.90,
and is described at Features/Ad_hoc_Networking
I believe XO-1's can be adjusted to default to Ad-hoc as well if desired

Activities

xo-au

Accessories

Repair

Upgrades

Subpage index