I previously wrote:
<quote>
"Last night scanimage was working great. This morning I keep getting the scsi_read: snapscan_cmd command failed: Error during device I/O
scanimage: sane_read: Error during device I/O
error.
I have tried different settings, etc. Xscanimage locks up upon changing the mode from Colour to anything else. I am guessing that this is something to do with the scanimage problems.
I have a text file with the output of scanimage in SANE_DEBUG_SNAPSCAN=255 mode, at http://playstation.webhostme.com/other/snapscan_debug_output.txt
I have had this scanner working great under sane 1.0.1, but 1.0.4 seems to be a bit of a problem. It is an Acer 640U. I am using the CVS snapscan backend which included support for this scanner.
I noticed that in this version of the snapscan backend that if the scanner outputs FlatbedScanner13 that the PRISA620 is selected. When everything was working before, the older snapscan backend selected SNAPSCAN600 on a FlatbedScanner13. I would have changed this to begin with, but I read in the archives of this list that there were some color alignment problems with the old backend.
I am not sure if this makes a difference, but the firmware that works for me is called U96V121.BIN. This is different from most people with an acer 6**U* scanner. ie, 620U, 640UT, etc."
</quote>
I tried changing snapscan.c to point to SNAPSCAN600 when FlatbedScanner13 came up, but it did not help.
I have been continually repeating these steps to get some sort of feeling for what the errors going on is. 1. rmmod scanner, 2. powering off scanner, 3. power on scanner. 4.modprobe scanner. 5. export SANE_DEBUG_SNAPSCANN 6. upload firmware 7. scanimage --resolution 75 --mode LineArt --predef-window 8.5x11 > pic.pnm.
I can here scanner movement, and I notice that the bulb positions itself in the proper location to start scanning but, then the scanimage freezes. Eventually the device I/O error is thrown.
If I shut the scanner off and turn it on again, The bulb then moves slowly as if it were scanning. sometimes I can't rmmod scanner, saying scanner: Device or resource busy. System does not lock-up but rebooting the system is the only way to remove scanner module.
If there is anything else I can tell you let, me know.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Thu Jan 25 2001 - 16:44:43 PST