[sane-devel] Still Working on HP Scanjet 5370C

[Dan McGhee]

Before I present my information, I want to apologize to this list and to 
the maintainers for my previous whining about trying to get this scanner 
working.  For some reason, known only to someone other than me, I didn't 
hook onto the debug functions of SANE until this morning.  So my 
previous questions were not informed and I didn't present anything but 
general "help me" to this list.  I apologize.

I downloaded and installed the CVS versions of both frontends and 
backends yesterday (August 6).  My symptoms are:

1.  In either 'scanimage' or 'xscanimage,' whether as root or me, I hear 
the scanner start, immediately stop, then SANE quits with "FAIL Error: 
Error during device I/O."

2.  I must cycle the power switch on the scanner for SANE to detect it 
on any following attempts to scan.

3.  I cannot exit xscanimage by using "Exit" on the file menu.  I must 
use 'CTRL-C' in the terminal from which I ran the application.

I ran 'export SANE_DEBUG_DLL=4 && export SANE_DEBUG_USB=4 && export 
SANE_DEBUG_AVISION=7 && scanimage -d avision -T'.  I received lots of 
output and I don't know which parts of it are completely relevant, but 
this is the sequence at the end:

[avision] start_scan:
[avision] start_scan: sending command. Bytes: 6
[avision] filling command to have a length of 10, was: 6
[avision] avision_usb_status: timeout 5000
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 1, status: 0
[avision] dev->scsi_buffer_size / 2: 524288
[avision] bytes_per_line: 7632, pixels_per_line: 2544
[avision] lines_per_stripe: 18, lines_per_output: 9
[avision] max_bytes_per_read: 61056, stripe_size: 137376, out_size: 68688
[avision] reader_process: total_size: 26696736
[avision] reader_process: processed_bytes: 0, total_size: 26696736
[avision] reader_process: this_read: 61056
[avision] avision_usb_status: timeout 5000
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] === Got error 9 trying to write, wrote: 0. ===
[avision] try to read status to clear the FIFO
[avision] avision_usb_status: timeout 500
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] === Got error 9 trying to read status. ===
[avision] reader_process: read_data failed with status: 9
[avision] reader_process: cleanup
[avision] release unit:
[avision] filling command to have a length of 10, was: 6
[avision] === Got error 9 trying to write, wrote: 0. ===
[avision] try to read status to clear the FIFO
[avision] avision_usb_status: timeout 500
[avision] ==> (interrupt read) going down ...
[avision] <== (interrupt read) got: 0, status: 2
[avision] === Got error 9 trying to read status. ===
[avision] reader_process: release_unit failed
[avision] reader_process: returning success
[avision] sane_read: got 0 bytes, err: 11 Resource temporarily unavailable
[avision] do_eof:
[avision] do_eof: returning 9
FAIL Error: Error during device I/O
[dll] sane_cancel(handle=0x80539b8)
[avision] sane_cancel:
[dll] sane_close(handle=0x80539b8)
[avision] sane_close:

[dll] sane_exit: exiting
[dll] sane_exit: calling backend `avision's exit function
[avision] sane_exit:
[dll] sane_exit: finished

I have the whole output but didn't attach it here for bandwidth 
reasons.  If someone has more questions about the output, I would be 
happy to supply the appropriate ( or all (: ) information.

Reading through these messages, I am now wondering whether or not I have 
a device issue or SANE issue.  There is no device in /dev.  Therefore, I 
don't know whether I need a udev rule or not.  I thought that libusb 
would take care of all of this.  Could someone hit me with the "clue bat."

Thanks,

Dan