Thanks for the help. Here is the requested output:
root at gw:~# SANE_DEBUG_XEROX_MFP=255 SANE_DEBUG_SANEI_USB=255 scanimage -L [sanei_debug] Setting debug level of xerox_mfp to 255. [xerox_mfp] sane_init: Xerox backend (build 12), version != null, authorize != null [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: marking existing devices [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory [sanei_usb] sanei_usb_init: Looking for libusb devices usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 007 on 001 usb_os_find_devices: Found 006 on 001 usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 001 usb_os_find_devices: Found 003 on 001 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device [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 [sanei_usb] sanei_usb_init: device 0x051d/0x0002, interface 0 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x051d/0x0002: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x0781/0x5566, interface 0 doesn't look like a scanner (0/8) [sanei_usb] sanei_usb_init: device 0x0781/0x5566: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x1a40/0x0101, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x1a40/0x0101: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x1a40/0x0201, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x1a40/0x0201: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x1d6b/0x0002, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x1d6b/0x0002: no suitable interfaces [sanei_usb] sanei_usb_init: found 2 devices [sanei_usb] sanei_usb_init: device 00 is libusb:001:007 [sanei_usb] sanei_usb_init: device 01 is libusb:001:006 [xerox_mfp] sane_xerox_mfp_get_devices: 0x7fb2f410, 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:~# So, the line: [sanei_usb] sanei_usb_find_devices: vendor=0x04e8, product=0x342e is referring to the scanner, but it does not seem to do anything with it. Rogan On 01/06/2012 22:03, m. allan noah wrote: > Nevermind- I got your two debugging outputs mixed up. > > try increasing the USB debugging to 255, and use scanimage -L > > allan > > On Fri, Jun 1, 2012 at 4:01 PM, m. allan noah<kitno455 at gmail.com> wrote: >> Try: >> >> SANE_DEBUG_DLL=255 scanimage -L >> >> and lets see why xerox_mfp is not called. >> >> allan >> >> On Fri, Jun 1, 2012 at 3:34 PM, Rogan Dawes<rogan at dawes.za.net> wrote: >>> 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:/# >>>> >>>> >>> >>> >>> -- >>> sane-devel mailing list: sane-devel at lists.alioth.debian.org >>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel >>> Unsubscribe: Send mail with subject "unsubscribe your_password" >>> to sane-devel-request at lists.alioth.debian.org >> >> >> >> -- >> "The truth is an offense, but not a sin" > > >
