|
Hi All I'm trying to get a laptop running JDS (which is SuSE 8.1), with an updated kernel (2.4.30) to connect to a Treo 600. The distro comes with pilot-link .11.7 and gnome-pilot 2.0.10. With this config, I could get pilot-xfer working fine (using dev/pilot, which is a symlink to /dev/ttyUSB1), but when I tried to run the gpilot config applet it always gave a segmentation error when it tried launch gpilotd. So, I uninstalled the shipping stuff and installed pilot-link .11.8 and gnome-pilot-2.0.12 (following the great instructions at http://howto.pilot-link.org/). After some giggling around (installing various packages I was missing), it now all seems correctly configured and installed. pilot-xfer once again works (using .11.8) and gpilotd tells me it's built for the right version. Now I run the config applet, it tells me "your running this for the first time", I set /dev/pilot (which works fine for pilot-xfer) or /dev/ttyUSB1 just in case), 9600, USB (or serial) and 100 sec timout. I then get to the "have you synced with this pilot before (no)" and then OK - press hotsync now. At this point before, I got the segmentation errors. Now, I get .... nothing at all. It just sits there and eventually the phone times out. So, after a bit of goggling and a bit of hacking of the config file to manually put in the port, name etc entries (some of which I got from the treo using an install-user), I then tried ./gpilotd --oaf-activate-iid=OAFIID:GNOME_Pilot_Daemon in a terminal and get the following .... gpilotd-Message: gnome-pilot 2.0.12 starting... gpilotd-Message: compiled for pilot-link version 0.11.8 gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] gpilotd-Message: Activating CORBA server IOR:01f3ffbf1b00000049444c3a474e4f4d452f50696c6f742f4461656d6f6e3a312e300028030000000054424f5c0000000101026905000000554e4958000000000d0000006e696b6b692d6c6170746f70000001052d0000002f746d702f6f726269742d6e733131323537322f6c696e632d6461342d302d3731383433626365353234646400444c3a00000000caaedfba580000000101026d2d0000002f746d702f6f726269742d6e733131323537322f6c696e632d6461342d302d37313834336263653532346464007400001c0000000000000040fa8c601c0568a88c932928282828286770696c6f74640001000000480000000138343302000000050000001c0000000000000040fa8c601c0568a88c932928282828286770696c6f74640001000000140000000137322f01000105000000000901010000000000 gpilotd-Message: bonobo_activation_active_server_register = 0 gpilotd-Message: Watching Cradle (/dev/ttyUSB1) gpilotd-Message: Found 4766, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0502, 0736 gpilotd-Message: Using net TRUE gpilotd-Message: Found 091e, 0004 gpilotd-Message: Using net TRUE gpilotd-Message: Found 082d, 0100 gpilotd-Message: Using net FALSE gpilotd-Message: Found 082d, 0200 gpilotd-Message: Using net TRUE gpilotd-Message: Found 082d, 0300 gpilotd-Message: Using net FALSE gpilotd-Message: Found 0830, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0002 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0003 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0020 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0031 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0040 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0050 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0060 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0070 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0080 gpilotd-Message: Using net TRUE gpilotd-Message: Found 04e8, 8001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 04e8, 6601 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0038 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0066 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0095 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 009a gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00c9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00da gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00e9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0144 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0169 gpilotd-Message: Using net TRUE gpilotd-Message: Found 12ef, 0100 gpilotd-Message: Using net TRUE and it'll just sit there for ever - until I press cntrl-c when it'll break nice and cleanly. Has anyone got any ideas asto how I can fix this. 2.0.12 says it supports the treo and the config is in the devices.xml and its vendor/product id seems to be listed (and, is this the behaviour I would see if it didn't recognise the device?). . In general, how can I get more logging about what's going on - at the moment the h/w side seems to be fine (all the pilot-link utils seems to work fine), but gnome-pilot just doesn't do anything and I have no error messages or debug to go on - so I'm kinda stuck - there's nothing in log/messages other than connecting and then disconnecting the Visor device. any help much appreciated pete S |