Nakal wrote: >>And you should tell FreeBSD not to look for all LUNs of the scanner >>while it tries to detect devices on the SCSI bus. > > > Yupp, I did that too, still same. It still gets timeout. I found out that I > can scan gray pictures, because it's only one pass. It works perfectly! But > as soon as the scanner tries another pass (e.g. color mode) then it does not > react (like it forgot the last SCSI command it got). It does not freeze. The > scanner is simply idle. > > I think, sane should repeat the SCSI-command until it succeeds and gets ACK > and not just wait for ACK, because there won't come any as long as the > scanner moves back the carriage. I can directly start another scan after > pressing control+C. There is no problem, but it will always get timeout while > initializing the scan for the second pass in 3-pass mode. > > I remember that earlier (1 or 2 years ago) when I used Linux, sane worked > with > my microtek without problems.
That could be due to different timeout settings. Older versions of Sane had different SCSI command timeoit settings for different operating systems. This is meanwhile "unified" to 2 minutes, which might be too small for the Scanmaker II. IIRC, the delay between two scan passes is really long. So you could try to increase that time to 3 or 4 minutes or whatever might be appropriate. You can do this by setting the environment variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). Abel
