On Thursday 14 June 2007 18:31, Mike Durian wrote: > On Saturday 26 May 2007, Mike Durian wrote: > > On Tuesday 24 April 2007, Hans Petter Selasky wrote: > > > On Friday 20 April 2007 17:36, Mike Durian wrote: > > > > On Friday 20 April 2007, Hans Petter Selasky wrote: > > > > > I would suggest you install the new USB stack from: > > > > > > > > > > http://www.turbocat.net/~hselasky/usb4bsd/ > > > > > > > > > > How to get the latest sources: > > > > > > > > > > svn --username anonsvn --password anonsvn \ > > > > > checkout svn://svn.turbocat.net/i4b > > > > > # > > > > > # The following commands will > > > > > # install the driver on FreeBSD: > > > > > # > > > > > cd i4b/trunk/i4b/FreeBSD.usb > > > > > make S=../src package > > > > > make install > > > > > > > > > > Install on FreeBSD 6.x . > > > > > > > > > > When you have rebooted your computer, then you turn on debugging: > > > > > > > > > > sysctl hw.usb.umass.debug=-1 > > > > > > > > > > Then post the dmesg you get. > > > > > > > > > > --HPS > > > > > > I have found a small data-toggle bug in my EHCI driver. I assume that > > > your device is USB2.0. Could you do a "svn update", repeat the install > > > procedure, and then build a new kernel. > > > > > > Then send me the dmesg with "sysctl hw.usb.umass.debug=-1", when you > > > plug your device. > > > > > > --HPS > > > > I've cvsup'd my source tree and svn updated the i4b code (both as of > > May 26, 2007) but I'm still not having any luck with the card reader. > > It seemed to work in single user mode, but fails in multi-user mode. > > It didn't detect card insertion in single user mode either. I had to > > unplug the entire card reader, insert the compact flash card and then > > plug-in the card reader to get it to detect the card in single user mode. > > > > I'm attaching two debug outputs. One from single user mode and the other > > from multi-user mode. > > > > mike > > Since I've hit a wall with the experimental USB code with regards to > the card reader, perhaps it is time to return to my original question. > > How does one determine which proto and quirk values are necessary for > finicky umass devices? > > mike
You need to turn on "umass" debugging and see what fails. sysctl hw.usb.umass.debug=-1 --HPS _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
