Well, their pretty good with basic installation stuff, and sometimes they just tell you. If you bought pro it came with some free installation support. I don't know if palm is covered though. Also, have you tried pilot-link? Apparently that's supposted to work pretty well.

-Peter

I see I'm not the only one with issues here...

I had SuSE 9.1 and all was well with my Palm Tungsten E. About a month ago, I purchases and did a clean install of 9.2. I have not been able to get my Palm to sync. Not a really big deal, as I do most synching at work on my XP machine.

Anyway, here's what I'm seeing. (I have KDE running.)

When I plug the palm in and turn it on, I get an icon in the MyComputer folder which looks like a Palm. Okay, that tells me there's something connecting.

By the way, my USB printer (Epson CX3200), USB camera (Fujitsu F510), memory sticks, and USB mouse (Kidz Mouse) all connect just fine when I plug and unplug them. In fact, when I press, Sync on the Palm, I notice a definate slowdown in the system as it does stuff.

HOWEVER:

In Kpilot, I've tried /dev/palm, /dev/ttyUSB0, 1, 2, 3, 4, - all to no avail. I'm pretty sure USB0 is the printer. I have never unplugged that one.

Here's my log:

Version: KPilot 4.4.5 (Augsburg)
Version: pilot-link 0.11.8
Version: KDE 3.3.0
Version: Qt 3.3.3

HotSync Log

06:09:23 Daemon status is `Waiting for sync'
06:09:40 Pilot device /dev/ttyUSB0 does not exist. Assuming the device uses DevFS.
06:09:41 Trying to open device /dev/ttyUSB0...
06:09:41 Device link ready.
06:09:54 Pilot device /dev/ttyUSB3 is not read-write.
06:09:55 Trying to open device /dev/ttyUSB3...
06:09:55 Device link ready.
06:10:14 Pilot device /dev/ttyUSB2 is not read-write.
06:10:15 Trying to open device /dev/ttyUSB2...
06:10:15 Device link ready.
06:10:23 Pilot device /dev/ttyUSB2 is not read-write.
06:10:24 Trying to open device /dev/ttyUSB2...
06:10:24 Device link ready.
06:10:37 Pilot device /dev/ttyUSB4 does not exist. Assuming the device uses DevFS.
06:10:38 Trying to open device /dev/ttyUSB4...
06:10:38 Device link ready.
06:11:26 Pilot device /dev/ttyUSB1 does not exist. Assuming the device uses DevFS.
06:11:27 Trying to open device /dev/ttyUSB1...
06:11:27 Device link ready.

I have no clue what this all means...

Try plugging the palm in the same port as the printer. Last time I checked SuSE had like 20 usb port designations. If not, try looking at the properties for the little palm icon in 'My Computer'. As far as I know it should tell you device it's linking to. Apachedude, maybe you could do this two. Do you get the little icon? If not: do you have a Toshiba machine? I'm on a Toshiba Tecra 8200, and the last time I had 9.1, nothing USB or PCMCIA worked, so mayber 9.2 has the same problem. If that's true, call support!!!! I talked to them about my machine, and they said that since I downloaded it they couldn't help me, but if I bought it they could. Since you have pro, they can help you probably.

-Peter

Thanks for the tip - I did try replacing the printer - same thing.


As for the icon in MyComputer, it shows a little palm pilot and the properties say:

Type: Desktop Config File
Location: /var/lib/desktop
Size: /var/lib/desktop/kpilot.desktop is a file but a folder was expected
Mounted On: /dev/shm

Ok, I'm a newbie, but try using /dev/shm in kpilot. I think that should recognise it.

-Peter

Thanks - /dev/shm is a reference to shortcuts. It isn't a device, AFAIK. I did try that but no luck.

Now, I'm pissed - I HAVE to make it work! :P

Same problem. Back at square one. =T

By the way, I think this post of mine a while back that was ignored underscores all our problems.

We can't pinpoint where the sync should be.

Clearly, it's getting detected. lsusb shows that and gives the right device (0061). So my guess is that it keeps jumping across these /dev/ttyUSBn thingies.

Another possibility is as follows. If you go to the KPilot site, it says that you must compile the KPilot with a given version of pilot-link, and thereafter, not change either. Maybe SuSE did something wrong? Or maybe I accidentally changed KPilot when I upgradeded KDE?

What else could be wrong?

Edit: Worldgnat, no, I do not have the Toshiba machine. I have a desktop, which I built myself. I do get the KPilot icon under My Computer (drives:/). Properties shows that its location is /var/lib/Desktop and that it is mounted to /dev/shm. (Size: /var/lib/Desktop/kpilot.desktop is a file, but a folder was expected.)

Hmmm. I don't know, as for the post you refered to, that's way out of my league. Otherwise, I have no idea. I've got a headache right now, so I'll check back in a second. Although.... try some IRC channels. There might be one of these linux geniuses who knows how to make the world go round on a linux box. They could probably help.

-Peter

Generally, this is the case. But the #kpilot channel on freenode gets like 6 users. And they're all idle.

I'm kind of hoping that the upcoming KPilot 4.4.7 and pilot-link-0.12 play nice.

Okay, here we go!

Set device to /dev/usb/ttyUSB1

Added myself to the group uucp.

Voila! It worked!

Version: KPilot 4.4.5 (Augsburg)
Version: pilot-link 0.11.8
Version: KDE 3.3.0
Version: Qt 3.3.3

HotSync Log

08:46:21 Starting the KPilot daemon ...
08:46:21 Daemon status is `not running'
08:46:33 Trying to open device /dev/usb/ttyUSB1...
08:46:33 Could not open device: /dev/usb/ttyUSB1 (will retry)
08:46:40 Device link ready.
08:46:41 Checking last PC...
08:46:41 KPilot 4.4.5 (Augsburg) HotSync starting...

08:46:41 [File Installer]
08:46:41 No Files to install
08:46:41 Synchronizing changes by the internal editors of KPilot:
08:46:42 Databases with changed records:

Congrats, filesiteguy. Are you running SuSE 9.1 still? I had 9.1 working, but 9.2 is broken. I'm adding myself to uucp and trying all the combinations I can think of. Nothing working yet, but fingers crossed.

I've been trying KPilot, JPilot, and Evolution the last few days. Strangely enough, JPilot synched once, but the others failed to sync completely. I was unable to get JPilot to sync after that one time.

I find that, furthermore, gives me a list of files on my Palm, but pilot-xfer -l -p /dev/ttyUSB1 does not. And although I can list the contents of the palm, I cannot back it up, even using pilot-xfer from the command line.

I got KPilot to sync! The trick was that even though dmesg showed both /dev/ttyUSB0 and /dev/ttyUSB1, the appropriate path was /dev/usb/ttyUSB1.

Well, I'm glad you got it working. I sent a message back to SuSE telling them that thier instructions in teh manual are a bit underdeveloped.

Yes, I'm running 9.2 - that's when things broke. Running the utility on 9.1 was no issue.

Ah, well, it works!

On to figure out a CAD solution to read AutoCAD 2004 files...

It broke again. And I hadn't done anything since it synched last. Which is quite unfortunate, because the KDE PIM interface is great. The KPilot daemon (and pilot-link) are ridiculous though.