sane-project-website/old-archive/1999-10/0067.html

67 wiersze
3.0 KiB
HTML

<!-- received="Sat Oct 9 16:47:52 1999 PDT" -->
<!-- sent="Sat, 9 Oct 1999 17:55:46 -0600 (MDT)" -->
<!-- name="Kevin Charter" -->
<!-- email="charter@cs.ualberta.ca" -->
<!-- subject="Re: SANE 1.0.1 locks up system: Linux 2.2.10, Agfa SnapScan 1236s" -->
<!-- id="19991009235551Z433429-9075+139@scapa.cs.ualberta.ca" -->
<!-- inreplyto="Pine.BSF.3.96.991007174031.14909A-100000@condor.resnet.mtu.edu" -->
<title>sane-devel: Re: SANE 1.0.1 locks up system: Linux 2.2.10, Agfa SnapScan 1236s</title>
<h1>Re: SANE 1.0.1 locks up system: Linux 2.2.10, Agfa SnapScan 1236s</h1>
<b>Kevin Charter</b> (<a href="mailto:charter@cs.ualberta.ca"><i>charter@cs.ualberta.ca</i></a>)<br>
<i>Sat, 9 Oct 1999 17:55:46 -0600 (MDT)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#67">[ date ]</a><a href="index.html#67">[ thread ]</a><a href="subject.html#67">[ subject ]</a><a href="author.html#67">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0068.html">Jean-François Straeten: "Re: releasing a backend"</a>
<li> <b>Previous message:</b> <a href="0066.html">Kevin Charter: "Re: Acer 310s?"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<i>&gt; On Mon, 4 Oct 1999, abel deuring wrote:</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; Make sure that you have the latest version of the Agfa backend</i><br>
<i>&gt; &gt; installed. There is an incompatibility between older version of the</i><br>
<i>&gt; &gt; backend and Linux kernels &gt;= 2.2.6.</i><br>
<i>&gt; </i><br>
<i>&gt; --&gt; Just tried that...it still locks up my system solid.</i><br>
<i>&gt; </i><br>
<p>
When you run xscanimage, does it start up successfully or does the<br>
machine lock up immediately? I'm wondering whether it's the sequence<br>
of commands for scanning an image that cause the problem, and whether<br>
there are some commands that cause no problems (presumably INQUIRY<br>
is fine, since find-scanner uses it).<br>
<p>
I realize that you may not get much if the machine hangs, but could<br>
you try setting the environment variable SANE_DEBUG_SNAPSCAN to<br>
5 or 10 and running scanimage or xscanimage again, piping stderr to<br>
a file? If we're lucky, the debugging output might at least<br>
show where things hang.<br>
<p>
Kevin<br>
<p>
<p>
<pre>
--
Kevin Charter
<a href="mailto:charter@cs.rice.edu">charter@cs.rice.edu</a> | charter@cs.ualberta.ca
<a href="http://www.cs.rice.edu/~charter">http://www.cs.rice.edu/~charter</a> | http://www.cs.ualberta.ca/~charter
<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="0068.html">Jean-François Straeten: "Re: releasing a backend"</a>
<li> <b>Previous message:</b> <a href="0066.html">Kevin Charter: "Re: Acer 310s?"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>