De bureaubladomgeving K

Hoofdstuk 3. FAQ

3.1. KPilot Crashes...

This section answers questions of the most common sort: KPilot refuses to run at all.

3.1.1. KPilot says "Can't connect to pilot"

3.1.1. KPilot says "Can't connect to pilot"

This can have various causes. Check that:

  • The pilot device (usually /dev/pilot) exists and points to the serial port the Pilot is actually connected to.

    To link the Pilot device to the correct serial port, you can either fill in /dev/ttySn in the Pilot Device field in the setup dialog or (preferably) link /dev/pilot to /dev/ttySn with the following command (as root): ln -s /dev/ttySn /dev/pilot Here /dev/ttySn is the name of the serial port; replace n with the correct number (usually 0 or 1).

  • Check that you have permission to read and write to the serial port. The permissions for the serial port should be such that you can write to it. This is most easily done by running the following (as root): chmod 666 /dev/ttySn

  • Try starting the daemon by hand before starting KPilot.

  • (For Mandrake 7 systems) Check the system security level: settings higher than 3 prevent some forms of inter-process communication which are necessary for KPilot to operate correctly.

    (Mandrake security information courtesy of Jay Summett) To set your MSEC (Mandrake SECurity) settings to not block the KPilot socket (to localhost connect) you can login as root and type /etc/security/msec/init.sh 3 Which will set your msec level to 3 (regular security). For more information about the various security levels, etc, see: the Mandrake reference guide.