On September 1, 2003 10:05 am, Scott Banwart wrote: > On Monday 01 September 2003 05:30 am, gabriel wrote: > > On September 1, 2003 03:15 am, Steven Elling wrote: > > > Whare are the permission on the device file and the usb file system if > > > you're using usb? It's been a while since I got mine working but I > > > think the problem was with the device file or usb. > > > > (~) $ ls -l /dev/usb/tts/ > > total 0 > > crwxrwxrwx 1 root root 188, 0 Dec 31 1969 0 > > crwxrwxrwx 1 root root 188, 1 Dec 31 1969 1 > > > > "/dev/pilot" and "/dev/palm" both link to "/dev/usb/tts/1" > > > > so given the above permissions, i don't see how that can be the issue... > > What device file is kpilot pointing to? If it's pointing to one of the > above symlinks, try pointing to /dev/usb/tts/1 directly. For some reason, > I've never been able to get kpilot to work with a symlinked USB device.
heh, already ahead of you, i tried that too and got the same result. i did however run kpilotDaemon from the command linek, and since i compiled it with debugging on, i found the following in the console: kpilotdaemon: open: Binding to path /dev/usb/tts/1 kpilotdaemon: open: Tried /dev/usb/tts/1 and got No such file or directory kpilotdaemon: open: Binding to path /dev/usb/tts/1 kpilotdaemon: open: Tried /dev/usb/tts/1 and got No such file or directory kpilotdaemon: open: Binding to path /dev/usb/tts/1 kpilotdaemon: open: Tried /dev/usb/tts/1 and got No such file or directory kpilotdaemon: open: Binding to path /dev/usb/tts/1 kpilotdaemon: open: Tried /dev/usb/tts/1 and got No such file or directory kpilotdaemon: open: Binding to path /dev/usb/tts/1 kpilotdaemon: open: Tried /dev/usb/tts/1 and got No such file or directory kpilotdaemon: open: Binding to path /dev/usb/tts/1 kpilotDaemon: statusString (pilotDaemon.cc:470) kpilotDaemon: syncTypeString (pilotDaemon.cc:602) kpilotDaemon: statusString (kpilotlink.cc:684) kpilotDaemon: acceptDevice (kpilotlink.cc:434) kpilotDaemon: statusString (kpilotlink.cc:684) kpilotdaemon: acceptDevice: Current status KPilotDeviceLink=DeviceOpen and master 10 kpilotDaemon: WARNING: pi_accept: Connection timed out kpilotDaemon: logError (pilotDaemon.cc:728) kpilotDaemon: statusString (pilotDaemon.cc:470) kpilotDaemon: syncTypeString (pilotDaemon.cc:602) kpilotDaemon: statusString (kpilotlink.cc:684) kpilotDaemon: close (kpilotlink.cc:139) kpilotdaemon: close: Closing sockets -1 and 10 ...course i have no idea what all that means -- giving it up would mean... it would mean that all along they'd been wrong. it would mean that they'd never known how to rule the world. it would mean... relinquishing their pretensions to godhood. - Daniel Quinn's "ishmael" -- [EMAIL PROTECTED] mailing list
