[sane-devel] intel OSX10.4.10 + epson 1660

Mattias Ellert mattias.ellert at tsl.uu.se
Mon Sep 17 13:46:16 UTC 2007


mån 2007-09-17 klockan 14:25 +0100 skrev Rob Thomas:
> Here's the SANE_DEBUG_EPSON=255 scanimage -L
> [sanei_debug] Setting debug level of epson to 255.
> [epson] sane_init: sane-backends 1.0.18-cvs
> [epson] sane_init, ># epson.conf<
> [epson] sane_init, >#<
> [epson] sane_init, ># here are some examples for how to configure the
> EPSON backend<
> [epson] sane_init, >#<
> [epson] sane_init, ># SCSI scanner:<
> [epson] sane_init, >scsi EPSON<
> [epson] sane_init, ># for the GT-6500:<
> [epson] sane_init, >scsi "EPSON SC"<
> [epson] sane_init, >#<
> [epson] sane_init, ># Parallel port scanner:<
> [epson] sane_init, >#pio 0x278<
> [epson] sane_init, >#pio 0x378<
> [epson] sane_init, >#pio 0x3BC<
> [epson] sane_init, >#<
> [epson] sane_init, ># USB scanner:<
> [epson] sane_init, ># There are two different methods of configuring a
> USB scanner: libusb and the kernel module<
> [epson] sane_init, ># For any system with libusb support (which is
> pretty much any recent Linux distribution) the<
> [epson] sane_init, ># following line is sufficient. This however
> assumes that the connected scanner (or to be more<
> [epson] sane_init, ># accurate, it's device ID) is known to the backend.<
> [epson] sane_init, >usb<
> [epson] attach_one_usb()
> [epson] SANE Epson Backend v0.2.47 - 2006-08-21
> [epson] attach(, 3)
> [epson] attach: opening
> [epson] attach_one_usb(libusb:005:002-04b8-011e-ff-ff)
> [epson] SANE Epson Backend v0.2.47 - 2006-08-21
> [epson] attach(libusb:005:002-04b8-011e-ff-ff, 3)
> [epson] attach: opening libusb:005:002-04b8-011e-ff-ff
> [epson] sane_init, ># For libusb support for unknown scanners use the
> following command<
> [epson] sane_init, ># usb <product ID> <device ID><
> [epson] sane_init, ># e.g.:<
> [epson] sane_init, >usb 0x4b8 0x11e<
> [epson] attach_one_usb(libusb:005:002-04b8-011e-ff-ff)
> [epson] SANE Epson Backend v0.2.47 - 2006-08-21
> [epson] attach(libusb:005:002-04b8-011e-ff-ff, 3)
> [epson] attach: opening libusb:005:002-04b8-011e-ff-ff
> [epson] sane_init, ># And for the scanner module, use the following
> configuration:<
> [epson] sane_init, >#usb /dev/usbscanner0<
> [epson] sane_init, >#usb /dev/usb/scanner0<
> [epson] sane_get_devices()
> 
> 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).
> 
> Rob.

You are attaching the scanner to the backend twice. Both the general
"usb" line in the config file that scans a list of hardcoded usb ids in
the backend and your explicit "usb 0x4b8 0x11e" match your scanner. As a
result sane_init is sent twice to the scanner, which screws things up.
Try removing or commenting out one of the two lines.

	Mattias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 1230 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070917/01b76163/attachment.bin 


More information about the sane-devel mailing list