[Solved] palm m130 sync issues

crashbox · 2007-03-21 01:37:01

I have followed the jpilot howto for palm sync and its still not working for some reason udev isnt properly listing my palm. I have added my own rules for udev and restarted and it still doesnt help here is my udev rules

 BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[13579]", NAME="pilot", GROUP="uucp", MODE="0660"

and here is what a ls im my dev directory shows when i hit the sync button on my usb cradle

usbdev1.1_ep00
usbdev1.1_ep81
usbdev2.1_ep00
usbdev2.1_ep81
usbdev2.2_ep00
usbdev2.2_ep81

please help

Last edited by crashbox (2007-03-23 01:14:20)

byte · 2007-03-21 01:45:00

Besides adding my user to the 'tty' group (not 'uucp'!) I didn't have to do anything to sync my Handspring Visor.

crashbox · 2007-03-21 02:04:24

unfortunately my user is already in tty group...did change the above udev rule's group from uucp to tty and still nothing.

byte · 2007-03-21 02:09:38

Kill that rule completely. Default udev.rules already has provisions for Palm stuff.

crashbox · 2007-03-21 02:28:38

eliminated the udev rule listed...hit hotsync on palm. my dev directory is shown below...

adsp     hdc       port   ram9        tty10  tty29  tty47  tty8
audio    initctl   ppp    random      tty11  tty3   tty48  tty9
bus      input     psaux  rd          tty12  tty30  tty49  ttyS0
cd       kmem      ptmx   root        tty13  tty31  tty5   ttyS1
cdrom    kmsg      pts    rtc         tty14  tty32  tty50  ttyS2
cdrom0   loop      ram0   sda         tty15  tty33  tty51  ttyS3
cdrw     loop0     ram1   sda1        tty16  tty34  tty52  urandom
cdrw0    loop1     ram10  sequencer   tty17  tty35  tty53  usbdev1.1_ep00
console  loop2     ram11  sequencer2  tty18  tty36  tty54  usbdev1.1_ep81
core     loop3     ram12  shm         tty19  tty37  tty55  usbdev1.20_ep00
disk     loop4     ram13  snapshot    tty2   tty38  tty56  usbdev1.20_ep03
dsp      loop5     ram14  snd         tty20  tty39  tty57  usbdev1.20_ep82
dvd      loop6     ram15  sound       tty21  tty4   tty58  usbdev2.1_ep00
dvd0     loop7     ram2   stderr      tty22  tty40  tty59  usbdev2.1_ep81
fd       lp0       ram3   stdin       tty23  tty41  tty6   usbdev2.2_ep00
full     mem       ram4   stdout      tty24  tty42  tty60  usbdev2.2_ep81
hda      misc      ram5   tts         tty25  tty43  tty61  vc
hda1     mixer     ram6   tty         tty26  tty44  tty62  vcc
hda2     null      ram7   tty0        tty27  tty45  tty63  zero
hda3     parport0  ram8   tty1        tty28  tty46  tty7

after the palm times out on hotsync it shows as this:

adsp     hdc       port   ram9        tty10  tty29  tty47  tty8
audio    initctl   ppp    random      tty11  tty3   tty48  tty9
bus      input     psaux  rd          tty12  tty30  tty49  ttyS0
cd       kmem      ptmx   root        tty13  tty31  tty5   ttyS1
cdrom    kmsg      pts    rtc         tty14  tty32  tty50  ttyS2
cdrom0   loop      ram0   sda         tty15  tty33  tty51  ttyS3
cdrw     loop0     ram1   sda1        tty16  tty34  tty52  urandom
cdrw0    loop1     ram10  sequencer   tty17  tty35  tty53  usbdev1.1_ep00
console  loop2     ram11  sequencer2  tty18  tty36  tty54  usbdev1.1_ep81
core     loop3     ram12  shm         tty19  tty37  tty55  usbdev2.1_ep00
disk     loop4     ram13  snapshot    tty2   tty38  tty56  usbdev2.1_ep81
dsp      loop5     ram14  snd         tty20  tty39  tty57  usbdev2.2_ep00
dvd      loop6     ram15  sound       tty21  tty4   tty58  usbdev2.2_ep81
dvd0     loop7     ram2   stderr      tty22  tty40  tty59  vc
fd       lp0       ram3   stdin       tty23  tty41  tty6   vcc
full     mem       ram4   stdout      tty24  tty42  tty60  zero
hda      misc      ram5   tts         tty25  tty43  tty61
hda1     mixer     ram6   tty         tty26  tty44  tty62
hda2     null      ram7   tty0        tty27  tty45  tty63
hda3     parport0  ram8   tty1        tty28  tty46  tty7

the only difference i can see is the entries starting with usbdev1.20. and the number after 1. (20 in this instance) changes every time i hit hotsync on the palm, so kind of impractical to try to map jpilot to it to sync to.

So far anything i've tried, with the udev rule, without it, that is the only entries I see appearing or dissapearing in my /dev directory.

Edit:
the "tts" directory has 4 entries in it. 0, 1, 2, and 3. And that is it. The entries in the tts directory never change. If I'm trying to hotsync or not. I only mention this because some of the info I've read on setting up a palm is that inside tts should be a ttyUSB entry, and I have yet to see one.

Last edited by crashbox (2007-03-21 02:31:15)

mouse256 · 2007-03-22 12:49:28

