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

[much output deleted...]
!> Perhaps there's still another trick to force a connection with ucom/uvisor.
!did you change the usbd.conf entry to say ucom? 
!
!There are also issues with the usb stuff with Pilot-Link (the pilot-link
!guys are working on it). 
!
!Here is my usbd.conf entry for a ucom connected M515:
!device "Palm Handheld"
!       devname "ucom0"
!       vendor 0x0830
!       product 0x0003
!       release 0x0100
!#       attach "/home/ler/bin/pilot-sync.sh ${DEVNAME}"
!
!mangle to taste. 
!
!Also, did someone fix the coldsync port to actually enable the USB
!stuff? 

Thanks for the data point.
I updated /etc/usbd.conf with a devname entry as suggested,
restarted usbd, then hit the HotSync button.
usbdevs reports the device on the bus,
but no other activity is seen (ugen was removed from the kernel) --
while both ucom & uvisor kernel modules were loaded previously.

Now then, my 4.7-R upgrade has been less than smooth with broken
Linux emulation
(e.g., Wordperfect can't find /compat/linux/lib/ld-linux.so.1)
and X troubles
(e.g., rxvt reports /usr/X11R6/lib/libXrender.so.1:
Undefined symbol "XextFindDisplay") !

Must be a bunch of magic I'm missing this time around !
--
Gary E. RAFE, PhD
[email protected]

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