Test Config Notes

Turn on All logs

• Edit the /home/olpc/.xinitrc file to uncomment the line source .sugar.debug
• Edit the /home/olpc/.sugar.debug to include export SUGAR_LOGGER_LEVEL=debug
• If you want to add debugging only for some acitivities, you can find the name of the activity when you scroll over them in the home view. Use the Enable logging instructions.
• The activity names are those which show up when you scroll over them in the home view.
• Reboot the computer after changing the files.

Turn on MPP Capability

As of build 570, automatic MPP (mesh portal) is turned off. If you want to turn it on, log in as root (either from the VT with Ctl+Alt+F1 or 'su -' from the Dev Console in sugar), and do:

 /sbin/chkconfig --level 345 NetworkManagerDispatcher on
 /sbin/service NetworkManagerDispatcher start

Next time you reboot (or the next time you click on an AP) the mesh portal will come back on.

Testing of Different Connection Configurations

1. Under a Tree
2. Connected to AP
3. One Laptop acting as MPP
4. Same Mesh Same Server

Reformat a bad USB drive

MAC:

1. Insert the USB into your mac
2. Open Disk Utility (which you can find in the applications/utilities directory)
3. Click on '967.5 MB USB 2.0...', the usb disk on the left.
4. Click on the Partition tab
5. Click on Partition to reformat the USB (this erases everything on the stick)

Customizing a NAND image

See Customizing NAND images

Modify the Mesh Discovery Sequence

You can put the following values in /etc/NetworkManager/mesh-start

• school-mpp
• infra
• xo-mpp
• local

These will control where the mesh device starts. Since the mesh device is the first device that gets picked at startup, this affects the immediate connection search of the laptop.

Remember, the current automatic connection cycle is this. You can jump to a specific step in this cycle by putting the string above into mesh-start.

/* Steps:
 *
 * 1. For each channel in [1, 6, 11]:
 *    a. try DHCP
 *    b. if DHCP times out, try next channel
 *    c. if DHCP response includes a non-link-local IP address,
 *      then CONNECTED/DONE
 *
 * 2. Try last successful AP connection
 *    a. if success then CONNECTED/DONE
 *
 * 3. For each channel in [1, 6, 11]
 *    a. try DHCP
 *    b. if DHCP times out, try next channel
 *    c. if DHCP response includes a link-local IP address,
 *      then acquire autoip address and apply DHCP settings (except for
 *      IP address), CONNECTED/DONE
 *
 * 4. Jump to channel 1
 *    a. acquire autoip address, CONNECTED/DONE
 */

XO Files

list of .xo files (usually most updated ones).

GCompris — gcompris xo files

See also: {{OBX xobundle}} which will categorize all references to bundles (the category name needs to be determined)

Check Which Activity Version you have

• Open the /usr/share/activities/{activity_name}.activity/activity.info file
• Check the activity_version setting

Internationalization Testing

• OLPC Keyboard layouts
• Checking the Layout configuration

Fixing XOs with bogus clocks

Some pre-test machines (C4s at the moment) don't have valid manufacturing data. This isn't too much of a problem, but they also have clocks which are set to crazy values, which is. To fix this, boot with the X key pressed and press Esc when prompted to get an OFW prompt. At the 'ok' prompt type:

clock-node @ iselect  decimal   00 40 16   14 09 2007  set-time

The numbers here are the time and date: second, minute, hour, day, month, year. You can substitute the current time and date if you like, but the machine will activate correctly as long as it has a somewhat-sane date. You can use the date above, for example.

Turning on Activity Containerization

To play with activity containerization, you should:

1. rainbow-daemon
2. touch /etc/olpc-security
3. restart sugar (e.g. type Ctrl-Alt-Erase)
4. try out various activities; perhaps examine the output of rainbow-daemon
5. rm /etc/olpc-security
6. restart sugar

Note: it is important that rainbow-daemon be running when Sugar restarts. Therefore, rainbow-daemon should be started either on a virtual terminal (i.e. after htting Ctrl-Alt-F1 [F1 is the mesh-key]) or over SSH.

Please direct questions and comments to me: --Michael Stone 13:02, 17 September 2007 (EDT)

Mesh Forwarding Table

Information on the Mesh Forwarding Table are available here.