View previous topic :: View next topic |
Author |
Message |
pksings Tux's lil' helper
Joined: 26 Oct 2003 Posts: 110 Location: Southern California
|
Posted: Tue Feb 22, 2005 5:59 pm Post subject: Pilot (Clie) sync |
|
|
Hello all,
I cannot sync my Clie with Evolution or Jpilot. I can get responses from pilot-xfer.
pilot-xfer --port /dev/usb/tts/0 --list gives me a list of files.
(No/Yes it is not the correct UDEV enumerated file, UDEV won't boot my SATA controller, so I'm stuck with Devfs, that was a different post)
I tried re-emerging Evolution making sure I had the "pda" use flag enabled and it made no difference.
phred root # emerge -pv evolution
[ebuild R ] mail-client/evolution-2.0.2-r1 +crypt -debug -doc -ipv6 -kerberos +ldap +mozilla -nntp +pda +spell +ssl 0 kB
phred root # emerge -pv jpilot
[ebuild R ] app-pda/jpilot-0.99.6-r1 +gtk2 +nls 0 kB
the visor module loads with no errors and seems to work since I can get pilot-xfer to tranfer data.
I can find no logs to look at that might tell me what is wrong.
I have followed every HOWTO I can find in the forums, Probably four or five different ones, most of them are posted because the authors were successful. So I figured I would be if I followed them. But I'm missing something....
Any help is greatly appreciated.
PK _________________ PK |
|
Back to top |
|
|
k-root Guru
Joined: 08 Jan 2005 Posts: 428
|
Posted: Tue Feb 22, 2005 7:42 pm Post subject: [PDA] Clie USB Sync with Jpilot & Evolution |
|
|
what tell you dmesg ? what tell you lsusb ?
if you plug you clie on usb and power it on... it wont create any usb device until you presse the sync button on hit.
pressing sync on my plam (udev) :
Quote: |
#dmesg
usb 3-2: new full speed USB device using uhci_hcd and address 14
visor 3-2:1.0: Handspring Visor / Palm OS converter detected
usb 3-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 3-2: Handspring Visor / Palm OS converter now attached to ttyUSB1
|
and i get the following device
Quote: |
/dev/tts/USB0
/dev/tts/USB1
|
Quote: |
#lsusb
Bus 003 Device 016: ID 0830:0060 Palm, Inc. Palm Tungsten T
|
i had to tell jpilot to use /dev/tts/USB1 ...
Quote: |
For Palm devices, you will need no more than two of these devices,
/dev/ttyUSB0 and /dev/ttyUSB1, depending on your Palm device
manufacturer (as of the time of this README, two Sony models use
/dev/ttyUSB0, and the rest of the Sony and Palm models seem to be
using /dev/ttyUSB1)
those are for (DEVFS)
# /bin/mknod /dev/ttyUSB0 c 188 0
# /bin/mknod /dev/ttyUSB1 c 188 1
|
for usb palm -> http://pilot-link.org/README.usb
for evolution ->http://howto.pilot-link.org/evosync
[not sur about the fact that pilot-xfer require or not the palm sync button to be hit) |
|
Back to top |
|
|
aethyr Veteran
Joined: 06 Apr 2003 Posts: 1085 Location: NYC
|
Posted: Tue Feb 22, 2005 10:21 pm Post subject: |
|
|
I believe evolution and jpilot look for a /dev/pilot link pointing to your pda.
Do you have that link present? I'm not sure if devfs/udev do it automatically.
Alternatively, you might be able to configure those programs to look in the right place. |
|
Back to top |
|
|
pksings Tux's lil' helper
Joined: 26 Oct 2003 Posts: 110 Location: Southern California
|
Posted: Wed Feb 23, 2005 6:54 am Post subject: Thanks guys for looking at this. |
|
|
phred / # lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 005: ID 054c:0144 Sony Corp.
Bus 003 Device 003: ID 051d:0002 American Power Conversion Back-UPS Pro 500
Bus 003 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
usb 3-2: new full speed USB device using ohci_hcd and address 5
visor 3-2:1.0: Sony Clie 5.0 converter detected
usb 3-2: Sony Clie 5.0 converter now attached to ttyUSB0
usb 3-2: Sony Clie 5.0 converter now attached to ttyUSB1
I have tried pointing Jpilot and gpilotd at /dev/ttyUSB0 and /dev/ttyUSB1, which works on my laptop but not here.
Seems like it ought to work.... _________________ PK |
|
Back to top |
|
|
jpjacobs n00b
Joined: 02 Nov 2004 Posts: 10
|
Posted: Thu Feb 24, 2005 9:09 am Post subject: Palm Zire |
|
|
More or less the same problem here
lsusb returns:
Code: | #lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 005: ID 0830:0070 Palm, Inc.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000 |
dmesg output:
Code: | # dmesg|grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new driver usb-storage
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: USB disconnect, address 2
usb 3-1: new full speed USB device using uhci_hcd and address 3
usb 3-1: USB disconnect, address 3
usb 3-1: new full speed USB device using uhci_hcd and address 4
usb 3-1: USB disconnect, address 4
usb 3-1: new full speed USB device using uhci_hcd and address 5
|
but it doesn't create any devices... |
|
Back to top |
|
|
FluffyArmada Tux's lil' helper
Joined: 13 Mar 2004 Posts: 107 Location: Dortmund
|
Posted: Mon Mar 07, 2005 11:25 pm Post subject: Just made mine work. |
|
|
You *MUST* have the Serial Convertor AND Visor compiled into your kernel.
The way the Gentoo kernel is patched instead of putting the clie's dev note as /dev/ttyUSB* but instead will be
/dev/tts/USB*
hope that helps
As for those programs, KPilot *WILL NOT* autodetect a clie you MUST manually specify the device. _________________ -- fluffyarmada
"Fancy thinking that the beast is something you can hunt and kill." |
|
Back to top |
|
|
jpjacobs n00b
Joined: 02 Nov 2004 Posts: 10
|
Posted: Tue Mar 08, 2005 7:37 pm Post subject: |
|
|
thanks for your advice, It helped me a lot... |
|
Back to top |
|
|
FluffyArmada Tux's lil' helper
Joined: 13 Mar 2004 Posts: 107 Location: Dortmund
|
Posted: Tue Mar 08, 2005 10:01 pm Post subject: :)` |
|
|
lol.. me helping someone is probably a first.
but your welcome, I was in the process of making mine work when I found this topic. _________________ -- fluffyarmada
"Fancy thinking that the beast is something you can hunt and kill." |
|
Back to top |
|
|
pcardout n00b
Joined: 11 Mar 2005 Posts: 34 Location: Socorro, NM
|
Posted: Sat Apr 02, 2005 6:04 am Post subject: Did you ever get your pilot synching? I may have the answer |
|
|
I had run pilot-xfer too, but I was unaware of the program
install-use", which (comes with the pilot-xfer package) and sucks the userid out of an already running Palm / Clie.
This was what finally got my pilot working. _________________ I was born not knowing and have only
had a little time to change that here and there.
--Richard Feynman |
|
Back to top |
|
|
David916 n00b
Joined: 11 Dec 2002 Posts: 60 Location: My basement
|
Posted: Tue Nov 08, 2005 3:43 am Post subject: Another suggestion |
|
|
I realize this is probably way after the time of being useful, but someone else may find it helpful.
I was originally having the problem where the /dev/tts/USB0 and USB1 were not read/writeable by my user. I had to add myself to the tts group to get it working as a non-root user.
Helpful? _________________ -David Wahl
dmwahl at wisc dot edu
$ man woman
No manual entry for woman |
|
Back to top |
|
|
pcardout n00b
Joined: 11 Mar 2005 Posts: 34 Location: Socorro, NM
|
Posted: Tue Nov 08, 2005 3:38 pm Post subject: User of tts group |
|
|
All such lore is helpful. Thanks for contributing. _________________ I was born not knowing and have only
had a little time to change that here and there.
--Richard Feynman |
|
Back to top |
|
|
hazer n00b
Joined: 02 Sep 2004 Posts: 55
|
Posted: Thu Apr 06, 2006 5:31 pm Post subject: |
|
|
and now to resurect an old thread.
I'm able to sync as root, but not as my user account. Not overly supprizing given the 'normal' /dev permissions. When I went to look for the tts group to add my user (as suggested above) I'm finding there is no tts group. There's a tty group but I'm betting that's not the same.
One of the HOWTOs listed that you can make a new rule chain for udev that would allow you to track when the device was connected and make the proper permission changes, but in doing so you had to have the serial number of the device. From what was printed you could get that info from "cat /proc/bus/usb/devices", but I see no entry that looks like a serial number when my Clie is active.
Thoughts, suggestions, flames for the noob who refuses to sync the unit with his WinXP VMWare session? |
|
Back to top |
|
|
pcardout n00b
Joined: 11 Mar 2005 Posts: 34 Location: Socorro, NM
|
Posted: Fri Apr 07, 2006 12:33 am Post subject: |
|
|
Hi -- When I got it working about a year ago -- I took notes. I'll dump my notes.
I did not have to mess with groups. I had to create a link with mknod. I found that
install-user worked for me, and I can sync as myself, without being root.
HERE GOES
First I needed to install kernel options to support Palm. Rather than doing as modules, I compiled them straight in by changing my
config file. More data follows.
The above was easy for me because I'm on Gentoo -- but then, so is everyone on this forum.
There have been discussions about udev and hotplug. I did not mess with any of these.
Instead I followed these directions.
The golden directions!
http://www.linuxpda.com/visor/howto/current/introduction.html (and the documents below this)
They were really clear!!
Having followed the above advice
At first I got the message:
"unable to bind to the port"
This was because the node /dev/ttyUSB0 and /dev/ttyUSB1 did not exist.
So the Palm wanted to put itself there, but I hadn't created them.
Thus:
Code: |
mknod /dev/ttyUSB0 c 188 0
mknod /dev/ttyUSB1 c 188 1
mknod /dev/ttyUSB2 c 188 2
mknod /dev/ttyUSB3 c 188 3
chmod 666 /dev/ttyUSB*
|
Since I'm told /dev/ttyUSB0 is for future use and /dev/ttyUSB1 is for
synching, I created a symbolic link.
Code: | cd /dev
ln -s /dev/ttyUSB1 pilot |
Then in Jpilot, I can use /dev/pilot as the synching device in preferences.
langley permissions.d # pilot-xfer -p /dev/pilot -L
Before the first time you run jpilot, you need to run install-user
(which comes with the pilot-link package).
Code: |
install-user
No $PILOTPORT specified and no -p <port> given.
Defaulting to '/dev/pilot'
Port not connected, sleeping for 2 seconds, 3 retries..
Listening to port: /dev/pilot
Please press the HotSync button now... Connected
Palm user: John Jacob Jingleheimer Schmidt
UserID: 7454
|
richard@dirac dev $ ls -l pilot
lr-xr-xr-x 1 root root 12 Mar 23 21:54 pilot -> /dev/ttyUSB1 _________________ I was born not knowing and have only
had a little time to change that here and there.
--Richard Feynman |
|
Back to top |
|
|
|