kopia lustrzana https://gitlab.com/sane-project/website
160 wiersze
8.1 KiB
HTML
160 wiersze
8.1 KiB
HTML
|
<!-- received="Wed Sep 22 03:15:56 1999 PDT" -->
|
|||
|
|
<!-- sent="Wed, 22 Sep 1999 12:37:13 +0200" -->
|
|||
|
|
<!-- name="Bernd Schroeder" -->
|
|||
|
|
<!-- email="bernd@aquila.muc.de" -->
|
|||
|
|
<!-- subject="Re: ppSCSI and Microtek Phantom 330 CX" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="wugso48jm8d.fsf@pcmic216.lirmm.fr" -->
|
|||
|
|
<title>sane-devel: Re: ppSCSI and Microtek Phantom 330 CX</title>
|
|||
|
|
<h1>Re: ppSCSI and Microtek Phantom 330 CX</h1>
|
|||
|
|
<b>Bernd Schroeder</b> (<a href="mailto:bernd@aquila.muc.de"><i>bernd@aquila.muc.de</i></a>)<br>
|
|||
|
|
<i>Wed, 22 Sep 1999 12:37:13 +0200</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#136">[ date ]</a><a href="index.html#136">[ thread ]</a><a href="subject.html#136">[ subject ]</a><a href="author.html#136">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0137.html">Camille DIOU: "Re: ppSCSI and Microtek Phantom 330 CX"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0135.html">Fred Willingham: "Re: gimp and xsane"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0137.html">Camille DIOU: "Re: ppSCSI and Microtek Phantom 330 CX"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0137.html">Camille DIOU: "Re: ppSCSI and Microtek Phantom 330 CX"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Hi,<br>
|
|||
|
|
<p>
|
|||
|
|
On Tue, Sep 21, 1999 at 05:52:18PM +0200, Camille DIOU wrote:<br>
|
|||
|
|
<i>> Hi all,</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> I've been looking the mailing-list archive to get my Phantom 330 CX</i><br>
|
|||
|
|
<i>> working until Linux. I found what I was looking for, but there are</i><br>
|
|||
|
|
<i>> still some problems. </i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> First, I attached the ppscsi 0.91 patch to my 2.2.10 kernel. I also</i><br>
|
|||
|
|
<i>> applied the patch (thanks to Michele Bini) I found in the</i><br>
|
|||
|
|
<i>> mailing-list Juny archive to the microtek2 backend source.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> That seems to work. When I load the onscsi module, I get the following </i><br>
|
|||
|
|
<i>> message :</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> [root@localhost scsi]# insmod onscsi</i><br>
|
|||
|
|
<i>> onscsi.1: onscsi 0.90 (0.91), OnSpec 90c26 at 0x378 mode 0 (Nybble) dly 1 nice</i><br>
|
|||
|
|
<i>> 0 sg 16</i><br>
|
|||
|
|
<i>> scsi0 : onscsi</i><br>
|
|||
|
|
<i>> scsi : 1 host.</i><br>
|
|||
|
|
<i>> Vendor: Model: scanner 330CS Rev: 1.26</i><br>
|
|||
|
|
<i>> Type: Scanner ANSI SCSI revision: 02</i><br>
|
|||
|
|
<i>> Detected scsi generic sga at scsi0, channel 0, id 2, lun 0</i><br>
|
|||
|
|
<i>> [root@localhost scsi]#</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Also, 'find-scanner' responds:</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> [root@localhost /root]# find-scanner </i><br>
|
|||
|
|
<i>> find-scanner: found scanner " scanner 330CS 1.26" at device /dev/sg0</i><br>
|
|||
|
|
<i>> find-scanner: found scanner " scanner 330CS 1.26" at device /dev/sga</i><br>
|
|||
|
|
<i>> [root@localhost /root]# </i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> All right, but :</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> - scanimage doesn't work. The message I get is identical to those I</i><br>
|
|||
|
|
<i>> could have read on the Juny archive concerning the Phantom 330/336</i><br>
|
|||
|
|
<i>> CX. The only difference is that the revision number is 1.26. </i><br>
|
|||
|
|
<i>> The scanner doesn't scan anything but goes forward and backward for </i><br>
|
|||
|
|
<i>> 2 or 3 cm, never more (even if the 'no-backtrack-option' is set to</i><br>
|
|||
|
|
<i>> 'on' in microtek2.conf), until the programm die a few seconds</i><br>
|
|||
|
|
<i>> later. All what I get is:</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> [ ... I cut the scanner-ID output ... ]</i><br>
|
|||
|
|
<i>> P6</i><br>
|
|||
|
|
<i>> # SANE data follows</i><br>
|
|||
|
|
<i>> 612 838</i><br>
|
|||
|
|
<i>> 255</i><br>
|
|||
|
|
<i>> onscsi.1: PDMA timeout, bs=11 cb=10 db=1842 bu=1 sg=0 rd=1 lp=31 pe=0 cc=41</i><br>
|
|||
|
|
<i>> onscsi.1: Arbitration failure, bs=11 cb=0 db=1842 bu=0 sg=0 rd=1 lp=0 pe=0 cc=42</i><br>
|
|||
|
|
<i>> onscsi.1: Bus reset</i><br>
|
|||
|
|
<i>> onscsi.1: Arbitration failure, bs=31 cb=0 db=1842 bu=0 sg=0 rd=1 lp=0 pe=0 cc=43</i><br>
|
|||
|
|
<i>> [root@localhost scsi]#</i><br>
|
|||
|
|
<p>
|
|||
|
|
Even if the 'no-backtrack-option' is set it is possible that the scanner<br>
|
|||
|
|
stops and starts, but should not move back. Here it looks as if one<br>
|
|||
|
|
or more buffers are read, but then the device fails to read another buffer.<br>
|
|||
|
|
I don't know what the error messages mean, but it looks like a problem<br>
|
|||
|
|
with the ppSCSI stuff. Maybe you should ask on the linux-parport mailinglist.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> After that, I have to unload the onscsi module, turn off the</i><br>
|
|||
|
|
<i>> scanner and then on, and last reload the module.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> - xscanimage works better, but I have the same problems as Michele Bini: </i><br>
|
|||
|
|
<i>> * I also have an offset around 15-20 mm (at 24bpp)</i><br>
|
|||
|
|
<i>> * the preview is working well but the head doesn't stop and hits</i><br>
|
|||
|
|
<i>> the upper side of the scanner: I must turn off the scanner by hand.</i><br>
|
|||
|
|
<i>> * the acquisition itself does work well too, but when finished, the </i><br>
|
|||
|
|
<i>> head comes back to the bottom side, doesn't stop, and hits it.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Note that with xscanimage, the no-backtrack-option seems to work well.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Thus, some questions now. </i><br>
|
|||
|
|
<i>> How could you explain that xscanimage (almost) works, but scanimage</i><br>
|
|||
|
|
<i>> doesn't ? How to get it working ?</i><br>
|
|||
|
|
<p>
|
|||
|
|
I don't know. During a scan the only commands that are executed are<br>
|
|||
|
|
'read image', and they should be the same for scanimage and xscanimage.<br>
|
|||
|
|
Maybe scanimage and xscanimage use different internal buffer sizes for<br>
|
|||
|
|
the scan data.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> Is there any way to avoid the head hitting the borders of the</i><br>
|
|||
|
|
<i>> scanner? (I didn't find any solution in the archive since Juny).</i><br>
|
|||
|
|
<p>
|
|||
|
|
For some reason the device doesn't find the zero position. I think that<br>
|
|||
|
|
if a preview scan is done it tries to scan an A4 sized image, but because<br>
|
|||
|
|
a number of lines are missing at the beginning it tries to scan beyond<br>
|
|||
|
|
the bottom of the scan area. If this is the case it should at least work<br>
|
|||
|
|
better, if you do a normal scan, but don't specify the whole scan area.<br>
|
|||
|
|
<p>
|
|||
|
|
There is one SCSI command that sets all the parameters for a scan - including<br>
|
|||
|
|
the scan area - and these are set correctly, so it should start at<br>
|
|||
|
|
position 0.<br>
|
|||
|
|
<p>
|
|||
|
|
One thing you can try is: Set the still experimental and undocumented<br>
|
|||
|
|
'option backend-calibration on' in the microtek2.conf file, if it exists<br>
|
|||
|
|
in your version. Otherwise download a newer version from<br>
|
|||
|
|
<a href="ftp://ftp.muc.de/people/bernds/mtek2">ftp://ftp.muc.de/people/bernds/mtek2</a>.<br>
|
|||
|
|
<p>
|
|||
|
|
If this option is set this will enable an additional option in the<br>
|
|||
|
|
frontend (Calibration by backend). If this option is checked the backend<br>
|
|||
|
|
instead of the device will do a colour calibration at the beginning<br>
|
|||
|
|
of a scan. This will involve some additional commands to position the<br>
|
|||
|
|
scan head. I don't know if it helps, but I think it's worth a try.<br>
|
|||
|
|
<p>
|
|||
|
|
When the scan head returns to its home position after a scan the backend<br>
|
|||
|
|
it not involved at all. After the last buffer has been read the head moves<br>
|
|||
|
|
back automatically, and there is no command to position it.<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="0137.html">Camille DIOU: "Re: ppSCSI and Microtek Phantom 330 CX"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0135.html">Fred Willingham: "Re: gimp and xsane"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0137.html">Camille DIOU: "Re: ppSCSI and Microtek Phantom 330 CX"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0137.html">Camille DIOU: "Re: ppSCSI and Microtek Phantom 330 CX"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|