| 1 |
On 12/18/05, Richard Fish <bigfish@××××××××××.org> wrote: |
| 2 |
> On 12/17/05, smoke3 <smoke3@×××××.com> wrote: |
| 3 |
> > Hello all, |
| 4 |
> > I've got a CX5400 EPSON All-in-One printer/scanner. |
| 5 |
> > |
| 6 |
> > I tried to configure sane-backends in order to get it working on my |
| 7 |
> > 2.6.14-gentoo (amd 64), but I think I'm doing something wrong. |
| 8 |
> > That is, when I type: |
| 9 |
> > # sane-find-scanner -q |
| 10 |
> > |
| 11 |
> > I get: |
| 12 |
> > found USB scanner (vendor=0x04b8 [EPSON], product=0x0808 [USB MFP]) at |
| 13 |
> > libusb:002:003 |
| 14 |
> > |
| 15 |
> > But, after configuring /etc/sane.d/epkowa.conf with |
| 16 |
> > usb 0x04b8 0x0808 |
| 17 |
> |
| 18 |
> According to the sane project, the CX5400 should be using the epson |
| 19 |
> backend, not epkowa: |
| 20 |
|
| 21 |
NO WAY though... |
| 22 |
I tried the same with epson backend, but |
| 23 |
# SANE_DEBUG_EPSON=128 scanimage -L |
| 24 |
|
| 25 |
still gives the same output as epkowa does: |
| 26 |
[sanei_debug] Setting debug level of epson to 128. |
| 27 |
[epson] sane_init: sane-backends 1.0.16 |
| 28 |
[epson] sane_init, ># epson.conf< |
| 29 |
[epson] sane_init, >#< |
| 30 |
[epson] sane_init, ># here are some examples for how to configure the EPSON |
| 31 |
backend< |
| 32 |
[epson] sane_init, >#< |
| 33 |
[epson] sane_init, ># SCSI scanner:< |
| 34 |
[epson] sane_init, >#scsi EPSON< |
| 35 |
[epson] sane_init, ># for the GT-6500, comment out the previous line and |
| 36 |
uncomment the following line:< |
| 37 |
[epson] sane_init, >#scsi< |
| 38 |
[epson] sane_init, >#< |
| 39 |
[epson] sane_init, ># Parallel port scanner:< |
| 40 |
[epson] sane_init, >#pio 0x278< |
| 41 |
[epson] sane_init, >#pio 0x378< |
| 42 |
[epson] sane_init, >#pio 0x3BC< |
| 43 |
[epson] sane_init, >#< |
| 44 |
[epson] sane_init, ># USB scanner:< |
| 45 |
[epson] sane_init, ># There are two different methods of configuring a USB |
| 46 |
scanner: libusb and the kernel module< |
| 47 |
[epson] sane_init, ># For any system with libusb support (which is pretty |
| 48 |
much any recent Linux distribution) the< |
| 49 |
[epson] sane_init, ># following line is sufficient. This however assumes |
| 50 |
that the connected scanner (or to be more< |
| 51 |
[epson] sane_init, ># accurate, it's device ID) is known to the backend.< |
| 52 |
[epson] sane_init, >usb 0x4b8 0x808< |
| 53 |
[epson] attach_one_usb(libusb:002:002) |
| 54 |
[epson] SANE Epson Backend v0.2.45 - 2000-01-09 |
| 55 |
[epson] attach(libusb:002:002, 3) |
| 56 |
[epson] attach: opening libusb:002:002 |
| 57 |
[epson] sane_init, ># For libusb support for unknown scanners use the |
| 58 |
following command< |
| 59 |
[epson] sane_init, ># usb <product ID> <device ID>< |
| 60 |
[epson] sane_init, ># e.g.:< |
| 61 |
[epson] sane_init, ># And for the scanner module, use the following |
| 62 |
configuration:< |
| 63 |
[epson] sane_init, >#usb /dev/usbscanner0< |
| 64 |
[epson] sane_init, >#usb /dev/usb/scanner0< |
| 65 |
[epson] sane_get_devices() |
| 66 |
|
| 67 |
No scanners were identified. If you were expecting something different, |
| 68 |
check that the scanner is plugged in, turned on and detected by the |
| 69 |
sane-find-scanner tool (if appropriate). Please read the documentation |
| 70 |
which came with this software (README, FAQ, manpages). |
| 71 |
|
| 72 |
Any other idea on what's going wrong? |
| 73 |
Thanks, |
| 74 |
S.G. |
| 75 |
|
| 76 |
-- |
| 77 |
You can't learn what you think you know. |
Archives