How to set up for development on linux emulation

From OLPC
Jump to navigation Jump to search
542-stopicon.png This page has a more up-to-date location: Emulation


Here, in one place, are assembled all the steps to get you to a working emulated XO. Assuming you are running on linux, and have already installed qemu and kqemu.

The following will not work on your virtual xo: sound in TamTam, camera. The first because no one has gotten around to figuring out why it isn't working[1]. The second because qemu doesn't yet support them.

downloading a build image

Go to http://xs-dev.laptop.org/cscott/olpc/streams/joyride/latest/devel_ext3/ or http://xs-dev.laptop.org/cscott/olpc/streams/ship.2/latest/devel_ext3/ and obtain the numbered -devel_ext3.img.bz2 and its md5. Sometimes builds don't work in qemu. See Emulating the XO for recommendations.

For this example I used build 602. 

md5sum -c olpc-redhat-stream-development-build-602-20070920_2254-devel_ext3.img.bz2.md5

bzcat olpc-redhat-stream-development-build-602-20070920_2254-devel_ext3.img.bz2 > xo-602a.img

The resulting file is 1 GB.

running qemu

export PORT=2221
qemu -kernel-kqemu -serial `tty` -m 256 -redir tcp:$PORT::22 -soundhw es1370 \
    -net user -net nic,model=rtl8139 -hda your-image-file

If you have a x86_64 cpu, use qemu-system-x86_64 instead of qemu.

The screen will very briefly be black, and then show the blue "GNU GRUB" screen. If it stays black, that's a qemu bug. Kill qemu and try again.

The boot messages will scroll by, and you should eventually see the normal XO first-time login. We'll save that for later.

using a non-english name

If you want to enter a name with diacritics, you need to do the following. In the window where you started qemu, you should see a login: prompt.

  1. Enter root
  2. Then:
su olpc -c"DISPLAY=:0 xmodmap -e 'keycode  77 = Multi_key'"

This sets up Num_lock as Multi_key. Unfortunately, the next time X is restarted, you will lose it. A better solution is needed.

And Num_lock isn't a great choice. MitchellNCharity 10:46, 29 September 2007 (EDT)
killall X

Killing X should restart sugar.

Change the keymapping to your local keyboard layout

To change the keyboard layout when you are using an Emulation do:

1. enter Console (Alt-Ctrl-F1)
2. login as root (just hit RETURN, no password needed)
3. type 

loadkeys xy
where xy is your keyboard layout shortcut, e.g. "de" for german layout.
(be careful: as you havn't changed your keyboard layout when you type the command, you might have to hit the key "z" to get an "y" and/or the key "q" to get an "a".)

4. edit /etc/sysconfig/keyboard (this changes the keyboard layout within SUGAR) 

vi /etc/sysconfig/keyboard
"a" starts edit-mode (insert after cursor)
change "us" to your keycode two times.
leave edit-mode (ESCAPE)
type ":wq" and hit Enter to write the changes and quit the editor
If you produced a chaos and want to quit without writing the changes, type ":q!"
You find additional information about the codes used in /etc/sysconfig/keyboard in the Manufacturing Data page.

5. edit /etc/rc.d/rc.local (this changes the keyboard layout permanently for the console) 

vi /etc/rc.d/rc.local
"a" starts edit-mode (insert after cursor)
move the cursor to the end of the file, hit RETURN to create a new line.
type "loadkeys de" (or whatever keycode you want)
leave edit-mode (ESCAPE)
type ":wq" and hit Enter to write the changes and quit the editor
If you produced a chaos and want to quit without writing the changes, type ":q!"

If you don't know the mapname/code for your keyboard layout, go to /lib/kdb/keymaps, switch to the subdirectory that covers your architecture (eg "i386" for Intel-platforms), and then enter the subdirectory which covers your keyboard type (look at the first six letters on the upper left of your keyboard to distinguish the "azerty", "qwerty" or "qwertz" layout type). In the subdirectory, you find some keymaps for your keyboard layout - find out which one fits your keyboard exactly. The keymap code is the filename without "map.gz".

Valid examples (among others) are:

"by", "cf", "cz", "dk", "emacs", "es", "et", "fi", "gr", "hu101", "il", "is-latin1", "it", "jp106", "ko", la-latin1", "lt", "nk", "nl", "no", "pc110", "pl", "pt", "ro", "ru", "se-latin1", "sk-qwerty", "sr-latin", "sv-latin", "trq", "ua", "uk", "us" (QWERTY)
 "cz-us-qwertz", "de", "croat", "fr", "fr_CH", "sg", "sk-qwertz", "slovene", "hu" (QWERTZ)
 "azerty", "be-latin1", "fr", "wangbe" (AZERTY)

If those examples don't fit your keyboard layout exactly, please have a look into the directories for yourself to look for alternatives or define your own keymap (see http://wiki.linuxquestions.org/wiki/Configuring_keyboards#The_Loadkeys_Method for instructions)

done, sort of

At this point you could just proceed to use your new XO. However, the screen resolution is wrong (1024x768). So for development, or to get a more accurate feel for how things really look, some extra steps are required.

Once you reach the main sugar screen, you should check the Neighborhood view (F1). If you can't see other people, either the we are having problems with the presence server, you are behind an unusually picky firewall, or networking on qemu is broken again in the build number you are using. (Remember that ping doesn't work inside of qemu).

