On Tue, 23 Nov 2010, Mattieu Baptiste wrote: > On Tue, Nov 23, 2010 at 10:51 PM, Miod Vallat <m...@online.fr> wrote: > > > Could this be caused by changes in the kernel and/or in xsane? Did you > > try e.g. an older xsane against a kernel which attaches your hardware as > > uscanner, and against a kernel with the uscanner.c chunk reverted? > > In fact, if my memory serves me right, I've never been able to use my > scanner with uscanner (I have this device since years). > > I always had to "disable uscanner" at boot time, let the device attach > as ugen, and run xsane. Then xsane works like a charm. <...>
Yes, this is the prefered way to do it. And xsane had nothing to do with it, libsane from sane-backends is what is accessing your device. At one point, the best would be to remove uscanner entirely as it's impossible to keep track of all devices anyway. IIRC at least Linux and FreeBSD now use libusb with sane for scanning (which is what you are doing when you "disable uscanner"). Cheers! -- Antoine
