On 01/06/2012 17:08, ABC wrote: > Your logs does not show communication of driver with the device. > If you able to change that, do not even touch sane-find-scanner, > concentrate on scanimage -L. > > -abc
I'm not sure what you mean by this. I really want to "change that", and I am asking for help in figuring out *how* to change it. I assume there is a "if" statement of some sort that is failing, and I'm hoping someone can help me figure out how to fix it. Would strace output help, perhaps? Rogan > > On Thu, May 31, 2012 at 05:23:19PM +0200, Rogan Dawes wrote: >> scanimage -L, however, fails to identify this device: >> >> root at gw:/# SANE_DEBUG_XEROX_MFP=128 SANE_DEBUG_SANEI_USB=4 scanimage -L >> [sanei_debug] Setting debug level of xerox_mfp to 128. >> [xerox_mfp] sane_init: Xerox backend (build 12), version != null, >> authorize != null >> [sanei_debug] Setting debug level of sanei_usb to 4. >> [sanei_usb] sanei_usb_init: marking existing devices >> [sanei_usb] sanei_usb_init: Looking for kernel scanner devices >> [sanei_usb] sanei_usb_init: Looking for libusb devices >> [sanei_usb] sanei_usb_init: found libusb device (0x067b/0x2303) >> interface 0 at libusb:001:007 >> [sanei_usb] store_device: add dn 0 with libusb:001:007 >> [sanei_usb] sanei_usb_init: found libusb device (0x04e8/0x342e) >> interface 0 at libusb:001:006 >> [sanei_usb] store_device: add dn 1 with libusb:001:006 >> [xerox_mfp] sane_xerox_mfp_get_devices: 0x7fcb5f60, 0 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04e8, product=0x342e >> [xerox_mfp] list_one_device: libusb:001:006 >> >> No scanners were identified. If you were expecting something different, >> check that the scanner is plugged in, turned on and detected by the >> sane-find-scanner tool (if appropriate). Please read the documentation >> which came with this software (README, FAQ, manpages). >> root at gw:/# >
