sane-project-website/old-archive/1998-09/0078.html

168 wiersze
7.2 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 Sep 13 11:18:53 1998 PDT" -->
<!-- sent="Sun, 13 Sep 1998 18:04:15 +0000" -->
<!-- name="Durk Talsma" -->
<!-- email="D.Talsma@direct.a2000.nl" -->
<!-- subject="Having problems with canon backend" -->
<!-- id="" -->
<!-- inreplyto="" -->
<title>sane-devel: Having problems with canon backend</title>
<h1>Having problems with canon backend</h1>
<b>Durk Talsma</b> (<a href="mailto:D.Talsma@direct.a2000.nl"><i>D.Talsma@direct.a2000.nl</i></a>)<br>
<i>Sun, 13 Sep 1998 18:04:15 +0000</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#78">[ date ]</a><a href="index.html#78">[ thread ]</a><a href="subject.html#78">[ subject ]</a><a href="author.html#78">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0079.html">Michael Kayz-Hyman: "Re: Primax Colorado Direct (parallel) support - bad news ?"</a>
<li> <b>Previous message:</b> <a href="0077.html">Roy-Anders Larsen: "UMAX 610P and (in)SANE"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hello everybody,<br>
<p>
Last week I posted a message here because I was having trouble with<br>
getting my Canon Canoscan 300 to work. After some communication with a<br>
few other list members, I came to the conclusion that my setup should<br>
now in principle be okay. But there still appears to be going something<br>
wrong though. <br>
<p>
I have an NCR810 scsi host adapter, with generic scsi support configured<br>
as a module. Currently, I'm running linux 2.0.35. Running<br>
tools/find-scanner reports the following. <br>
<p>
find-scanner: found scanner "CANON IX-03035B 2.01" at device<br>
/dev/scanner<br>
find-scanner: found scanner "CANON IX-03035B 2.01" at device /dev/sgc<br>
<p>
Now, when I try to run xscanimage, using 'xscanimage canon:/dev/sga' (as<br>
root), I get the following error dialog: <br>
Failed to open device 'canon:/dev/scanner'. Invalid argument.<br>
<p>
After this I find the following lines in /var/log/messages:<br>
<p>
Sep 9 18:35:44 galactica kernel: Detected scsi generic sgc at<br>
scsi0,channel 0, id 3, lun 0<br>
Sep 9 18:35:44 galactica kernel: ncr53c810-0-&lt;3,0&gt;: asynchronous.<br>
Sep 9 18:35:54 galactica kernel: ncr53c810-0:3: ERROR (0:4)<br>
(9-0-0)(e0/33) @ script (eb8:1900000c).<br>
Sep 9 18:35:54 galactica kernel: ncr53c810-0: script cmd = 88080000<br>
Sep 9 18:35:54 galactica kernel: ncr53c810-0: regdump: da 00 80 33 47<br>
e0 03 1f 01 09 83 00 80 00 09 02.<br>
Sep 9 18:35:54 galactica kernel: ncr53c810-0: have to clear fifos.<br>
Sep 9 18:35:54 galactica kernel: ncr53c810-0: unexpected disconnect<br>
Sep 9 18:35:54 galactica kernel: ncr53c810-0: restart (scsi reset).<br>
Sep 9 18:35:56 galactica kernel: ncr53c810-0-&lt;3,0&gt;: asynchronous.<br>
Sep 9 18:35:56 galactica kernel: ncr53c810-0-&lt;0,0&gt;: SLOW SCSI 5.0 MB/s<br>
(200 ns, offset 8)<br>
<p>
After setting the SANE_DEBUG_DLL, SANE_DEBUG_CANON, and<br>
SANEI_DEBUG_SANEI_SCSI env. variables to 128, I get the following<br>
messages:<br>
<p>
sanei_init_debug]: Setting debug level of dll to 128.<br>
[dll] adding backend artec<br>
[dll] adding backend canon<br>
[dll] adding backend coolscan<br>
[dll] adding backend dc25<br>
[dll] adding backend dmc<br>
[dll] adding backend epson<br>
[dll] adding backend hp<br>
[dll] adding backend microtek<br>
[dll] adding backend microtek2<br>
[dll] adding backend mustek<br>
[dll] adding backend pint<br>
[dll] adding backend pnm<br>
[dll] adding backend qcam<br>
[dll] adding backend s9036<br>
[dll] adding backend snapscan<br>
[dll] adding backend tamarack<br>
[dll] adding backend umax<br>
[dll] loading backend canon<br>
[dll] dlopen()ing `/usr/local/lib/sane/libsane-canon.so.0'<br>
[dll] init: initializing backend `canon'<br>
[sanei_init_debug]: Setting debug level of canon to 128.<br>
[canon] &gt;&gt; sane_init<br>
[canon] sane_init: sane 0.74<br>
[canon] &gt;&gt; attach<br>
[canon] attach: opening /dev/scanner<br>
[sanei_init_debug]: Setting debug level of sanei_scsi to 128.<br>
[canon] attach: sending (standard) INQUIRY<br>
[canon] &gt;&gt; inquiry<br>
[sanei_scsi] scsi_req_enter: entered 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x806f960<br>
[sanei_scsi] sanei_scsi.issue: 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: read 72 bytes<br>
[canon] &lt;&lt; inquiry<br>
[canon] attach: sending TEST_UNIT_READY<br>
[canon] &gt;&gt; test_unit_ready<br>
[sanei_scsi] scsi_req_enter: entered 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x806f960<br>
[sanei_scsi] sanei_scsi.issue: 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[canon] &lt;&lt; test_unit_ready<br>
[canon] attach: sending MEDIUM POSITION<br>
[canon] &gt;&gt; medium_psosition<br>
[sanei_scsi] scsi_req_enter: entered 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x806f960<br>
[sanei_scsi] sanei_scsi.issue: 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: read 36 bytes<br>
[canon] &lt;&lt; medium_psosition<br>
[canon] attach: sending (extended) INQUIRY<br>
[canon] &gt;&gt; inquiry<br>
[sanei_scsi] scsi_req_enter: entered 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x806f960<br>
[sanei_scsi] sanei_scsi.issue: 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: read 110 bytes<br>
[canon] &lt;&lt; inquiry<br>
[canon] attach: sending MODE SENSE<br>
[canon] &gt;&gt; mode_sense<br>
[sanei_scsi] scsi_req_enter: entered 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x806f960<br>
[sanei_scsi] sanei_scsi.issue: 0x806f960<br>
[sanei_scsi] sanei_scsi_req_wait: read 48 bytes<br>
[sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success<br>
[canon] &lt;&lt; mode_sense<br>
[canon] attach: MODE_SENSE failed<br>
[canon] &lt;&lt; sane_init<br>
[canon] &gt;&gt; sane_open<br>
[dll] exiting<br>
[dll] calling backend `canon's exit function<br>
[canon] &gt;&gt; sane_exit<br>
[canon] &lt;&lt; sane_exit<br>
<p>
Well, I hope this is useful information. If someone has a clue of what<br>
might be wrong please let me know. I'm very eager to use sane.<br>
<p>
Regards,<br>
Durk Talsma<br>
<pre>
--
-----------------------------------------------------------------------
You can contact me at:
<a href="mailto:pn_talsma@macmail.psy.uva.nl">pn_talsma@macmail.psy.uva.nl</a> (work)
<a href="mailto:talsma@uvapsy.psy.uva.nl">talsma@uvapsy.psy.uva.nl</a> (more work)
<a href="mailto:d.talsma@direct.a2000.nl">d.talsma@direct.a2000.nl</a> (home at last)
<p>
Or visit my website at:
<a href="http://people.a2000.nl/dtals">http://people.a2000.nl/dtals</a>
----------------------------------------------------------------------
"Dave, this conversation can serve no further purpose anymore, goodbye"
<p>
- HAL 9000 -
<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="0079.html">Michael Kayz-Hyman: "Re: Primax Colorado Direct (parallel) support - bad news ?"</a>
<li> <b>Previous message:</b> <a href="0077.html">Roy-Anders Larsen: "UMAX 610P and (in)SANE"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>