I'm using fedora core 3 as my main OS. My old Zire used to work under
linux (back when it was Redhat 9, or perhaps FC1). But, somewhere
along the line it stopped working and I only just started fiddling
with it.

The unit does hotsync under windows, so, I know it "works".

Here's what I get under lsub when I try to hotsync:

[strangepork 40] archives > lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 0830:0060 Palm, Inc. Palm Tungsten T
Bus 001 Device 001: ID 0000:0000

Here's what I see when I tail /var/log/messages and (again) hotsync:

[strangepork 10] goldmoon > tail -f /var/log/messages
Feb 14 23:46:23 localhost kernel: usb 1-1: Handspring Visor / Palm OS
converter now attached tottyUSB0
Feb 14 23:46:23 localhost kernel: usb 1-1: Handspring Visor / Palm OS
converter now attached tottyUSB1
Feb 14 23:48:39 localhost kernel: usb 1-1: USB disconnect, address 5
Feb 14 23:48:39 localhost kernel: visor ttyUSB0: Handspring Visor /
Palm OS converter now disconnected from ttyUSB0
Feb 14 23:48:39 localhost kernel: visor ttyUSB1: Handspring Visor /
Palm OS converter now disconnected from ttyUSB1
Feb 14 23:48:39 localhost kernel: visor 1-1:1.0: device disconnected
Feb 14 23:49:57 localhost kernel: usb 1-1: new full speed USB device
using address 6
Feb 14 23:49:57 localhost kernel: visor 1-1:1.0: Handspring Visor /
Palm OS converter detected
Feb 14 23:49:57 localhost kernel: usb 1-1: Handspring Visor / Palm OS
converter now attached tottyUSB0
Feb 14 23:49:58 localhost kernel: usb 1-1: Handspring Visor / Palm OS
converter now attached tottyUSB1

[4]+  Stopped                 tail -f /var/log/messages

Note that it's being listed as connected to ttyUSB0 and 1 at the same
time. Maybe this is part of the problem?

In the Kpilot FAQ, it suggests making sure that pilot-link is
functional by using the following command:
[strangepork 16] goldmoon > pilot-xfer -p ttyUSB1 -L

The device ttyUSB1 does not exist..
Possible solution:

mknod ttyUSB1 c <major> <minor>

Unable to bind to port: ttyUSB1
Please use --help for more information

Here, it's telling me that ttyUSB1 does not exist (this also happens
with ttyUSB0). I've made a point of hitting 'enter' when the device
shows up in the tail log, so, ttyUSB0 (and 1) _do_ exist at the moment
I'm sending the command. in fact, they both exist at the same time
(which, again, may be why it's breaking?)

I realize I won't be able to sync it till /dev/pilot points to the
correct port, but, I can't point it to that port until the system will
recognize it as existing, can I?

Gwen

[ Post a follow-up to this message ]

On Tue, 15 Feb 2005 00:04:20 -0500, Gwen Morse wrote:
> Note that it's being listed as connected to ttyUSB0 and 1 at the same
> time. Maybe this is part of the problem?

Nope.  That's normal.  There are always 2 devices for every USB connection.

> Here, it's telling me that ttyUSB1 does not exist (this also happens
> with ttyUSB0). I've made a point of hitting 'enter' when the device
> shows up in the tail log, so, ttyUSB0 (and 1) _do_ exist at the moment
> I'm sending the command. in fact, they both exist at the same time
> (which, again, may be why it's breaking?)

Hmmm... Interesting.  The device should exist.  I use pilot-link all the
time for my Tungsten C.  You should be able to press the hot sync button,
then enter the pilot-link command and everything should work.

Just remember that the device doesn't exist until after you press the hot
sync button (and it may take a moment for the device to show up).

> I realize I won't be able to sync it till /dev/pilot points to the
> correct port, but, I can't point it to that port until the system will
> recognize it as existing, can I?

Right.  But all you need to do is (as root) "ln -s /dev/ttyUSB1
/dev/pilot" as soon as the ttyUSB1 device shows up.

[ Post a follow-up to this message ]

On Tue, 15 Feb 2005 00:04:20 -0500, Gwen Morse wrote:
> I'm using fedora core 3 as my main OS. My old Zire used to work under
> linux (back when it was Redhat 9, or perhaps FC1). But, somewhere
> along the line it stopped working and I only just started fiddling
> with it.

Palm syncing broke with the FC3 early kernels.  You need to upgrade to
an updated FC3 kernel - I'm using 2.6.10-1.760_FC3smp and that's OK,
as was the release before that.

Hope this helps.

--
Trevor Barton

[ Post a follow-up to this message ]