The palm m130 isn't a serial connection? My palm m100 was, and I thought m130 was also serial.
anyway: what's your output from dmesg when you connect your palm?

crashbox · 2007-03-22 17:10:00

Nope this m130 cradle is usb. here's the dmesg output when trying to hotsync the palm: (didn't include entire dmesg output since it would be quite long, but will repost with entire output if that will help. No where in the output did it mention a palm device and these are the last 2 lines of dmesg output)

usb 1-7: new full speed USB device using ohci_hcd and address 3
usb 1-7: configuration #1 chosen from 1 choice

here's what lsusb shows while trying to hotsync:

Bus 002 Device 002: ID 05e3:0606 Genesys Logic, Inc. 
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 003: ID 0830:0050 Palm, Inc. Palm M130
Bus 001 Device 001: ID 0000:0000

dmesg after hotsync has timed out:

usb 1-7: new full speed USB device using ohci_hcd and address 3
usb 1-7: configuration #1 chosen from 1 choice
usb 1-7: USB disconnect, address 3

lsusb code after timeout of hotsync:

Bus 002 Device 002: ID 05e3:0606 Genesys Logic, Inc. 
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 001: ID 0000:0000

I hope this info can help someone help to provide me with a answer. I have no idea what's going on at this point.
Any help is greatly appreciated.

mouse256 · 2007-03-23 00:18:17

Well then,
I did have some problems getting my z22 to sync too. It was caused by the fact that the z22 makes a short usb disconnect and reconnect when you push the hotsync button. It seems to mee your m130 might be doing something like that.
I have no problems with it using gnome-pilot, kpilot was a bit of a prolem. For jpilot, I first have to push the hotsync button on the palm, and then the hotsync button in jpilot.
Also: do you have the visor module loaded?
"lsmod | grep visor" if you don't know how to check this ;-)

crashbox · 2007-03-23 01:01:59

Mouse256, that did help some. No i didn't have visor module loaded. When I checked the modules section of rc.conf file it had usbserial disabled.......enabled it. Now visor module shows up in lsmod and I am getting a pilot symlink in dev directory that points to /dev/tts/USB1 when i try to hotsync.

Now however neither jpilot or gnome-pilot will sync, they simply do nothing when i try to sync until the palm times out on the hotsync.

crashbox · 2007-03-23 01:13:55

Got it!

Thanks for all of your help everyone! Figured out why jpilot wasn't syncing up. I ran dmesg while trying to sync and it shows the palm connecting to /dev/tts/USB0 and /dev/tts/USB1. /dev/pilot symlink points to /dev/tts/USB1. If I tell jpilot to use /dev/tts/USB0 then it syncs fine. Don't know why it's connecting to both ports and only USB0 is working. If anyone has any info on this I'd like to figure out why and all, but at least it works.

mouse256 · 2007-03-23 08:54:30

Great!
And for the 2 usb ports: I don't know how it is for the palm m130, but the z22 also creates 2 usb entries (usb0 and usb1), and when you hotsync it does a fast disconnect and reconnect, which sometimes causes udev to create usb3 and usb4. Afaik the pilot-link developers did not find any good explanation for this :-)
As you see in your udev rules:

 BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[13579]", NAME="pilot", GROUP="uucp", MODE="0660"

The symlink is only created to the odd USB numbers. Maybe in your case you should change it to only even numbers?
Anyway, if you don't use any other serial over usb device and your m130 isn't doing the stupid reconnect, I assume you can trust it will always be /dev/tts/USB0 you can use ;-)

crashbox · 2007-03-23 23:28:44

Thanks again. I added

BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[02468]", NAME="pilot", GROUP="uucp", MODE="0660"

To my udev rules. (i changed the ttyUSB[13579] to ttyUSB[02468] like you suggested, and restarted udev.

Now when I hotsync in /dev/tts/ i had only "USB3" show up. and /dev/pilot wasn't a symlink anymore. I'm not sure what it's called but when I do a ls -l on /dev/pilot it shows as:

 
crw-rw---- 1 root tty 188, 2 2007-03-23 18:28 pilot

That may still be a symlink but i don't know what the "c" bit in the permission listing refers to. I know 'd' is directory, and "l" is link or symlink, so it may still be a link, but I just don't know what "c" is referring to.
in either case i was able to tell jpilot to hotsync to /dev/pilot and it worked. Thanks again for all of your advise and help.

Last edited by crashbox (2007-03-23 23:30:39)

Arch Linux

#1 2007-03-21 01:37:01

[Solved] palm m130 sync issues

#2 2007-03-21 01:45:00

Re: [Solved] palm m130 sync issues

#3 2007-03-21 02:04:24

Re: [Solved] palm m130 sync issues

#4 2007-03-21 02:09:38

Re: [Solved] palm m130 sync issues

#5 2007-03-21 02:28:38

Re: [Solved] palm m130 sync issues

#6 2007-03-22 12:49:28

Re: [Solved] palm m130 sync issues

#7 2007-03-22 17:10:00

Re: [Solved] palm m130 sync issues

#8 2007-03-23 00:18:17

Re: [Solved] palm m130 sync issues

#9 2007-03-23 01:01:59

Re: [Solved] palm m130 sync issues

#10 2007-03-23 01:13:55

Re: [Solved] palm m130 sync issues

#11 2007-03-23 08:54:30

Re: [Solved] palm m130 sync issues

#12 2007-03-23 23:28:44

Re: [Solved] palm m130 sync issues

Board footer