sane-project-website/old-archive/1999-03/0007.html

76 wiersze
3.6 KiB
HTML

<!-- received="Mon Mar 1 08:24:10 1999 PST" -->
<!-- sent="Mon, 01 Mar 1999 09:20:15 +0100" -->
<!-- name="Rainer Krienke" -->
<!-- email="krienke@uni-koblenz.de" -->
<!-- subject="SCSI-Tomeout since Linux Kernel 2.2" -->
<!-- id="" -->
<!-- inreplyto="" -->
<title>sane-devel: SCSI-Tomeout since Linux Kernel 2.2</title>
<h1>SCSI-Tomeout since Linux Kernel 2.2</h1>
<b>Rainer Krienke</b> (<a href="mailto:krienke@uni-koblenz.de"><i>krienke@uni-koblenz.de</i></a>)<br>
<i>Mon, 01 Mar 1999 09:20:15 +0100</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#7">[ date ]</a><a href="index.html#7">[ thread ]</a><a href="subject.html#7">[ subject ]</a><a href="author.html#7">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0008.html">John Garrison: "Re: SCSI not detected"</a>
<li> <b>Previous message:</b> <a href="0006.html">Wolfgang Goeller: "Re: Snapscan 310"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hello,<br>
<p>
since quite a long time I am successfully using sane to work with my<br>
mustek scanner connected to my one one and only ADAPTEC 2940 controller.<br>
Until now I ran kernel 2.0.36 on my machine. In order to avoid to much<br>
backtracking I used a static buffer for the sg scsi devices of a size of<br>
about 1MByte by patching the sg.c and sg.h files in the kernel sources.<br>
This way scanning used to work fine without (SCSI) problems. <br>
<p>
Lately I "upgraded" my kernel to release 2.2.2. I changed the files sg.c<br>
and sg.h in order to support a larger SG_BIG_BUFFER like I had done in<br>
Version 2.0.36 before (the patch was actually a little different from<br>
that for kernel 2.0.36).<br>
Basically it works just fine. However since the new kernel, without any<br>
other change neither to the system nor to the sane software, I sometimes<br>
experience SCSI timeouts when scanning. I know that I could avoid this<br>
by setting the strip-height parameter to a small value, but that again<br>
would lead to to much undesired backtracking. <br>
<p>
Since the SCSI resets occur only since kernel 2.2 and nothing else has<br>
changed, I guess that there must be a timeout parameter in the kernel<br>
(driver) sources that has changed. I searched a little around in the<br>
driver (aic7xxx) for my controller but did not find any obvious<br>
parameter that could help. Does anyone else know if such a parameter<br>
exists or what else I might do to avoid those timeouts without<br>
increasing backtacking? Did anyone else observe a similar behaviour when<br>
changing from an older kernel to the 2.2 release?<br>
<p>
Thank you very much<br>
Rainer Krienke<br>
<pre>
--
---------------------------------------------------------------------
Rainer Krienke <a href="mailto:krienke@uni-koblenz.de">krienke@uni-koblenz.de</a>
Universitaet Koblenz, <a href="http://www.uni-koblenz.de/~krienke">http://www.uni-koblenz.de/~krienke</a>
Rechenzentrum, Voice: +49 261 287 - 1312
Rheinau 1, 56075 Koblenz, Germany Fax: +49 261 287 - 1355
---------------------------------------------------------------------
<p>
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0008.html">John Garrison: "Re: SCSI not detected"</a>
<li> <b>Previous message:</b> <a href="0006.html">Wolfgang Goeller: "Re: Snapscan 310"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>