XSCE on XO-1.5

This recipe for installing XSCE on a XO-1.5 is patterned after the instructions for installing on XO-1.75. (I’ll make insertions, as I discover problems and/or fixes). This version of the XO/XS will use the wifi adapter as the internet gateway, and will get an ip address from your network environment.)

  1. Start with the released version of XO software at http://wiki.laptop.org/go/Release_notes/12.1.0#XO-1.5
  2. turn off automatic power management in control panel, and make Terminal Activity a favorite (hidden down in list view of activities)
  3. Connect the XO-1.5 to the internet.  If you fail to connect to the repo, check that the date on the XO is set correctly. If it is not correct, use the date command: “date mmddhhmmyyyy” m=month, d=day, h=hour, m=minute, y=year.
  4. As root, cd to /etc/yum.repos.d/, and
  5.  “wget http://georgejhunt.com/olpc/files/myrepo/i386/xs.repo
  6. Issue command “yum -y install xs-config-xo”
  7. Then as root, (“su”), type “bootstrap-xo” into a Terminal window.
  8. reboot
  9. Then, again as root, issue the command “xs-setup” . This “xs-setup” command generates a long list of “yum” install requests, similar to the normal adding of function that you would do if you loaded a minimal “network” install cd from Fedora, and then added additional functions one at a time. (I noted that during the install of ejabberd, it appeared to be stalled. Later I learned that ejabberd take a very long time to start up the first time).
  10. 40 minutes later, my XS was ready for a reboot (internet speed is determinant).
  11. Problems on the 1.5 appeared. Httpd didn’t start until i manually created /var/log/httpd folder. After connecting ethernet dongle, needed to rerun xs-setup-network. After that, discovered using “route -n” that the gateway was connected to the lan adapter. After a reboot, neither the lan or wan had ip addresses. Disabled /usr/lib/udev/rules.d/60-net.rules. Ran xs-setup-network again because NetworkManager uses mac address and the last time it was run, the adapters had the wrong name. Deleted all entries in resolv.conf except the lan adapter (172.18.96.1). Achieved normal network setup.
  12. Use “ifconfig” to determine the ip address of the XS, and test out the web server by pointing a browser to “http://<ip address or localhost>/top/en” to get to the client interface. The Browse activity of the XO (localhost/top/en) or your normal web client should work equally well.
  13. To access the XS via ssh, verify the ability to ping,  and connect using a new unprivliged username “ssh admin@<wan ip>” (password=12admin). Early on, I usually come in via the WAN adapter (sshd is attached to all interfaces–the second interface should be availlable 172.18.96.1 if you have attached a USB ethernet dongle).
  14. If you have a ethernet dongle, you will need to run “xs-setup-network”, and reboot.
  15. In order to get proper gateway function, I needed to replace the contents of /etc/resolv.conf with “nameserver localhost”, and restart the name service using the command “systemctl restart named.service”.
  16. If you have a ethernet dongle, and an access point, you should be able to connect them to the new XS, and then connect another XO  to the XS via wifi.
  17. The acid test of the XS gateway function is to ping “yahoo.com” from a connected client.

I didn’t have the ethernet dongle plugged in during the installation. I found that I needed to do a “sudo xs-setup-network”, and a reboot, before everything worked.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s