sane-project-website/old-archive/1999-11/0191.html

99 wiersze
4.8 KiB
HTML

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

<!-- received="Sun Nov 21 08:06:16 1999 PST" -->
<!-- sent="Sun, 21 Nov 1999 16:07:26 +0100" -->
<!-- name="Bernd Schroeder" -->
<!-- email="bernd@aquila.muc.de" -->
<!-- subject="Re: Another Microtek Phantom 636 Problem" -->
<!-- id="" -->
<!-- inreplyto="l03130300b4534f896aab@[192.168.2.2]" -->
<title>sane-devel: Re: Another Microtek Phantom 636 Problem</title>
<h1>Re: Another Microtek Phantom 636 Problem</h1>
<b>Bernd Schroeder</b> (<a href="mailto:bernd@aquila.muc.de"><i>bernd@aquila.muc.de</i></a>)<br>
<i>Sun, 21 Nov 1999 16:07:26 +0100</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#191">[ date ]</a><a href="index.html#191">[ thread ]</a><a href="subject.html#191">[ subject ]</a><a href="author.html#191">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0192.html">Bernd Schroeder: "Update of the microtek2 backend"</a>
<li> <b>Previous message:</b> <a href="0190.html">Bernd Schroeder: "Re: Microtek Scanmaker changes colors"</a>
<li> <b>In reply to:</b> <a href="0117.html">Christoph: "Re: Another Microtek Phantom 636 Problem"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hi,<br>
<p>
On Sat, Nov 13, 1999 at 06:28:24PM +0100, Christoph wrote:<br>
<i>&gt; Hi again!</i><br>
<i>&gt; </i><br>
<i>&gt; &gt;Does the scanhead at least move a little bit? If so, then it might be</i><br>
<i>&gt; &gt;that the SCSI setup is wrong. In most cases the settings for</i><br>
<i>&gt; &gt;disconnect/reconnect cause this problem.</i><br>
<i>&gt; </i><br>
<i>&gt; Yes it does, but it seems like it moves the wrong direction.</i><br>
<i>&gt; So what does it mean? Is it the aha152x driver?</i><br>
<p>
This is normal behaviour. The device starts a color calibration scan<br>
below the normal scan area.<br>
<p>
<i>&gt; Meantime it I took the advice from Douglas and patched the kernel down to</i><br>
<i>&gt; 2.2.5 but that didn't help ether.</i><br>
<i>&gt; It seems like it takes longer to crash but it still crashes :-(</i><br>
<i>&gt; </i><br>
<i>&gt; &gt;</i><br>
<i>&gt; &gt;If not, can you provide a trace with SANE_DEBUG_MICROTEK2 and</i><br>
<i>&gt; &gt;SANE_DEBUG_SANEI_SCSI set to 30 (although I fear that the last lines</i><br>
<i>&gt; &gt;of trace will be missing, if the system freezes).</i><br>
<i>&gt; </i><br>
<i>&gt; Just in case it is useful here are the last few lines before the crash:</i><br>
<i>&gt; </i><br>
<i>&gt; [microtek2] set_exposure: ms=0x8056f00</i><br>
<i>&gt; [microtek2] scsi_send_gamma: pos=0x8067de8, size=8192, word=1, color=3</i><br>
<i>&gt; [sanei_scsi] scsi_req_enter: entered 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi.issue: 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: read 36 bytes</i><br>
<i>&gt; [microtek2] scsi_set_window: ms=0x8056f00, wnd=1</i><br>
<i>&gt; [sanei_scsi] scsi_req_enter: entered 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi.issue: 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: read 36 bytes</i><br>
<i>&gt; [microtek2] scsi_read_image_info: ms=0x8056f00</i><br>
<i>&gt; [sanei_scsi] scsi_req_enter: entered 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi.issue: 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: read 52 bytes</i><br>
<i>&gt; [microtek2] scsi_read_image_info: ppl=612, bpl=1842, lines=842, remain=1550964</i><br>
<i>&gt; [microtek2] scsi_wait_for_image: ms=0x8056f00</i><br>
<i>&gt; [microtek2] scsi_read_image_status: ms=0x8056f00</i><br>
<i>&gt; [sanei_scsi] scsi_req_enter: entered 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi_req_wait: waiting for 0x804eeb8</i><br>
<i>&gt; [sanei_scsi] sanei_scsi.issue: 0x804eeb8</i><br>
<p>
This means, that the host does not get an answer from the device. Did<br>
you try to load the aha152x module with the parameters aha152x=0x140,10,7,1,1 ?<br>
IRQ and IO port might vary on your system.<br>
<p>
Bernd<br>
<p>
<pre>
--
Bernd Schroeder
Email: <a href="mailto:bernd@aquila.muc.de">mailto:bernd@aquila.muc.de</a>
PGP public key available: <a href="mailto:pgp@aquila.muc.de">mailto:pgp@aquila.muc.de</a> | Subject: send key
<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="0192.html">Bernd Schroeder: "Update of the microtek2 backend"</a>
<li> <b>Previous message:</b> <a href="0190.html">Bernd Schroeder: "Re: Microtek Scanmaker changes colors"</a>
<li> <b>In reply to:</b> <a href="0117.html">Christoph: "Re: Another Microtek Phantom 636 Problem"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>