Troubleshooting

Many of the problems encountered when running an x-kernel turn out to be configuration problems. The following are three of the most common symptoms, and some things you might try if these symptoms occur.

• The x-kernel aborts with the message

  could not open protocol table file prottbl
  ...

  Make sure you edited the last line of graph.comp correctly in step 5, and that /usr/xkernel/etc/prottbl.std exists and is readable.

• The x-kernel hangs (doesn't abort) and repeatedly prints out the message

  ARP: Could not get my ip address for interface eth (still trying)

  Make sure you edited the two rom files correctly in step 6, and that you started the server on machine A and the client on machine B in step 10.

• Both the client and server initialize, but then seem to hang. You will know that the server has successfully initialized when it prints the message

  tcp timing test
  I am the server

  and that the client has successfully initialized when it prints the message

  tcp timing test
  I am the client
  Sending (1) ...
  msg lengh: 1

  Make sure you edited the two rom files correctly in step 6.