[coldsync-hackers] Re: coldsync 2.1, USB, & FreeBSD -- oops

[James Widman <j-widman@cornell-iowa.edu>]

ok, the short answer is that I didn't do enough testing and made some hasty conclusions


"Louis A. Mamakos" wrote:

<snip>

> > > But this block has to be in /etc/usbd.conf.  (I think this is because
> > >>it tells usbd to associate the visor with /dev/ugen0 so that it can be
> > >> read from and written to
> 
> I don't think that's the case at all.  It's NEVER been necessary for me.

oops.  my bad; sorry

after a large number of syncs and sync attempts, I killed usbd and made usbd.conf blank.  Then I tried ~/bin/ugly (multiple coldsync processes) and that worked.  I tried the timing trick and that *didn't* work until after I rebooted my PC.
The timing trick seems to get some pretty random results (i.e., the time window where it works seems to shift around at random within the 30 seconds that coldsync waits), except that it only seems to work a few times, and those few times have to be among the first few sync attempts since the system was booted -- but that's mostly just speculation.

> >       I know this sounds like finger-pointing, but this looks like
> > an OS bug or setup problem to me. You may want to try running
> > 'usbdevs' 
ok:
#usbdevs
addr1: UHCI root hub, VIA

> > and "echo foo < /dev/ugen0" in the "attach" script (and save
> > the output, naturally).
> >       If this is an OS or setup problem, then I would expect the
> > "< /dev/ugen0" or "< /dev/ugen0.2" to fail under the same conditions
> > as ColdSync:
> >
> >       # echo foo < /dev/ugen0
> >       /dev/ugen0: Device not configured.

That's what happens if it's run at the command prompt *and* the visor is not showing the "Connecting with the desktop" message.  
but "/bin/echo foo < /dev/ugen0 > /usr/home/james/out" leaves a file with the line "foo" in my home directory if I run that command while the visor is trying to sync (with a blank usbd.conf) *or* if that command is run as an attach statement in usbd.conf

> I would try a more recent version of FreeBSD.  Alternatively, you
> could try building a kernel with some of the USB debugging features
> turned on.
> 
> Louis Mamakos

Yeah, a system update is definitely my next step (probably should have been the first, as I haven't synced and made world in a couple of months now).  The problem, assuming it's in BSD's USB subsystem, has probably been fixed by now, but I'll turn on debugging features just in case.

Thanks guys :)

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.