sane-project-website/old-archive/1998-03/0149.html

<!-- received="Sat Mar 21 10:02:10 1998 PST" -->
<!-- sent="Sat, 21 Mar 1998 19:01:58 +0100" -->
<!-- name="Dr. Andreas Bolsch" -->
<!-- email="a.bolsch@ic.ac.uk" -->
<!-- subject="non-Linux &amp; Mustek ScanExpress" -->
<!-- id="35140096.D6478B37@ic.ac.uk" -->
<!-- inreplyto="" -->
<title>sane-devel: non-Linux &amp; Mustek ScanExpress</title>
<h1>non-Linux &amp; Mustek ScanExpress</h1>
<b>Dr. Andreas Bolsch</b> (<a href="mailto:a.bolsch@ic.ac.uk"><i>a.bolsch@ic.ac.uk</i></a>)<br>
<i>Sat, 21 Mar 1998 19:01:58 +0100</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#149">[ date ]</a><a href="index.html#149">[ thread ]</a><a href="subject.html#149">[ subject ]</a><a href="author.html#149">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0150.html">Hugo van der Kooij: "Re: Drivers..."</a>
<li> <b>Previous message:</b> <a href="0148.html">Justin Clay: "Acer scanners"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0158.html">Arjen Schoneveld: "Re: non-Linux &amp; Mustek ScanExpress"</a>
<li> <b>Reply:</b> <a href="0158.html">Arjen Schoneveld: "Re: non-Linux &amp; Mustek ScanExpress"</a>
<li> <b>Reply:</b> <a href="0160.html">Dr. Andreas Bolsch: "Re: non-Linux &amp; Mustek ScanExpress"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
This is a multi-part message in MIME format.<br>
--------------6C116EAF2ADC05C9C2FD0164<br>
Content-Type: text/plain; charset=us-ascii<br>
Content-Transfer-Encoding: 7bit<br>
<p>
Does anybody have experience with a Mustek ScanExpress on a non-Linux<br>
system? On my Linux box the ScanExpress 12000SP is connected via<br>
the DTCT436 card shipped with scanner. The scanner is detected and<br>
reacts (to some extent) to the SCSI commands. <br>
<p>
After twiddling around with the backend (sane-0.70) I am now convinced<br>
that the command set (Thanks, David!) of the scanner itself is not the<br>
real problem. <br>
<p>
There seems to be a flaw in the SCSI driver on either side because<br>
after mode_select a get_image_status just echoes the parameters of<br>
the previous mode_select. I tried several weird numbers as parameters<br>
for mode_select, always the same effect. Without a request_sense<br>
between the commands it becomes even worse. Probably a timing or<br>
handshake problem. Used kernel 2.0.32 and mustek patch.<br>
<p>
Debug output:<br>
--------------6C116EAF2ADC05C9C2FD0164<br>
Content-Type: text/plain; charset=us-ascii; name="debug"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline; filename="debug"<br>
<p>
[sanei_init_debug]: Setting debug level of mustek to 128.<br>
[mustek] attach: opening /dev/scanner as scsi device<br>
[sanei_init_debug]: Setting debug level of sanei_scsi to 128.<br>
[mustek] attach: sending INQUIRY<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
12  00  00  00  60  00  <br>
<p>
bytes read:<br>
06  00  01  01  5B  01  00  00  53  43  41  4E  4E  45  52  20  20  20  20  20  20  20  20  20  20  20  20  20  20  20  20  20  31  2E  30  31  4D  55  53  54  45  4B  20  20  20  43  30  36  20  53  31  32  49  44  57  4D  31  32  33  37  31  37  01  00  01  03  01  01  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  FF  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 132 bytes<br>
[mustek] scsi_wait_ready: sending TEST_UNIT_READY<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
00  00  00  00  00  00  <br>
<p>
bytes read:<br>
<p>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[mustek] scsi_wait_ready: unit signaled READY<br>
[mustek] attach: firmware revision 1.01<br>
[mustek] attach: scanner has automatic line-distance correction<br>
[mustek] attach: found Mustek scanner model  C06 S12IDW (flatbed scanner), 1-pass<br>
[sanei_init_debug]: Setting debug level of sanei_scsi to 128.<br>
[mustek] scsi_wait_ready: sending TEST_UNIT_READY<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
00  00  00  00  00  00  <br>
<p>
bytes read:<br>
<p>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[mustek] scsi_wait_ready: unit signaled READY<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
04  00  00  00  12  00  08  00  00  00  00  74  12  74  12  88  00  00  00  00  74  12  74  12  <br>
<p>
bytes read:<br>
<p>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
03  00  00  00  04  00  <br>
<p>
bytes read:<br>
00  00  00  00  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 40 bytes<br>
[mustek] request_sense: got error code 00<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
15  00  00  00  0D  00  8B  00  00  00  05  72  00  00  00  00  00  1E  00  <br>
<p>
bytes read:<br>
<p>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
03  00  00  00  04  00  <br>
<p>
bytes read:<br>
00  00  00  00  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 40 bytes<br>
[mustek] request_sense: got error code 00<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
03  00  00  00  04  00  <br>
<p>
bytes read:<br>
00  00  00  00  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 40 bytes<br>
[mustek] request_sense: got error code 00<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
1B  00  00  00  41  00  <br>
<p>
bytes read:<br>
<p>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
03  00  00  00  04  00  <br>
<p>
bytes read:<br>
00  00  00  00  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 40 bytes<br>
[mustek] request_sense: got error code 00<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
03  00  00  00  04  00  <br>
<p>
bytes read:<br>
00  00  00  00  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 40 bytes<br>
[mustek] request_sense: got error code 00<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
11  00  00  00  05  00  <br>
<p>
bytes read:<br>
00  00  00  00  05  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 41 bytes<br>
[mustek] line_distance: got factor=0, (r/g/b)=(0/0/5)<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
03  00  00  00  04  00  <br>
<p>
bytes read:<br>
00  00  00  00  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 40 bytes<br>
[mustek] request_sense: got error code 00<br>
[sanei_scsi] scsi_req_enter: entered 0x805a210<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x805a210<br>
[sanei_scsi] sanei_scsi.issue: 0x805a210<br>
bytes written:<br>
0F  00  00  00  06  00  <br>
<p>
bytes read:<br>
00  00  00  00  05  72  <br>
<p>
[sanei_scsi] sanei_scsi_req_wait: read 42 bytes<br>
[mustek] get_image_status: bytes_per_line=0, lines=7472384<br>
./scan: line 5:  5128 Floating point exceptionfrontend/scanimage -v -d mustek:/dev/scanner -x 100 -y 100 --res 30 --mode Gray<br>
<p>
--------------6C116EAF2ADC05C9C2FD0164--<br>
<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="0150.html">Hugo van der Kooij: "Re: Drivers..."</a>
<li> <b>Previous message:</b> <a href="0148.html">Justin Clay: "Acer scanners"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0158.html">Arjen Schoneveld: "Re: non-Linux &amp; Mustek ScanExpress"</a>
<li> <b>Reply:</b> <a href="0158.html">Arjen Schoneveld: "Re: non-Linux &amp; Mustek ScanExpress"</a>
<li> <b>Reply:</b> <a href="0160.html">Dr. Andreas Bolsch: "Re: non-Linux &amp; Mustek ScanExpress"</a>
<!-- reply="end" -->
</ul>