[sane-devel] sane-epkowa backend for EPSON V500

[nbi at wideopenwest.com]

Sorry, false alarm. It does work. Something seems to have gotten fouled 
up in the initial installation. I completely uninstalled sane and the 
Epson software. I then reinstalled sane 18 via a .deb package and did 
likewise for the Epson RPMs after converting to .deb packages. 
Previously I built both from source (everything built cleanly, but 
evidently didn't install right). Seems to work ok now.

nbi at wideopenwest.com wrote:
> As requested in the man page I'm reporting status.
>
> The current backend (EPKOWA SANE Backend 2.11.0 - 2008-02-07) which 
> can be downloaded from AVASYS 
> (http://avasys.jp/hp/menu000000500/hpg000000442.htm) does *not* enable 
> successful scanning for the EPSON V500 under Debian etch with kernel 
> 2.6.24.4. I have attempted installation both via alien and by building 
> from source. In both cases installation was successful but the 
> software fails at runtime. The os, 'lsusb', and 'sane-find-scanner' 
> all correctly detect the V500. However, 'scanimage' and 'iscan' fail. 
> With debugging enabled iscan fails as follows:
>
> ----------------------------------------------------------------------------------------------------------------------- 
>
> iscan
> [sanei_debug] Setting debug level of epkowa to 128.
> [epkowa] sane_init: iscan 2.11.0
> [sanei_debug] Setting debug level of sanei_usb to 128.
> [sanei_usb] sanei_usb_init: HAVE_LIBUSB
> [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or 
> directory
> usb_set_debug: Setting debugging level to 255 (on)
> usb_os_find_busses: Found 005
> usb_os_find_busses: Found 004
> usb_os_find_busses: Found 003
> usb_os_find_busses: Found 002
> usb_os_find_busses: Found 001
> usb_os_find_busses: Skipping non bus directory devices
> usb_os_find_devices: Found 001 on 005
> usb_os_find_devices: Found 001 on 004
> usb_os_find_devices: Found 001 on 003
> usb_os_find_devices: Found 001 on 002
> usb_os_find_devices: Found 003 on 001
> usb_os_find_devices: Found 002 on 001
> skipped 1 class/vendor specific interface descriptors
> usb_os_find_devices: Found 001 on 001
> error obtaining child information: Inappropriate ioctl for device
> error obtaining child information: Inappropriate ioctl for device
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
> [sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x0130) 
> interface 0  at libusb:001:003
> [sanei_usb] sanei_usb_init: device 0x1058/0x0903, interface 0 doesn't 
> look like a scanner (0/8)
> [sanei_usb] sanei_usb_init: device 0x1058/0x0903, interface 1 doesn't 
> look like a scanner (0/3)
> [sanei_usb] sanei_usb_init: device 0x1058/0x0903: no suitable interfaces
> [sanei_usb] sanei_usb_init: device 0x0000/0x0000 looks like a root hub
> [sanei_usb] sanei_usb_init: found 1 devices
> [epkowa] sane_init, ># epkowa.conf -- sample configuration for the 
> EPKOWA SANE backend<
> [epkowa] sane_init, ># Copyright (C) 2004  Olaf Meeuwissen<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, ># See sane-epkowa(5), sane-scsi(5) and 
> sane-usb(5) for details.<
> [epkowa] sane_init, ><
> [epkowa] sane_init, ># SCSI scanners can be configured simply by 
> listing the path to the<
> [epkowa] sane_init, ># device.  For example, if your system claims to 
> have a /dev/scanner<
> [epkowa] sane_init, ># SCSI device, all you have to do is uncomment 
> the following line:<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#/dev/scanner<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, ># In the interest of maintainability, most 
> installations would have<
> [epkowa] sane_init, ># /dev/scanner sym-linked to the real SCSI 
> scanner device node.<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, ># An alternative way that works for many 
> operating systems and is a<
> [epkowa] sane_init, ># little bit more generic, is to have the backend 
> probe for your SCSI<
> [epkowa] sane_init, ># scanner with the following configuration command:<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#scsi EPSON<
> [epkowa] sane_init, ><
> [epkowa] sane_init, ># On systems with libusb, the following line is 
> sufficient to get the<
> [epkowa] sane_init, ># backend to recognise your USB scanners.  It 
> presumes, however, that<
> [epkowa] sane_init, ># the scanner---more precisely, it's USB product 
> ID---is known to the<
> [epkowa] sane_init, ># backend.<
> [epkowa] sane_init, ># For all USB scanners that are officially 
> supported by this backend,<
> [epkowa] sane_init, ># this presumption is true.  A list of such 
> scanners can be found in<
> [epkowa] sane_init, ># sane-epkowa(5).<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#usb<
> [epkowa] sane_init, ><
> [epkowa] sane_init, ># For any USB scanner not known to the backend 
> (yet), you may, at your<
> [epkowa] sane_init, ># own peril(!!), force the backend to recognise 
> and use it via libusb.<
> [epkowa] sane_init, ># You can do so by the following configuration 
> command:<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#   usb <USB vendor ID> <USB product ID><
> [epkowa] sane_init, >#<
> [epkowa] sane_init, ># SEIKO EPSON's USB vendor ID is '0x04b8' 
> (without quotes).  In order<
> [epkowa] sane_init, ># to find the USB product ID, use lsusb(1) or, on 
> Linux systems, peek<
> [epkowa] sane_init, ># at the information in /proc/bus/usb/devices.<
> [epkowa] sane_init, ># A sample configuration for the Perfection 1650 
> (GT-8200), which has<
> [epkowa] sane_init, ># a product ID of 0x0110, would look as follows:<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#usb 0x04b8 0x0110<
> [epkowa] sane_init, >usb 0x04b8 0x0130<
> [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0130
> [epkowa] attach_one_usb(libusb:001:003)
> [epkowa] EPKOWA SANE Backend 2.11.0 - 2008-02-07
> [epkowa] attach(libusb:001:003, 3)
> [epkowa] attach: opening libusb:001:003
> [sanei_usb] sanei_usb_open: trying to open device `libusb:001:003'
> [sanei_usb] could not get bound driver: No data available[sanei_usb] 
> sanei_usb_open: found bulk-in endpoint (address 1)
> [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 2)
> [sanei_usb] sanei_usb_open: opened usb device `libusb:001:003' (*dn=0)
> [sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, 
> productID: 0x0130
> [sanei_usb] sanei_usb_close: closing device 0
> [epkowa] sane_init, ><
> [epkowa] sane_init, ># When not accessing your USB scanner via libusb, 
> you may need to use<
> [epkowa] sane_init, ># one of the configuration commands below or 
> commands that are almost<
> [epkowa] sane_init, ># the same.  These commands typically access the 
> scanner via a kernel<
> [epkowa] sane_init, ># scanner module.<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#usb /dev/usb/scanner0<
> [epkowa] sane_init, >#usb /dev/usbscanner0<
> [epkowa] sane_init, >#usb /dev/uscanner0<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, ># Linux had a scanner module until version 
> 2.6.2.  As of version 2.6.3<
> [epkowa] sane_init, ># libusb is your only option.  Linux' scanner 
> module can be loaded via<
> [epkowa] sane_init, ># the modprobe(8) command like so:<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#   modprobe scanner vendor=<USB vendor ID> 
> product=<USB product ID><
> [epkowa] sane_init, >#<
> [epkowa] sane_init, ># If the scanner module already knows the vendor 
> and product IDs, you<
> [epkowa] sane_init, ># do not have to specify them.  If you want to 
> have this done automa-<
> [epkowa] sane_init, ># tically every time you boot, you can add the 
> above line, except for<
> [epkowa] sane_init, ># the modprobe command itself, to your 
> /etc/modules file.<
> [epkowa] sane_init, ><
> [epkowa] sane_init, ># Although not tested with this backend, parallel 
> port scanners should<
> [epkowa] sane_init, ># be usable.  You can configure them as shown 
> below, but I do not know<
> [epkowa] sane_init, ># much about the details.  Information is welcome.<
> [epkowa] sane_init, >#<
> [epkowa] sane_init, >#pio 0x278<
> [epkowa] sane_init, >#pio 0x378<
> [epkowa] sane_init, >#pio 0x3BC<
> [epkowa] sane_get_devices()
> ----------------------------------------------------------------------------------------------------------------------- 
>
> The critical point seems to be at "[sanei_usb] could not get bound 
> driver". I don't have the usb expertise to know what that means 
> without doing further research. Any help would be greatly appreciated.
> Thanks.
>
>