Re: coldsync-2.2.5 w/Palm m130 via USB ?

!Sure, here we go:
!Sep 27 16:06:55 piglet /kernel: ucom0: Palm, Inc. Palm Handheld, rev
!1.00/1.00, addr 3
!
!> Or give more info...
!> this is my output.
!> Kernel has :  ucom, uplcom and uvscom devices/support
!> Sep 27 13:04:51 dori /kernel: ugen0: Palm, Inc. Palm Handheld, rev
!> 1.00/1.00, addr 2
!
!It is important that you don't let the ugen driver get the device.
!This means you either should load uvisor (kldload uvisor) prior to
!pressing the sync button (for e.g. in /etc/rc.local) or you should
!configure usbd to load the driver (which means the first sync will
!fail - or at least I don't know how to do it ;).
!
!Put the following lines in /etc/usbd.conf for the second approach:
!device "Palm m125"
!   vendor  0x830
!   product 0x0040
!   release 0x0100
!   attach "if ! kldstat -n uvisor > /dev/null 2>&1 ; then kldload uvisor; fi"

Hank -- We just upgraded our Toshiba Satellite Pro 4600 to 4.7-R
and gave our USB-connected Palm m130 cradle a go with the information
you forwarded earlier.

With devices "ucom" & "uvisor" compiled into the kernel,
we still get the ugen0 connection when the HotSync button is pressed:

	ugen0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 5

With the Palm device connected, "usbdevs -v" returns:

	port 4 addr 5: self powered, config 1, Palm Handheld(0x0050), Palm, Inc.(0x0830), rev 1.00

Following your original suggestion, we took the ucom & uvisor devices
out of the kernel, recompiled, and updated /etc/usbd.conf with
"product 0x0050", as noted in usbdevs.

Pressing the HotSync button loads the ucom & uvisor kernel modules OK,
but ugen continues to pick it up, instead !

I suppose the next step is to build a kernel without "ugen" & see how
the kernel reacts to the HotSync button.

Perhaps there's still another trick to force a connection with ucom/uvisor.
--
Gary E. RAFE, PhD
[email protected]

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message