Test Config Notes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (+cat) |
||
Line 5: | Line 5: | ||
* The activity names are those which show up when you scroll over them in the home view. |
* The activity names are those which show up when you scroll over them in the home view. |
||
* The sugar_emulator_debug will enable the logs for presence and telepathy. |
* The sugar_emulator_debug will enable the logs for presence and telepathy. |
||
* Each activity that you want to see a log of must be added to the .sugar.debug file. |
* Each activity that you want to see a log of must be added to the <tt>.sugar.debug</tt> file. |
||
* Reboot the computer after changing the files. |
* Reboot the computer after changing the files. |
||
Line 11: | Line 11: | ||
===Reformat a bad USB drive=== |
===Reformat a bad USB drive=== |
||
MAC: |
MAC: |
||
#Insert the USB into your mac |
# Insert the USB into your mac |
||
#Open Disk Utility (which you can find in the applications/utilities directory) |
# Open Disk Utility (which you can find in the applications/utilities directory) |
||
#Click on '967.5 MB USB 2.0...', the usb disk on the left. |
# Click on '967.5 MB USB 2.0...', the usb disk on the left. |
||
#Click on the Partition tab |
# Click on the Partition tab |
||
#Click on Partition to reformat the USB (this erases everything on the stick) |
# Click on Partition to reformat the USB (this erases everything on the stick) |
||
===Customizing a NAND image=== |
===Customizing a NAND image=== |
||
See [[Customizing NAND images]] |
|||
[[Customizing_NAND_images|Customize NAND]] |
|||
===Modify the Mesh Discovery Sequence=== |
===Modify the Mesh Discovery Sequence=== |
||
You can put the following values in /etc/NetworkManager/mesh-start |
You can put the following values in <tt>/etc/NetworkManager/mesh-start</tt> |
||
* school-mpp |
* school-mpp |
||
Line 30: | Line 30: | ||
* local |
* local |
||
These will control where the |
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. |
||
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 |
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. |
||
to a specific step in this cycle by putting the string above into |
|||
mesh-start. |
|||
/* Steps: |
/* Steps: |
||
Line 62: | Line 58: | ||
===Language Testing=== |
===Language Testing=== |
||
* [[ |
* [[OLPC Keyboard layouts]] |
||
[[Category:HowTo]] |
|||
[[Category:Developers]] |
Revision as of 19:25, 7 September 2007
Turn on All logs
- The activity names are those which show up when you scroll over them in the home view.
- The sugar_emulator_debug will enable the logs for presence and telepathy.
- Each activity that you want to see a log of must be added to the .sugar.debug file.
- Reboot the computer after changing the files.
Reformat a bad USB drive
MAC:
- Insert the USB into your mac
- Open Disk Utility (which you can find in the applications/utilities directory)
- Click on '967.5 MB USB 2.0...', the usb disk on the left.
- Click on the Partition tab
- Click on Partition to reformat the USB (this erases everything on the stick)
Customizing a NAND image
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 */