[sane-devel] freebsd usb

[Brian K. White]

Hi,

I have a CanoScan N670U and freebsd 4.8-stable and sane-backends 1.0.11

after utterly _failing_ to figure out the government secret as to what 
exactly is the correct syntax for device "libusb:..." in plustek.conf
(why can't this be documented somewhere?, sane-find-scanner reported 
"libusb:/dev/usb0:/dev/ugen0" neither that nor any of several pointless 
guesses caused scanimage -L to work)

I gave up and edited uscanner.c and usbdevs to add my CanoScan N670U to 
the kernel so that when I plug it in, it now shows up on /dev/uscanner0 
instead of /dev/ugen0

I then got scanimage -L to recognize the scanner by putting this in 
plustek.conf:
[usb] 0x04A9 0x220D
device /dev/uscanner0

bash-2.05a# scanimage -L
device `plustek:/dev/uscanner0' is a Canon N670U/N676U/LiDE20 USB flatbed 
scanner

Great! At this point the scanner works in xscanimage. I can scan and 
preview and set image quality settings. Ye-ha and thank you sane developers :)


Here's my question:
whenever I try to run scanimage or xscanimage, it takes a very long time 
before the program actually does anything, and in the mean time I get a 
lot of this:

umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT

How/where do I go about figuriung out what's wrong and how to fix it?
I would rather not have to choose between being able to scan or being able 
to use my zip drive & cf/mmc readers. (meaning I'd rather not fix the 
scanner by removing umass from the kernel)
Any ideas?

Thanks.

-- 
Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani