35
edits
Changes
Jump to navigation
Jump to search
Line 131:
Line 131: + − TBD + + + + + + + + + + + + + + + + + + + + + + + + + +
→Failing To Connect
===Failing To Connect===
===Failing To Connect===
After checking the board is turned on, if connection fails on clicking "Connect" then try it a few more times. For reasons unknown at the moment it may take two or three attempts before connection succeeds. Still no luck? Turn off, turn on, try again. Still no luck? Now we need to identify the problem. The board needs to be recognised by the OS and a Linux device file mounted, the device file must be assigned a group in common with the user named "olpc" and the group must have read-write permissions on the device file. Here is how to check using the Terminal activity:
1. Shortly after plugging the device/ turning it on enter the following command:
[olpc@xo-73-22-91 ~]$ dmesg | tail -n 8
[22543.590117] usb 3-1: new full speed USB device using uhci_hcd and address 4
[22543.755225] usb 3-1: New USB device found, idVendor=0461, idProduct=0033
[22543.755238] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[22543.755249] usb 3-1: Product: SERIAL DEMO
[22543.755257] usb 3-1: Manufacturer: CCS
[22543.755708] usb 3-1: configuration #1 chosen from 1 choice
[22543.757578] cdc_acm 3-1:1.0: This device cannot do calls on its own. It is not a modem.
[22543.757797] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
2. The output above shows the GoGo-Board is assigned the "ttyACM0" device. The permissions of that device can be determined with the following:
[olpc@xo-73-22-91 ~]$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 2011-01-17 18:26 /dev/ttyACM0
3. Above we can see the device is a member of the "dialout" group, which has rw permissions. Now to check what groups user "olpc" is a member of:
[olpc@xo-73-22-91 ~]$ groups
olpc wheel uucp dialout video audio
...yep, user "olpc" is a member of "dialout". So in the above example all is well. If your results differ from these then please post a bug at SugarLabs Bug website [4]. Note that some older XO/OS's use different device files and/or groups and it may need root access to fix any problem.
==Upcoming Changes==
==Upcoming Changes==