sane-project-website/old-archive/1997-10/0105.html

247 wiersze
10 KiB
HTML

<!-- received="Sat Oct 18 00:35:48 1997 MST" -->
<!-- sent="Sat, 18 Oct 1997 09:34:20 +0200 (MET DST)" -->
<!-- name="Klaus Weglehner" -->
<!-- email="klaus@amsys.nbg.sub.org" -->
<!-- subject="Re: Mustek600IICD / lost lines" -->
<!-- id="199710180734.JAA15611@amsys.nbg.sub.org" -->
<!-- inreplyto="199710180537.WAA00586@panda.mostang.com" -->
<title>sane-devel: Re: Mustek600IICD / lost lines</title>
<h1>Re: Mustek600IICD / lost lines</h1>
<b>Klaus Weglehner</b> (<a href="mailto:klaus@amsys.nbg.sub.org"><i>klaus@amsys.nbg.sub.org</i></a>)<br>
<i>Sat, 18 Oct 1997 09:34:20 +0200 (MET DST)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#105">[ date ]</a><a href="index.html#105">[ thread ]</a><a href="subject.html#105">[ subject ]</a><a href="author.html#105">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0106.html">Oliver.Rauch@Wolfsburg.DE: "Re: umax-backend"</a>
<li> <b>Previous message:</b> <a href="0104.html">David Mosberger-Tang: "Re: Mustek600IICD / lost lines"</a>
<li> <b>In reply to:</b> <a href="0104.html">David Mosberger-Tang: "Re: Mustek600IICD / lost lines"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hello David!<br>
------------<br>
<p>
<i>&gt; This appears to be a feature of newer firmware revisions. If SANE</i><br>
<i>&gt; recognizes your scanner, you should be OK, though.</i><br>
<p>
The Firmware is 2.03. Perhaps I should send you the complete output<br>
of the SCSI initialization too:<br>
<p>
&lt;4&gt;Started kswapd v 1.4.2.2 <br>
&lt;6&gt;FDC 0 is an 8272A<br>
&lt;4&gt;aha152x: processing commandline: ok<br>
&lt;4&gt;aha152x: BIOS test: passed, detected 1 controller(s)<br>
&lt;4&gt;aha152x0: vital data: PORTBASE=0x340, IRQ=12, SCSI ID=7, reconnect=disabled, parity=disabled,<br>
synchronous=disabled, delay=100, extended translation=disabled<br>
&lt;4&gt;aha152x: trying software interrupt, ok.<br>
&lt;4&gt;scsi0 : Adaptec 152x SCSI driver; $Revision: 1.18 $<br>
&lt;4&gt;scsi : 1 host.<br>
&lt;4&gt; Vendor: SCANNER Model: Rev: 2.03<br>
&lt;4&gt; Type: Scanner ANSI SCSI revision: 01 CCS<br>
&lt;4&gt;Detected scsi generic sga at scsi0, channel 0, id 0, lun 0<br>
&lt;4&gt;scsi : detected total.<br>
&lt;6&gt;SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).<br>
<p>
Is it ok?<br>
<p>
<i>&gt; </i><br>
<i>&gt; Klaus&gt; I tried to scan a</i><br>
<i>&gt; Klaus&gt; LineArt picture and everything seems to work well. But when I</i><br>
<i>&gt; Klaus&gt; tried to scan Color or even Grayscale pictures the scanner</i><br>
<i>&gt; Klaus&gt; mechanic moves to its physical end and makes the well known</i><br>
<i>&gt; Klaus&gt; sound which is described in the PROBLEMS file. I can limit</i><br>
<i>&gt; Klaus&gt; the scaning area to a non-dangerous value, but the image</i><br>
<i>&gt; Klaus&gt; seems to be compressed in y-direction and the scaning range</i><br>
<i>&gt; Klaus&gt; was always more than I have specified on the</i><br>
<i>&gt; Klaus&gt; comandline.</i><br>
<i>&gt; </i><br>
<i>&gt; That's strange. It appears as if the line-distance command does not</i><br>
<i>&gt; get issued. If you run sane-0.66, make sure that "option</i><br>
<i>&gt; linedistance-fix" is turned on (if you use the default mustek.conf,</i><br>
<i>&gt; you should be fine, but verify to be sure: it's in</i><br>
<i>&gt; /usr/local/etc/sane.d/mustek.conf).</i><br>
<p>
Yes, it's turned on. The file looks like this:<br>
(Btw: why comes the default file with several spaces in front of the option<br>
commands so that the driver does not recognize it?)<br>
<p>
<i>|# See sane-mustek(5) for documentation.</i><br>
<i>|</i><br>
<i>|option strip-height 1</i><br>
<i>|</i><br>
<i>|/dev/scanner</i><br>
<i>|option linedistance-fix</i><br>
<i>|option lineart-fix # lineart may be faster with this option off.</i><br>
<p>
<i>&gt; If you have the linedistance-fix on and it still doesn't work, can you</i><br>
<i>&gt; invoke scanimage with environment variable SANE_DEBUG_MUSTEK set to</i><br>
<i>&gt; 255 and send me the output you get?</i><br>
<p>
Yep, comes at the end of the mail.<br>
<p>
<i>&gt; Klaus&gt; A tip how to get the Adaptec 1505 with the supplied</i><br>
<i>&gt; Klaus&gt; Windows-Twain-Driver working would be very useful too.</i><br>
<i>&gt; Hmmh, sane-scsi(5) lists the Adaptec AHA-1505 to be working fine. I'm</i><br>
<i>&gt; not familiar with that adapter, but if it has some sort of BIOS</i><br>
<i>&gt; configuration, you may have to disable synchronous transfers, tagged</i><br>
<i>&gt; queueing, and target disconnects (as documented in sane-mustek(5)).</i><br>
<i>&gt; If you get it working, please let me know what you had to do so I can</i><br>
<i>&gt; add it to the man page.</i><br>
It has no bios. But I made the configuration shown in the SCSI<br>
startup at the begining of this mail via lilo append line and I<br>
think it's ok. The only thing I'm in doubt is the tagged queueing.<br>
There is no kernel comandline option to turn it off and on. I<br>
tried to set a DEFINE in aha152x.h to zero which says something about<br>
the number of queueable commands. But I don't know whether this define<br>
really means TAGGED queuing or queuing at all. (I don't know if there<br>
is a difference) However, the behaviour has not changed since.<br>
<p>
Ok, here comes the debug output:<br>
The comand was:<br>
scanimage -l90 -x20 -y30 --resolution 600 &gt;test.pnm 2&gt;debug.txt<br>
<p>
[sanei_init_debug]: Setting debug level of mustek to 255.<br>
[mustek] sane_init: strip-height set to 1 inches<br>
[mustek] attach: opening /dev/scanner<br>
[mustek] attach: sending INQUIRY<br>
[mustek] wait_ready: sending TEST_UNIT_READY<br>
[mustek] attach: firmware revision 2.03<br>
[mustek] attach: found Mustek scanner model MFC-06000CZ (flatbed scanner), 1-pass<br>
[mustek] sane_init: enabling linedistance-fix for /dev/scanner<br>
[mustek] sane_init: enabling lineart-fix for /dev/scanner<br>
[mustek] wait_ready: sending TEST_UNIT_READY<br>
[mustek] line_distance: got factor=65535, (r/g/b)=(0/4/8)<br>
[mustek] line_distance: fixed up to factor=65535, (r/g/b)=(0/4/8)<br>
^^^^^<br>
Is this ok?<br>
<p>
[mustek] get_image_status: bytes_per_line=470, lines=710<br>
[mustek] lines_per_buffer=277, bytes_per_line=470<br>
[mustek] reader_process: line=554 (num_lines=710), num_reqs=2<br>
[mustek] reader_process.send_data: data=0x80fb000, lpb=277, bpl=470, extra=0x813b000<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] reader_process: line=710 (num_lines=710), num_reqs=2<br>
[mustek] reader_process.send_data: data=0x811ac8e, lpb=277, bpl=470, extra=0x813b000<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] reader_process: line=710 (num_lines=710), num_reqs=1<br>
[mustek] reader_process.send_data: data=0x80fb000, lpb=156, bpl=470, extra=0x813b000<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] read 4096 bytes<br>
[mustek] reader_process: line=710 (num_lines=710), num_reqs=0<br>
[mustek] read 4096 bytes<br>
[mustek] read 1924 bytes<br>
[mustek] read 0 bytes<br>
[mustek] do_stop: terminating reader process<br>
[mustek] do_stop: reader process terminated with status 0x0<br>
[mustek] do_stop: closing scanner<br>
<p>
A note about the windows driver of the Controller:<br>
They deliver a Lite-Version of the driver with the card. But<br>
for scanning with the TWAIN driver which comes with the<br>
scanner it seems that the full version is necessary.<br>
I found this behaviour of Adaptec very bad because they<br>
make advertisement by talking about the "wonderful" scanning<br>
speed of the device but opening the package you<br>
discover that you have to *buy* the Driver first.<br>
Very strange.<br>
But I would prefer to scan with linux either :-).<br>
<p>
Many thanks!!<br>
Klaus<br>
<br>
<br>
<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="0106.html">Oliver.Rauch@Wolfsburg.DE: "Re: umax-backend"</a>
<li> <b>Previous message:</b> <a href="0104.html">David Mosberger-Tang: "Re: Mustek600IICD / lost lines"</a>
<li> <b>In reply to:</b> <a href="0104.html">David Mosberger-Tang: "Re: Mustek600IICD / lost lines"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>