[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]



ich habe mir einen Epson V200 Photo Scanner gekauft und versuche den
epkowa-Treiber von Epson/Avasys zu nutzen. Das Sane-backend-extras-Paket
habe ich vorher deinstalliert. Das Problem ist, dass sane-find-scanner den Scanner
findet, scanimage -L aber nicht. Ich nutze ein Debian Testing Amd64 System.
Hat jemand eine Idee?

[sanei_debug] Setting debug level of dll to 128.
[dll] sane_init: SANE dll backend version 1.0.12 from sane-backends 1.0.18-cvs
[dll] sane_init/read_dlld: processing /etc/sane.d/dll.d ...
[dll] sane_init/read_dlld: done.
[dll] sane_init/read_config: reading dll.conf
[dll] add_backend: adding backend `epkowa'
[dll] sane_get_devices
[dll] load: searching backend `epkowa' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-epkowa.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-epkowa.so.1'
[dll] init: initializing backend `epkowa'
[sanei_debug] Setting debug level of epkowa to 128.
[epkowa] sane_init: iscan 2.8.0
[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] attach_one_usb()
[epkowa] EPKOWA SANE Backend 2.8.0 - 2007-03-07
[epkowa] attach(, 3)
[epkowa] attach: opening
[epkowa] attach_one_usb(libusb:011:006)
[epkowa] EPKOWA SANE Backend 2.8.0 - 2007-03-07
[epkowa] attach(libusb:011:006, 3)
[epkowa] attach: opening libusb:011:006
[epkowa] attach_one_usb(libusb:011:006)
[epkowa] EPKOWA SANE Backend 2.8.0 - 2007-03-07
[epkowa] attach(libusb:011:006, 3)
[epkowa] attach: opening libusb:011:006
[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 0x012e<
[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<
[dll] init: backend `epkowa' is version 1.0.208
[epkowa] sane_get_devices()
[dll] sane_get_devices: found 0 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).
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `epkowa's exit function
[epkowa] sane_exit
[dll] sane_exit: finished


Reply to: