On Wed, 2002-10-23 at 15:54, Phil Dibowitz wrote: > Dmitri wrote: > > > > a) Load visor driver > > Got it. It was hidden under 'serial converters' Doh! I just changed the > config made modules and modules_install, and it modprobed fine. > > > b) $ pilot-xfer -p /dev/usb/ttyUSB1 -l # (or like that) > > > > Note: you should use the SECOND of two devices that materialize after > > you press the sync button on the cradle. Press sync BEFORE you run the > > command (b). > > Small change... /dev/ttyUSB1 (there is no /dev/usb/ttyUSB1 so I'm just > guessing that was a typo).
Not a typo, but it does not matter. You can have /dev special files
anywhere, in any directory, as long as they carry the right numbers. It
is the preferred way to have /dev/usb/ directory, but you don't have to.
> $ pilot-xfer -p /dev/ttyUSB1 -l
> Port: /dev/ttyUSB1
>
> Please press the HotSync button now...
>
> It just hangs there.
> I've tried it as my normal user (which has rw access to that device) as
> well as root, and it just hangs.
I had Visor, not Palm - I don't know if there is any difference between
them. Worked for me...
> I pushed hotsync on the cardle, saw it come up in /var/log/messages,
> then ran the command... just sits. I also tried hitting hotsync again
> after that... no cigar.
And no errors in /var/log/messages either? Could you post the portion of
/var/log/messages that is relevant to this? (from the moment you load
the driver to the moment the Palm times out.)
Also, how recent your kernel is?
Also, can you post the output of this?
# ls -l /dev/ttyUSB*
Thanks,
Dmitri
--
174. If I am dangling over a precipice and the hero reaches his hand
down to me, I will not attempt to pull him down with me. I will allow
him to rescue me, thank him properly, then return to the safety of my
fortress and order his execution. ("Evil Overlord" by Peter Anspach and
John VanSickl)
signature.asc
Description: This is a digitally signed message part
