[sane-devel] Epson 640U and sane1.0.18+cvs20061127-1

[Bjoern Daehn]

Hello!

Thanks for your response.

I tried now setting "SANE_EPSON_CMD_LVL", but neither setting it to "D1" nor
unsetting it helps. It is still throwing the  out-of-memory exception:

[root at printserver root]$ SANE_DEBUG_EPSON=255 scanimage -L
[sanei_debug] Setting debug level of epson to 255.
[epson] sane_init: sane-backends 1.0.18
[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.46 - 2006-06-11
[epson] attach(, 3)
[epson] attach: opening
[epson] attach_one_usb(/dev/usb/scanner0)
[epson] SANE Epson Backend v0.2.46 - 2006-06-11
[epson] attach(/dev/usb/scanner0, 3)
[epson] attach: opening /dev/usb/scanner0
[epson] Found valid EPSON scanner: 0x4b8/0x10c (vendorID/productID)
[epson] reset()
[epson] send buf, size = 2
[epson] buf[0] 1b .
[epson] buf[1] 40 @
[epson] w_cmd_count = 1
[epson] r_cmd_count = 0
[epson] w_cmd_count = 1
[epson] r_cmd_count = 1
[epson] receive buf, expected = 1, got = 1
[epson] buf[0] 06 .
[epson] get_identity_information()
[epson] send buf, size = 2
[epson] buf[0] 1b .
[epson] buf[1] 49 I
[epson] w_cmd_count = 2
[epson] r_cmd_count = 1
[epson] w_cmd_count = 2
[epson] r_cmd_count = 2
[epson] receive buf, expected = 4, got = 4
[epson] buf[0] 02 .
[epson] buf[1] 00 .
[epson] buf[2] 13 .
[epson] buf[3] 00 .
[epson] code   02
[epson] status 00
[epson] count  19
[epson] w_cmd_count = 2
[epson] r_cmd_count = 3
[epson] receive buf, expected = 19, got = 19
[epson] buf[0] 44 D
[epson] buf[1] 31 1
[epson] buf[2] 52 R
[epson] buf[3] 4b K
[epson] buf[4] 00 .
[epson] buf[5] 52 R
[epson] buf[6] 96 .
[epson] buf[7] 00 .
[epson] buf[8] 52 R
[epson] buf[9] 2c ,
[epson] buf[10] 01 .
[epson] buf[11] 52 R
[epson] buf[12] 58 X
[epson] buf[13] 02 .
[epson] buf[14] 41 A
[epson] buf[15] ec .
[epson] buf[16] 13 .
[epson] buf[17] 7c |
[epson] buf[18] 1b .
[epson] type    D 0x44
[epson] level   1 0x31
[epson] type    D 0x44
[epson] level   1 0x31
[epson] forced
[epson] no option equipment installed
[epson] out of memory (line 5959)
...


Does that mean, that it is running out of RAM or out of memory on the
scanner?

Thanks
  /bjoern



On 28.06.2007 5:56 Uhr, "Olaf Meeuwissen" <olaf.meeuwissen at avasys.jp> wrote:

> Bjoern Daehn <bjoern at daehn-online.net> writes:
> 
>> Hello!
> 
> Hello!
> 
>> I trying to use an EPSON 640U with sane 1.0.18+cvs20061127-1.
>> 
>> The platform is a WL500gp running Oleg¹s firmware (Linux 2.4.20/mips). I
>> have sane-backend installed and ³scanner.o² module is recognizing the
>> scanner:
>> ...
>> scanner.c: USB scanner device (0x04b8/0x010c) now attached to scanner0
>> scanner.c: 0.4.16:USB Scanner Driver
>> 
>> sane-find-scanner  results:
>> ...
>> found USB scanner (vendor=0x04b8, product=0x010c) at /dev/usb/scanner0
>> ...
>> 
>> Access rights to /dev/usb/scanner0 are fine ­ a ³SANE_DEBUG_EPSON='255'
>> scanimage ­L² results:
>> 
>> [snip]
>> [epson] type    D 0x44
>> [epson] level   1 0x31
>> [epson] type     0x00
>> [epson] level   T 0x54
>> [epson] forced
> 
> Hmm, this looks suspicious.  Have you set the SANE_EPSON_CMD_LVL
> environment variable?  If so, unset it or set it to D1.  Somehow the
> backend picks up a non-existent command level setting.  Looking at the
> code (around line 5888) that only happens when that environment
> variable is set.
> 
> Hope this helps,