Hi

Have got evolution up and running but have an issue trying to find the right sync software.

evolution says it needs gnome pilot but gpilot and the gpilot conduits do not appear to be on the repositories.

Any idea where would I find them and how I would install them if they are not repository based?

Cheers

PCB

pilot-link 0.12.3 is in the current repository -- might that help you?

Thanks, yes, I know as I checked that and have it installed

My understanding is that pilot-link is the command line / background element of the sync and gpilot (and gpilotd) is the Gnome front end that evolution needs to have installed so that you can do the sync. If I try and select the Sync options on evolution I get "GNOME Pilot tools not installed".

I have tried a manual package install of downloads of gnome-pilot and the conduits from their website but they were not built for Zenwalk / Slackware and there are package dependency issues and issues around make / make install that I cannot resolve (only a n00b).

So, what I need to do is find a way of installing Zenwalk compliant packages for gnome-pilot and gnome-pilot-conduits (ideally through xnetpkg) and then be set it up, run gpilotd and sync.

There appears to be very little information out there on the interweb about gpilot and Linux and most of it is too general rather than Zenwalk specific.

Any help would be greatly appreciated.

PCB

Have found http://www.linuxpackages.net/ which seems to be a store of Slackware packages and contains gpilot etc.

have also STFW and found:

tar -zxvf file.tgz
./configure
make
make install

Which I think installs packages the hard way.

Watch this space....

try these two:
http://repository.slacky.eu/slackware-1 ... 86-1as.tgz
http://repository.slacky.eu/slackware-1 ... 86-1as.tgz

Install it by right-clicking and select Install in Thunar. Then, try to launch it. If it doesn't launch, open up terminal and type the command to see what error message you get. If it works, then you can try to build the 2.0.17 version using the included script with the package. It can be found in /usr/doc/gnome-pilot*. You will need the *SlackBuild and slack-desc files to build the new version, and of course edit the SlackBuild with the correct version number.

Hope this is not too confusing. Good luck!

Hi

Thanks for that! I learned something new there!

I loaded and it runs OK but...

whatever device I used, it would not detect my PDA.

I have a Palm Zire 31 and I tried it as USB | Time out = 2 | /dev/ttyUSB1 | 57600 and tried to send to PDA whilst hot syncing the Palm first but it refused to spot the Palm.

I looked in the device file in /user/.../gpilot/... and the device and model is enumerated there. It just does not see the Palm.

Sooo close.

Any suggestions?

PCB

after you connect it via usb, run this command as root user: dmesg |tail and post the output here. Also, please provide the output of this command: ls -l /dev/ttyUSB*

Cheers

Doesn't look encouraging...

dmesg | tail (Swapping USB from one port the other seems to be only way to get something to happen)



ls -l /dev/ttyUSB*

okay.... so, I went on to read README.usb of pilot-link and find few things that you can try.

1. In terminal, as a root user, issue the following commands:
modprobe usbserial
modprobe visor
2. Plug in your Zire 31 and again use
dmesg | tail
3. let's check if you have ttyUSB0 and/or ttyUSB1 in your /dev/directory:
ls -l /dev/ttyUSB*

Please report back.

Hmmm....



or






Did it again and got /dev/ttyUSB created.

It seems to randomly connect the device and then randomly drop, often if the device powers down or I do one of the term commands.

Basically it can't establish and maintain the link consistently.

I ass

well... at least we now know that the driver modules need to be loaded for it to be recognized. This is a good start. Now, let's put these in your /etc/rc.d/rc.local. So, as root, open up /etc/rc.d/rc.local in your favorite text editor and add:

Now, retype those two commands in Terminal so they are loaded. Moving on...

According to what you wrote, /dev/ttyUSB* on your later attempt. So, let's try this:

1. Still as root user, create /etc/udev/rules.d/pilot.rules using your favorite text editor (i.e. create pilot.rules in /etc/udev/rules.d directory)
2. Add the following lines:

3. Restart udev in Terminal:


You can logout from root and try connecting your palm again as a regular user. Hopefully, this time, it will work fine.

Good luck!

Sooooooo close...

I did this and I get


and



But the connection still times out.

I had a look on pilot link but a bit clueless where to go from here...

The dmesg looks promising. If my readings are correct, the kernel only detects it when you attempt to hotsync and disconnect when hotsyncing is done or has failed because it times out. If it timed out, that means gpilot wasn't connecting to your zire. Or, most likely gpilot wasn't looking in the right place.

So.... with my lack knowledge of gpilot, I shall attempt to walk you through this, based on what I have read. It is my understanding that gpilot has some sort of wizard to help you with hotsyncing, right?
First, launch the gpilot wizard
Second, in the Wizard Screen #2, check to make sure you have correct information

Third, before proceeding to the next wizard screen, press hotsync on your Zire
Fourth, proceed to Wizard screen #3 and then Wizard screen #4

I didn't realize how complicated it is to connect Palm via USB. I abandoned using the USB-serial adapter for my Palm Vx when I bought my laptop which comes with infrared port. I use jpilot for my syncing. It wasn't easy too in the beginning since I didn't realize that the earlier incarnations of ZW didn't have my IR port compiled as a module. Now, my Palm Vx is happily talking to my laptop via IR. Anyhoo... I hope yours will work. I am keeping my fingers crossed for you.

Let's hope it will work this time.

Nope - still refuses to detect the palm.

Everything set up hunky dory but just flat out refuses to make the connection.

I think I shall take the hint and go on to eBay and get a palm which has a serial connector...

well... if that's the route you wish to take, then go for it. While waiting for it, could you try launching gpilot from Terminal and then attempt hotsyncing. When it failed to sync, please post what the output on the Terminal screen says.