sane-project-website/old-archive/1999-06/0211.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 Jun 27 11:25:58 1999 PDT" -->
<!-- sent="Sun, 27 Jun 1999 14:29:17 -0400" -->
<!-- name="Douglas Gilbert" -->
<!-- email="dgilbert@interlog.com" -->
<!-- subject="Re: Umax 1200S on LinuxPPC R5" -->
<!-- id="" -->
<!-- inreplyto="Umax 1200S on LinuxPPC R5" -->
<title>sane-devel: Re: Umax 1200S on LinuxPPC R5</title>
<h1>Re: Umax 1200S on LinuxPPC R5</h1>
<b>Douglas Gilbert</b> (<a href="mailto:dgilbert@interlog.com"><i>dgilbert@interlog.com</i></a>)<br>
<i>Sun, 27 Jun 1999 14:29:17 -0400</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#211">[ date ]</a><a href="index.html#211">[ thread ]</a><a href="subject.html#211">[ subject ]</a><a href="author.html#211">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0212.html">joel@cs.rochester.edu: "X6EL modes under OS/2?"</a>
<li> <b>Previous message:</b> <a href="0210.html">Dr. Ing. Dieter Jurzitza: "SE 12000SP (Mustek)"</a>
<li> <b>Maybe in reply to:</b> <a href="0140.html">Simon Piette: "Umax 1200S on LinuxPPC R5"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0215.html">Simon Piette: "Re: Umax 1200S on LinuxPPC R5"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Simon Piette wrote:<br>
<i>&gt; </i><br>
<i>&gt; Douglas Gilbert wrote:</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; &gt;</i><br>
<i>&gt; &gt; &gt; Ok, so it looks like a problem with the scsi-card or driver or the sg driver.</i><br>
<i>&gt; &gt; &gt; I don`t know if the umax backend is ever tested on a big endian machine,</i><br>
<i>&gt; &gt; &gt; but if the inquiry command returns with an error I don't think it is a problem</i><br>
<i>&gt; &gt; &gt; with the umax backend.</i><br>
<i>&gt; &gt; &gt;</i><br>
<i>&gt; &gt;</i><br>
<i>&gt; &gt; As I posted recently, if a problem with the sg driver is</i><br>
<i>&gt; &gt; suspected then the user should download the utility and</i><br>
<i>&gt; &gt; test program tarball from:</i><br>
<i>&gt; &gt; <a href="http://www.torque.net/sg">http://www.torque.net/sg</a></i><br>
<i>&gt; &gt;</i><br>
<i>&gt; &gt; and run "sg_scan -i". This goes through ever SCSI</i><br>
<i>&gt; &gt; device mapped to /dev/sg* and sends an INQUIRY command</i><br>
<i>&gt; &gt; to it and outputs the result. That program should work</i><br>
<i>&gt; &gt; on any linux kernel from from 2.0 to 2.3.8 .</i><br>
<i>&gt; </i><br>
<i>&gt; OK. Here is the results from sg_scan -i:</i><br>
<i>&gt; </i><br>
<i>&gt; /dev/sga: scsi0, channel=0, id=0, lun=0, type=0</i><br>
<i>&gt; QUANTUM FIREBALL ST2.1S 0F0C, byte_7=0x1a</i><br>
<i>&gt; /dev/sgb: scsi0, channel=0, id=2, lun=0, type=0</i><br>
<i>&gt; QUANTUM FIREBALL ST2100S 0F0D, byte_7=0x1a</i><br>
<i>&gt; /dev/sgc: scsi0, channel=0, id=3, lun=0, type=5</i><br>
<i>&gt; PIONEER CD-ROM DR-U10X 1.07, byte_7=0x10</i><br>
<i>&gt; /dev/sgd: scsi0, channel=0, id=4, lun=0, type=0</i><br>
<i>&gt; QUANTUM FIREBALL ST2100S 0F0J, byte_7=0x1a</i><br>
<i>&gt; /dev/sge: scsi1, channel=0, id=2, lun=0, type=0</i><br>
<i>&gt; SyQuest EZ135S 1_13, byte_7=0x18</i><br>
<i>&gt; /dev/sgf: scsi1, channel=0, id=5, lun=0, type=6</i><br>
<i>&gt; UMAX Astra 1200S V1.3, byte_7=0x0</i><br>
<i>&gt; </i><br>
<i>&gt; The output is very similar to ./tools/findscanner:</i><br>
<i>&gt; </i><br>
<i>&gt; # ./find-scanner</i><br>
<i>&gt; find-scanner: found scanner "UMAX Astra 1200S V1.3" at device</i><br>
<i>&gt; /dev/scanner</i><br>
<i>&gt; find-scanner: found scanner "UMAX Astra 1200S V1.3" at device /dev/sg5</i><br>
<i>&gt; find-scanner: found scanner "UMAX Astra 1200S V1.3" at device /dev/sgf</i><br>
<i>&gt; </i><br>
<p>
So the sg device on your box has no trouble handling SCSI<br>
INQUIRY commands. You may like to try "sginfo -a /dev/sgf"<br>
to see if mode page info comes out ok. My 1220S only<br>
defines a few mode pages. "sginfo" is in the same tarball<br>
referred to above (it is a "sg" equivalent of Eric Youngdale's<br>
scsiinfo program). You may also find "sginfo -l" interesting.<br>
<p>
BTW Could someone tell me if scanners generally support<br>
the READ BUFFER command. If so the test program "sg_rbuf"<br>
from the same tarball could be very useful.<br>
<p>
<p>
Doug Gilbert<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="0212.html">joel@cs.rochester.edu: "X6EL modes under OS/2?"</a>
<li> <b>Previous message:</b> <a href="0210.html">Dr. Ing. Dieter Jurzitza: "SE 12000SP (Mustek)"</a>
<li> <b>Maybe in reply to:</b> <a href="0140.html">Simon Piette: "Umax 1200S on LinuxPPC R5"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0215.html">Simon Piette: "Re: Umax 1200S on LinuxPPC R5"</a>
<!-- reply="end" -->
</ul>