Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Palm Centro sync problems
28 views
Skip to first unread message
Jim Janney
Jan 19, 2013, 3:11:36 PM1/19/13
to
I have a new mintBox running Linux Mint 13, and I'm trying to see if I
can sync my Palm Centro (I know, I know) to it. I've installed the
pilot-link, pilot-manager, and jpilot packages. When I try to sync
(first press the sync button in JPilot, then the button on the Palm)
nothing seems to happen, and the Centro eventually times out.
After I connect the Centro, running dmesg shows
[94601.932078] usb 7-3: new full-speed USB device number 26 using ohci_hcd
[94602.105220] visor 7-3:1.0: Handspring Visor / Palm OS converter detected
[94602.105522] usb 7-3: Handspring Visor / Palm OS converter now attached to ttyUSB0
[94602.105721] usb 7-3: Handspring Visor / Palm OS converter now attached to ttyUSB1
After some light googling I tried running
pilot-xfer -l -p usb:
at the command line. That hung in exactly the same way, but when I ran it again as
sudo pilot-xfer -l -p usb:
it fired up and connected right away. So, some kind of permissions
problem. I guess I could just run jpilot in sudo, but I'd like to know
the right way to do this. How are USB permission settings supposed to
work?
--
Jim Janney
can sync my Palm Centro (I know, I know) to it. I've installed the
pilot-link, pilot-manager, and jpilot packages. When I try to sync
(first press the sync button in JPilot, then the button on the Palm)
nothing seems to happen, and the Centro eventually times out.
After I connect the Centro, running dmesg shows
[94601.932078] usb 7-3: new full-speed USB device number 26 using ohci_hcd
[94602.105220] visor 7-3:1.0: Handspring Visor / Palm OS converter detected
[94602.105522] usb 7-3: Handspring Visor / Palm OS converter now attached to ttyUSB0
[94602.105721] usb 7-3: Handspring Visor / Palm OS converter now attached to ttyUSB1
After some light googling I tried running
pilot-xfer -l -p usb:
at the command line. That hung in exactly the same way, but when I ran it again as
sudo pilot-xfer -l -p usb:
it fired up and connected right away. So, some kind of permissions
problem. I guess I could just run jpilot in sudo, but I'd like to know
the right way to do this. How are USB permission settings supposed to
work?
--
Jim Janney
Jim Janney
Jan 19, 2013, 9:04:40 PM1/19/13
to
still having problems with jpilot but this is probably the wrong place
to ask about that.
--
Jim Janney
0 new messages