preparing for ssh/scp

While this next step is not strictly required, it will enable you to use ssh and scp, which can be handy to move stuff back and forth between your host and xo.

Still as root on the xo,

1. Change the root password. 

passwd

Don't worry if it says something like "BAD PASSWORD: ", and complains about the password you picked. It will still work.

2. Change the olpc password. 

passwd olpc

Now you can use ssh and scp.

getting 1200x900

The current released version of QEMU doesn't support 1200x900, so we use a Xephyr remote X server. Each time you boot the xo, if you want 1200x900, you'll need to do these next steps again, except for the ones marked "(First time only)".

1. Still as root on the xo: 

init 3
sleep 5
ifup eth0

su olpc
grep export /usr/bin/sugar > ~/env
source ~/env

If the ifup eth0 fails with an "already running" message, that's ok. Perhaps it is no longer needed.

2. Back on the host, prepare Xephyr (First time only) 

mcookie > xephyr-cookie
export COOKIE=`cat xephyr-cookie`
rm -f xephyr-xauth; echo "add :1 . $COOKIE" | xauth -f xephyr-xauth
echo $COOKIE

3. On the xo, still as "su olpc", record the cookie: (First time only) 

echo "add 10.0.2.2:1 . " PUT-THE-COOKIE-HERE | xauth

4. Back on the host, start a Xephyr: 

Xephyr :1 -auth xephyr-xauth -reset -screen 1200x900x8 -dpi 200

You will probably want to do this in its own window, as it periodically dies and needs to be restarted.

5. On the xo, still as "su olpc", start sugar: 

DISPLAY=10.0.2.2:1 sugar

Actually, I usually ssh in from the host, and run sugar that way:

a. On the host, 

ssh -o NoHostAuthenticationForLocalhost=yes -p 2222 olpc@localhost

b. in the resulting shell, 

source ~/env
export DISPLAY=10.0.2.2:1
sugar

You may also want to run 

xmodmap -e 'keycode  77 = Multi_key'

to be able to enter diacritics with the Num_lock key. But I find doing it first thing tends to kill Xephyr. :(

You should now see the XO first-login screen in correct resolution. You can use Num_lock to enter diacritics. Congratulations. Sorry it was so much bother.

Update from Hklv, 18:00, 13 April 2008
Qemu does indeed support 1200x900, with the help of a special modeline.
Here's the relevent parts extracted from my xorg.conf : 

Section "Device"
	Identifier	"Carte vidéo générique"
	Driver		"cirrus"
	BusID		"PCI:0:2:0"
EndSection
Section "Monitor"
	Identifier	"Moniteur générique"
	Option		"DPMS"
	HorizSync	28-51
	VertRefresh	43-60
	Modeline 	"1152x864@43" 55.75 1152 1184 1392 1424 864 883 889 908
	Modeline 	"1200x900@43" 60.82 1200 1232 1456 1488 900 919 926 946
EndSection
Section "Screen"
	Identifier	"Écran générique"
	Device		"Carte vidéo générique"
	Monitor		"Moniteur générique"
	DefaultDepth	16
	SubSection "Display"
		Modes	"1200x900@43" "1152x864@43" "1024x768"
	EndSubSection
EndSection

running multiple xo's

To run multiple xo's (to play with collaboration, for instance), you can repeat the above steps. Create a xo-485b.img, and use a different PORT number (like 2222). If you are using Xephyr, start a second Xephyr, which will be 10.0.2.2:2, use that instead of ...:1 in the instructions. You should now be able to see yourself, and collaborate in Write.

simplifying ssh use

The following will save you having to periodically type your xo password, but is optional, and can just as easily be done later.

Back on the host,

1. Create an ssh key if you don't already have one. See Emulating the XO/Help_and_tips#SSH into qemu, using a key.

2. Copy it to the xo, 

scp -o NoHostAuthenticationForLocalhost=yes -P $PORT ~/.ssh/id_rsa.pub root@localhost:~/

3. On the xo, as root, spread the key around: 

mkdir ~root/.ssh
mkdir ~olpc/.ssh
cat ~root/id_rsa.pub >> ~root/.ssh/authorized_keys
cat ~root/id_rsa.pub >> ~olpc/.ssh/authorized_keys

You can now ssh and scp without retyping your password.

Questions?

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=How_to_set_up_for_development_on_linux_emulation&oldid=234767"