Palm Treo 650 on SLED 10
Ok, so I got a free Palm Treo 650 today (CDMA) and it only comes with windows and Mac drivers .. so what am I supposed to be searching for to get it up and running?
Remember I'm a complete Noob... if its something I can just search in the "software management" option in yast then I'd be really happy |
Ok, I've tried synching with J Pilot, and its not working.
Quote:
|
Anyone???????
|
palm treo on sled 10
Sorry. You are not alone. Me too.
|
That error can normally be avoided by pressing the sync button on the treo first (thereby creating /dev/ttyUSB0 & /dev/ttyUSB1) and then pressing the sync button in jpilot one second later. Set the device in jpilot to /dev/ttyUSB1
|
Well personally, I use kpilot and kontact for the PIM stuff - it syncs quite well with few problems.
If you tried this and you find that the sync fails part of the way through (like mine has done with some distros), if you then record what it looks like crashed the kpilot daemon you can add that part to the comma seperated list of things that don't get "sunk". In my case it was a couple of the java related things (J9MIDP Bundle and one other that I can't recall). I never did have any luck with jpilot or gpilot. Have a look at the treoquestions treo forum, linked on the right hand column of this. regards John |
I sync my Treo 680 with JPilot on Debian Unstable. I had to set it to use /dev/ttyUSB1 (my previous PDA, a Clie, used USB0). Then I click the HotSync button (to create /dev/ttyUSB1), wait a couple of seconds, and tell JPilot to sync. Works every time.
Instead of "waiting a couple of seconds", you can also check the output of /var/log/messages to see when the Treo has connected. I use "tail -f /var/log/messages" in a console window for this. Finally, you'll have to make sure you have permission to access /dev/ttyUSB1. In my case, it was a simple matter of adding myself to the appropriate group. |
visor platinum on a 2.6 kernel with USB
I read this thread and saw the suggestion to use kpilot. I thought that sounded like a god idea. I started it up and it asked me to configure it with the option of automatically detecting the settings. I didn't know what the original setting were so I selected that option and guess what.... it detected the PDA! Unfortunately it won't sync. Any ideas?
Perhaps this has something to do with the configuration file being out of date. To fix this problem it instructs me to 'run kpilot' but that is the program that is instructing me to do this. Any suggestions as to what to do? hmmmmmm....it says: Version: KPilot 4.6.0 (blivit) Version: pilot-link 0.11.8 Version: KDE 3.5.3 Version: Qt 3.3.6 HotSync Log 13:59:45 Starting the KPilot daemon ... 13:59:45 Daemon status is `not running' 14:05:00 Changed username to `Mike Havens'. ---edit--- hmmmmmm.... this is interesting...... I type 'sudo kpilot&' to start the program and right when kpilot appears I get an error message appears on rxvt statin that it 'probably crashed.' |
All times are GMT -5. The time now is 01:58 PM. |