Hi, On 2006-02-04 15:55, Bill Brelsford wrote: > > If no, send a log file: > > SANE_DEBUG_EPSON=255 SANE_DEBUG_SANEI_USB=255 scanimage -L > > This time sane-find-scanner got "libusb:002:003". The log file:
This is not a log file, it's only the output from libusb. > USB error: could not set config 1: Device or resource busy If this happens with your scanner, it looks like some other program or kernel driver keeps it open. A normal logfile starts like this: [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such device [...] [sanei_debug] Setting debug level of epson to 255. [epson] sane_init: sane-backends 1.0.17-cvs [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [...] If you don't get any debug messages this usually means that SANE is not properly installed and the epson backend is not laoded at all. Cehcing with "SANE_DEBUG_DLL=255" may show what's wrong. On the other hand I'm surprised about the libusb debug messages in this case. Bye, Henning
