Differences between revisions 1 and 2
Revision 1 as of 2005-11-20 07:33:47
Size: 3953
Editor: ?CharlesStevenson
Comment: Added the old TWiki FAQ (converted with some perl sed... hopefully it's not bad)
Revision 2 as of 2005-11-22 21:46:38
Size: 3957
Editor: PeMac
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Assuming that `target-` is your target tarball: Assuming that `target-` is your target ["tarball"]:

Frequently Asked Questions

Q: Sweet, there is a new build, how do I update my NFS system

Assuming that target- is your target ["tarball"]:

$ mkdir ~/targets/target.; cd ~/targets/target.
$ tar xvfj /home/services/tftpboot/v2.0.1.11/target-
$ cp ~/targets/my.old.nfs.build/root/ppcstream/stream.cfg root/ppcstream/stream.cfg

The stream.cfg is a file that contains the contents of the Flash configuration (to avoid writing to flash for debugging). Add the following line in /etc/exports

/users/firmware/`whoami`/targets/target. *(rw,no_root_squash,no_all_squash,async)

and edit the dhcp.conf file in /etc/ so that your board (MAC address) points to this new directory:

group {
  host svc.01{
         hardware ethernet 00:04:a5:04:05:53;
         option root-path "/users/firmware/mleeman/targets/target.";
# More boards

Finally, restart the appropriate servers

# /etc/init.d/nfs-kernel-server restart
# /etc/init.d/dchp restart

The command which are executed during the build can be found in the file debug_command.log located in the build directory. Check this file for more information. The system is explained in more explained in ["NFSSystem"].

Q: Why does it not work?

Information saying "it does not work" is no information at all. In any case, you should try to be as precise in your information as you can. In order to have a timely fix for your problem, the following When reporting bugs, the following needs to be checked

  • See if the PPC is dead. This can be done by performing a ping

$ ping
c:\windows> ping -n 1000
  • If you do not get a reply, this does not mean that your board is dead, the board might just be configured with the wrong network settings. Check this by attaching a cross cable and connecting to the default (hardwired) address. Note that you can also have a configuration fetched from the Flash: check the history of the board.

  • If the ping is fine, check if you can login to the board. When you are a using a CRAMFS system, the one should be related to the other, but this is not the case when using an NFS system.
  • You might also have a problem that you initially get replies from the system and after a while none. This is useful since this might indicate that the network is reconfigured or the crash occurs in some application. Try to estimate as close as possible the time before crash.

$ telnet
  • If you keep on getting ping replies, try to log in.
    • If you fail to log in, and you have an NFS system: this indicates that your kernel is running but your telnetd has not been started. Check your configuration (and that of inetd).

    • You can log in, but your connection gets stuck or reset: this indicates that the board got started; the network was configured but some application crashed the system or had the system rebooted. Have a look at the kernel buffer or use a NFSSystem and load the modules one by one and start the applications one by one.
  • When the error is not that grave, but only the functionality is impaired; you should provide the final log entries of the applications. These are found in the Administration Login section of the web interface, or in the logfiles under


Finally, submit this information to a Bug Tracking System if available.

Q: Where do I get the kernel source for platform X


You just make and configure as you used to, just add the correct CROSS_COMPILATION prefix if you are not developing on the same architecutre as your target:

$ make ARCH=ppc CROSS_COMPILE=powerpc-linux-uclibc- oldconfig
$ make ARCH=ppc CROSS_COMPILE=powerpc-linux-uclibc- dep
$ make ARCH=ppc CROSS_COMPILE=powerpc-linux-uclibc-