The following sections provide information for resolving frequently encountered problems.
Scratchbox
Issue
My prompt in Scratchbox says something like "I have no name!@svnamelnx:"
Resolution
Did you copy your host ~/.bashrc into your Scratchbox environment, but forget to guard (or fix) the prompt-setting code?
You may be experiencing a known issue: "dot in name": the Linux adduser command refuses periods in the username by default. The LDAP authentication scheme overrides this to provide transparency with Windows Active Directory. You can force the creation of a local account in the build environment that matches your system account by using the -force-badname option with adduser.
Simulator
Troubleshooting the Simulator Boot Process
Look over the issues in the section "Other Simulator Issues"; if none of them seem applicable, the following may help:
- You might need to stop the
uml-utilitiesprocess. Issue the following command from the host shell (not from within scratchbox):sudo /etc/init.d/uml-utilities stop
- The file
/dev/net/tunon the host may not have the correct permission. Look at it and make sure it's set to 666. Make sure you see the following:crw-rw-rw- 1 root root 10, 200 2006-05-22 04:49 /dev/net/tun
sudo chmod 666 /dev/net/tun
- If using KUbuntu, edit your
kdmrcfile (as root; usesudo vi /etc/kde3/kdm/kdmrc) and changeServerArgsLocal=-nolisten tcptoServerArgsLocal="": - If you are told to install the
uml-utilitiespackage, be sure to do this from a host shell, not from within Scratchbox. - Try resetting the simulator by issuing the following command:
alp-simulator --factory-reset
- If all else fails, restart your machine and then try starting the Simulator again.
Using VNC
The nested xserver is set to run from DISPLAY=:0 (console only). If you VNC to your machine, you should make sure it matches your DISPLAY. You need to modify the /etc/profile and /etc/init.d/rc.sysinit files in your Simulator target tree (that is, /scratchbox/users/$USER/targets/alp-simulator). Change every occurrence of :0 to the number of your display. Some references to the display are part of certain command lines in the scripts, so search for :0 throughout the files. Run echo $DISPLAY from outside of Scratchbox to see what number your display is (not including the number following the decimal point). For example, if DISPLAY is set to :1.0, change every occurrence of :0 to :1.
Other Simulator Issues
Issue
I tried alp-sim but got some error about GDM.
Resolution
Follow the instructions provided by the alp-sim script to fix this. Generally, this involves editing your gdm.conf file (as root; use sudo vi /etc/gdm/gdm.conf) and change DisallowTCP=true to DisallowTCP=false:
Issue
UML won't start up on my system.
Resolution
Verify that you are running Ubuntu 6.10 or 7.10 and that you followed all of the instructions in the "Installation and Configuration" chapter. If you need to uninstall a previous version of the SDK, remember to remove the /scratchbox directory and the .alp-dev directory before you reinstall a new version.
Issue
I don't seem to have any network connectivity from the Simulator beyond the Linux box it's running on.
Resolution
If you want to run Internet applications (like a web browser, or anything else that might need to resolve a DNS name into an IP address), you'll need to edit the /etc/resolv.conf file on your Simulator target. The easiest solution is to just copy the /etc/resolv.conf file from your host (Linux machine) directly into your Scratchbox target. To do this, type the following into a host shell:
sudo cp /etc/resolv.conf /scratchbox/users/$USER/targets/alp-simulator/etc
Issue
I need to kill the Simulator from my host. What should I do?
Resolution
Normally, closing the alp-sim window will shut down the simulator. If the terminal window remains open, however, you can type halt after logging in as root. If for some reason you need to kill a running Simulator from your host, you can usually do this (without having to reboot) by typing killall alp-linux.
If the desktop GUI is unresponsive for some reason, you can try logging in to your host via SSH from another machine and then typing killall alp-linux.
Building and Debugging Applications
Issue
Whenever I try to build one of the samples, either with make (from the command line) or by using Eclipse, I see an error of the form:
scratchbox -d /home/test/workspace-scratchbox/worldclock make all
make: *** No rule to make target `all'. Stop.
Resolution
Errors of this type often arise because the file make_common was not copied along with the sample sources; the ACCESS Linux Platform makefiles used in the sample applications rely heavily upon make_common. Because it contains common makefile instructions, copies are not included along with each sample's code; instead, a single copy is located one level above: in /opt/alp-dev/sdk/samples/. Copy make_common to the appropriate location (either one level above the directory containing your application's source code or in the project directory itself) and ensure that the makefile includes the correct location of make_common.
