Hello,

I thought the USB MFC was a good time to try again synchronizing my PDA.
It is a Sony Cli� PEG-SJ22 running PalmOS�4.1.  I'm trying to access it
using the uvisor driver (1.7.2.9 2004/04/04) and coldsync (2.2.5 from
ports) using a setup which works under Linux (Debian Sarge with 2.4 and
2.6 kernels) but, to be clear, never did with FreeBSD (STABLE).  And I'm
afraid it still doesn't with 4.10-BETA.

It goes like this: first I tap Hotsync on the Cli�, so that it attaches
itself as a USB device, then either usbd takes over or I start coldsync
manually.  Here is an extract from /var/log/messages:

Apr 11 21:42:51 krakatoa /kernel: ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 
2
Apr 11 21:42:51 krakatoa /kernel: ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 
2
Apr 11 21:43:52 krakatoa /kernel: ucom0: at uhub0 port 2 (addr 2) disconnected
Apr 11 21:43:52 krakatoa /kernel: ucom0: detached

For usbd, with the following in /etc/usbd.conf:

device "Sony Clie"
        devname "ucom[0-9]+"
        vendor  0x054c
        product 0x0066
        attach "/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb"

I get these messages:

krakatoa ~ % sudo /usr/sbin/usbd -d -v
Password:
usbd: opened /dev/usb0
usbd: reading configuration file /etc/usbd.conf
usbd: opened /dev/usb
usbd: driver-attach event cookie=3217027820 devname=ucom0
USB_EVENT_DRIVER_ATTACH
usbd: device-attach event at 1081712571.593824000, Palm Handheld, Palm, Inc.:
  vndr=0x054c prdct=0x0066 rlse=0x0100 clss=0x0000 subclss=0x0000 prtcl=0x0000
  device names: ucom0
usbd: Found action 'Sony Clie' for Palm Handheld, Palm, Inc. at ucom0
usbd: Executing '/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb'
pconn_usb_open: Can't get information about USB device.
ioctl(USB_GET_DEVICEINFO): Inappropriate ioctl for device
Error: Can't open connection.
usbd: '/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb' returned 1
usbd: device-detach event at 1081712632.003093000, Sony Clie v4.0, Sony:
  vndr=0x054c prdct=0x0066 rlse=0x0100 clss=0x0000 subclss=0x0000 prtcl=0x0000

And if I try coldsync manually:

krakatoa ~ % coldsync -v 
Please press the HotSync button.
netsync_read: read: Input/output error
Error: Can't connect to Palm.
tcdrain: Input/output error

The error messages are displayed as the device detaches; coldsync hangs
at "press the HotSync button", which I can't do since I don't have an
external cradle and the HotSync application on the Cli� won't let me tap
the icon while it's trying to connect.  And if I try to start coldsync
before the HotSync, it exits right away with:

krakatoa ~ % coldsync -v
Error: Can't open "/dev/ucom0".
open: Device not configured
Error: Can't open connection.

The /usr/local/etc/palms file seems correct, and my .coldsyncrc reads:

listen serial {
        protocol: simple;
        device: /dev/ucom0;
}
pda "skrode" {
        snum: <serial#>
        directory: /home/ware/.palm;
        username: "skrode";
        userid: <uid>;
        default;
}

This is the same file as with Linux (except "device: /dev/ttyUSB1;"),
but I tried many combinations ("listen usb" instead of "listen serial",
"protocol: net" instead of "protocol: simple", setting the speed...)
and the end result is the same, although the error messages do change
sometimes.  More information on request.

The pilot-xfer program has exactly the same behavior ("Please press the
HotSync button now...") except that it doesn't exit when the Cli� times
out and detaches.

This happens both with the GENERIC kernel and a customized one, either
with "device ucom" and "device uvisor", or loading them as modules.
This is all with last Friday's STABLE; I believe I had tried with 5.1
or 5.2 in January, without success, but I don't have a CURRENT machine
at hand to check now.

Should I try something else?  Any idea to make it work?

                                                Thanks,
                                                Cedric Ware.
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to