[sane-devel] Umax Astra 2200 USB

Leigh Orf Leigh Orf <orf@mailbag.com>
Wed, 26 Feb 2003 17:43:54 -0500


I was happy to see the Umax Astra 2200 being supported via USB as I had
used the scsi interface before but was having problems with my scsi
card. However, I am having regular problems getting things to work. I'm
using gimp and the xsane plugin. What happens is about 98% of the image
will be read in as indicated by the progress meter (and the debug output
below) and then xsane freezes and gimp freezes and but the scanner head
goes back as if the scan had been completed succesfully.

here is the tail end of the debug output (SANE_DEBUG_SANEI_SCSI=255
SANE_DEBUG_UMAX=255). This behavior occurred with the 2.4.18 redhat
kernel as well as the stock 2.4.20 kernel, and occurs with various
settings of the following umax.conf parameters:
scsi-buffer-size-min
scsi-buffer-size-max
scsi-maxqueue


[umax] umax_reader_process: buffer of 45400 bytes read; 71505 bytes to go
[umax] umax_queue_read_image_data_req for buffer[0], length = 45400
[umax] Sending SCSI cmd 0x28 cdb len 10, param len 0, result len 45400
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax]   SCSI cmd returned 45400 bytes
[umax]   SCSI command successfully executed
[umax] umax_queue_read_image_data_req: id for buffer[0] is 0x818b570
[umax] umax_reader_process: read image data queued for buffer[0] 
[umax] umax_wait_queued_image_data for buffer[0] (id=0x818b570)
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] umax_reader_process: buffer of 45400 bytes read; 26105 bytes to go
[umax] umax_queue_read_image_data_req for buffer[0], length = 26105
[umax] Sending SCSI cmd 0x28 cdb len 10, param len 0, result len 26105
[umax] sane_read: read 4096 bytes
[umax] sane_read: read -1 bytes
[umax] sane_read: EAGAIN
[umax] error in sanei_pv8630_bulkread (got 02)
[umax] umax_queue_read_image_data_req: command returned status Error during device I/O
[umax] ERROR: umax_reader_process: unable to queue read image data request!
[umax] [umax] sane_read: read 3128 bytes
[umax] sane_read: read 0 bytes
[umax] do_cancel
[umax] killing reader_process
[umax] reader_process: terminated by signal 15
[umax] reader_process killed
[umax] trying to release scanner ...
[umax] Sending SCSI cmd 0x17 cdb len 6, param len 0, result len 0

...and then everything hangs.

Then I have to power cycle the scanner to get things to "work" again.

Sometimes I'll get 4 scans in a row to work and then twice in a row it won't.

I did read somewhere that an odd-numbered buffer caused problems with a
different scanner driver...?

Leigh

--
Leigh Orf
KG4ULP
Assistant Professor of Atmospheric Sciences
University of North Carolina
Asheville, NC 28804