[jp] Treo 650 sync problem

>> I just got a Treo 650 and am having trouble syncing.  When I plug 
>> the USB in, I see the following in /var/log/messages.  I am still 
>> running Fedore Core 1 (I know, I know I should upgrade, just haven't 
>> had the time or need until now).  Does anyone know of problems with 
>> FC1 and the Treo?
>
>     Yes, the Treo came out long after FC1 was released. Its kernel 
>probably knows nothing about how to communicate with the Treo650.
>
>     Have you updated the kernel to the most-current kernel that 
>FC1 supports?
>
>     Or have you modified the method by which the visor driver is 
>loaded, by passing in the proper parameters to recognize your Treo650?
>
>     That would look like this:
>
>     modprobe visor product=0x61 vendor=0x830
>
>     Alternately, these options can go into your distribution's 
>modprobe.conf, modules.conf, or whatever other location is used to 
>pass parameters to modules at module load time.
>
>

This appeard to get the system to recognize the device, as you can see by this snippet from /var/log/messages:

Jul 28 11:19:20 gondor kernel: visor.c: Untested USB device specified at time of module insertion
Jul 28 11:19:20 gondor kernel: visor.c: Warning: This is not guaranteed to work
Jul 28 11:19:20 gondor kernel: visor.c: Using a newer kernel is preferred to this method
Jul 28 11:19:20 gondor kernel: visor.c: Adding Palm OS protocol 4.x support for unknown device: 0x830/0x61
Jul 28 11:19:20 gondor kernel: usbserial.c: USB Serial support registered for user specified device with Palm 4.x protocols
Jul 28 11:19:20 gondor kernel: usbserial.c: USB Serial support registered for Handspring Visor / Treo / Palm 4.0 / Clie 4.x
Jul 28 11:19:20 gondor kernel: usbserial.c: USB Serial support registered for Sony Clie 3.5
Jul 28 11:19:20 gondor kernel: visor.c: USB HandSpring Visor, Palm m50x, Treo, Sony Clie driver v1.7

But I can tell which usb port its on (cdrecord, etc. which I use for the flash reader doesn't show it up - I am stretching my experience and knowledge a bit here - but for the flash readers, linux treats them more like scsi...)

So I tried the brute force method (after much googling) and just ran jpilot-sync, passing "-p ttyUSB<number>" for each one.  The all returned with:

    pi_bind: No such device
    pi_bind Illegal seek
    Check your serial port and settings
    Exiting with status SYNC_ERROR_BIND
    Finished

    Error: connecting to serial port

Short of upgrading, I am not sure what more I can do.  Are there any tools like sg_scan that shows you what is on USB?

Any help is much appreciated.

-- Susan
 
_____________________________ 
Susan Macchia 
mailto:susan at smacchia.net 
http://www.smacchia.net 
_____________________________