Difference between revisions of "Talk:OLPC"

From Sugar Labs
Jump to navigation Jump to search
m (→‎XO-1 & XO-1.5 links & notes: Fix: Loss of wireless AP on XO-1.5)
Line 44: Line 44:
 
:http://build.laptop.org/11.2.0/os9/xo-1.5/
 
:http://build.laptop.org/11.2.0/os9/xo-1.5/
 
:OLPC News: http://www.olpcnews.com/forum/index.php
 
:OLPC News: http://www.olpcnews.com/forum/index.php
 +
:http://wiki.laptop.org/go/Speech_Server
 
===Activities===
 
===Activities===
 
:http://wiki.laptop.org/go/Activities/G1G1/
 
:http://wiki.laptop.org/go/Activities/G1G1/

Revision as of 11:54, 25 January 2012

XO-1 & XO-1.5 links & notes

  • XO-1 HomePage:
OLPC Wiki: http://wiki.laptop.org/go/The_OLPC_Wiki
OLPC Release Notes: http://wiki.laptop.org/go/Release_notes
dx3 downloads:http://download.sugarlabs.org/dextrose/testing/dx3/xo1/?C=M;O=D
Activity Tracker: http://dev.laptop.org/
Collections OLPC: http://wiki.laptop.org/go/Collections
Testing Talk:Community/Distributions/Fedora
Mesh Networking: (Re: [Testing] [OLPC New Zealand] os873 on XO-1.5 and os873 on XO-1 -07/15/2011) testing@lists.laptop.org 07/18/2011
  • Loss of wireless AP on XO-1.5
Go to Control Panel/Power and uncheck [ ] powersaving
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
  • Sugar 0.92.1 has a bug with jabber.sugarlabs.org
 The large number of avitars being sent cause long delays on starting activities. dbus timeouts. 
 If CP/Network does not start here, it is not possible to delete the jabber entry. 
 It is possible to do this with the old terminal OLPC command: 
Commands:
 sugar-control-panel -l ( Lists commands )
 sugar-control-panel -s jabber ""
        suggested by Cerlyn  ("" is null string which forces salut )
To check setting change:
 sugar-control-panel -g jabber (which lists current setting to see if it is changed. Shows blank line)
  • MY Settings/About Me/ click on different color avitar; restart; gdm log in and jabber will not be a problem
  • after using the Ad-hoc connection; disconnecting and connecting to the Access Point; you must restart sugar to get jabber to reconnect.
http://wiki.laptop.org/go/OS_images
http://wiki.laptop.org/go/Release_notes/10.1.3
Dextrose
http://build.laptop.org/11.2.0/os9/xo-1.5/
OLPC News: http://www.olpcnews.com/forum/index.php
http://wiki.laptop.org/go/Speech_Server

Activities

http://wiki.laptop.org/go/Activities/G1G1/
Config for 11.3.0 XO-1.5: http://dev.laptop.org/git/projects/olpc-os-builder/tree/examples/f14-xo1.5.ini showing activities included

IRC_session_where_a_12_year_old_is_helped_in_upgrading_her_XO-1_to_the_latest_software

update XO-1 IRC session transcript

xo-au

https://dev.laptop.org.au/projects/xo-au/wiki/Virtual_machine
https://dev.laptop.org.au/projects/xo-au-usb/wiki
Tonyforster: User:Tonyforster

Accessories

Solar Panel to charge X0-1:http://www.ilovemyxo.com/product/xo-10wattsolarpanel.html

Repair

http://wiki.laptop.org/go/Repair
http://wiki.laptop.org/go/Disassembly

XO-1.75

  • ARM
http://wiki.laptop.org/go/XO-1.75

XO-3

http://en.wikipedia.org/wiki/OLPC_XO-3